2024-04-23 16:22:35.263 UTC postmaster[7550] LOG:  starting PostgreSQL 17devel on aarch64-darwin, compiled by clang-14.0.3, 64-bit
2024-04-23 16:22:35.264 UTC postmaster[7550] LOG:  listening on Unix socket "/var/folders/xc/tpssff9959345bnqq4c6tlww0000gn/T/pg_regress-FLUoLj/.s.PGSQL.40051"
2024-04-23 16:22:35.319 UTC startup[7557] LOG:  database system was shut down at 2024-04-23 16:22:34 UTC
2024-04-23 16:22:35.323 UTC client backend[7558] [unknown] FATAL:  the database system is starting up
2024-04-23 16:22:35.331 UTC postmaster[7550] LOG:  database system is ready to accept connections
2024-04-23 16:22:40.246 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "34.5" at character 34
2024-04-23 16:22:40.246 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('34.5');
2024-04-23 16:22:40.247 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "      " at character 34
2024-04-23 16:22:40.247 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('      ');
2024-04-23 16:22:40.250 UTC client backend[7900] pg_regress/int2 ERROR:  value "100000" is out of range for type smallint at character 34
2024-04-23 16:22:40.250 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('100000');
2024-04-23 16:22:40.252 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "xxx" at character 34
2024-04-23 16:22:40.252 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('xxx');
2024-04-23 16:22:40.254 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "asdf" at character 34
2024-04-23 16:22:40.254 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('asdf');
2024-04-23 16:22:40.255 UTC client backend[7896] pg_regress/int8 ERROR:  value "3908203590239580293850293850329485" is out of range for type bigint at character 34
2024-04-23 16:22:40.255 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485');
2024-04-23 16:22:40.257 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "    " at character 34
2024-04-23 16:22:40.257 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('    ');
2024-04-23 16:22:40.259 UTC client backend[7896] pg_regress/int8 ERROR:  value "-1204982019841029840928340329840934" is out of range for type bigint at character 34
2024-04-23 16:22:40.259 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934');
2024-04-23 16:22:40.260 UTC client backend[7901] pg_regress/text ERROR:  function length(integer) does not exist at character 8
2024-04-23 16:22:40.260 UTC client backend[7901] pg_regress/text HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:40.260 UTC client backend[7901] pg_regress/text STATEMENT:  select length(42);
2024-04-23 16:22:40.261 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "- 1234" at character 34
2024-04-23 16:22:40.261 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('- 1234');
2024-04-23 16:22:40.262 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "- 123" at character 34
2024-04-23 16:22:40.262 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('- 123');
2024-04-23 16:22:40.264 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "4 444" at character 34
2024-04-23 16:22:40.264 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('4 444');
2024-04-23 16:22:40.265 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "  345     5" at character 34
2024-04-23 16:22:40.265 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('  345     5');
2024-04-23 16:22:40.266 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "123 dt" at character 34
2024-04-23 16:22:40.266 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('123 dt');
2024-04-23 16:22:40.266 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "" at character 34
2024-04-23 16:22:40.266 UTC client backend[7896] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('');
2024-04-23 16:22:40.267 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "" at character 34
2024-04-23 16:22:40.267 UTC client backend[7900] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('');
2024-04-23 16:22:40.267 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "test" at character 13
2024-04-23 16:22:40.267 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'test' AS error;
2024-04-23 16:22:40.267 UTC client backend[7901] pg_regress/text ERROR:  operator does not exist: integer || numeric at character 10
2024-04-23 16:22:40.267 UTC client backend[7901] pg_regress/text HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:40.267 UTC client backend[7901] pg_regress/text STATEMENT:  select 3 || 4.0;
2024-04-23 16:22:40.268 UTC client backend[7897] pg_regress/float4 ERROR:  "10e70" is out of range for type real at character 36
2024-04-23 16:22:40.268 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70');
2024-04-23 16:22:40.269 UTC client backend[7897] pg_regress/float4 ERROR:  "-10e70" is out of range for type real at character 36
2024-04-23 16:22:40.269 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70');
2024-04-23 16:22:40.270 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "foo" at character 13
2024-04-23 16:22:40.270 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'foo' AS error;
2024-04-23 16:22:40.270 UTC client backend[7897] pg_regress/float4 ERROR:  "10e-70" is out of range for type real at character 36
2024-04-23 16:22:40.270 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70');
2024-04-23 16:22:40.273 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "" at character 33
2024-04-23 16:22:40.273 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('');
2024-04-23 16:22:40.274 UTC client backend[7897] pg_regress/float4 ERROR:  "-10e-70" is out of range for type real at character 36
2024-04-23 16:22:40.274 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70');
2024-04-23 16:22:40.274 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "    " at character 33
2024-04-23 16:22:40.274 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('    ');
2024-04-23 16:22:40.274 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "asdfasd" at character 33
2024-04-23 16:22:40.274 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('asdfasd');
2024-04-23 16:22:40.275 UTC client backend[7897] pg_regress/float4 ERROR:  value out of range: overflow
2024-04-23 16:22:40.275 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8);
2024-04-23 16:22:40.275 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "yeah" at character 13
2024-04-23 16:22:40.275 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'yeah' AS error;
2024-04-23 16:22:40.275 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "99asdfasd" at character 33
2024-04-23 16:22:40.275 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('99asdfasd');
2024-04-23 16:22:40.275 UTC client backend[7897] pg_regress/float4 ERROR:  value out of range: overflow
2024-04-23 16:22:40.275 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8);
2024-04-23 16:22:40.275 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "5    d" at character 33
2024-04-23 16:22:40.275 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('5    d');
2024-04-23 16:22:40.276 UTC client backend[7897] pg_regress/float4 ERROR:  value out of range: underflow
2024-04-23 16:22:40.276 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8);
2024-04-23 16:22:40.276 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "    5d" at character 33
2024-04-23 16:22:40.276 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('    5d');
2024-04-23 16:22:40.277 UTC client backend[7897] pg_regress/float4 ERROR:  value out of range: underflow
2024-04-23 16:22:40.277 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8);
2024-04-23 16:22:40.277 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "nay" at character 13
2024-04-23 16:22:40.277 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'nay' AS error;
2024-04-23 16:22:40.277 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: "5    5" at character 33
2024-04-23 16:22:40.277 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('5    5');
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 ERROR:  "10e400" is out of range for type real at character 36
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400');
2024-04-23 16:22:40.278 UTC client backend[7894] pg_regress/oid ERROR:  invalid input syntax for type oid: " - 500" at character 33
2024-04-23 16:22:40.278 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES (' - 500');
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 ERROR:  "-10e400" is out of range for type real at character 36
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400');
2024-04-23 16:22:40.278 UTC client backend[7894] pg_regress/oid ERROR:  value "32958209582039852935" is out of range for type oid at character 33
2024-04-23 16:22:40.278 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935');
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 ERROR:  "10e-400" is out of range for type real at character 36
2024-04-23 16:22:40.278 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400');
2024-04-23 16:22:40.279 UTC client backend[7894] pg_regress/oid ERROR:  value "-23582358720398502385" is out of range for type oid at character 33
2024-04-23 16:22:40.279 UTC client backend[7894] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385');
2024-04-23 16:22:40.279 UTC client backend[7897] pg_regress/float4 ERROR:  "-10e-400" is out of range for type real at character 36
2024-04-23 16:22:40.279 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400');
2024-04-23 16:22:40.279 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "o" at character 13
2024-04-23 16:22:40.279 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'o' AS error;
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "" at character 36
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('');
2024-04-23 16:22:40.280 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "on_" at character 13
2024-04-23 16:22:40.280 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'on_' AS error;
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "       " at character 36
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('       ');
2024-04-23 16:22:40.280 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "off_" at character 13
2024-04-23 16:22:40.280 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool 'off_' AS error;
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "xyz" at character 36
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz');
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "5.0.0" at character 36
2024-04-23 16:22:40.280 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0');
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "5 . 0" at character 36
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0');
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "11" at character 13
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool '11' AS error;
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "5.   0" at character 36
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5.   0');
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "     - 3.0" at character 36
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('     - 3.0');
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "000" at character 13
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool '000' AS error;
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "123            5" at character 36
2024-04-23 16:22:40.281 UTC client backend[7897] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('123            5');
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "" at character 13
2024-04-23 16:22:40.281 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT bool '' AS error;
2024-04-23 16:22:40.300 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "34.5" at character 34
2024-04-23 16:22:40.300 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('34.5');
2024-04-23 16:22:40.300 UTC client backend[7904] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "31:12:" at character 8
2024-04-23 16:22:40.300 UTC client backend[7904] pg_regress/txid STATEMENT:  select '31:12:'::txid_snapshot;
2024-04-23 16:22:40.300 UTC client backend[7910] pg_regress/int4 ERROR:  value "1000000000000" is out of range for type integer at character 34
2024-04-23 16:22:40.300 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('1000000000000');
2024-04-23 16:22:40.300 UTC client backend[7904] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "0:1:" at character 8
2024-04-23 16:22:40.300 UTC client backend[7904] pg_regress/txid STATEMENT:  select '0:1:'::txid_snapshot;
2024-04-23 16:22:40.301 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "asdf" at character 34
2024-04-23 16:22:40.301 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('asdf');
2024-04-23 16:22:40.301 UTC client backend[7904] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "12:13:0" at character 8
2024-04-23 16:22:40.301 UTC client backend[7904] pg_regress/txid STATEMENT:  select '12:13:0'::txid_snapshot;
2024-04-23 16:22:40.302 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "     " at character 34
2024-04-23 16:22:40.302 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('     ');
2024-04-23 16:22:40.302 UTC client backend[7903] pg_regress/varchar ERROR:  value too long for type character varying(1)
2024-04-23 16:22:40.302 UTC client backend[7903] pg_regress/varchar STATEMENT:  INSERT INTO VARCHAR_TBL (f1) VALUES ('cd');
2024-04-23 16:22:40.302 UTC client backend[7902] pg_regress/char ERROR:  value too long for type character(1)
2024-04-23 16:22:40.302 UTC client backend[7902] pg_regress/char STATEMENT:  INSERT INTO CHAR_TBL (f1) VALUES ('cd');
2024-04-23 16:22:40.303 UTC client backend[7904] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8
2024-04-23 16:22:40.303 UTC client backend[7904] pg_regress/txid STATEMENT:  select '12:16:14,13'::txid_snapshot;
2024-04-23 16:22:40.303 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "   asdf   " at character 34
2024-04-23 16:22:40.303 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('   asdf   ');
2024-04-23 16:22:40.303 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "" at character 8
2024-04-23 16:22:40.303 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Missing left parenthesis or bracket.
2024-04-23 16:22:40.303 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select ''::textrange;
2024-04-23 16:22:40.305 UTC client backend[7915] pg_regress/bit ERROR:  bit string length 2 does not match type bit(11)
2024-04-23 16:22:40.305 UTC client backend[7915] pg_regress/bit STATEMENT:  INSERT INTO BIT_TABLE VALUES (B'10');
2024-04-23 16:22:40.305 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "- 1234" at character 34
2024-04-23 16:22:40.305 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('- 1234');
2024-04-23 16:22:40.305 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "-[a,z)" at character 8
2024-04-23 16:22:40.305 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Missing left parenthesis or bracket.
2024-04-23 16:22:40.305 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '-[a,z)'::textrange;
2024-04-23 16:22:40.306 UTC client backend[7905] pg_regress/enum ERROR:  invalid input value for enum rainbow: "mauve" at character 8
2024-04-23 16:22:40.306 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT 'mauve'::rainbow;
2024-04-23 16:22:40.308 UTC client backend[7909] pg_regress/float8 ERROR:  "10e400" is out of range for type double precision at character 8
2024-04-23 16:22:40.308 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '10e400'::float8;
2024-04-23 16:22:40.308 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "123       5" at character 34
2024-04-23 16:22:40.308 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('123       5');
2024-04-23 16:22:40.309 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38
2024-04-23 16:22:40.309 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F');
2024-04-23 16:22:40.310 UTC client backend[7909] pg_regress/float8 ERROR:  "-10e400" is out of range for type double precision at character 8
2024-04-23 16:22:40.310 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '-10e400'::float8;
2024-04-23 16:22:40.310 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "" at character 34
2024-04-23 16:22:40.310 UTC client backend[7910] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('');
2024-04-23 16:22:40.311 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38
2024-04-23 16:22:40.311 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}');
2024-04-23 16:22:40.311 UTC client backend[7909] pg_regress/float8 ERROR:  "10e-400" is out of range for type double precision at character 8
2024-04-23 16:22:40.311 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '10e-400'::float8;
2024-04-23 16:22:40.312 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38
2024-04-23 16:22:40.312 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111');
2024-04-23 16:22:40.312 UTC client backend[7915] pg_regress/bit ERROR:  bit string length 12 does not match type bit(11)
2024-04-23 16:22:40.312 UTC client backend[7915] pg_regress/bit STATEMENT:  INSERT INTO BIT_TABLE VALUES (B'101011111010');
2024-04-23 16:22:40.312 UTC client backend[7909] pg_regress/float8 ERROR:  "-10e-400" is out of range for type double precision at character 8
2024-04-23 16:22:40.312 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '-10e-400'::float8;
2024-04-23 16:22:40.312 UTC client backend[7900] pg_regress/int2 ERROR:  table "f" has 1 columns available but 2 columns specified
2024-04-23 16:22:40.312 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT * FROM INT2_TBL AS f(a, b);
2024-04-23 16:22:40.312 UTC client backend[7918] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "G/0" at character 32
2024-04-23 16:22:40.312 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('G/0');
2024-04-23 16:22:40.313 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38
2024-04-23 16:22:40.313 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 ');
2024-04-23 16:22:40.313 UTC client backend[7900] pg_regress/int2 ERROR:  table "s" has 1 columns available but 2 columns specified
2024-04-23 16:22:40.313 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT * FROM (TABLE int2_tbl) AS s (a, b);
2024-04-23 16:22:40.313 UTC client backend[7918] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "-1/0" at character 32
2024-04-23 16:22:40.313 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('-1/0');
2024-04-23 16:22:40.314 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38
2024-04-23 16:22:40.314 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111');
2024-04-23 16:22:40.314 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "" at character 36
2024-04-23 16:22:40.314 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('');
2024-04-23 16:22:40.315 UTC client backend[7918] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: " 0/12345678" at character 32
2024-04-23 16:22:40.315 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES (' 0/12345678');
2024-04-23 16:22:40.315 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "N A N" at character 8
2024-04-23 16:22:40.315 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT 'N A N'::float4;
2024-04-23 16:22:40.315 UTC client backend[7912] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38
2024-04-23 16:22:40.315 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111');
2024-04-23 16:22:40.316 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "     " at character 36
2024-04-23 16:22:40.316 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('     ');
2024-04-23 16:22:40.316 UTC client backend[7918] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "ABCD/" at character 32
2024-04-23 16:22:40.316 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('ABCD/');
2024-04-23 16:22:40.317 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: "NaN x" at character 8
2024-04-23 16:22:40.317 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT 'NaN x'::float4;
2024-04-23 16:22:40.317 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "xyz" at character 36
2024-04-23 16:22:40.317 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz');
2024-04-23 16:22:40.317 UTC client backend[7918] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "/ABCD" at character 32
2024-04-23 16:22:40.317 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('/ABCD');
2024-04-23 16:22:40.318 UTC client backend[7897] pg_regress/float4 ERROR:  invalid input syntax for type real: " INFINITY    x" at character 8
2024-04-23 16:22:40.318 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT ' INFINITY    x'::float4;
2024-04-23 16:22:40.318 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5.0.0" at character 36
2024-04-23 16:22:40.318 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0');
2024-04-23 16:22:40.320 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5 . 0" at character 36
2024-04-23 16:22:40.320 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0');
2024-04-23 16:22:40.321 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5.   0" at character 36
2024-04-23 16:22:40.321 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5.   0');
2024-04-23 16:22:40.321 UTC client backend[7915] pg_regress/bit ERROR:  bit string too long for type bit varying(11)
2024-04-23 16:22:40.321 UTC client backend[7915] pg_regress/bit STATEMENT:  INSERT INTO VARBIT_TABLE VALUES (B'101011111010');
2024-04-23 16:22:40.322 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "    - 3" at character 36
2024-04-23 16:22:40.322 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('    - 3');
2024-04-23 16:22:40.322 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "  tru e "
2024-04-23 16:22:40.322 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT '  tru e '::text::boolean AS invalid;
2024-04-23 16:22:40.322 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "123           5" at character 36
2024-04-23 16:22:40.322 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('123           5');
2024-04-23 16:22:40.323 UTC client backend[7915] pg_regress/bit ERROR:  " " is not a valid binary digit at character 8
2024-04-23 16:22:40.323 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT b' 0';
2024-04-23 16:22:40.323 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: ""
2024-04-23 16:22:40.323 UTC client backend[7899] pg_regress/boolean STATEMENT:  SELECT ''::text::boolean AS invalid;
2024-04-23 16:22:40.323 UTC client backend[7915] pg_regress/bit ERROR:  " " is not a valid binary digit at character 8
2024-04-23 16:22:40.323 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT b'0 ';
2024-04-23 16:22:40.324 UTC client backend[7915] pg_regress/bit ERROR:  " " is not a valid hexadecimal digit at character 8
2024-04-23 16:22:40.324 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT x' 0';
2024-04-23 16:22:40.324 UTC client backend[7915] pg_regress/bit ERROR:  " " is not a valid hexadecimal digit at character 8
2024-04-23 16:22:40.324 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT x'0 ';
2024-04-23 16:22:40.324 UTC client backend[7904] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22
2024-04-23 16:22:40.324 UTC client backend[7904] pg_regress/txid STATEMENT:  SELECT txid_snapshot '1:9223372036854775808:3';
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "N A N" at character 8
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT 'N A N'::float8;
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "NaN x" at character 8
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT 'NaN x'::float8;
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 ERROR:  invalid input syntax for type double precision: " INFINITY    x" at character 8
2024-04-23 16:22:40.327 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT ' INFINITY    x'::float8;
2024-04-23 16:22:40.327 UTC client backend[7915] pg_regress/bit ERROR:  negative substring length not allowed
2024-04-23 16:22:40.327 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error";
2024-04-23 16:22:40.328 UTC client backend[7915] pg_regress/bit ERROR:  negative substring length not allowed
2024-04-23 16:22:40.328 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error";
2024-04-23 16:22:40.328 UTC client backend[7897] pg_regress/float4 ERROR:  division by zero
2024-04-23 16:22:40.328 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT f.f1 / '0.0' from FLOAT4_TBL f;
2024-04-23 16:22:40.331 UTC client backend[7911] pg_regress/money ERROR:  value "123456789012345678" is out of range for type money at character 8
2024-04-23 16:22:40.331 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '123456789012345678'::money;
2024-04-23 16:22:40.331 UTC client backend[7911] pg_regress/money ERROR:  value "9223372036854775807" is out of range for type money at character 8
2024-04-23 16:22:40.331 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '9223372036854775807'::money;
2024-04-23 16:22:40.332 UTC client backend[7911] pg_regress/money ERROR:  value "-123456789012345678" is out of range for type money at character 8
2024-04-23 16:22:40.332 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '-123456789012345678'::money;
2024-04-23 16:22:40.332 UTC client backend[7911] pg_regress/money ERROR:  value "-9223372036854775808" is out of range for type money at character 8
2024-04-23 16:22:40.332 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '-9223372036854775808'::money;
2024-04-23 16:22:40.333 UTC client backend[7911] pg_regress/money ERROR:  value "-92233720368547758.09" is out of range for type money at character 8
2024-04-23 16:22:40.333 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '-92233720368547758.09'::money;
2024-04-23 16:22:40.333 UTC client backend[7911] pg_regress/money ERROR:  value "92233720368547758.08" is out of range for type money at character 8
2024-04-23 16:22:40.333 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '92233720368547758.08'::money;
2024-04-23 16:22:40.334 UTC client backend[7911] pg_regress/money ERROR:  value "-92233720368547758.085" is out of range for type money at character 8
2024-04-23 16:22:40.334 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '-92233720368547758.085'::money;
2024-04-23 16:22:40.334 UTC client backend[7911] pg_regress/money ERROR:  value "92233720368547758.075" is out of range for type money at character 8
2024-04-23 16:22:40.334 UTC client backend[7911] pg_regress/money STATEMENT:  SELECT '92233720368547758.075'::money;
2024-04-23 16:22:40.342 UTC client backend[7902] pg_regress/char ERROR:  value too long for type character(4)
2024-04-23 16:22:40.342 UTC client backend[7902] pg_regress/char STATEMENT:  INSERT INTO CHAR_TBL (f1) VALUES ('abcde');
2024-04-23 16:22:40.343 UTC client backend[7903] pg_regress/varchar ERROR:  value too long for type character varying(4)
2024-04-23 16:22:40.343 UTC client backend[7903] pg_regress/varchar STATEMENT:  INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde');
2024-04-23 16:22:40.344 UTC client backend[7905] pg_regress/enum ERROR:  invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto"
2024-04-23 16:22:40.344 UTC client backend[7905] pg_regress/enum DETAIL:  Labels must be 63 bytes or less.
2024-04-23 16:22:40.344 UTC client backend[7905] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE
	  'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto';
2024-04-23 16:22:40.344 UTC client backend[7900] pg_regress/int2 ERROR:  smallint out of range
2024-04-23 16:22:40.344 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i;
2024-04-23 16:22:40.344 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.344 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.344 UTC client backend[7897] pg_regress/float4 ERROR:  smallint out of range
2024-04-23 16:22:40.344 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '32767.6'::float4::int2;
2024-04-23 16:22:40.344 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.344 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL;
2024-04-23 16:22:40.344 UTC client backend[7909] pg_regress/float8 ERROR:  zero raised to a negative power is undefined
2024-04-23 16:22:40.344 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT power(float8 '0', float8 '-inf');
2024-04-23 16:22:40.349 UTC client backend[7905] pg_regress/enum ERROR:  "zeus" is not an existing enum label
2024-04-23 16:22:40.349 UTC client backend[7905] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus';
2024-04-23 16:22:40.350 UTC client backend[7905] pg_regress/enum ERROR:  enum label "mercury" already exists
2024-04-23 16:22:40.350 UTC client backend[7905] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE 'mercury';
2024-04-23 16:22:40.350 UTC client backend[7897] pg_regress/float4 ERROR:  smallint out of range
2024-04-23 16:22:40.350 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '-32768.6'::float4::int2;
2024-04-23 16:22:40.350 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.350 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.351 UTC client backend[7900] pg_regress/int2 ERROR:  smallint out of range
2024-04-23 16:22:40.351 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i;
2024-04-23 16:22:40.351 UTC client backend[7897] pg_regress/float4 ERROR:  integer out of range
2024-04-23 16:22:40.351 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '2147483647'::float4::int4;
2024-04-23 16:22:40.352 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.352 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.352 UTC client backend[7899] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "XXX" at character 43
2024-04-23 16:22:40.352 UTC client backend[7899] pg_regress/boolean STATEMENT:  INSERT INTO BOOLTBL2 (f1)
	   VALUES (bool 'XXX');
2024-04-23 16:22:40.354 UTC client backend[7897] pg_regress/float4 ERROR:  integer out of range
2024-04-23 16:22:40.354 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '-2147483900'::float4::int4;
2024-04-23 16:22:40.354 UTC client backend[7900] pg_regress/int2 ERROR:  smallint out of range
2024-04-23 16:22:40.354 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i;
2024-04-23 16:22:40.354 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.354 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.355 UTC client backend[7897] pg_regress/float4 ERROR:  bigint out of range
2024-04-23 16:22:40.355 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '9223372036854775807'::float4::int8;
2024-04-23 16:22:40.356 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.356 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.358 UTC client backend[7897] pg_regress/float4 ERROR:  bigint out of range
2024-04-23 16:22:40.358 UTC client backend[7897] pg_regress/float4 STATEMENT:  SELECT '-9223380000000000000'::float4::int8;
2024-04-23 16:22:40.358 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.358 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i;
2024-04-23 16:22:40.360 UTC client backend[7900] pg_regress/int2 ERROR:  smallint out of range
2024-04-23 16:22:40.360 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT (-32768)::int2 * (-1)::int2;
2024-04-23 16:22:40.360 UTC client backend[7900] pg_regress/int2 ERROR:  smallint out of range
2024-04-23 16:22:40.360 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT (-32768)::int2 / (-1)::int2;
2024-04-23 16:22:40.363 UTC client backend[7909] pg_regress/float8 ERROR:  a negative number raised to a non-integer power yields a complex result
2024-04-23 16:22:40.363 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT power(float8 '-inf', float8 '3.5');
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0b" at character 13
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0b';
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0o" at character 13
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0o';
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0x" at character 13
2024-04-23 16:22:40.364 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0x';
2024-04-23 16:22:40.365 UTC client backend[7900] pg_regress/int2 ERROR:  value "0b1000000000000000" is out of range for type smallint at character 13
2024-04-23 16:22:40.365 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0b1000000000000000';
2024-04-23 16:22:40.366 UTC client backend[7900] pg_regress/int2 ERROR:  value "0o100000" is out of range for type smallint at character 13
2024-04-23 16:22:40.366 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0o100000';
2024-04-23 16:22:40.366 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.366 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 * (-1)::int4;
2024-04-23 16:22:40.366 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.366 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 / (-1)::int4;
2024-04-23 16:22:40.366 UTC client backend[7900] pg_regress/int2 ERROR:  value "0x8000" is out of range for type smallint at character 13
2024-04-23 16:22:40.366 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '0x8000';
2024-04-23 16:22:40.367 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.367 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 * (-1)::int2;
2024-04-23 16:22:40.367 UTC client backend[7900] pg_regress/int2 ERROR:  value "-0b1000000000000001" is out of range for type smallint at character 13
2024-04-23 16:22:40.367 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '-0b1000000000000001';
2024-04-23 16:22:40.367 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.367 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 / (-1)::int2;
2024-04-23 16:22:40.367 UTC client backend[7900] pg_regress/int2 ERROR:  value "-0o100001" is out of range for type smallint at character 13
2024-04-23 16:22:40.367 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '-0o100001';
2024-04-23 16:22:40.368 UTC client backend[7900] pg_regress/int2 ERROR:  value "-0x8001" is out of range for type smallint at character 13
2024-04-23 16:22:40.368 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '-0x8001';
2024-04-23 16:22:40.368 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.368 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT gcd((-2147483648)::int4, 0::int4);
2024-04-23 16:22:40.368 UTC client backend[7896] pg_regress/int8 ERROR:  value "-9223372036854775809" is out of range for type bigint at character 8
2024-04-23 16:22:40.368 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775809'::int8;
2024-04-23 16:22:40.369 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.369 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT gcd((-2147483648)::int4, (-2147483648)::int4);
2024-04-23 16:22:40.369 UTC client backend[7896] pg_regress/int8 ERROR:  value "9223372036854775808" is out of range for type bigint at character 8
2024-04-23 16:22:40.369 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775808'::int8;
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "[a,z) - " at character 8
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '[a,z) - '::textrange;
2024-04-23 16:22:40.369 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.369 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT lcm((-2147483648)::int4, 1::int4);
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(",a)" at character 8
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Unexpected end of input.
2024-04-23 16:22:40.369 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(",a)'::textrange;
2024-04-23 16:22:40.370 UTC client backend[7910] pg_regress/int4 ERROR:  integer out of range
2024-04-23 16:22:40.370 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT lcm(2147483647::int4, 2147483646::int4);
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 STATEMENT:  select -('-9223372036854775808'::int8);
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "_100" at character 13
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '_100';
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(,,a)" at character 8
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Too many commas.
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(,,a)'::textrange;
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 STATEMENT:  select 0::int8 - '-9223372036854775808'::int8;
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(),a)" at character 8
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Missing comma after lower bound.
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(),a)'::textrange;
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "100_" at character 13
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '100_';
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.370 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '9223372036854775800'::int8;
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(a,))" at character 8
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2024-04-23 16:22:40.370 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(a,))'::textrange;
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "10__000" at character 13
2024-04-23 16:22:40.370 UTC client backend[7900] pg_regress/int2 STATEMENT:  SELECT int2 '10__000';
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 + '-9223372036854775800'::int8;
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(],a)" at character 8
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Missing comma after lower bound.
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(],a)'::textrange;
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 - '-9223372036854775800'::int8;
2024-04-23 16:22:40.371 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0b" at character 13
2024-04-23 16:22:40.371 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0b';
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes ERROR:  malformed range literal: "(a,])" at character 8
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '(a,])'::textrange;
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.371 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '9223372036854775800'::int8;
2024-04-23 16:22:40.371 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0o" at character 13
2024-04-23 16:22:40.371 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0o';
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2024-04-23 16:22:40.371 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '[z,a]'::textrange;
2024-04-23 16:22:40.372 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.372 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '9223372036854775800'::int8;
2024-04-23 16:22:40.372 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0x" at character 13
2024-04-23 16:22:40.372 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0x';
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  division by zero
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 / '0'::int8;
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  division by zero
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 % '0'::int8;
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 ERROR:  value "0b10000000000000000000000000000000" is out of range for type integer at character 13
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0b10000000000000000000000000000000';
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select abs('-9223372036854775808'::int8);
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '100'::int4;
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 ERROR:  value "0o20000000000" is out of range for type integer at character 13
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0o20000000000';
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '100'::int4;
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '100'::int4;
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 ERROR:  value "0x80000000" is out of range for type integer at character 13
2024-04-23 16:22:40.373 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '0x80000000';
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.373 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '100'::int4 + '9223372036854775800'::int8;
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-100'::int4 - '9223372036854775800'::int8;
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 ERROR:  value "-0b10000000000000000000000000000001" is out of range for type integer at character 13
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '-0b10000000000000000000000000000001';
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '100'::int4 * '9223372036854775800'::int8;
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '100'::int2;
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '100'::int2;
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 ERROR:  value "-0o20000000001" is out of range for type integer at character 13
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '-0o20000000001';
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '100'::int2;
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 ERROR:  division by zero
2024-04-23 16:22:40.374 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-9223372036854775808'::int8 / '0'::int2;
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 ERROR:  value "-0x80000001" is out of range for type integer at character 13
2024-04-23 16:22:40.374 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '-0x80000001';
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '100'::int2 + '9223372036854775800'::int8;
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '-100'::int2 - '9223372036854775800'::int8;
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '100'::int2 * '9223372036854775800'::int8;
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  division by zero
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  select '100'::int2 / '0'::int8;
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "_100" at character 13
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '_100';
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  integer out of range
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456;
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "100_" at character 13
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '100_';
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 ERROR:  invalid input syntax for type integer: "100__000" at character 13
2024-04-23 16:22:40.375 UTC client backend[7910] pg_regress/int4 STATEMENT:  SELECT int4 '100__000';
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 ERROR:  smallint out of range
2024-04-23 16:22:40.375 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456;
2024-04-23 16:22:40.376 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.376 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT CAST('922337203685477580700.0'::float8 AS int8);
2024-04-23 16:22:40.385 UTC client backend[7896] pg_regress/int8 ERROR:  OID out of range
2024-04-23 16:22:40.385 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS oid) FROM INT8_TBL;
2024-04-23 16:22:40.385 UTC client backend[7918] pg_regress/pg_lsn ERROR:  pg_lsn out of range
2024-04-23 16:22:40.385 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric;
2024-04-23 16:22:40.386 UTC client backend[7901] pg_regress/text ERROR:  VARIADIC argument must be an array at character 32
2024-04-23 16:22:40.386 UTC client backend[7901] pg_regress/text STATEMENT:  select concat_ws(',', variadic 10);
2024-04-23 16:22:40.386 UTC client backend[7918] pg_regress/pg_lsn ERROR:  pg_lsn out of range
2024-04-23 16:22:40.386 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  SELECT '0/1'::pg_lsn - 2::numeric;
2024-04-23 16:22:40.386 UTC client backend[7896] pg_regress/int8 ERROR:  step size cannot equal zero
2024-04-23 16:22:40.386 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0);
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int8;
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int8;
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int4;
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int4;
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int2;
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.387 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int2;
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT gcd((-9223372036854775808)::int8, 0::int8);
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8);
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT lcm((-9223372036854775808)::int8, 1::int8);
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  bigint out of range
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8);
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0b" at character 13
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0b';
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0o" at character 13
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0o';
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0x" at character 13
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0x';
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000';
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 ERROR:  value "0o1000000000000000000000" is out of range for type bigint at character 13
2024-04-23 16:22:40.388 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0o1000000000000000000000';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  value "0x8000000000000000" is out of range for type bigint at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '0x8000000000000000';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  value "-0o1000000000000000000001" is out of range for type bigint at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '-0o1000000000000000000001';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  value "-0x8000000000000001" is out of range for type bigint at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '-0x8000000000000001';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "_100" at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '_100';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "100_" at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '100_';
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "100__000" at character 13
2024-04-23 16:22:40.389 UTC client backend[7896] pg_regress/int8 STATEMENT:  SELECT int8 '100__000';
2024-04-23 16:22:40.394 UTC client backend[7914] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:40.394 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select numrange(2.0, 1.0);
2024-04-23 16:22:40.394 UTC client backend[7918] pg_regress/pg_lsn ERROR:  cannot add NaN to pg_lsn
2024-04-23 16:22:40.394 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric;
2024-04-23 16:22:40.394 UTC client backend[7901] pg_regress/text ERROR:  too few arguments for format()
2024-04-23 16:22:40.394 UTC client backend[7901] pg_regress/text STATEMENT:  select format('Hello %s %s', 'World');
2024-04-23 16:22:40.394 UTC client backend[7918] pg_regress/pg_lsn ERROR:  cannot subtract NaN from pg_lsn
2024-04-23 16:22:40.394 UTC client backend[7918] pg_regress/pg_lsn STATEMENT:  SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric;
2024-04-23 16:22:40.394 UTC client backend[7901] pg_regress/text ERROR:  too few arguments for format()
2024-04-23 16:22:40.394 UTC client backend[7901] pg_regress/text STATEMENT:  select format('Hello %s');
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  unrecognized format() type specifier "x"
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text HINT:  For a single "%" use "%%".
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('Hello %x', 20);
2024-04-23 16:22:40.395 UTC client backend[7909] pg_regress/float8 ERROR:  value out of range: overflow
2024-04-23 16:22:40.395 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT f.f1 * '1e200' from FLOAT8_TBL f;
2024-04-23 16:22:40.395 UTC client backend[7909] pg_regress/float8 ERROR:  value out of range: overflow
2024-04-23 16:22:40.395 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT f.f1 ^ '1e200' from FLOAT8_TBL f;
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  null values cannot be formatted as an SQL identifier
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello');
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  too few arguments for format()
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%1$s %4$s', 1, 2, 3);
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  too few arguments for format()
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  format specifies argument 0, but arguments are numbered from 1
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%0$s', 'Hello');
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  format specifies argument 0, but arguments are numbered from 1
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%*0$s', 'Hello');
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  unterminated format() type specifier
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text HINT:  For a single "%" use "%%".
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%1$', 1);
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text ERROR:  unterminated format() type specifier
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text HINT:  For a single "%" use "%%".
2024-04-23 16:22:40.395 UTC client backend[7901] pg_regress/text STATEMENT:  select format('%1$1', 1);
2024-04-23 16:22:40.396 UTC client backend[7914] pg_regress/rangetypes ERROR:  result of range union would not be contiguous
2024-04-23 16:22:40.396 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select numrange(1.0, 2.0) + numrange(2.5, 3.0);
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "foo.boo[]"
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('foo.boo[]');
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: " "
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident(' ');
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: " .aaa"
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name DETAIL:  No valid identifier before ".".
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident(' .aaa');
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: " aaa . "
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name DETAIL:  No valid identifier after ".".
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident(' aaa . ');
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "aaa.a%b"
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('aaa.a%b');
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "X
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
2024-04-23 16:22:40.397 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: ""c".X XXXXXXXXXX"
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident(E'"c".X XXXX\002XXXXXX');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "1020"
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('1020');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "10.20"
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('10.20');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "."
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name DETAIL:  No valid identifier before ".".
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('.');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: ".1020"
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name DETAIL:  No valid identifier before ".".
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('.1020');
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name ERROR:  string is not a valid identifier: "xxx.1020"
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name DETAIL:  No valid identifier after ".".
2024-04-23 16:22:40.398 UTC client backend[7893] pg_regress/name STATEMENT:  SELECT parse_ident('xxx.1020');
2024-04-23 16:22:40.399 UTC client backend[7912] pg_regress/uuid ERROR:  duplicate key value violates unique constraint "guid1_unique_btree"
2024-04-23 16:22:40.399 UTC client backend[7912] pg_regress/uuid DETAIL:  Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists.
2024-04-23 16:22:40.399 UTC client backend[7912] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111');
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ;
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 ERROR:  value out of range: underflow
2024-04-23 16:22:40.402 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT exp(f.f1) from FLOAT8_TBL f;
2024-04-23 16:22:40.403 UTC client backend[7909] pg_regress/float8 ERROR:  division by zero
2024-04-23 16:22:40.403 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT f.f1 / '0.0' from FLOAT8_TBL f;
2024-04-23 16:22:40.404 UTC client backend[7909] pg_regress/float8 ERROR:  input is out of range
2024-04-23 16:22:40.404 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT acosh(float8 '-infinity');
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit ERROR:  cannot AND bit strings of different sizes
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit STATEMENT:  select B'001' & B'10';
2024-04-23 16:22:40.405 UTC client backend[7909] pg_regress/float8 ERROR:  input is out of range
2024-04-23 16:22:40.405 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT atanh(float8 'infinity');
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit ERROR:  cannot OR bit strings of different sizes
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit STATEMENT:  select B'0111' | B'011';
2024-04-23 16:22:40.405 UTC client backend[7909] pg_regress/float8 ERROR:  input is out of range
2024-04-23 16:22:40.405 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT atanh(float8 '-infinity');
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit ERROR:  cannot XOR bit strings of different sizes
2024-04-23 16:22:40.405 UTC client backend[7915] pg_regress/bit STATEMENT:  select B'0010' # B'011101';
2024-04-23 16:22:40.406 UTC client backend[7905] pg_regress/enum ERROR:  value for domain rgb violates check constraint "rgb_check"
2024-04-23 16:22:40.406 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT 'purple'::rgb;
2024-04-23 16:22:40.406 UTC client backend[7905] pg_regress/enum ERROR:  value for domain rgb violates check constraint "rgb_check"
2024-04-23 16:22:40.406 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT 'purple'::rainbow::rgb;
2024-04-23 16:22:40.406 UTC client backend[7909] pg_regress/float8 ERROR:  "10e400" is out of range for type double precision at character 36
2024-04-23 16:22:40.406 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400');
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 ERROR:  "-10e400" is out of range for type double precision at character 36
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400');
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 ERROR:  "10e-400" is out of range for type double precision at character 36
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400');
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 ERROR:  "-10e-400" is out of range for type double precision at character 36
2024-04-23 16:22:40.407 UTC client backend[7909] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400');
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 ERROR:  smallint out of range
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '32767.6'::float8::int2;
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 ERROR:  smallint out of range
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '-32768.6'::float8::int2;
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 ERROR:  integer out of range
2024-04-23 16:22:40.414 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '2147483647.6'::float8::int4;
2024-04-23 16:22:40.415 UTC client backend[7909] pg_regress/float8 ERROR:  integer out of range
2024-04-23 16:22:40.415 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '-2147483648.6'::float8::int4;
2024-04-23 16:22:40.415 UTC client backend[7909] pg_regress/float8 ERROR:  bigint out of range
2024-04-23 16:22:40.415 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '9223372036854775807'::float8::int8;
2024-04-23 16:22:40.416 UTC client backend[7909] pg_regress/float8 ERROR:  bigint out of range
2024-04-23 16:22:40.416 UTC client backend[7909] pg_regress/float8 STATEMENT:  SELECT '-9223372036854780000'::float8::int8;
2024-04-23 16:22:40.418 UTC client backend[7916] pg_regress/regproc ERROR:  operator does not exist: ||// at character 16
2024-04-23 16:22:40.418 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regoper('||//');
2024-04-23 16:22:40.419 UTC client backend[7916] pg_regress/regproc ERROR:  operator does not exist: ++(int4,int4) at character 20
2024-04-23 16:22:40.419 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regoperator('++(int4,int4)');
2024-04-23 16:22:40.419 UTC client backend[7916] pg_regress/regproc ERROR:  function "know" does not exist at character 16
2024-04-23 16:22:40.419 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regproc('know');
2024-04-23 16:22:40.420 UTC client backend[7916] pg_regress/regproc ERROR:  function "absinthe(numeric)" does not exist at character 21
2024-04-23 16:22:40.420 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regprocedure('absinthe(numeric)');
2024-04-23 16:22:40.421 UTC client backend[7905] pg_regress/enum ERROR:  insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey"
2024-04-23 16:22:40.421 UTC client backend[7905] pg_regress/enum DETAIL:  Key (parent)=(blue) is not present in table "enumtest_parent".
2024-04-23 16:22:40.421 UTC client backend[7905] pg_regress/enum STATEMENT:  INSERT INTO enumtest_child VALUES ('blue');
2024-04-23 16:22:40.421 UTC client backend[7916] pg_regress/regproc ERROR:  relation "pg_classes" does not exist at character 17
2024-04-23 16:22:40.421 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regclass('pg_classes');
2024-04-23 16:22:40.423 UTC client backend[7905] pg_regress/enum ERROR:  update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child"
2024-04-23 16:22:40.423 UTC client backend[7905] pg_regress/enum DETAIL:  Key (id)=(red) is still referenced from table "enumtest_child".
2024-04-23 16:22:40.423 UTC client backend[7905] pg_regress/enum STATEMENT:  DELETE FROM enumtest_parent;
2024-04-23 16:22:40.423 UTC client backend[7916] pg_regress/regproc ERROR:  type "int3" does not exist at character 16
2024-04-23 16:22:40.423 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regtype('int3');
2024-04-23 16:22:40.425 UTC client backend[7916] pg_regress/regproc ERROR:  operator does not exist: ng_catalog.||/ at character 16
2024-04-23 16:22:40.425 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regoper('ng_catalog.||/');
2024-04-23 16:22:40.426 UTC client backend[7905] pg_regress/enum ERROR:  foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented
2024-04-23 16:22:40.426 UTC client backend[7905] pg_regress/enum DETAIL:  Key columns "parent" and "id" are of incompatible types: bogus and rainbow.
2024-04-23 16:22:40.426 UTC client backend[7905] pg_regress/enum STATEMENT:  CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent);
2024-04-23 16:22:40.426 UTC client backend[7916] pg_regress/regproc ERROR:  operator does not exist: ng_catalog.+(int4,int4) at character 20
2024-04-23 16:22:40.426 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regoperator('ng_catalog.+(int4,int4)');
2024-04-23 16:22:40.427 UTC client backend[7916] pg_regress/regproc ERROR:  function "ng_catalog.now" does not exist at character 16
2024-04-23 16:22:40.427 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regproc('ng_catalog.now');
2024-04-23 16:22:40.428 UTC client backend[7916] pg_regress/regproc ERROR:  function "ng_catalog.abs(numeric)" does not exist at character 21
2024-04-23 16:22:40.428 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regprocedure('ng_catalog.abs(numeric)');
2024-04-23 16:22:40.428 UTC client backend[7916] pg_regress/regproc ERROR:  relation "ng_catalog.pg_class" does not exist at character 17
2024-04-23 16:22:40.428 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regclass('ng_catalog.pg_class');
2024-04-23 16:22:40.428 UTC client backend[7915] pg_regress/bit ERROR:  bit index 16 out of valid range (0..15)
2024-04-23 16:22:40.428 UTC client backend[7915] pg_regress/bit STATEMENT:  SELECT set_bit(B'0101011000100100', 16, 1);
2024-04-23 16:22:40.428 UTC client backend[7905] pg_regress/enum ERROR:  "red" is not an existing enum label
2024-04-23 16:22:40.428 UTC client backend[7905] pg_regress/enum STATEMENT:  ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson';
2024-04-23 16:22:40.429 UTC client backend[7905] pg_regress/enum ERROR:  enum label "green" already exists
2024-04-23 16:22:40.429 UTC client backend[7905] pg_regress/enum STATEMENT:  ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green';
2024-04-23 16:22:40.430 UTC client backend[7916] pg_regress/regproc ERROR:  schema "ng_catalog" does not exist at character 16
2024-04-23 16:22:40.430 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regtype('ng_catalog.int4');
2024-04-23 16:22:40.431 UTC client backend[7916] pg_regress/regproc ERROR:  collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21
2024-04-23 16:22:40.431 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regcollation('ng_catalog."POSIX"');
2024-04-23 16:22:40.433 UTC client backend[7916] pg_regress/regproc ERROR:  role "regress_regrole_test" does not exist at character 16
2024-04-23 16:22:40.433 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regrole('regress_regrole_test');
2024-04-23 16:22:40.434 UTC client backend[7905] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus at character 8
2024-04-23 16:22:40.434 UTC client backend[7905] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2024-04-23 16:22:40.434 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT 'new'::bogus;
2024-04-23 16:22:40.435 UTC client backend[7916] pg_regress/regproc ERROR:  role "regress_regrole_test" does not exist at character 16
2024-04-23 16:22:40.435 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regrole('"regress_regrole_test"');
2024-04-23 16:22:40.435 UTC client backend[7916] pg_regress/regproc ERROR:  role "nonexistent" does not exist at character 16
2024-04-23 16:22:40.435 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regrole('Nonexistent');
2024-04-23 16:22:40.436 UTC client backend[7916] pg_regress/regproc ERROR:  role "Nonexistent" does not exist at character 16
2024-04-23 16:22:40.436 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regrole('"Nonexistent"');
2024-04-23 16:22:40.436 UTC client backend[7905] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus
2024-04-23 16:22:40.436 UTC client backend[7905] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2024-04-23 16:22:40.436 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT enum_last(null::bogus);
2024-04-23 16:22:40.436 UTC client backend[7916] pg_regress/regproc ERROR:  invalid name syntax at character 16
2024-04-23 16:22:40.436 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regrole('foo.bar');
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc ERROR:  schema "nonexistent" does not exist at character 21
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regnamespace('Nonexistent');
2024-04-23 16:22:40.437 UTC client backend[7905] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus
2024-04-23 16:22:40.437 UTC client backend[7905] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2024-04-23 16:22:40.437 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT enum_range(null::bogus);
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc ERROR:  schema "Nonexistent" does not exist at character 21
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regnamespace('"Nonexistent"');
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc ERROR:  invalid name syntax at character 21
2024-04-23 16:22:40.437 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT regnamespace('foo.bar');
2024-04-23 16:22:40.440 UTC client backend[7905] pg_regress/enum ERROR:  unsafe use of new value "bad" of enum type bogon at character 8
2024-04-23 16:22:40.440 UTC client backend[7905] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2024-04-23 16:22:40.440 UTC client backend[7905] pg_regress/enum STATEMENT:  SELECT 'bad'::bogon;
2024-04-23 16:22:40.482 UTC client backend[7916] pg_regress/regproc ERROR:  syntax error at or near "type" at character 11
2024-04-23 16:22:40.482 UTC client backend[7916] pg_regress/regproc CONTEXT:  invalid type name "incorrect type name syntax"
2024-04-23 16:22:40.482 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype');
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc ERROR:  invalid NUMERIC type modifier
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype');
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc ERROR:  improper qualified name (too many dotted names): way.too.many.names
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype');
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc ERROR:  cross-database references are not implemented: no_such_catalog.schema.name
2024-04-23 16:22:40.483 UTC client backend[7916] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype');
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'inf'::numeric / '0';
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '-inf'::numeric / '0';
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '0'::numeric / '0';
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'inf'::numeric % '0';
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.489 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '-inf'::numeric % '0';
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '0'::numeric % '0';
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT div('inf'::numeric, '0');
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT div('-inf'::numeric, '0');
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.490 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT div('0'::numeric, '0');
2024-04-23 16:22:40.540 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take square root of a negative number
2024-04-23 16:22:40.540 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT sqrt('-1'::numeric);
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take square root of a negative number
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT sqrt('-inf'::numeric);
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT ln('0'::numeric);
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT ln('-1'::numeric);
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT ln('-inf'::numeric);
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('0'::numeric, '10');
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('10'::numeric, '0');
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('-inf'::numeric, '10');
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.628 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('10'::numeric, '-inf');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('inf'::numeric, '0');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('inf'::numeric, '-inf');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT log('-inf'::numeric, 'inf');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT power('0'::numeric, '-1');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT power('0'::numeric, '-inf');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT power('-2'::numeric, '3.3');
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2024-04-23 16:22:40.629 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT power('-2'::numeric, '-1.5');
2024-04-23 16:22:40.630 UTC client backend[7908] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2024-04-23 16:22:40.630 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT power('-inf'::numeric, '4.5');
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 must round to an absolute value less than 1.
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (3, '1.0');
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 must round to an absolute value less than 1.
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (6, '0.99995');
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 cannot hold an infinite value.
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (10, 'Inf');
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 cannot hold an infinite value.
2024-04-23 16:22:40.632 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (11, '-Inf');
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  bigint out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT (-9223372036854775808.5)::int8;
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  bigint out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 9223372036854775807.5::int8;
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  integer out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT (-2147483648.5)::int4;
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  integer out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 2147483647.5::int4;
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  smallint out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT (-32768.5)::int2;
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric ERROR:  smallint out of range
2024-04-23 16:22:40.738 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 32767.5::int2;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert NaN to smallint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int2;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to smallint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int2;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to smallint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int2;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert NaN to integer
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int4;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to integer
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int4;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to integer
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int4;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert NaN to bigint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int8;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to bigint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int8;
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert infinity to bigint
2024-04-23 16:22:40.740 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int8;
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric ERROR:  count must be greater than zero
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0, 3.0, 4.0, 0);
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric ERROR:  count must be greater than zero
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0, 3.0, 4.0, -5);
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric ERROR:  lower bound cannot equal upper bound
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(3.5, 3.0, 3.0, 888);
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric ERROR:  count must be greater than zero
2024-04-23 16:22:40.759 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  count must be greater than zero
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  lower bound cannot equal upper bound
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  operand, lower bound, and upper bound cannot be NaN
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket('NaN', 3.0, 4.0, 888);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  operand, lower bound, and upper bound cannot be NaN
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(2.0, 3.0, '-inf', 888);
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.760 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888);
2024-04-23 16:22:40.761 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.761 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10);
2024-04-23 16:22:40.761 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.761 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20);
2024-04-23 16:22:40.762 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.762 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10);
2024-04-23 16:22:40.763 UTC client backend[7908] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2024-04-23 16:22:40.763 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20);
2024-04-23 16:22:40.771 UTC client backend[7908] pg_regress/numeric ERROR:  integer out of range
2024-04-23 16:22:40.771 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(1::float8, 0, 1, 2147483647);
2024-04-23 16:22:40.771 UTC client backend[7908] pg_regress/numeric ERROR:  integer out of range
2024-04-23 16:22:40.771 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, 1, 0, 2147483647);
2024-04-23 16:22:40.818 UTC client backend[7914] pg_regress/rangetypes ERROR:  conflicting key value violates exclusion constraint "test_range_excl_room_during_excl"
2024-04-23 16:22:40.818 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Key (room, during)=([123,124), ["Sat Jan 02 10:10:00 2010","Sat Jan 02 11:00:00 2010")) conflicts with existing key (room, during)=([123,124), ["Sat Jan 02 10:00:00 2010","Sat Jan 02 11:00:00 2010")).
2024-04-23 16:22:40.818 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  insert into test_range_excl
	  values(int4range(123, 123, '[]'), int4range(3, 3, '[]'), '[2010-01-02 10:10, 2010-01-02 11:00)');
2024-04-23 16:22:40.819 UTC client backend[7914] pg_regress/rangetypes ERROR:  conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl"
2024-04-23 16:22:40.819 UTC client backend[7914] pg_regress/rangetypes DETAIL:  Key (speaker, during)=([1,2), ["Sat Jan 02 10:10:00 2010","Sat Jan 02 11:00:00 2010")) conflicts with existing key (speaker, during)=([1,2), ["Sat Jan 02 10:00:00 2010","Sat Jan 02 11:00:00 2010")).
2024-04-23 16:22:40.819 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  insert into test_range_excl
	  values(int4range(125, 125, '[]'), int4range(1, 1, '[]'), '[2010-01-02 10:10, 2010-01-02 11:00)');
2024-04-23 16:22:40.820 UTC client backend[7914] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2024-04-23 16:22:40.820 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange;
2024-04-23 16:22:40.823 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "     " at character 40
2024-04-23 16:22:40.823 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('     ');
2024-04-23 16:22:40.825 UTC client backend[7914] pg_regress/rangetypes ERROR:  function float4mi(double precision, double precision) does not exist
2024-04-23 16:22:40.825 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi);
2024-04-23 16:22:40.825 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "   1234   %" at character 40
2024-04-23 16:22:40.825 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('   1234   %');
2024-04-23 16:22:40.825 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "xyz" at character 40
2024-04-23 16:22:40.825 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('xyz');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "- 1234" at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('- 1234');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "5 . 0" at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('5 . 0');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "5. 0   " at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('5. 0   ');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "" at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: " N aN " at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES (' N aN ');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "+NaN" at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('+NaN');
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "-NaN" at character 40
2024-04-23 16:22:40.826 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('-NaN');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "+ infinity" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('+ infinity');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "_123" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('_123');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123_" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123_');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "12__34" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('12__34');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123_.456" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123_.456');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123._456" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123._456');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e_34" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e_34');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e34_" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e34_');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e3__4" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e3__4');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0b1112" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0b1112');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0c1112" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0c1112');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0o12345678" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0o12345678');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x1eg" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x1eg');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x12.34" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x12.34');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x__1234" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x__1234');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x1234_" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x1234_');
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x12__34" at character 40
2024-04-23 16:22:40.827 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x12__34');
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale -6 cannot hold an infinite value.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millions) VALUES ('inf');
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale -6 must round to an absolute value less than 10^9.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millions) VALUES (999500000);
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale -3 must round to an absolute value less than 10^6.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (thousands) VALUES (999500);
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale 0 must round to an absolute value less than 10^3.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (units) VALUES (999.5);
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale 3 must round to an absolute value less than 1.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (thousandths) VALUES (0.9995);
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric ERROR:  numeric field overflow
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric DETAIL:  A field with precision 3, scale 6 must round to an absolute value less than 10^-3.
2024-04-23 16:22:40.833 UTC client backend[7908] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millionths) VALUES (0.0009995);
2024-04-23 16:22:40.843 UTC client backend[7908] pg_regress/numeric ERROR:  value overflows numeric format
2024-04-23 16:22:40.843 UTC client backend[7908] pg_regress/numeric STATEMENT:  select 10.0 ^ 2147483647 as overflows;
2024-04-23 16:22:40.844 UTC client backend[7908] pg_regress/numeric ERROR:  value overflows numeric format
2024-04-23 16:22:40.844 UTC client backend[7908] pg_regress/numeric STATEMENT:  select 117743296169.0 ^ 1000000000 as overflows;
2024-04-23 16:22:40.845 UTC client backend[7908] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2024-04-23 16:22:40.845 UTC client backend[7908] pg_regress/numeric STATEMENT:  select 0.0 ^ (-12.34);
2024-04-23 16:22:40.845 UTC client backend[7908] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2024-04-23 16:22:40.845 UTC client backend[7908] pg_regress/numeric STATEMENT:  select (-12.34) ^ 1.2;
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric ERROR:  step size cannot equal zero
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series(-100::numeric, 100::numeric, 0::numeric);
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric ERROR:  step size cannot be NaN
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric);
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric ERROR:  start value cannot be NaN
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series('nan'::numeric, 100::numeric, 10::numeric);
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric ERROR:  stop value cannot be NaN
2024-04-23 16:22:40.847 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric);
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric ERROR:  start value cannot be infinity
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric);
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric ERROR:  stop value cannot be infinity
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric);
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric ERROR:  step size cannot be infinity
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric);
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric STATEMENT:  select ln(-12.34);
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.848 UTC client backend[7908] pg_regress/numeric STATEMENT:  select ln(0.0);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric CONTEXT:  SQL function "log" statement 1
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(-12.34);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric CONTEXT:  SQL function "log" statement 1
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(0.0);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(-12.34, 56.78);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(-12.34, -56.78);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(12.34, -56.78);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(0.0, 12.34);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  cannot take logarithm of zero
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(12.34, 0.0);
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric ERROR:  division by zero
2024-04-23 16:22:40.849 UTC client backend[7908] pg_regress/numeric STATEMENT:  select log(1.0, 12.34);
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot drop type mydomain because other objects depend on it
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes DETAIL:  type mydomainrange depends on type mydomain
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  drop domain mydomain;
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes ERROR:  value for domain restrictedrange violates check constraint "restrictedrange_check"
2024-04-23 16:22:40.883 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select '[4,50)'::restrictedrange @> 7;
2024-04-23 16:22:40.884 UTC client backend[7914] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:40.884 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select textrange1('a','Z') @> 'b'::text;
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes ERROR:  function anyarray_anyrange_func(integer[], numrange) does not exist at character 8
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20));
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function bogus_func(anyelement)
	  returns anyrange as 'select int4range(1,10)' language sql;
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:40.885 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function bogus_func(int)
	  returns anyrange as 'select int4range(1,10)' language sql;
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes ERROR:  function rangetypes_sql(numrange, integer[]) does not exist at character 8
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select rangetypes_sql(numrange(1,10), ARRAY[2,20]);
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes ERROR:  function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20));
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:22:40.886 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function bogus_func(anycompatible)
	  returns anycompatiblerange as 'select int4range(1,10)' language sql;
2024-04-23 16:22:40.895 UTC client backend[7908] pg_regress/numeric LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp7908.0", size 1400000
2024-04-23 16:22:40.895 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT SUM(9999::numeric) FROM generate_series(1, 100000);
2024-04-23 16:22:40.909 UTC client backend[7914] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:40.909 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  select arrayrange(ARRAY[2,1], ARRAY[1,2]);
2024-04-23 16:22:41.051 UTC client backend[7908] pg_regress/numeric LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp7908.1", size 1400000
2024-04-23 16:22:41.051 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT SUM((-9999)::numeric) FROM generate_series(1, 100000);
2024-04-23 16:22:41.103 UTC client backend[7914] pg_regress/rangetypes ERROR:  composite type two_ints cannot be made a member of itself
2024-04-23 16:22:41.103 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  alter type two_ints add attribute c two_ints_range;
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function outparam_fail(i anyelement, out r anyrange, out t text)
	  as $$ select '[1,10]', 'foo' $$ language sql;
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function inoutparam_fail(inout i anyelement, out r anyrange)
	  as $$ select $1, '[1,10]' $$ language sql;
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:41.106 UTC client backend[7914] pg_regress/rangetypes STATEMENT:  create function table_fail(i anyelement) returns table(i anyelement, r anyrange)
	  as $$ select $1, '[1,10]' $$ language sql;
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  value overflows numeric format
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2);
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  value overflows numeric format
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT factorial(100000);
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  factorial of a negative number is undefined
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT factorial(-4);
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  pg_lsn out of range
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT pg_lsn(-1::numeric);
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  pg_lsn out of range
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT pg_lsn(18446744073709551616::numeric);
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric ERROR:  cannot convert NaN to pg_lsn
2024-04-23 16:22:41.180 UTC client backend[7908] pg_regress/numeric STATEMENT:  SELECT pg_lsn('NaN'::numeric);
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box ERROR:  invalid input syntax for type box: "(2.3, 4.5)" at character 34
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)');
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box ERROR:  invalid input syntax for type box: "[1, 2, 3, 4)" at character 34
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)');
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box ERROR:  invalid input syntax for type box: "(1, 2, 3, 4]" at character 34
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]');
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box ERROR:  invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34
2024-04-23 16:22:42.569 UTC client backend[8252] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x');
2024-04-23 16:22:42.570 UTC client backend[8252] pg_regress/box ERROR:  invalid input syntax for type box: "asdfasdf(ad" at character 34
2024-04-23 16:22:42.570 UTC client backend[8252] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad');
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path ERROR:  invalid input syntax for type path: "[]" at character 30
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[]');
2024-04-23 16:22:42.570 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "1997-02-29" at character 30
2024-04-23 16:22:42.570 UTC client backend[8255] pg_regress/date STATEMENT:  INSERT INTO DATE_TBL VALUES ('1997-02-29');
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path ERROR:  invalid input syntax for type path: "[(,2),(3,4)]" at character 30
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]');
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path ERROR:  invalid input syntax for type path: "[(1,2),(3,4)" at character 30
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)');
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path ERROR:  invalid input syntax for type path: "(1,2,3,4" at character 30
2024-04-23 16:22:42.570 UTC client backend[8251] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('(1,2,3,4');
2024-04-23 16:22:42.571 UTC client backend[8251] pg_regress/path ERROR:  invalid input syntax for type path: "(1,2),(3,4)]" at character 30
2024-04-23 16:22:42.571 UTC client backend[8251] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]');
2024-04-23 16:22:42.574 UTC client backend[8256] pg_regress/time ERROR:  invalid input syntax for type time: "15:36:39 America/New_York" at character 30
2024-04-23 16:22:42.574 UTC client backend[8256] pg_regress/time STATEMENT:  INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York');
2024-04-23 16:22:42.575 UTC client backend[8254] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(-100,0),-100>" at character 32
2024-04-23 16:22:42.575 UTC client backend[8254] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>');
2024-04-23 16:22:42.576 UTC client backend[8253] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "0.0" at character 37
2024-04-23 16:22:42.576 UTC client backend[8253] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('0.0');
2024-04-23 16:22:42.576 UTC client backend[8254] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(100,200),10" at character 32
2024-04-23 16:22:42.576 UTC client backend[8254] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10');
2024-04-23 16:22:42.576 UTC client backend[8253] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0.0 0.0" at character 37
2024-04-23 16:22:42.576 UTC client backend[8253] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0');
2024-04-23 16:22:42.576 UTC client backend[8254] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(100,200),10> x" at character 32
2024-04-23 16:22:42.576 UTC client backend[8254] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x');
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0,1,2)" at character 37
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)');
2024-04-23 16:22:42.577 UTC client backend[8254] pg_regress/circle ERROR:  invalid input syntax for type circle: "1abc,3,5" at character 32
2024-04-23 16:22:42.577 UTC client backend[8254] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5');
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0,1,2,3" at character 37
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3');
2024-04-23 16:22:42.577 UTC client backend[8254] pg_regress/circle ERROR:  invalid input syntax for type circle: "(3,(1,2),3)" at character 32
2024-04-23 16:22:42.577 UTC client backend[8254] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)');
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "asdf" at character 37
2024-04-23 16:22:42.577 UTC client backend[8253] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('asdf');
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time ERROR:  date/time field value out of range: "24:00:00.01" at character 8
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT '24:00:00.01'::time;
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time ERROR:  date/time field value out of range: "23:59:60.01" at character 8
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT '23:59:60.01'::time;
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "1/8/1999" at character 13
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1/8/1999';
2024-04-23 16:22:42.578 UTC client backend[8259] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32
2024-04-23 16:22:42.578 UTC client backend[8259] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York');
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "123    08:00:2b:01:02:03" at character 8
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '123    08:00:2b:01:02:03'::macaddr8;
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time ERROR:  date/time field value out of range: "24:01:00" at character 8
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT '24:01:00'::time;
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "1/18/1999" at character 13
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1/18/1999';
2024-04-23 16:22:42.578 UTC client backend[8259] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 m2" at character 32
2024-04-23 16:22:42.578 UTC client backend[8259] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2');
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03  123" at character 8
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03  123'::macaddr8;
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time ERROR:  date/time field value out of range: "25:00:00" at character 8
2024-04-23 16:22:42.578 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT '25:00:00'::time;
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "18/1/1999" at character 13
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.578 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '18/1/1999';
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "123    08:00:2b:01:02:03:04:05" at character 8
2024-04-23 16:22:42.578 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '123    08:00:2b:01:02:03:04:05'::macaddr8;
2024-04-23 16:22:42.579 UTC client backend[8262] pg_regress/inet ERROR:  table "inet_tbl" does not exist
2024-04-23 16:22:42.579 UTC client backend[8262] pg_regress/inet STATEMENT:  DROP TABLE INET_TBL;
2024-04-23 16:22:42.579 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05  123" at character 8
2024-04-23 16:22:42.579 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03:04:05  123'::macaddr8;
2024-04-23 16:22:42.579 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "" at character 8
2024-04-23 16:22:42.579 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Missing left brace.
2024-04-23 16:22:42.579 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select ''::textmultirange;
2024-04-23 16:22:42.579 UTC client backend[8264] pg_regress/macaddr ERROR:  invalid input syntax for type macaddr: "0800:2b01:0203" at character 37
2024-04-23 16:22:42.579 UTC client backend[8264] pg_regress/macaddr STATEMENT:  INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203');
2024-04-23 16:22:42.580 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8
2024-04-23 16:22:42.580 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8;
2024-04-23 16:22:42.580 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{,}" at character 8
2024-04-23 16:22:42.580 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected range start.
2024-04-23 16:22:42.580 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{,}'::textmultirange;
2024-04-23 16:22:42.580 UTC client backend[8264] pg_regress/macaddr ERROR:  invalid input syntax for type macaddr: "not even close" at character 37
2024-04-23 16:22:42.580 UTC client backend[8264] pg_regress/macaddr STATEMENT:  INSERT INTO macaddr_data VALUES (9, 'not even close');
2024-04-23 16:22:42.581 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8
2024-04-23 16:22:42.581 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8;
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(,)}." at character 8
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Junk after closing right brace.
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(,)}.'::textmultirange;
2024-04-23 16:22:42.581 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8
2024-04-23 16:22:42.581 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08002b:01020304050607'::macaddr8;
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{[a,c),}" at character 8
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected range start.
2024-04-23 16:22:42.581 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{[a,c),}'::textmultirange;
2024-04-23 16:22:42.582 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b01020304050607" at character 8
2024-04-23 16:22:42.582 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08002b01020304050607'::macaddr8;
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{,[a,c)}" at character 8
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected range start.
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{,[a,c)}'::textmultirange;
2024-04-23 16:22:42.582 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "January 8, 99 BC" at character 13
2024-04-23 16:22:42.582 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.582 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date 'January 8, 99 BC';
2024-04-23 16:22:42.582 UTC client backend[8256] pg_regress/time ERROR:  operator is not unique: time without time zone + time without time zone at character 11
2024-04-23 16:22:42.582 UTC client backend[8256] pg_regress/time HINT:  Could not choose a best candidate operator. You might need to add explicit type casts.
2024-04-23 16:22:42.582 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL;
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{-[a,z)}" at character 8
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected range start.
2024-04-23 16:22:42.582 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{-[a,z)}'::textmultirange;
2024-04-23 16:22:42.582 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "0z002b0102030405" at character 8
2024-04-23 16:22:42.582 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '0z002b0102030405'::macaddr8;
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{[a,z) - }" at character 8
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{[a,z) - }'::textmultirange;
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b010203xyza" at character 8
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08002b010203xyza'::macaddr8;
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(",a)}" at character 8
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Unexpected end of input.
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(",a)}'::textmultirange;
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00-2b:01:02:03:04:05'::macaddr8;
2024-04-23 16:22:42.583 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08-Jan-99" at character 13
2024-04-23 16:22:42.583 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.583 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08-Jan-99';
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed range literal: "(,,a)" at character 8
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Too many commas.
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(,,a)}'::textmultirange;
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8
2024-04-23 16:22:42.583 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00-2b:01:02:03:04:05'::macaddr8;
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed range literal: "()" at character 8
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Missing comma after lower bound.
2024-04-23 16:22:42.583 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(),a)}'::textmultirange;
2024-04-23 16:22:42.584 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8
2024-04-23 16:22:42.584 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01.02:03:04:05'::macaddr8;
2024-04-23 16:22:42.584 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "badly formatted interval" at character 39
2024-04-23 16:22:42.584 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval');
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "Jan-08-99" at character 13
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date 'Jan-08-99';
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(a,))}" at character 8
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(a,))}'::textmultirange;
2024-04-23 16:22:42.584 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8
2024-04-23 16:22:42.584 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01.02:03:04:05'::macaddr8;
2024-04-23 16:22:42.584 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "@ 30 eons ago" at character 39
2024-04-23 16:22:42.584 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago');
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed range literal: "(]" at character 8
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Missing comma after lower bound.
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(],a)}'::textmultirange;
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(a,])}" at character 8
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{(a,])}'::textmultirange;
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2024-04-23 16:22:42.584 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{[z,a]}'::textmultirange;
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2024-04-23 16:22:42.584 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08 Jan 99" at character 13
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08 Jan 99';
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "Jan 08 99" at character 13
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date 'Jan 08 99';
2024-04-23 16:22:42.585 UTC client backend[8262] pg_regress/inet ERROR:  invalid cidr value: "192.168.1.2/30" at character 37
2024-04-23 16:22:42.585 UTC client backend[8262] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2024-04-23 16:22:42.585 UTC client backend[8262] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226');
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08-01-99" at character 13
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.585 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08-01-99';
2024-04-23 16:22:42.585 UTC client backend[8262] pg_regress/inet ERROR:  invalid input syntax for type cidr: "1234::1234::1234" at character 37
2024-04-23 16:22:42.585 UTC client backend[8262] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4');
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08-01-1999" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08-01-1999';
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "01-08-99" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '01-08-99';
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet ERROR:  invalid cidr value: "192.168.1.2/30" at character 42
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226');
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "01-08-1999" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '01-08-1999';
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet ERROR:  invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2024-04-23 16:22:42.586 UTC client backend[8262] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226');
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08 01 99" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08 01 99';
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "08 01 1999" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '08 01 1999';
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "01 08 99" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '01 08 99';
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "01 08 1999" at character 13
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.586 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '01 08 1999';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "1/18/1999" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1/18/1999';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-Jan-08" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-Jan-08';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99 Jan 08" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 Jan 08';
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99 08 Jan" at character 13
2024-04-23 16:22:42.587 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 08 Jan';
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-01-08" at character 13
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-01-08';
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-08-01" at character 13
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-08-01';
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99 01 08" at character 13
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 01 08';
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99 08 01" at character 13
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 08 01';
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "18/1/1999" at character 13
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.588 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '18/1/1999';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-Jan-08" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-Jan-08';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99 Jan 08" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 Jan 08';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  invalid input syntax for type date: "99 08 Jan" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 08 Jan';
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-01-08" at character 13
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.589 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-01-08';
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99-08-01" at character 13
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99-08-01';
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99 01 08" at character 13
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 01 08';
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date ERROR:  date/time field value out of range: "99 08 01" at character 13
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '99 08 01';
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date ERROR:  date out of range: "4714-11-23 BC" at character 13
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '4714-11-23 BC';
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date ERROR:  date out of range: "5874898-01-01" at character 13
2024-04-23 16:22:42.590 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT date '5874898-01-01';
2024-04-23 16:22:42.633 UTC client backend[8259] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32
2024-04-23 16:22:42.633 UTC client backend[8259] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2');
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz ERROR:  date/time field value out of range: "24:00:00.01 PDT" at character 8
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT '24:00:00.01 PDT'::timetz;
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz ERROR:  date/time field value out of range: "23:59:60.01 PDT" at character 8
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT '23:59:60.01 PDT'::timetz;
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz ERROR:  date/time field value out of range: "24:01:00 PDT" at character 8
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT '24:01:00 PDT'::timetz;
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz ERROR:  date/time field value out of range: "25:00:00 PDT" at character 8
2024-04-23 16:22:42.634 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT '25:00:00 PDT'::timetz;
2024-04-23 16:22:42.635 UTC client backend[8259] pg_regress/timetz ERROR:  operator does not exist: time with time zone + time with time zone at character 11
2024-04-23 16:22:42.635 UTC client backend[8259] pg_regress/timetz HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.635 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL;
2024-04-23 16:22:42.637 UTC client backend[8256] pg_regress/time ERROR:  unit "day" not supported for type time without time zone
2024-04-23 16:22:42.637 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT EXTRACT(DAY         FROM TIME '2020-05-26 13:30:25.575401');
2024-04-23 16:22:42.637 UTC client backend[8259] pg_regress/timetz ERROR:  unit "day" not supported for type time with time zone
2024-04-23 16:22:42.637 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT EXTRACT(DAY         FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04');
2024-04-23 16:22:42.638 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.638 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT -('-2147483648 months'::interval);
2024-04-23 16:22:42.638 UTC client backend[8256] pg_regress/time ERROR:  unit "fortnight" not recognized for type time without time zone
2024-04-23 16:22:42.638 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT EXTRACT(FORTNIGHT   FROM TIME '2020-05-26 13:30:25.575401');
2024-04-23 16:22:42.638 UTC client backend[8259] pg_regress/timetz ERROR:  unit "fortnight" not recognized for type time with time zone
2024-04-23 16:22:42.638 UTC client backend[8259] pg_regress/timetz STATEMENT:  SELECT EXTRACT(FORTNIGHT   FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04');
2024-04-23 16:22:42.639 UTC client backend[8256] pg_regress/time ERROR:  unit "timezone" not supported for type time without time zone
2024-04-23 16:22:42.639 UTC client backend[8256] pg_regress/time STATEMENT:  SELECT EXTRACT(TIMEZONE    FROM TIME '2020-05-26 13:30:25.575401');
2024-04-23 16:22:42.640 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.640 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT -('-2147483648 days'::interval);
2024-04-23 16:22:42.640 UTC client backend[8267] pg_regress/strings ERROR:  syntax error at or near "' - third line'" at character 75
2024-04-23 16:22:42.640 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT 'first line'
	' - next line' /* this comment is not allowed here */
	' - third line'
		AS "Illegal comment within continuation";
2024-04-23 16:22:42.641 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.641 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT -('-9223372036854775808 us'::interval);
2024-04-23 16:22:42.642 UTC client backend[8269] pg_regress/point ERROR:  invalid input syntax for type point: "asdfasdf" at character 35
2024-04-23 16:22:42.642 UTC client backend[8269] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf');
2024-04-23 16:22:42.643 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.643 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval);
2024-04-23 16:22:42.643 UTC client backend[8269] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0 10.0)" at character 35
2024-04-23 16:22:42.643 UTC client backend[8269] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)');
2024-04-23 16:22:42.643 UTC client backend[8269] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0, 10.0) x" at character 35
2024-04-23 16:22:42.643 UTC client backend[8269] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x');
2024-04-23 16:22:42.645 UTC client backend[8269] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0,10.0" at character 35
2024-04-23 16:22:42.645 UTC client backend[8269] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0');
2024-04-23 16:22:42.646 UTC client backend[8269] pg_regress/point ERROR:  "1e+500" is out of range for type double precision at character 35
2024-04-23 16:22:42.646 UTC client backend[8269] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)');
2024-04-23 16:22:42.647 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483648 days" at character 42
2024-04-23 16:22:42.647 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days');
2024-04-23 16:22:42.649 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 days" at character 42
2024-04-23 16:22:42.649 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days');
2024-04-23 16:22:42.650 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range at character 42
2024-04-23 16:22:42.650 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years');
2024-04-23 16:22:42.651 UTC client backend[8263] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "not even close" at character 38
2024-04-23 16:22:42.651 UTC client backend[8263] pg_regress/macaddr8 STATEMENT:  INSERT INTO macaddr8_data VALUES (9, 'not even close');
2024-04-23 16:22:42.651 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range at character 42
2024-04-23 16:22:42.651 UTC client backend[8261] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years');
2024-04-23 16:22:42.652 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.652 UTC client backend[8261] pg_regress/interval STATEMENT:  select extract(epoch from '256 microseconds'::interval * (2^55)::float8);
2024-04-23 16:22:42.655 UTC client backend[8271] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30
2024-04-23 16:22:42.655 UTC client backend[8271] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)');
2024-04-23 16:22:42.656 UTC client backend[8271] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[1,2,3, 4" at character 30
2024-04-23 16:22:42.656 UTC client backend[8271] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4');
2024-04-23 16:22:42.658 UTC client backend[8271] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30
2024-04-23 16:22:42.658 UTC client backend[8271] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]');
2024-04-23 16:22:42.658 UTC client backend[8271] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30
2024-04-23 16:22:42.658 UTC client backend[8271] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)');
2024-04-23 16:22:42.658 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape at character 18
2024-04-23 16:22:42.658 UTC client backend[8267] pg_regress/strings HINT:  Unicode escapes must be \XXXX or \+XXXXXX.
2024-04-23 16:22:42.658 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \061';
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "{}" at character 30
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{}');
2024-04-23 16:22:42.659 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape at character 18
2024-04-23 16:22:42.659 UTC client backend[8267] pg_regress/strings HINT:  Unicode escapes must be \XXXX or \+XXXXXX.
2024-04-23 16:22:42.659 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+0061';
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "{0" at character 30
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0');
2024-04-23 16:22:42.659 UTC client backend[8267] pg_regress/strings ERROR:  UESCAPE must be followed by a simple string literal at or near "+" at character 33
2024-04-23 16:22:42.659 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE +;
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0}" at character 30
2024-04-23 16:22:42.659 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0}');
2024-04-23 16:22:42.660 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape character at or near "'+'" at character 33
2024-04-23 16:22:42.660 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE '+';
2024-04-23 16:22:42.660 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0,1" at character 30
2024-04-23 16:22:42.660 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1');
2024-04-23 16:22:42.661 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2024-04-23 16:22:42.661 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99';
2024-04-23 16:22:42.661 UTC client backend[8273] pg_regress/line ERROR:  invalid line specification: A and B cannot both be zero at character 30
2024-04-23 16:22:42.661 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1}');
2024-04-23 16:22:42.662 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2024-04-23 16:22:42.662 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99xy';
2024-04-23 16:22:42.662 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0,1} x" at character 30
2024-04-23 16:22:42.662 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1} x');
2024-04-23 16:22:42.662 UTC client backend[8255] pg_regress/date ERROR:  unit "microseconds" not supported for type date
2024-04-23 16:22:42.662 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(MICROSECONDS  FROM DATE '2020-08-11');
2024-04-23 16:22:42.663 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2024-04-23 16:22:42.663 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99\\';
2024-04-23 16:22:42.663 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30
2024-04-23 16:22:42.663 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)');
2024-04-23 16:22:42.663 UTC client backend[8255] pg_regress/date ERROR:  unit "milliseconds" not supported for type date
2024-04-23 16:22:42.663 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(MILLISECONDS  FROM DATE '2020-08-11');
2024-04-23 16:22:42.664 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2024-04-23 16:22:42.664 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99\0061';
2024-04-23 16:22:42.664 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "[1,2,3, 4" at character 30
2024-04-23 16:22:42.664 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[1,2,3, 4');
2024-04-23 16:22:42.664 UTC client backend[8255] pg_regress/date ERROR:  unit "second" not supported for type date
2024-04-23 16:22:42.664 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(SECOND        FROM DATE '2020-08-11');
2024-04-23 16:22:42.664 UTC client backend[8255] pg_regress/date ERROR:  unit "minute" not supported for type date
2024-04-23 16:22:42.664 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(MINUTE        FROM DATE '2020-08-11');
2024-04-23 16:22:42.664 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "[(,2),(3,4)]" at character 30
2024-04-23 16:22:42.664 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]');
2024-04-23 16:22:42.665 UTC client backend[8255] pg_regress/date ERROR:  unit "hour" not supported for type date
2024-04-23 16:22:42.665 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(HOUR          FROM DATE '2020-08-11');
2024-04-23 16:22:42.665 UTC client backend[8273] pg_regress/line ERROR:  invalid input syntax for type line: "[(1,2),(3,4)" at character 30
2024-04-23 16:22:42.665 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)');
2024-04-23 16:22:42.665 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 26
2024-04-23 16:22:42.665 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+00db99\+000061';
2024-04-23 16:22:42.666 UTC client backend[8273] pg_regress/line ERROR:  invalid line specification: must be two distinct points at character 30
2024-04-23 16:22:42.666 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]');
2024-04-23 16:22:42.666 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape value at character 18
2024-04-23 16:22:42.666 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+2FFFFF';
2024-04-23 16:22:42.666 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "123a" at character 8
2024-04-23 16:22:42.666 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 123abc;
2024-04-23 16:22:42.666 UTC client backend[8273] pg_regress/line ERROR:  invalid line specification: must be two distinct points
2024-04-23 16:22:42.666 UTC client backend[8273] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)'));
2024-04-23 16:22:42.667 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0x0o" at character 8
2024-04-23 16:22:42.667 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0x0o;
2024-04-23 16:22:42.667 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.a" at character 8
2024-04-23 16:22:42.667 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0.a;
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape at character 17
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings HINT:  Unicode escapes must be \uXXXX or \UXXXXXXXX.
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \u061';
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0a" at character 8
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0.0a;
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape at character 17
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings HINT:  Unicode escapes must be \uXXXX or \UXXXXXXXX.
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \U0061';
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near ".0a" at character 8
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT .0a;
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "'" at character 23
2024-04-23 16:22:42.668 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99';
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e1a" at character 8
2024-04-23 16:22:42.668 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0.0e1a;
2024-04-23 16:22:42.669 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "x" at character 23
2024-04-23 16:22:42.669 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99xy';
2024-04-23 16:22:42.669 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e" at character 8
2024-04-23 16:22:42.669 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0.0e;
2024-04-23 16:22:42.669 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\" at character 23
2024-04-23 16:22:42.669 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99\\';
2024-04-23 16:22:42.669 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e+" at character 8
2024-04-23 16:22:42.669 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0.0e+a;
2024-04-23 16:22:42.670 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\u0061" at character 23
2024-04-23 16:22:42.670 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99\u0061';
2024-04-23 16:22:42.670 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after parameter at or near "$1a" at character 22
2024-04-23 16:22:42.670 UTC client backend[8270] pg_regress/numerology STATEMENT:  PREPARE p1 AS SELECT $1a;
2024-04-23 16:22:42.670 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\U00000061" at character 27
2024-04-23 16:22:42.670 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \U0000db99\U00000061';
2024-04-23 16:22:42.670 UTC client backend[8270] pg_regress/numerology ERROR:  invalid binary integer at or near "0b" at character 8
2024-04-23 16:22:42.670 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0b;
2024-04-23 16:22:42.671 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape value at or near "\U002FFFFF" at character 17
2024-04-23 16:22:42.671 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'wrong: \U002FFFFF';
2024-04-23 16:22:42.671 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1b" at character 8
2024-04-23 16:22:42.671 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1b;
2024-04-23 16:22:42.671 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0b0x" at character 8
2024-04-23 16:22:42.671 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0b0x;
2024-04-23 16:22:42.672 UTC client backend[8270] pg_regress/numerology ERROR:  invalid octal integer at or near "0o" at character 8
2024-04-23 16:22:42.672 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0o;
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061";
2024-04-23 16:22:42.672 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1o" at character 8
2024-04-23 16:22:42.672 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1o;
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.672 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*';
2024-04-23 16:22:42.673 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0o0x" at character 8
2024-04-23 16:22:42.673 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0o0x;
2024-04-23 16:22:42.673 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.673 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.673 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&' \' UESCAPE '!' AS "tricky";
2024-04-23 16:22:42.673 UTC client backend[8270] pg_regress/numerology ERROR:  invalid hexadecimal integer at or near "0x" at character 8
2024-04-23 16:22:42.673 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0x;
2024-04-23 16:22:42.674 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1x" at character 8
2024-04-23 16:22:42.674 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1x;
2024-04-23 16:22:42.674 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.674 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.674 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \061';
2024-04-23 16:22:42.674 UTC client backend[8255] pg_regress/date ERROR:  unit "timezone" not supported for type date
2024-04-23 16:22:42.674 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE      FROM DATE '2020-08-11');
2024-04-23 16:22:42.675 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0x0y" at character 8
2024-04-23 16:22:42.675 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 0x0y;
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+0061';
2024-04-23 16:22:42.675 UTC client backend[8255] pg_regress/date ERROR:  unit "timezone_m" not supported for type date
2024-04-23 16:22:42.675 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE_M    FROM DATE '2020-08-11');
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when standard_conforming_strings is off.
2024-04-23 16:22:42.675 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE '+';
2024-04-23 16:22:42.676 UTC client backend[8255] pg_regress/date ERROR:  unit "timezone_h" not supported for type date
2024-04-23 16:22:42.676 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE_H    FROM DATE '2020-08-11');
2024-04-23 16:22:42.677 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.677 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '3000000 months'::interval * 1000;
2024-04-23 16:22:42.677 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.677 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '3000000 months'::interval / 0.001;
2024-04-23 16:22:42.678 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.678 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '3000000 days'::interval * 1000;
2024-04-23 16:22:42.678 UTC client backend[8267] pg_regress/strings ERROR:  invalid hexadecimal data: odd number of digits at character 8
2024-04-23 16:22:42.678 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'\\xDeAdBeE'::bytea;
2024-04-23 16:22:42.679 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.679 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '3000000 days'::interval / 0.001;
2024-04-23 16:22:42.679 UTC client backend[8265] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:42.679 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select nummultirange(numrange(2.0, 1.0));
2024-04-23 16:22:42.679 UTC client backend[8267] pg_regress/strings ERROR:  invalid hexadecimal digit: "x" at character 8
2024-04-23 16:22:42.679 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'\\xDeAdBeEx'::bytea;
2024-04-23 16:22:42.680 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.680 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '1 month 2146410 days'::interval * 1000.5002;
2024-04-23 16:22:42.680 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.680 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '4611686018427387904 usec'::interval / 0.1;
2024-04-23 16:22:42.681 UTC client backend[8270] pg_regress/numerology ERROR:  column "_100" does not exist at character 8
2024-04-23 16:22:42.681 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT _100;
2024-04-23 16:22:42.681 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "100_" at character 8
2024-04-23 16:22:42.681 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 100_;
2024-04-23 16:22:42.682 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "100_" at character 8
2024-04-23 16:22:42.682 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 100__000;
2024-04-23 16:22:42.682 UTC client backend[8270] pg_regress/numerology ERROR:  syntax error at or near ".5" at character 14
2024-04-23 16:22:42.682 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT _1_000.5;
2024-04-23 16:22:42.682 UTC client backend[8267] pg_regress/strings ERROR:  invalid input syntax for type bytea at character 8
2024-04-23 16:22:42.682 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT E'De\\678dBeEf'::bytea;
2024-04-23 16:22:42.683 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000_" at character 8
2024-04-23 16:22:42.683 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1_000_.5;
2024-04-23 16:22:42.683 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000._" at character 8
2024-04-23 16:22:42.683 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1_000._5;
2024-04-23 16:22:42.683 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.683 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_hours(interval '2147483647 days 24 hrs');
2024-04-23 16:22:42.684 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000.5_" at character 8
2024-04-23 16:22:42.684 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1_000.5_;
2024-04-23 16:22:42.684 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.684 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_days(interval '2147483647 months 30 days');
2024-04-23 16:22:42.684 UTC client backend[8270] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000.5e" at character 8
2024-04-23 16:22:42.684 UTC client backend[8270] pg_regress/numerology STATEMENT:  SELECT 1_000.5e_1;
2024-04-23 16:22:42.686 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.686 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '2147483647 months 30 days');
2024-04-23 16:22:42.687 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.687 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '-2147483648 months -30 days');
2024-04-23 16:22:42.689 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.689 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs');
2024-04-23 16:22:42.689 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.689 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs');
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 second 2 seconds" at character 8
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '1 second 2 seconds'::interval;
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '10 milliseconds 20 milliseconds'::interval;
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '5.5 seconds 3 milliseconds'::interval;
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8
2024-04-23 16:22:42.692 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '1:20:05 5 microseconds'::interval;
2024-04-23 16:22:42.693 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 day 1 day" at character 8
2024-04-23 16:22:42.693 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '1 day 1 day'::interval;
2024-04-23 16:22:42.695 UTC client backend[8255] pg_regress/date ERROR:  unit "microsec" not recognized for type date
2024-04-23 16:22:42.695 UTC client backend[8255] pg_regress/date STATEMENT:  SELECT EXTRACT(MICROSEC  FROM DATE 'infinity');
2024-04-23 16:22:42.696 UTC client backend[8262] pg_regress/inet ERROR:  result is out of range
2024-04-23 16:22:42.696 UTC client backend[8262] pg_regress/inet STATEMENT:  SELECT '127.0.0.1'::inet + 10000000000;
2024-04-23 16:22:42.697 UTC client backend[8262] pg_regress/inet ERROR:  result is out of range
2024-04-23 16:22:42.697 UTC client backend[8262] pg_regress/inet STATEMENT:  SELECT '127.0.0.1'::inet - 10000000000;
2024-04-23 16:22:42.698 UTC client backend[8262] pg_regress/inet ERROR:  result is out of range
2024-04-23 16:22:42.698 UTC client backend[8262] pg_regress/inet STATEMENT:  SELECT '126::1'::inet - '127::2'::inet;
2024-04-23 16:22:42.698 UTC client backend[8255] pg_regress/date ERROR:  date field value out of range: 0-07-15
2024-04-23 16:22:42.698 UTC client backend[8255] pg_regress/date STATEMENT:  select make_date(0, 7, 15);
2024-04-23 16:22:42.698 UTC client backend[8262] pg_regress/inet ERROR:  result is out of range
2024-04-23 16:22:42.698 UTC client backend[8262] pg_regress/inet STATEMENT:  SELECT '127::1'::inet - '126::2'::inet;
2024-04-23 16:22:42.698 UTC client backend[8255] pg_regress/date ERROR:  date field value out of range: 2013-02-30
2024-04-23 16:22:42.698 UTC client backend[8255] pg_regress/date STATEMENT:  select make_date(2013, 2, 30);
2024-04-23 16:22:42.698 UTC client backend[8267] pg_regress/strings ERROR:  negative substring length not allowed
2024-04-23 16:22:42.698 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error";
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date ERROR:  date field value out of range: 2013-13-01
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date STATEMENT:  select make_date(2013, 13, 1);
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date ERROR:  date field value out of range: 2013-11--1
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date STATEMENT:  select make_date(2013, 11, -1);
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date ERROR:  time field value out of range: 10:55:100.1
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date STATEMENT:  select make_time(10, 55, 100.1);
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date ERROR:  time field value out of range: 24:00:2.1
2024-04-23 16:22:42.699 UTC client backend[8255] pg_regress/date STATEMENT:  select make_time(24, 0, 2.1);
2024-04-23 16:22:42.700 UTC client backend[8262] pg_regress/inet ERROR:  cannot merge addresses from different families
2024-04-23 16:22:42.700 UTC client backend[8262] pg_regress/inet STATEMENT:  SELECT inet_merge(c, i) FROM INET_TBL;
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2' day to minute;
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2' day to second;
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2024-04-23 16:22:42.701 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2' hour to minute;
2024-04-23 16:22:42.702 UTC client backend[8267] pg_regress/strings ERROR:  SQL regular expression may not contain more than two escape-double-quote separators
2024-04-23 16:22:42.702 UTC client backend[8267] pg_regress/strings CONTEXT:  SQL function "substring" statement 1
2024-04-23 16:22:42.702 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error";
2024-04-23 16:22:42.702 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2024-04-23 16:22:42.702 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2' hour to second;
2024-04-23 16:22:42.702 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2024-04-23 16:22:42.702 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2' minute to second;
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 11" at character 17
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '123 11' day;
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 11" at character 17
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '123 11';
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 2:03 -2:04" at character 17
2024-04-23 16:22:42.703 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '123 2:03 -2:04';
2024-04-23 16:22:42.703 UTC client backend[8267] pg_regress/strings ERROR:  invalid escape string
2024-04-23 16:22:42.703 UTC client backend[8267] pg_regress/strings HINT:  Escape string must be empty or one character.
2024-04-23 16:22:42.703 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error;
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.345" at character 17
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2.345' day to second(2);
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.345" at character 17
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2.345' hour to second(2);
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.3456" at character 17
2024-04-23 16:22:42.704 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '1 2.3456' minute to second(2);
2024-04-23 16:22:42.704 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression option: "z"
2024-04-23 16:22:42.704 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z');
2024-04-23 16:22:42.705 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range at character 17
2024-04-23 16:22:42.705 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '2562047788:00:54.775807' second(2);
2024-04-23 16:22:42.705 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range at character 17
2024-04-23 16:22:42.705 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-2562047788:00:54.775807' second(2);
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "start": -1
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i');
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "n": -1
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i');
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression option: "1"
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings HINT:  If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly.
2024-04-23 16:22:42.706 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1');
2024-04-23 16:22:42.706 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "" at character 18
2024-04-23 16:22:42.706 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT  interval '';
2024-04-23 16:22:42.707 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2024-04-23 16:22:42.707 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_count('123123123123', '123', 0);
2024-04-23 16:22:42.707 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "start": -3
2024-04-23 16:22:42.707 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_count('123123123123', '123', -3);
2024-04-23 16:22:42.708 UTC client backend[8267] pg_regress/strings ERROR:  regexp_like() does not support the "global" option
2024-04-23 16:22:42.708 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_like('abc', 'a.c', 'g');
2024-04-23 16:22:42.708 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17
2024-04-23 16:22:42.708 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P.Y0M3DT4H5M6S';
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 0, 1);
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "n": 0
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 0);
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "endoption": -1
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1);
2024-04-23 16:22:42.709 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483648 years" at character 17
2024-04-23 16:22:42.709 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483648 years';
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "endoption": 2
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2);
2024-04-23 16:22:42.709 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 years" at character 17
2024-04-23 16:22:42.709 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483649 years';
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings ERROR:  regexp_instr() does not support the "global" option
2024-04-23 16:22:42.709 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g');
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483648 months" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483648 months';
2024-04-23 16:22:42.710 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "subexpr": -1
2024-04-23 16:22:42.710 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1);
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 months" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483649 months';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483648 days" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483648 days';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 days" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483649 days';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2562047789 hours" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2562047789 hours';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2562047789 hours" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2562047789 hours';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "153722867281 minutes" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '153722867281 minutes';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-153722867281 minutes" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-153722867281 minutes';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036855 seconds" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036855 seconds';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036855 seconds" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036855 seconds';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036854777 millisecond" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036854777 millisecond';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854777 millisecond" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854777 millisecond';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775808 microsecond" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036854775808 microsecond';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775809 microsecond" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854775809 microsecond';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P2147483648" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P2147483648';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-2147483649" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-2147483649';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P1-2147483647-2147483647';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT2562047789" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT2562047789';
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047789" at character 17
2024-04-23 16:22:42.710 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT-2562047789';
2024-04-23 16:22:42.710 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2024-04-23 16:22:42.710 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 0, 1);
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "n": 0
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 0);
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings ERROR:  regexp_substr() does not support the "global" option
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g');
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings ERROR:  invalid value for parameter "subexpr": -1
2024-04-23 16:22:42.711 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1);
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression option: "z"
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz');
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression: parentheses () not balanced
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$);
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression: invalid repetition count(s)
2024-04-23 16:22:42.712 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$);
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression option: "z"
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT foo, length(foo) FROM regexp_split_to_table('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'zippy') AS foo;
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings ERROR:  invalid regular expression option: "z"
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz');
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings ERROR:  regexp_split_to_table() does not support the "global" option
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT foo, length(foo) FROM regexp_split_to_table('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g') AS foo;
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings ERROR:  regexp_split_to_array() does not support the "global" option
2024-04-23 16:22:42.713 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g');
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 weeks" at character 17
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 weeks';
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 weeks" at character 17
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 weeks';
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 decades" at character 17
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 decades';
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 decades" at character 17
2024-04-23 16:22:42.713 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 decades';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 centuries" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 centuries';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 centuries" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 centuries';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 millennium" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 millennium';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 millennium" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 millennium';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "1 week 2147483647 days" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '1 week 2147483647 days';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-1 week -2147483648 days" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-1 week -2147483648 days';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 1 week" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 days 1 week';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -1 week" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 days -1 week';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P1W2147483647D" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P1W2147483647D';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-1W-2147483648D" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-1W-2147483648D';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D1W" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P2147483647D1W';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-1W" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-1W';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "1 decade 2147483647 years" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '1 decade 2147483647 years';
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "1 century 2147483647 years" at character 17
2024-04-23 16:22:42.714 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '1 century 2147483647 years';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "1 millennium 2147483647 years" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '1 millennium 2147483647 years';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-1 decade -2147483648 years" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-1 decade -2147483648 years';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-1 century -2147483648 years" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-1 century -2147483648 years';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-1 millennium -2147483648 years" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-1 millennium -2147483648 years';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 decade" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 decade';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 century" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 century';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 millennium" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 millennium';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 decade" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 decade';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 century" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 century';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 millennium" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 millennium';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 millennium 2147483647 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 millennium 2147483647 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 centuries 2147483647 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 centuries 2147483647 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 decades 2147483647 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 decades 2147483647 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 yrs 2147483647 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 yrs 2147483647 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 millennium -2147483648 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 millennium -2147483648 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 centuries -2147483648 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 centuries -2147483648 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 decades -2147483648 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 decades -2147483648 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 yrs -2147483648 months" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 yrs -2147483648 months';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 millennium" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 millennium';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 centuries" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 centuries';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 decades" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 decades';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 yrs" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 yrs';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 millennium" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 millennium';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 centuries" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 centuries';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 decades" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 decades';
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 yrs" at character 17
2024-04-23 16:22:42.715 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 yrs';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 months 2147483647 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 months 2147483647 days';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 months -2147483648 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 months -2147483648 days';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 0.1 months" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 days 0.1 months';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -0.1 months" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 days -0.1 months';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.5 weeks 2147483647 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.5 weeks 2147483647 days';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.5 weeks -2147483648 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.5 weeks -2147483648 days';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 0.5 weeks" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2147483647 days 0.5 weeks';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -0.5 weeks" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 days -0.5 weeks';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.01 months 9223372036854775807 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.01 months -9223372036854775808 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.01 months';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.01 months';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 weeks 9223372036854775807 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 weeks -9223372036854775808 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.1 weeks';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.1 weeks';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 days 9223372036854775807 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-0.1 days -9223372036854775808 microseconds';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.1 days';
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17
2024-04-23 16:22:42.716 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.1 days';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.1Y2147483647M" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.1Y2147483647M';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-0.1Y-2147483648M" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-0.1Y-2147483648M';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P2147483647M0.1Y" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P2147483647M0.1Y';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648M-0.1Y" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-2147483648M-0.1Y';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.1M2147483647D" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.1M2147483647D';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-0.1M-2147483648D" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-0.1M-2147483648D';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D0.1M" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P2147483647D0.1M';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-0.1M" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-0.1M';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.5W2147483647D" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.5W2147483647D';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-0.5W-2147483648D" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-0.5W-2147483648D';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D0.5W" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P2147483647D0.5W';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-0.5W" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-0.5W';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.01MT2562047788H54.775807S';
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17
2024-04-23 16:22:42.717 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-0.01MT-2562047788H-54.775808S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.1DT2562047788H54.775807S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P-0.1DT-2562047788H-54.775808S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788.1H54.775807S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT2562047788.1H54.775807S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT-2562047788.1H-54.775808S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT2562047788H0.1M54.775807S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT-2562047788H-0.1M-54.775808S';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P0.1-2147483647-00" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P0.1-2147483647-00';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P00-0.1-2147483647" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P00-0.1-2147483647';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P00-0.01-00T2562047788:00:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'P00-00-0.1T2562047788:00:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788.1:00:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT2562047788.1:00:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788:01.:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval 'PT2562047788:01.:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 2562047788:0:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 2562047788:0:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '0.1 2562047788:0:54.775808 ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2562047788.1:0:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2562047788.1:0:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2562047788.1:0:54.775808 ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2562047788:0.1:54.775807';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '2562047788:0.1:54.775808 ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 days ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago';
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.718 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(years := 178956971);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(years := -178956971);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(years := 1, months := 2147483647);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(years := -1, months := -2147483648);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(weeks := 306783379);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(weeks := -306783379);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(weeks := 1, days := 2147483647);
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.719 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(weeks := -1, days := -2147483648);
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval ERROR:  value out of range: overflow
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(secs := 1e308);
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(secs := 1e18);
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(secs := -1e18);
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(mins := 1, secs := 9223372036800.0);
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.720 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(mins := -1, secs := -9223372036800.0);
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval ERROR:  integer out of range
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(years := 'inf'::float::int);
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval ERROR:  integer out of range
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(months := 'NaN'::float::int);
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(secs := 'inf');
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.723 UTC client backend[8261] pg_regress/interval STATEMENT:  select make_interval(secs := 'NaN');
2024-04-23 16:22:42.724 UTC client backend[8261] pg_regress/interval ERROR:  unit "fortnight" not recognized for type interval
2024-04-23 16:22:42.724 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days');
2024-04-23 16:22:42.724 UTC client backend[8261] pg_regress/interval ERROR:  unit "timezone" not supported for type interval
2024-04-23 16:22:42.724 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days');
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us';
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us';
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us';
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.730 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot add infinite interval to time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT time '11:27:42' + interval 'infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot add infinite interval to time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT time '11:27:42' + interval '-infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT time '11:27:42' - interval 'infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT time '11:27:42' - interval '-infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot add infinite interval to time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' + interval 'infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot add infinite interval to time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' + interval '-infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' - interval 'infinity';
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2024-04-23 16:22:42.731 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' - interval '-infinity';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval 'infinity' * 'nan';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-infinity' * 'nan';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2;
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval 'infinity' * 0;
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-infinity' * 0;
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '0 days' * 'infinity'::float;
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '0 days' * '-infinity'::float;
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / 'infinity';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / '-infinity';
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.732 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / 'nan';
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / 'infinity';
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / '-infinity';
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / 'nan';
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval out of range
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5;
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  timestamps cannot be binned into infinite intervals
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00');
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  timestamps cannot be binned into infinite intervals
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00');
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp);
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp);
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2024-04-23 16:22:42.733 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '12:12:12'::time);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '12:12:12'::time);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '12:12:12'::timetz);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '12:12:12'::timetz);
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  cannot convert infinite interval to time
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT 'infinity'::interval::time;
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  cannot convert infinite interval to time
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT '-infinity'::interval::time;
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17
2024-04-23 16:22:42.734 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL '42 days 2 seconds ago ago';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "2 minutes ago 5 days" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL '2 minutes ago 5 days';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "hour 5 months" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'hour 5 months';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 year months days 5 hours" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL '1 year months days 5 hours';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "now" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'now';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "today" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'today';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "tomorrow" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'tomorrow';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "allballs" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'allballs';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "epoch" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'epoch';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "yesterday" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'yesterday';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "infinity years" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'infinity years';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "infinity ago" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL 'infinity ago';
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval ERROR:  invalid input syntax for type interval: "+infinity -infinity" at character 17
2024-04-23 16:22:42.735 UTC client backend[8261] pg_regress/interval STATEMENT:  SELECT INTERVAL '+infinity -infinity';
2024-04-23 16:22:42.754 UTC client backend[8267] pg_regress/strings ERROR:  negative substring length not allowed
2024-04-23 16:22:42.754 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT substr(f1, 5, -1) from toasttest;
2024-04-23 16:22:42.786 UTC client backend[8267] pg_regress/strings ERROR:  negative substring length not allowed
2024-04-23 16:22:42.786 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT substr(f1, 5, -1) from toasttest;
2024-04-23 16:22:42.797 UTC client backend[8267] pg_regress/strings ERROR:  field position must not be zero
2024-04-23 16:22:42.797 UTC client backend[8267] pg_regress/strings STATEMENT:  select split_part('joeuser@mydatabase','@',0) AS "an error";
2024-04-23 16:22:42.801 UTC client backend[8267] pg_regress/strings ERROR:  index 99 out of valid range, 0..71
2024-04-23 16:22:42.801 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT get_bit('\x1234567890abcdef00'::bytea, 99);
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings ERROR:  index 99 out of valid range, 0..71
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0);
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings ERROR:  index 99 out of valid range, 0..8
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT get_byte('\x1234567890abcdef00'::bytea, 99);
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings ERROR:  index 99 out of valid range, 0..8
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11);
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 8
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 24
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 42
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 62
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 80
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 98
2024-04-23 16:22:42.802 UTC client backend[8267] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:22:42.805 UTC client backend[8267] pg_regress/strings ERROR:  null character not permitted
2024-04-23 16:22:42.805 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT chr(0);
2024-04-23 16:22:42.806 UTC client backend[8267] pg_regress/strings ERROR:  negative substring length not allowed
2024-04-23 16:22:42.806 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error";
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \db99');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \db99\0061');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \+00db99\+000061');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode code point: 2FFFFF
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \+2FFFFF');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \udb99\u0061');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \U0000db99\U00000061');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode code point: 2FFFFF
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \U002FFFFF');
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings ERROR:  invalid Unicode escape
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings HINT:  Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX.
2024-04-23 16:22:42.807 UTC client backend[8267] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \xyz');
2024-04-23 16:22:42.874 UTC client backend[8265] pg_regress/multirangetypes ERROR:  value for domain restrictedmultirange violates check constraint "restrictedmultirange_check"
2024-04-23 16:22:42.874 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select '{[4,50)}'::restrictedmultirange @> 7;
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes ERROR:  type "intmultirange" already exists
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Failed while creating a multirange type for type "intrange".
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes HINT:  You can manually specify a multirange type name using the "multirange_type_name" attribute.
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create type intrange as range(subtype=int);
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes ERROR:  type "intr_multirange" already exists
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  Failed while creating a multirange type for type "intr".
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes HINT:  You can manually specify a multirange type name using the "multirange_type_name" attribute.
2024-04-23 16:22:42.875 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create type intr as range(subtype=int);
2024-04-23 16:22:42.876 UTC client backend[8265] pg_regress/multirangetypes ERROR:  type "int4" already exists
2024-04-23 16:22:42.876 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C");
2024-04-23 16:22:42.877 UTC client backend[8265] pg_regress/multirangetypes ERROR:  function multirange_of_text(textrange2) does not exist at character 8
2024-04-23 16:22:42.877 UTC client backend[8265] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.877 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select multirange_of_text(textrange2('a','Z'));
2024-04-23 16:22:42.877 UTC client backend[8265] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:42.877 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select multirange_of_text(textrange1('a','Z')) @> 'b'::text;
2024-04-23 16:22:42.878 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot alter multirange type multitextrange1
2024-04-23 16:22:42.878 UTC client backend[8265] pg_regress/multirangetypes HINT:  You can alter type textrange1, which will alter the multirange type as well.
2024-04-23 16:22:42.878 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  alter type multitextrange1 owner to regress_multirange_owner;
2024-04-23 16:22:42.879 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot set privileges of multirange types
2024-04-23 16:22:42.879 UTC client backend[8265] pg_regress/multirangetypes HINT:  Set the privileges of the range type instead.
2024-04-23 16:22:42.879 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  revoke usage on type multitextrange1 from public;
2024-04-23 16:22:42.891 UTC client backend[8265] pg_regress/multirangetypes ERROR:  permission denied for type multitextrange1
2024-04-23 16:22:42.891 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create temp table test2(f1 multitextrange1[]);
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes ERROR:  function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20)));
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function bogus_func(anyelement)
	  returns anymultirange as 'select int4multirange(int4range(1,10))' language sql;
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:42.933 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function bogus_func(int)
	  returns anymultirange as 'select int4multirange(int4range(1,10))' language sql;
2024-04-23 16:22:42.935 UTC client backend[8265] pg_regress/multirangetypes ERROR:  function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8
2024-04-23 16:22:42.935 UTC client backend[8265] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.935 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]);
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes ERROR:  function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20)));
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes ERROR:  function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:42.936 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20)));
2024-04-23 16:22:42.937 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.937 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:22:42.937 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function bogus_func(anycompatible)
	  returns anycompatiblerange as 'select int4range(1,10)' language sql;
2024-04-23 16:22:42.942 UTC client backend[8260] pg_regress/timestamptz ERROR:  time zone "america/does_not_exist" not recognized at character 37
2024-04-23 16:22:42.942 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist');
2024-04-23 16:22:42.942 UTC client backend[8260] pg_regress/timestamptz ERROR:  time zone "America/Does_not_exist" not recognized
2024-04-23 16:22:42.942 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist';
2024-04-23 16:22:42.942 UTC client backend[8265] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2024-04-23 16:22:42.942 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2]));
2024-04-23 16:22:42.950 UTC client backend[8260] pg_regress/timestamptz ERROR:  date/time field value out of range: "Feb 29 17:32:01 1997" at character 37
2024-04-23 16:22:42.950 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997');
2024-04-23 16:22:42.951 UTC client backend[8260] pg_regress/timestamptz ERROR:  time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37
2024-04-23 16:22:42.951 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097');
2024-04-23 16:22:42.951 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37
2024-04-23 16:22:42.951 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC');
2024-04-23 16:22:42.952 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8
2024-04-23 16:22:42.952 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT '4714-11-23 23:59:59+00 BC'::timestamptz;
2024-04-23 16:22:42.952 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp out of range: "294277-01-01 00:00:00+00" at character 8
2024-04-23 16:22:42.952 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT '294277-01-01 00:00:00+00'::timestamptz;
2024-04-23 16:22:42.953 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp out of range: "294277-12-31 16:00:00-08" at character 8
2024-04-23 16:22:42.953 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT '294277-12-31 16:00:00-08'::timestamptz;
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function mr_outparam_fail(i anyelement, out r anymultirange, out t text)
	  as $$ select '[1,10]', 'foo' $$ language sql;
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function mr_inoutparam_fail(inout i anyelement, out r anymultirange)
	  as $$ select $1, '[1,10]' $$ language sql;
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes ERROR:  cannot determine result data type
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:22:42.957 UTC client backend[8265] pg_regress/multirangetypes STATEMENT:  create function mr_table_fail(i anyelement) returns table(i anyelement, r anymultirange)
	  as $$ select $1, '[1,10]' $$ language sql;
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamps cannot be binned into intervals containing months or years
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT date_bin('5 months'::interval, timestamp with time zone '2020-02-01 01:01:01+00', timestamp with time zone '2001-01-01+00');
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamps cannot be binned into intervals containing months or years
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT date_bin('5 years'::interval,  timestamp with time zone '2020-02-01 01:01:01+00', timestamp with time zone '2001-01-01+00');
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  stride must be greater than zero
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT date_bin('0 days'::interval, timestamp with time zone '1970-01-01 01:00:00+00' , timestamp with time zone '1970-01-01 00:00:00+00');
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  stride must be greater than zero
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT date_bin('-2 days'::interval, timestamp with time zone '1970-01-01 01:00:00+00' , timestamp with time zone '1970-01-01 00:00:00+00');
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC');
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz);
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp out of range
2024-04-23 16:22:42.981 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz);
2024-04-23 16:22:42.987 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:42.987 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT timestamptz '294276-12-31 23:59:59 UTC' - timestamptz '1999-12-23 19:59:04.224192 UTC' AS overflows;
2024-04-23 16:22:42.992 UTC client backend[8274] pg_regress/timestamp ERROR:  time zone "america/does_not_exist" not recognized at character 35
2024-04-23 16:22:42.992 UTC client backend[8274] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist');
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp ERROR:  date/time field value out of range: "Feb 29 17:32:01 1997" at character 35
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997');
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp ERROR:  time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097');
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35
2024-04-23 16:22:42.994 UTC client backend[8274] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC');
2024-04-23 16:22:42.995 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamp out of range: "4714-11-23 23:59:59 BC" at character 8
2024-04-23 16:22:42.995 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT '4714-11-23 23:59:59 BC'::timestamp;
2024-04-23 16:22:42.995 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamp out of range: "294277-01-01 00:00:00" at character 8
2024-04-23 16:22:42.995 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT '294277-01-01 00:00:00'::timestamp;
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamps cannot be binned into intervals containing months or years
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01');
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamps cannot be binned into intervals containing months or years
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT date_bin('5 years'::interval,  timestamp '2020-02-01 01:01:01', timestamp '2001-01-01');
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  stride must be greater than zero
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT date_bin('0 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00');
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  stride must be greater than zero
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT date_bin('-2 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00');
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC');
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp);
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp ERROR:  timestamp out of range
2024-04-23 16:22:42.999 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp);
2024-04-23 16:22:43.003 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:43.003 UTC client backend[8274] pg_regress/timestamp STATEMENT:  SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows;
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz ERROR:  invalid input syntax for type numeric time zone: "2"
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz HINT:  Numeric time zones must have "-" or "+" as first character.
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2');
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz ERROR:  numeric time zone "+16" out of range
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16');
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz ERROR:  numeric time zone "-16" out of range
2024-04-23 16:22:43.010 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16');
2024-04-23 16:22:43.010 UTC client backend[8274] pg_regress/timestamp ERROR:  date field value out of range: 0-07-15
2024-04-23 16:22:43.010 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select make_timestamp(0, 7, 15, 12, 30, 15);
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  step size cannot equal zero
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select * from generate_series('2020-01-01 00:00'::timestamp,
	                              '2020-01-02 03:00'::timestamp,
	                              '0 hour'::interval);
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  step size cannot be infinite
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity');
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  step size cannot be infinite
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity');
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select timestamp 'infinity' - timestamp 'infinity';
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select timestamp '-infinity' - timestamp '-infinity';
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select age(timestamp 'infinity', timestamp 'infinity');
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp ERROR:  interval out of range
2024-04-23 16:22:43.011 UTC client backend[8274] pg_regress/timestamp STATEMENT:  select age(timestamp '-infinity', timestamp '-infinity');
2024-04-23 16:22:43.029 UTC client backend[8260] pg_regress/timestamptz ERROR:  time zone "Nehwon/Lankhmar" not recognized
2024-04-23 16:22:43.029 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar');
2024-04-23 16:22:43.035 UTC client backend[8260] pg_regress/timestamptz ERROR:  step size cannot equal zero
2024-04-23 16:22:43.035 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select * from generate_series('2020-01-01 00:00'::timestamptz,
	                              '2020-01-02 03:00'::timestamptz,
	                              '0 hour'::interval);
2024-04-23 16:22:43.036 UTC client backend[8260] pg_regress/timestamptz ERROR:  step size cannot be infinite
2024-04-23 16:22:43.036 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity');
2024-04-23 16:22:43.036 UTC client backend[8260] pg_regress/timestamptz ERROR:  step size cannot be infinite
2024-04-23 16:22:43.036 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity');
2024-04-23 16:22:43.046 UTC client backend[8260] pg_regress/timestamptz ERROR:  timestamp cannot be NaN
2024-04-23 16:22:43.046 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT to_timestamp('NaN'::float);
2024-04-23 16:22:43.086 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:43.086 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT timestamptz 'infinity' - timestamptz 'infinity';
2024-04-23 16:22:43.086 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:43.086 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT timestamptz '-infinity' - timestamptz '-infinity';
2024-04-23 16:22:43.087 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:43.087 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT age(timestamptz 'infinity', timestamptz 'infinity');
2024-04-23 16:22:43.088 UTC client backend[8260] pg_regress/timestamptz ERROR:  interval out of range
2024-04-23 16:22:43.088 UTC client backend[8260] pg_regress/timestamptz STATEMENT:  SELECT age(timestamptz '-infinity', timestamptz '-infinity');
2024-04-23 16:22:45.861 UTC client backend[8651] pg_regress/tstypes ERROR:  syntax error in tsvector: "'' '1' '2'" at character 8
2024-04-23 16:22:45.861 UTC client backend[8651] pg_regress/tstypes STATEMENT:  SELECT $$'' '1' '2'$$::tsvector;
2024-04-23 16:22:45.883 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33
2024-04-23 16:22:45.883 UTC client backend[8649] pg_regress/horology HINT:  Perhaps you need a different "datestyle" setting.
2024-04-23 16:22:45.883 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp with time zone '27/12/2001 04:05:06.789-08';
2024-04-23 16:22:45.894 UTC client backend[8647] pg_regress/geometry ERROR:  value out of range: underflow
2024-04-23 16:22:45.894 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT p1.f1, p2.f1, p1.f1 * p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p1.f1[0] < 1;
2024-04-23 16:22:45.911 UTC client backend[8647] pg_regress/geometry ERROR:  value out of range: overflow
2024-04-23 16:22:45.911 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT p1.f1, p2.f1, p1.f1 / p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p2.f1[0] > 1000;
2024-04-23 16:22:45.911 UTC client backend[8647] pg_regress/geometry ERROR:  division by zero
2024-04-23 16:22:45.911 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT p1.f1, p2.f1, p1.f1 / p2.f1 FROM POINT_TBL p1, POINT_TBL p2 WHERE p2.f1 ~= '(0,0)'::point;
2024-04-23 16:22:45.925 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type xid: "" at character 8
2024-04-23 16:22:45.925 UTC client backend[8683] pg_regress/xid STATEMENT:  select ''::xid;
2024-04-23 16:22:45.927 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type xid: "asdf" at character 8
2024-04-23 16:22:45.927 UTC client backend[8683] pg_regress/xid STATEMENT:  select 'asdf'::xid;
2024-04-23 16:22:45.930 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type xid8: "" at character 8
2024-04-23 16:22:45.930 UTC client backend[8683] pg_regress/xid STATEMENT:  select ''::xid8;
2024-04-23 16:22:45.934 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type xid8: "asdf" at character 8
2024-04-23 16:22:45.934 UTC client backend[8683] pg_regress/xid STATEMENT:  select 'asdf'::xid8;
2024-04-23 16:22:45.944 UTC client backend[8680] pg_regress/expressions WARNING:  TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6
2024-04-23 16:22:45.945 UTC client backend[8654] pg_regress/regex ERROR:  regexp_match() does not support the "global" option
2024-04-23 16:22:45.945 UTC client backend[8654] pg_regress/regex HINT:  Use the regexp_matches function instead.
2024-04-23 16:22:45.945 UTC client backend[8654] pg_regress/regex STATEMENT:  select regexp_match('abc', 'Bd', 'ig');
2024-04-23 16:22:45.946 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28
2024-04-23 16:22:45.946 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT time with time zone 'T040506.789 America/Los_Angeles';
2024-04-23 16:22:45.947 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06  J J J" at character 13
2024-04-23 16:22:45.947 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '1995-08-06  J J J';
2024-04-23 16:22:45.948 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "J J 1520447" at character 13
2024-04-23 16:22:45.948 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date 'J J 1520447';
2024-04-23 16:22:45.950 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33
2024-04-23 16:22:45.950 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08';
2024-04-23 16:22:45.950 UTC client backend[8680] pg_regress/expressions WARNING:  TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6
2024-04-23 16:22:45.951 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33
2024-04-23 16:22:45.951 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08';
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 epoch" at character 13
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 epoch';
2024-04-23 16:22:45.952 UTC client backend[8680] pg_regress/expressions WARNING:  TIME(7) precision reduced to maximum allowed, 6
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 infinity" at character 13
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 infinity';
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 -infinity" at character 13
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 -infinity';
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "today infinity" at character 13
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date 'today infinity';
2024-04-23 16:22:45.952 UTC client backend[8680] pg_regress/expressions WARNING:  TIMESTAMP(7) precision reduced to maximum allowed, 6
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type date: "-infinity infinity" at character 13
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '-infinity infinity';
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 epoch';
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18
2024-04-23 16:22:45.952 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 infinity';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 -infinity';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "epoch 01:01:01" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp 'epoch 01:01:01';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "infinity 01:01:01" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp 'infinity 01:01:01';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp '-infinity 01:01:01';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "now epoch" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp 'now epoch';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "-infinity infinity" at character 18
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp '-infinity infinity';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 epoch';
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid ERROR:  operator does not exist: xid < xid at character 17
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid STATEMENT:  select '1'::xid < '2'::xid;
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 infinity';
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20
2024-04-23 16:22:45.953 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 -infinity';
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid ERROR:  operator does not exist: xid <= xid at character 17
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid STATEMENT:  select '1'::xid <= '2'::xid;
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid ERROR:  operator does not exist: xid > xid at character 17
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.953 UTC client backend[8683] pg_regress/xid STATEMENT:  select '1'::xid > '2'::xid;
2024-04-23 16:22:45.954 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20
2024-04-23 16:22:45.954 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz 'epoch 01:01:01';
2024-04-23 16:22:45.954 UTC client backend[8683] pg_regress/xid ERROR:  operator does not exist: xid >= xid at character 17
2024-04-23 16:22:45.954 UTC client backend[8683] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.954 UTC client backend[8683] pg_regress/xid STATEMENT:  select '1'::xid >= '2'::xid;
2024-04-23 16:22:45.954 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20
2024-04-23 16:22:45.954 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz 'infinity 01:01:01';
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz '-infinity 01:01:01';
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "now epoch" at character 20
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz 'now epoch';
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20
2024-04-23 16:22:45.955 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamptz '-infinity infinity';
2024-04-23 16:22:45.958 UTC client backend[8649] pg_regress/horology ERROR:  operator does not exist: date - time with time zone at character 26
2024-04-23 16:22:45.958 UTC client backend[8649] pg_regress/horology HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.958 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC";
2024-04-23 16:22:45.961 UTC client backend[8649] pg_regress/horology ERROR:  timestamp out of range
2024-04-23 16:22:45.961 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range";
2024-04-23 16:22:45.967 UTC client backend[8647] pg_regress/geometry ERROR:  operator does not exist: lseg # point at character 23
2024-04-23 16:22:45.967 UTC client backend[8647] pg_regress/geometry HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.967 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT p.f1, l.s, l.s # p.f1 AS intersection
	   FROM LSEG_TBL l, POINT_TBL p;
2024-04-23 16:22:45.970 UTC client backend[8649] pg_regress/horology ERROR:  timestamp out of range
2024-04-23 16:22:45.970 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range";
2024-04-23 16:22:45.976 UTC client backend[8651] pg_regress/tstypes ERROR:  lexeme array may not contain nulls
2024-04-23 16:22:45.976 UTC client backend[8651] pg_regress/tstypes STATEMENT:  SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]);
2024-04-23 16:22:45.976 UTC client backend[8651] pg_regress/tstypes ERROR:  lexeme array may not contain empty strings
2024-04-23 16:22:45.976 UTC client backend[8651] pg_regress/tstypes STATEMENT:  SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']);
2024-04-23 16:22:45.977 UTC client backend[8651] pg_regress/tstypes ERROR:  weight array may not contain nulls
2024-04-23 16:22:45.977 UTC client backend[8651] pg_regress/tstypes STATEMENT:  SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}');
2024-04-23 16:22:45.981 UTC client backend[8649] pg_regress/horology ERROR:  cannot cast type time with time zone to interval at character 8
2024-04-23 16:22:45.981 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01";
2024-04-23 16:22:45.981 UTC client backend[8649] pg_regress/horology ERROR:  cannot cast type interval to time with time zone at character 8
2024-04-23 16:22:45.981 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08";
2024-04-23 16:22:45.986 UTC client backend[8680] pg_regress/expressions ERROR:  operator does not exist: point = box at character 23
2024-04-23 16:22:45.986 UTC client backend[8680] pg_regress/expressions HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:45.986 UTC client backend[8680] pg_regress/expressions STATEMENT:  select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0));
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "31:12:" at character 8
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid STATEMENT:  select '31:12:'::pg_snapshot;
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "0:1:" at character 8
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid STATEMENT:  select '0:1:'::pg_snapshot;
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "12:13:0" at character 8
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid STATEMENT:  select '12:13:0'::pg_snapshot;
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8
2024-04-23 16:22:45.987 UTC client backend[8683] pg_regress/xid STATEMENT:  select '12:16:14,13'::pg_snapshot;
2024-04-23 16:22:45.990 UTC client backend[8647] pg_regress/geometry ERROR:  open path cannot be converted to polygon
2024-04-23 16:22:45.990 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1);
2024-04-23 16:22:45.995 UTC client backend[8647] pg_regress/geometry ERROR:  division by zero
2024-04-23 16:22:45.995 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT p.f1, p1.f1, p.f1 / p1.f1 FROM PATH_TBL p, POINT_TBL p1 WHERE p1.f1 ~= '(0,0)'::point;
2024-04-23 16:22:45.998 UTC client backend[8683] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20
2024-04-23 16:22:45.998 UTC client backend[8683] pg_regress/xid STATEMENT:  SELECT pg_snapshot '1:9223372036854775808:3';
2024-04-23 16:22:46.004 UTC client backend[8647] pg_regress/geometry ERROR:  must request at least 2 points
2024-04-23 16:22:46.004 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>';
2024-04-23 16:22:46.004 UTC client backend[8647] pg_regress/geometry ERROR:  cannot convert circle with radius zero to polygon
2024-04-23 16:22:46.004 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>';
2024-04-23 16:22:46.009 UTC client backend[8649] pg_regress/horology ERROR:  date out of range for timestamp
2024-04-23 16:22:46.009 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT '2202020-10-05'::date::timestamp;
2024-04-23 16:22:46.010 UTC client backend[8647] pg_regress/geometry ERROR:  value out of range: overflow
2024-04-23 16:22:46.010 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT c.f1, p.f1, c.f1 / p.f1 FROM CIRCLE_TBL c, POINT_TBL p WHERE p.f1[0] > 1000;
2024-04-23 16:22:46.010 UTC client backend[8649] pg_regress/horology ERROR:  date out of range for timestamp
2024-04-23 16:22:46.010 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT '2202020-10-05'::date::timestamptz;
2024-04-23 16:22:46.010 UTC client backend[8647] pg_regress/geometry ERROR:  division by zero
2024-04-23 16:22:46.010 UTC client backend[8647] pg_regress/geometry STATEMENT:  SELECT c.f1, p.f1, c.f1 / p.f1 FROM CIRCLE_TBL c, POINT_TBL p WHERE p.f1 ~= '(0,0)'::point;
2024-04-23 16:22:46.011 UTC client backend[8649] pg_regress/horology ERROR:  date out of range for timestamp
2024-04-23 16:22:46.011 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT '4714-11-24 BC'::date::timestamptz;
2024-04-23 16:22:46.024 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "/Feb/16" for "Mon"
2024-04-23 16:22:46.024 UTC client backend[8649] pg_regress/horology DETAIL:  The given value did not match any of the allowed values for this field.
2024-04-23 16:22:46.024 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('97/Feb/16', 'YYMonDD');
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "JUNK" for "TZ"
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology DETAIL:  Time zone abbreviation is not recognized.
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ');
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology ERROR:  invalid value ".." for "TZ"
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ');
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "xy" for "OF"
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF');
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "xy" for "OF"
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.026 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF');
2024-04-23 16:22:46.027 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2018-11-02 12:34:56.123456789"
2024-04-23 16:22:46.027 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT i, to_timestamp('2018-11-02 12:34:56.123456789', 'YYYY-MM-DD HH24:MI:SS.FF' || i) FROM generate_series(1, 6) i;
2024-04-23 16:22:46.028 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "+" for "MON"
2024-04-23 16:22:46.028 UTC client backend[8649] pg_regress/horology DETAIL:  The given value did not match any of the allowed values for this field.
2024-04-23 16:22:46.028 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2000 + + JUN', 'YYYY  MON');
2024-04-23 16:22:46.029 UTC client backend[8681] pg_regress/unicode ERROR:  invalid normalization form: def
2024-04-23 16:22:46.029 UTC client backend[8681] pg_regress/unicode STATEMENT:  SELECT "normalize"('abc', 'def');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "x1" for "MM"
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2011 x12 x18', 'YYYYxMMxDD');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid combination of date conventions
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology HINT:  Do not mix Gregorian and ISO week date conventions in a formatting template.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2005527', 'YYYYIWID');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  source string too short for "MM" formatting field
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Field requires 2 characters, but only 1 remain.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology HINT:  If your source string is not fixed-width, try using the "FM" modifier.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('19971', 'YYYYMMDD');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "1)" for "MM"
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Field requires 2 characters, but only 1 could be parsed.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology HINT:  If your source string is not fixed-width, try using the "FM" modifier.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('19971)24', 'YYYYMMDD');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "da" for "DD"
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "uary" for "YYYY"
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  conflicting values for "Mon" field in formatting string
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  This value contradicts a previous setting for the same field type.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  invalid value "xy" for "DD"
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be an integer.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('199711xy', 'YYYYMMDD');
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology ERROR:  value for "YYYY" in source string is out of range
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology DETAIL:  Value must be in the range -2147483648 to 2147483647.
2024-04-23 16:22:46.029 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('10000000000', 'FMYYYY');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 25:00:00"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 15:60:00"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 15:50:60"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  hour "15" is invalid for the 12-hour clock
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology HINT:  Use the 24-hour clock, or give an hour between 1 and 12.
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-13-01 15:50:55"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-02-30 15:50:55"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-29 15:50:55"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-11 86400"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-11 86400"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-13-10"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2016-13-10', 'YYYY-MM-DD');
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016-02-30"
2024-04-23 16:22:46.030 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2016-02-30', 'YYYY-MM-DD');
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-29"
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2015-02-29', 'YYYY-MM-DD');
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2015 366"
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2015 366', 'YYYY DDD');
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology ERROR:  date/time field value out of range: "2016 367"
2024-04-23 16:22:46.031 UTC client backend[8649] pg_regress/horology STATEMENT:  SELECT to_date('2016 367', 'YYYY DDD');
2024-04-23 16:22:46.049 UTC client backend[8681] pg_regress/unicode ERROR:  invalid normalization form: def
2024-04-23 16:22:46.049 UTC client backend[8681] pg_regress/unicode STATEMENT:  SELECT is_normalized('abc', 'def');
2024-04-23 16:22:46.343 UTC client backend[8654] pg_regress/regex ERROR:  invalid regular expression: regular expression is too complex
2024-04-23 16:22:46.343 UTC client backend[8654] pg_regress/regex STATEMENT:  select 'x' ~ repeat('x*y*z*', 1000);
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex ERROR:  invalid regular expression: invalid backreference number
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex STATEMENT:  select 'xyz' ~ 'x(\w)(?=\1)';
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex ERROR:  invalid regular expression: invalid backreference number
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex STATEMENT:  select 'xyz' ~ 'x(\w)(?=(\1))';
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex ERROR:  invalid regular expression: invalid escape \ sequence
2024-04-23 16:22:46.352 UTC client backend[8654] pg_regress/regex STATEMENT:  select 'a' ~ '\x7fffffff';
2024-04-23 16:22:47.814 UTC client backend[8893] pg_regress/insert ERROR:  null value in column "col2" of relation "inserttest" violates not-null constraint
2024-04-23 16:22:47.814 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (null, null, testing).
2024-04-23 16:22:47.814 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT);
2024-04-23 16:22:47.822 UTC client backend[8893] pg_regress/insert ERROR:  INSERT has more target columns than expressions at character 37
2024-04-23 16:22:47.822 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT);
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert ERROR:  INSERT has more target columns than expressions at character 37
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (1, 2);
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert ERROR:  INSERT has more expressions than target columns at character 42
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (col1) values (1, 2);
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert ERROR:  INSERT has more expressions than target columns at character 48
2024-04-23 16:22:47.823 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (col1) values (DEFAULT, DEFAULT);
2024-04-23 16:22:47.840 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:47.840 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing;
2024-04-23 16:22:47.841 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:47.841 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing;
2024-04-23 16:22:47.842 UTC client backend[8895] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2024-04-23 16:22:47.842 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2024-04-23 16:22:47.844 UTC client backend[8895] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2024-04-23 16:22:47.844 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'g') to stdout;
2024-04-23 16:22:47.844 UTC client backend[8891] pg_regress/copyselect ERROR:  cannot copy from view "v_test1"
2024-04-23 16:22:47.844 UTC client backend[8891] pg_regress/copyselect HINT:  Try the COPY (SELECT ...) TO variant.
2024-04-23 16:22:47.844 UTC client backend[8891] pg_regress/copyselect STATEMENT:  copy v_test1 to stdout;
2024-04-23 16:22:47.844 UTC client backend[8895] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2024-04-23 16:22:47.844 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2024-04-23 16:22:47.846 UTC client backend[8895] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2024-04-23 16:22:47.846 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect ERROR:  COPY (SELECT INTO) is not supported
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect STATEMENT:  copy (select t into temp test3 from test1 where id=3) to stdout;
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect ERROR:  syntax error at or near "from" at character 28
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect STATEMENT:  copy (select * from test1) from stdin;
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect ERROR:  syntax error at or near "(" at character 28
2024-04-23 16:22:47.847 UTC client backend[8891] pg_regress/copyselect STATEMENT:  copy (select * from test1) (t,id) to stdout;
2024-04-23 16:22:47.848 UTC client backend[8891] pg_regress/copyselect ERROR:  cannot copy from view "v_test1"
2024-04-23 16:22:47.848 UTC client backend[8891] pg_regress/copyselect HINT:  Try the COPY (SELECT ...) TO variant.
2024-04-23 16:22:47.848 UTC client backend[8891] pg_regress/copyselect STATEMENT:  COPY  v_test1 TO STDOUT 
2024-04-23 16:22:47.855 UTC client backend[8895] pg_regress/copydml ERROR:  DO ALSO rules are not supported for the COPY
2024-04-23 16:22:47.855 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2024-04-23 16:22:47.863 UTC client backend[8895] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:47.863 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2024-04-23 16:22:47.866 UTC client backend[8891] pg_regress/copyselect ERROR:  division by zero
2024-04-23 16:22:47.866 UTC client backend[8891] pg_regress/copyselect STATEMENT:  copy (select 1) to stdout; select 1/0;
2024-04-23 16:22:47.866 UTC client backend[8891] pg_regress/copyselect ERROR:  division by zero
2024-04-23 16:22:47.866 UTC client backend[8891] pg_regress/copyselect STATEMENT:  select 1/0; copy (select 1) to stdout;
2024-04-23 16:22:48.081 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.081 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (lower(fruit) text_pattern_ops, upper(fruit) collate "C") do nothing;
2024-04-23 16:22:48.100 UTC client backend[8895] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:48.100 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2024-04-23 16:22:48.111 UTC client backend[8895] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2024-04-23 16:22:48.111 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2024-04-23 16:22:48.111 UTC client backend[8895] pg_regress/copydml ERROR:  DO ALSO rules are not supported for the COPY
2024-04-23 16:22:48.111 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2024-04-23 16:22:48.111 UTC client backend[8893] pg_regress/insert ERROR:  cannot set an array element to DEFAULT at character 32
2024-04-23 16:22:48.111 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (f2[1], f2[2]) values (1,default);
2024-04-23 16:22:48.112 UTC client backend[8895] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:48.112 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2024-04-23 16:22:48.243 UTC client backend[8895] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:48.243 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2024-04-23 16:22:48.243 UTC client backend[8893] pg_regress/insert ERROR:  cannot set a subfield to DEFAULT at character 33
2024-04-23 16:22:48.243 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttest (f3.if1, f3.if2) values (1,default);
2024-04-23 16:22:48.244 UTC client backend[8895] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2024-04-23 16:22:48.244 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2024-04-23 16:22:48.245 UTC client backend[8897] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52
2024-04-23 16:22:48.245 UTC client backend[8897] pg_regress/insert_conflict HINT:  For example, ON CONFLICT (column_name).
2024-04-23 16:22:48.245 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit;
2024-04-23 16:22:48.245 UTC client backend[8895] pg_regress/copydml ERROR:  DO ALSO rules are not supported for the COPY
2024-04-23 16:22:48.245 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2024-04-23 16:22:48.317 UTC client backend[8895] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:48.317 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict ERROR:  invalid reference to FROM-clause entry for table "excluded" at character 117
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict DETAIL:  There is an entry for table "excluded", but it cannot be referenced from this part of the query.
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit;
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict ERROR:  column "keyy" does not exist at character 64
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key".
2024-04-23 16:22:48.317 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.318 UTC client backend[8895] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2024-04-23 16:22:48.318 UTC client backend[8895] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2024-04-23 16:22:48.319 UTC client backend[8897] pg_regress/insert_conflict ERROR:  column excluded.fruitt does not exist at character 92
2024-04-23 16:22:48.319 UTC client backend[8897] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the column "excluded.fruit".
2024-04-23 16:22:48.319 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt;
2024-04-23 16:22:48.321 UTC client backend[8889] pg_regress/copy ERROR:  cannot perform COPY FREEZE on a partitioned table
2024-04-23 16:22:48.321 UTC client backend[8889] pg_regress/copy STATEMENT:  copy parted_copytest from '/Users/admin/pgsql/build/testrun/regress/regress/results/parted_copytest.csv' (freeze);
2024-04-23 16:22:48.322 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.322 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.324 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.324 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.325 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.325 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.325 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.325 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict ERROR:  invalid reference to FROM-clause entry for table "insertconflicttest" at character 106
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the table alias "ict".
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit;
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict ERROR:  column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict HINT:  SET target columns cannot be qualified with the relation name.
2024-04-23 16:22:48.367 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango';
2024-04-23 16:22:48.393 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.393 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.394 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.394 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.394 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.394 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.395 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.395 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.415 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.430 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.430 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.430 UTC client backend[8893] pg_regress/insert ERROR:  cannot set an array element to DEFAULT at character 33
2024-04-23 16:22:48.430 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (1,default);
2024-04-23 16:22:48.430 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.430 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (0,2);
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6);
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2024-04-23 16:22:48.431 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) select 0,8;
2024-04-23 16:22:48.690 UTC client backend[8893] pg_regress/insert ERROR:  cannot set a subfield to DEFAULT at character 34
2024-04-23 16:22:48.690 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,default);
2024-04-23 16:22:48.691 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2024-04-23 16:22:48.691 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,array[null]);
2024-04-23 16:22:48.692 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2024-04-23 16:22:48.692 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}');
2024-04-23 16:22:48.693 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2024-04-23 16:22:48.693 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}';
2024-04-23 16:22:48.693 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.693 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.694 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.694 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.694 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.694 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.711 UTC client backend[8897] pg_regress/insert_conflict ERROR:  duplicate key value violates unique constraint "fruit_index"
2024-04-23 16:22:48.711 UTC client backend[8897] pg_regress/insert_conflict DETAIL:  Key (fruit)=(Peach) already exists.
2024-04-23 16:22:48.711 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit;
2024-04-23 16:22:48.728 UTC client backend[8889] pg_regress/copy ERROR:  cannot use "match" with HEADER in COPY TO
2024-04-23 16:22:48.728 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest to stdout with (header match);
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing;
2024-04-23 16:22:48.728 UTC client backend[8889] pg_regress/copy ERROR:  header requires a Boolean value or "match"
2024-04-23 16:22:48.728 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header wrong_choice);
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:48.728 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) where fruit like '%berry' do update set fruit = excluded.fruit;
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy ERROR:  column name mismatch in header line field 1: got "a", expected "c"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	c"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest (c, b, a) from stdin with (header match);
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy ERROR:  column name mismatch in header line field 3: got null value ("\N"), expected "c"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	\N"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy ERROR:  wrong number of fields in header line: got 2, expected 3
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy ERROR:  wrong number of fields in header line: got 4, expected 3
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	c	d"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy ERROR:  column name mismatch in header line field 3: got "d", expected "c"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	d"
2024-04-23 16:22:49.834 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy ERROR:  wrong number of fields in header line: got 3, expected 2
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	........pg.dropped.2........	c"
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy ERROR:  wrong number of fields in header line: got 3, expected 2
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	c	b"
2024-04-23 16:22:49.842 UTC client backend[8889] pg_regress/copy STATEMENT:  copy header_copytest (a, c) from stdin with (header match);
2024-04-23 16:22:49.856 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_nnarray violates check constraint "insert_nnarray_check"
2024-04-23 16:22:49.856 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttesta (f1[1]) values (1);
2024-04-23 16:22:49.863 UTC client backend[8897] pg_regress/insert_conflict ERROR:  column excluded.ctid does not exist at character 82
2024-04-23 16:22:49.863 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text;
2024-04-23 16:22:49.863 UTC client backend[8889] pg_regress/copy ERROR:  value too long for type character varying(5)
2024-04-23 16:22:49.863 UTC client backend[8889] pg_regress/copy STATEMENT:  copy oversized_column_default (col2) from stdin;
2024-04-23 16:22:49.864 UTC client backend[8889] pg_regress/copy ERROR:  value too long for type character varying(5)
2024-04-23 16:22:49.864 UTC client backend[8889] pg_regress/copy STATEMENT:  copy oversized_column_default from stdin (default '');
2024-04-23 16:22:49.864 UTC client backend[8893] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2024-04-23 16:22:49.864 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into inserttestb (f1.if1) values (1);
2024-04-23 16:22:49.880 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2024-04-23 16:22:49.880 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 11).
2024-04-23 16:22:49.880 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 11);
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (a, 11).
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part1 values ('a', 11);
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (b, 1).
2024-04-23 16:22:49.907 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part1 values ('b', 1);
2024-04-23 16:22:49.912 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part4" violates partition constraint
2024-04-23 16:22:49.912 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (b, 21).
2024-04-23 16:22:49.912 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part4 values ('b', 21);
2024-04-23 16:22:49.913 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part4" violates partition constraint
2024-04-23 16:22:49.913 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (a, 10).
2024-04-23 16:22:49.913 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part4 values ('a', 10);
2024-04-23 16:22:49.920 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2024-04-23 16:22:49.920 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (null, null).
2024-04-23 16:22:49.920 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part1 values (null);
2024-04-23 16:22:49.922 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2024-04-23 16:22:49.922 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (1, null).
2024-04-23 16:22:49.922 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part1 values (1);
2024-04-23 16:22:49.935 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2024-04-23 16:22:49.935 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (cc, 1).
2024-04-23 16:22:49.935 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_aa_bb values ('cc', 1);
2024-04-23 16:22:49.936 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2024-04-23 16:22:49.936 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (AAa, 1).
2024-04-23 16:22:49.936 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_aa_bb values ('AAa', 1);
2024-04-23 16:22:49.937 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2024-04-23 16:22:49.937 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (null, null).
2024-04-23 16:22:49.937 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_aa_bb values (null);
2024-04-23 16:22:49.949 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_default" violates partition constraint
2024-04-23 16:22:49.949 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (aa, 2).
2024-04-23 16:22:49.949 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_default values ('aa', 2);
2024-04-23 16:22:49.950 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_default" violates partition constraint
2024-04-23 16:22:49.950 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (null, 2).
2024-04-23 16:22:49.950 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_default values (null, 2);
2024-04-23 16:22:49.955 UTC client backend[8897] pg_regress/insert_conflict ERROR:  table reference "excluded" is ambiguous at character 76
2024-04-23 16:22:49.955 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *;
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_ee_ff1" violates partition constraint
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (EE, 11).
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_ee_ff1 values ('EE', 11);
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_default_p2" violates partition constraint
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (gg, 43).
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_default_p2 values ('gg', 43);
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_ee_ff1" violates partition constraint
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (cc, 1).
2024-04-23 16:22:49.983 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_ee_ff1 values ('cc', 1);
2024-04-23 16:22:49.984 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "part_default" found for row
2024-04-23 16:22:49.984 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (43).
2024-04-23 16:22:49.984 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_default values ('gg', 43);
2024-04-23 16:22:49.999 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2024-04-23 16:22:49.999 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 0).
2024-04-23 16:22:49.999 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 0);
2024-04-23 16:22:50.012 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2024-04-23 16:22:50.012 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 20).
2024-04-23 16:22:50.012 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 20);
2024-04-23 16:22:50.013 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2024-04-23 16:22:50.013 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, null).
2024-04-23 16:22:50.013 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into range_parted values ('a');
2024-04-23 16:22:50.014 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "part_def" violates partition constraint
2024-04-23 16:22:50.014 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (b, 10).
2024-04-23 16:22:50.014 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_def values ('b', 10);
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "part_ee_ff" found for row
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (0).
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into list_parted values ('EE', 0);
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "part_ee_ff" found for row
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (0).
2024-04-23 16:22:50.015 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into part_ee_ff values ('EE', 0);
2024-04-23 16:22:50.025 UTC client backend[8897] pg_regress/insert_conflict ERROR:  duplicate key value violates unique constraint "twoconstraints_f1_key"
2024-04-23 16:22:50.025 UTC client backend[8897] pg_regress/insert_conflict DETAIL:  Key (f1)=(1) already exists.
2024-04-23 16:22:50.025 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(1, '((2,2),(3,3))');
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict ERROR:  conflicting key value violates exclusion constraint "twoconstraints_f2_excl"
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict DETAIL:  Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)).
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(2, '((0,0),(1,2))');
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict ERROR:  conflicting key value violates exclusion constraint "twoconstraints_f2_excl"
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict DETAIL:  Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)).
2024-04-23 16:22:50.026 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(2, '((0,0),(1,2))')
	  on conflict on constraint twoconstraints_f1_key do nothing;
2024-04-23 16:22:50.059 UTC client backend[8897] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2024-04-23 16:22:50.059 UTC client backend[8897] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2024-04-23 16:22:50.059 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0;
2024-04-23 16:22:50.062 UTC client backend[8897] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2024-04-23 16:22:50.062 UTC client backend[8897] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2024-04-23 16:22:50.062 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0;
2024-04-23 16:22:50.063 UTC client backend[8897] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2024-04-23 16:22:50.063 UTC client backend[8897] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2024-04-23 16:22:50.063 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0;
2024-04-23 16:22:50.080 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:50.080 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a;
2024-04-23 16:22:50.131 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "hpart0" violates partition constraint
2024-04-23 16:22:50.131 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (11).
2024-04-23 16:22:50.131 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into hpart0 values(11);
2024-04-23 16:22:50.301 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted1" found for row
2024-04-23 16:22:50.301 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains ((b + 0)) = (5).
2024-04-23 16:22:50.301 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted (a, b) values (1, 5);
2024-04-23 16:22:50.304 UTC client backend[8897] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2024-04-23 16:22:50.304 UTC client backend[8897] pg_regress/insert_conflict STATEMENT:  insert into parted_conflict_1 values (40, 'cuarenta')
	  on conflict (a) do update set b = excluded.b;
2024-04-23 16:22:50.339 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted11" violates check constraint "check_b"
2024-04-23 16:22:50.339 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (1, 4).
2024-04-23 16:22:50.339 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 2);
2024-04-23 16:22:50.403 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted1" violates partition constraint
2024-04-23 16:22:50.403 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (3, 2).
2024-04-23 16:22:50.403 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted1 (a, b) values (2, 3);
2024-04-23 16:22:50.589 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "lparted_nonullpart" found for row
2024-04-23 16:22:50.589 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (null).
2024-04-23 16:22:50.589 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into lparted_nonullpart values (1);
2024-04-23 16:22:50.713 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted5a" violates check constraint "check_b"
2024-04-23 16:22:50.713 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (1, 45, a).
2024-04-23 16:22:50.713 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'a');
2024-04-23 16:22:50.714 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted5a" violates partition constraint
2024-04-23 16:22:50.714 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (b, 1, 40).
2024-04-23 16:22:50.714 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted5 (a, b, c) values (1, 40, 'a');
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted_def" found for row
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a) = (70).
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (70, 100);
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted_def1" violates partition constraint
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (52, 50, null).
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted_def1 values (52, 50);
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mlparted_def2" violates partition constraint
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (34, 50, null).
2024-04-23 16:22:50.720 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted_def2 values (34, 50);
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted5_cd" found for row
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (c).
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'c', 1);
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted5" found for row
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (f).
2024-04-23 16:22:50.740 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'f', 1);
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted5_cd" found for row
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (c).
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'c', 1);
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mlparted5" found for row
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (f).
2024-04-23 16:22:50.761 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'f', 1);
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "key_desc_1" found for row
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into key_desc values (1, 1);
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "key_desc_1" found for row
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (1).
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into key_desc values (1, 1);
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "key_desc" found for row
2024-04-23 16:22:50.815 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into key_desc values (2, 1);
2024-04-23 16:22:50.823 UTC client backend[8893] pg_regress/insert ERROR:  every bound following MINVALUE must also be MINVALUE at character 75
2024-04-23 16:22:50.823 UTC client backend[8893] pg_regress/insert STATEMENT:  create table mcrparted0 partition of mcrparted for values from (minvalue, 0, 0) to (1, maxvalue, maxvalue);
2024-04-23 16:22:50.823 UTC client backend[8893] pg_regress/insert ERROR:  every bound following MAXVALUE must also be MAXVALUE at character 100
2024-04-23 16:22:50.823 UTC client backend[8893] pg_regress/insert STATEMENT:  create table mcrparted2 partition of mcrparted for values from (10, 6, minvalue) to (10, maxvalue, minvalue);
2024-04-23 16:22:50.824 UTC client backend[8893] pg_regress/insert ERROR:  every bound following MINVALUE must also be MINVALUE at character 79
2024-04-23 16:22:50.824 UTC client backend[8893] pg_regress/insert STATEMENT:  create table mcrparted4 partition of mcrparted for values from (21, minvalue, 0) to (30, 20, minvalue);
2024-04-23 16:22:50.859 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mcrparted" found for row
2024-04-23 16:22:50.859 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, abs(b), c) = (null, null, null).
2024-04-23 16:22:50.859 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mcrparted values (null, null, null);
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert ERROR:  no partition of relation "mcrparted" found for row
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, abs(b), c) = (11, 1, -1).
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mcrparted values (11, 1, -1);
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mcrparted3" violates partition constraint
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (11, 1, -1).
2024-04-23 16:22:50.865 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mcrparted3 values (11, 1, -1);
2024-04-23 16:22:50.867 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "mcrparted4" violates partition constraint
2024-04-23 16:22:50.867 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (30, 21, 20).
2024-04-23 16:22:50.867 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into mcrparted4 values (30, 21, 20);
2024-04-23 16:22:50.886 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2024-04-23 16:22:50.886 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (2, hi there).
2024-04-23 16:22:50.886 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into brtrigpartcon values (1, 'hi there');
2024-04-23 16:22:50.887 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2024-04-23 16:22:50.887 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (2, hi there).
2024-04-23 16:22:50.887 UTC client backend[8893] pg_regress/insert STATEMENT:  insert into brtrigpartcon1 values (1, 'hi there');
2024-04-23 16:22:50.893 UTC client backend[8893] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2024-04-23 16:22:50.893 UTC client backend[8893] pg_regress/insert DETAIL:  Failing row contains (a, b) = (2, hi there).
2024-04-23 16:22:50.893 UTC client backend[8893] pg_regress/insert STATEMENT:  with result as (insert into brtrigpartcon values (1, 'hi there') returning 1)
	  insert into inserttest3 (f3) select * from result;
2024-04-23 16:22:54.489 UTC client backend[9176] pg_regress/create_function_c ERROR:  could not access file "nosuchfile": No such file or directory
2024-04-23 16:22:54.489 UTC client backend[9176] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C
	    AS 'nosuchfile';
2024-04-23 16:22:54.489 UTC client backend[9176] pg_regress/create_function_c ERROR:  could not find function "nosuchsymbol" in file "/Users/admin/pgsql/build/src/test/regress/regress.dylib"
2024-04-23 16:22:54.489 UTC client backend[9176] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C
	    AS '/Users/admin/pgsql/build/src/test/regress/regress.dylib', 'nosuchsymbol';
2024-04-23 16:22:54.490 UTC client backend[9176] pg_regress/create_function_c ERROR:  there is no built-in function named "nosuch"
2024-04-23 16:22:54.490 UTC client backend[9176] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE internal
	    AS 'nosuch';
2024-04-23 16:22:54.491 UTC client backend[9177] pg_regress/create_operator ERROR:  operator right argument type must be specified
2024-04-23 16:22:54.491 UTC client backend[9177] pg_regress/create_operator DETAIL:  Postfix operators are not supported.
2024-04-23 16:22:54.491 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #%# (
	   leftarg = int8,		-- fail, postfix is no longer supported
	   procedure = factorial
	);
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist at character 6
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure HINT:  No procedure matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL nonexistent();
2024-04-23 16:22:54.492 UTC client backend[9177] pg_regress/create_operator ERROR:  operator does not exist: ###### integer
2024-04-23 16:22:54.492 UTC client backend[9177] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (NONE, int4) IS 'bad prefix';
2024-04-23 16:22:54.492 UTC client backend[9179] pg_regress/create_table ERROR:  column "u" has pseudo-type unknown
2024-04-23 16:22:54.492 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE unknowntab (
		u unknown    -- fail
	);
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure ERROR:  random() is not a procedure at character 6
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2024-04-23 16:22:54.492 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL random();
2024-04-23 16:22:54.493 UTC client backend[9177] pg_regress/create_operator ERROR:  postfix operators are not supported
2024-04-23 16:22:54.493 UTC client backend[9177] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (int4, NONE) IS 'bad postfix';
2024-04-23 16:22:54.493 UTC client backend[9179] pg_regress/create_table ERROR:  column "u" has pseudo-type unknown
2024-04-23 16:22:54.493 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TYPE unknown_comptype AS (
		u unknown    -- fail
	);
2024-04-23 16:22:54.493 UTC client backend[9177] pg_regress/create_operator ERROR:  operator does not exist: integer ###### bigint
2024-04-23 16:22:54.493 UTC client backend[9177] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (int4, int8) IS 'bad infix';
2024-04-23 16:22:54.493 UTC client backend[9179] pg_regress/create_table ERROR:  unrecognized parameter "Fillfactor"
2024-04-23 16:22:54.493 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE tas_case WITH ("Fillfactor" = 10) AS SELECT 1 a;
2024-04-23 16:22:54.494 UTC client backend[9177] pg_regress/create_operator ERROR:  operator does not exist: ###### integer
2024-04-23 16:22:54.494 UTC client backend[9177] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (NONE, int4);
2024-04-23 16:22:54.494 UTC client backend[9177] pg_regress/create_operator ERROR:  postfix operators are not supported
2024-04-23 16:22:54.494 UTC client backend[9177] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (int4, NONE);
2024-04-23 16:22:54.495 UTC client backend[9177] pg_regress/create_operator ERROR:  operator does not exist: integer ###### bigint
2024-04-23 16:22:54.495 UTC client backend[9177] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (int4, int8);
2024-04-23 16:22:54.495 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.495 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE SEQUENCE schema_not_existing.seq;
2024-04-23 16:22:54.495 UTC client backend[9177] pg_regress/create_operator ERROR:  syntax error at or near "=>" at character 17
2024-04-23 16:22:54.495 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR => (
	   rightarg = int8,
	   procedure = factorial
	);
2024-04-23 16:22:54.495 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.495 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE TABLE schema_not_existing.tab (id int);
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE INDEX ON schema_not_existing.tab (id);
2024-04-23 16:22:54.496 UTC client backend[9177] pg_regress/create_operator ERROR:  syntax error at or near ";" at character 14
2024-04-23 16:22:54.496 UTC client backend[9177] pg_regress/create_operator STATEMENT:  SELECT 10 !=-;
2024-04-23 16:22:54.496 UTC client backend[9180] pg_regress/create_type ERROR:  type "shell" already exists
2024-04-23 16:22:54.496 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TYPE shell;
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.496 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab
	  EXECUTE FUNCTION schema_trig.no_func();
2024-04-23 16:22:54.497 UTC client backend[9180] pg_regress/create_type ERROR:  type "shell" does not exist
2024-04-23 16:22:54.497 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP TYPE shell;
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE SEQUENCE schema_not_existing.seq;
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE TABLE schema_not_existing.tab (id int);
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.497 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE INDEX ON schema_not_existing.tab (id);
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab
	  EXECUTE FUNCTION schema_trig.no_func();
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE SEQUENCE schema_not_existing.seq;
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE TABLE schema_not_existing.tab (id int);
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2024-04-23 16:22:54.498 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2024-04-23 16:22:54.499 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2024-04-23 16:22:54.499 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE INDEX ON schema_not_existing.tab (id);
2024-04-23 16:22:54.499 UTC client backend[9181] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2024-04-23 16:22:54.499 UTC client backend[9181] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab
	  EXECUTE FUNCTION schema_trig.no_func();
2024-04-23 16:22:54.500 UTC client backend[9177] pg_regress/create_operator ERROR:  permission denied for schema schema_op1
2024-04-23 16:22:54.500 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR schema_op1.#*# (
	   rightarg = int8,
	   procedure = factorial
	);
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Internallength" not recognized at character 27
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Input" not recognized at character 50
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Output" not recognized at character 71
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Alignment" not recognized at character 94
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Default" not recognized at character 115
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type WARNING:  type attribute "Passedbyvalue" not recognized at character 132
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type ERROR:  type input function must be specified
2024-04-23 16:22:54.500 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (
		"Internallength" = 4,
		"Input" = int42_in,
		"Output" = int42_out,
		"Alignment" = int4,
		"Default" = 42,
		"Passedbyvalue"
	);
2024-04-23 16:22:54.501 UTC client backend[9180] pg_regress/create_type ERROR:  type input function array_in must return type bogus_type
2024-04-23 16:22:54.501 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (INPUT = array_in,
	    OUTPUT = array_out,
	    ELEMENT = int,
	    INTERNALLENGTH = 32);
2024-04-23 16:22:54.501 UTC client backend[9177] pg_regress/create_operator ERROR:  SETOF type not allowed for operator argument
2024-04-23 16:22:54.501 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = SETOF int8,
	   procedure = factorial
	);
2024-04-23 16:22:54.501 UTC client backend[9180] pg_regress/create_type ERROR:  type "bogus_type" does not exist
2024-04-23 16:22:54.501 UTC client backend[9180] pg_regress/create_type HINT:  Create the type as a shell type, then create its I/O functions, then do a full CREATE TYPE.
2024-04-23 16:22:54.501 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (INPUT = array_in,
	    OUTPUT = array_out,
	    ELEMENT = int,
	    INTERNALLENGTH = 32);
2024-04-23 16:22:54.501 UTC client backend[9177] pg_regress/create_operator ERROR:  SETOF type not allowed for operator argument
2024-04-23 16:22:54.501 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   rightarg = SETOF int8,
	   procedure = factorial
	);
2024-04-23 16:22:54.501 UTC client backend[9178] pg_regress/create_procedure ERROR:  ptest1(unknown) is a procedure at character 8
2024-04-23 16:22:54.501 UTC client backend[9178] pg_regress/create_procedure HINT:  To call a procedure, use CALL.
2024-04-23 16:22:54.501 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  SELECT ptest1('x');
2024-04-23 16:22:54.502 UTC client backend[9180] pg_regress/create_type ERROR:  type "bad" does not exist
2024-04-23 16:22:54.502 UTC client backend[9180] pg_regress/create_type STATEMENT:  COMMENT ON TYPE bad IS 'bad comment';
2024-04-23 16:22:54.502 UTC client backend[9180] pg_regress/create_type ERROR:  column "nope" of relation "default_test_row" does not exist
2024-04-23 16:22:54.502 UTC client backend[9180] pg_regress/create_type STATEMENT:  COMMENT ON COLUMN default_test_row.nope IS 'bad comment';
2024-04-23 16:22:54.502 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "invalid_att" not recognized
2024-04-23 16:22:54.503 UTC client backend[9177] pg_regress/create_operator ERROR:  operator argument types must be specified
2024-04-23 16:22:54.503 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #@%# (
	   procedure = factorial
	);
2024-04-23 16:22:54.503 UTC client backend[9180] pg_regress/create_type ERROR:  type "text_w_default" already exists
2024-04-23 16:22:54.503 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TYPE text_w_default;
2024-04-23 16:22:54.503 UTC client backend[9177] pg_regress/create_operator ERROR:  operator function must be specified
2024-04-23 16:22:54.503 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #@%# (
	   rightarg = int8
	);
2024-04-23 16:22:54.503 UTC client backend[9178] pg_regress/create_procedure ERROR:  CREATE TABLE is not yet supported in unquoted SQL function body
2024-04-23 16:22:54.503 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx()
	LANGUAGE SQL
	BEGIN ATOMIC
	  CREATE TABLE x (a int);
	END;
2024-04-23 16:22:54.504 UTC client backend[9177] pg_regress/create_operator ERROR:  permission denied for type type_op3
2024-04-23 16:22:54.504 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = type_op3,
	   rightarg = int8,
	   procedure = fn_op3
	);
2024-04-23 16:22:54.505 UTC client backend[9177] pg_regress/create_operator ERROR:  permission denied for type type_op4
2024-04-23 16:22:54.505 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = type_op4,
	   procedure = fn_op4
	);
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator ERROR:  permission denied for function fn_op5
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = int8,
	   procedure = fn_op5
	);
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator ERROR:  permission denied for type type_op6
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = int8,
	   procedure = fn_op6
	);
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator ERROR:  operator cannot be its own negator
2024-04-23 16:22:54.506 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    negator = ===
	);
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator ERROR:  operator cannot be its own negator
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR ===!!! (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4ne,
	    negator = ===!!!
	);
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator ERROR:  commutator operator = is already the commutator of operator =
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    commutator = =
	);
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator ERROR:  negator operator <> is already the negator of operator =
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    negator = <>
	);
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Leftarg" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Rightarg" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Procedure" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Commutator" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Negator" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Restrict" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Join" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Hashes" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator WARNING:  operator attribute "Merges" not recognized
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator ERROR:  operator function must be specified
2024-04-23 16:22:54.507 UTC client backend[9177] pg_regress/create_operator STATEMENT:  CREATE OPERATOR ===
	(
		"Leftarg" = box,
		"Rightarg" = box,
		"Procedure" = area_equal_function,
		"Commutator" = ===,
		"Negator" = !==,
		"Restrict" = area_restriction_function,
		"Join" = area_join_function,
		"Hashes",
		"Merges"
	);
2024-04-23 16:22:54.885 UTC client backend[9180] pg_regress/create_type ERROR:  cannot drop function base_fn_in(cstring) because other objects depend on it
2024-04-23 16:22:54.885 UTC client backend[9180] pg_regress/create_type DETAIL:  type base_type depends on function base_fn_in(cstring)
	function base_fn_out(base_type) depends on type base_type
2024-04-23 16:22:54.885 UTC client backend[9180] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:54.885 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP FUNCTION base_fn_in(cstring);
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type ERROR:  cannot drop function base_fn_out(base_type) because other objects depend on it
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type DETAIL:  type base_type depends on function base_fn_out(base_type)
	function base_fn_in(cstring) depends on type base_type
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP FUNCTION base_fn_out(base_type);
2024-04-23 16:22:54.886 UTC client backend[9178] pg_regress/create_procedure ERROR:  calling procedures with output arguments is not supported in SQL functions
2024-04-23 16:22:54.886 UTC client backend[9178] pg_regress/create_procedure CONTEXT:  SQL function "ptest4b"
2024-04-23 16:22:54.886 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptest4b(INOUT b int, INOUT a int)
	LANGUAGE SQL
	AS $$
	CALL ptest4a(a, b);  -- error, not supported
	$$;
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type ERROR:  cannot drop type base_type because other objects depend on it
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type DETAIL:  function base_fn_in(cstring) depends on type base_type
	function base_fn_out(base_type) depends on type base_type
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:54.886 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP TYPE base_type;
2024-04-23 16:22:54.887 UTC client backend[9180] pg_regress/create_type ERROR:  invalid NUMERIC type modifier at character 30
2024-04-23 16:22:54.887 UTC client backend[9180] pg_regress/create_type STATEMENT:  CREATE TEMP TABLE mytab (foo widget(42,13,7));
2024-04-23 16:22:54.900 UTC client backend[9179] pg_regress/create_table ERROR:  only temporary relations may be created in temporary schemas at character 23
2024-04-23 16:22:54.900 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE UNLOGGED TABLE pg_temp.unlogged3 (a int primary key);
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('(1,2)', 'widget');
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('{"(1,2)"}', 'widget[]');
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2024-04-23 16:22:54.900 UTC client backend[9180] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('("(1,2)")', 'mytab');
2024-04-23 16:22:54.901 UTC client backend[9179] pg_regress/create_table ERROR:  cannot create temporary relation in non-temporary schema at character 19
2024-04-23 16:22:54.901 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TEMP TABLE public.temp_to_perm (a int primary key);
2024-04-23 16:22:54.902 UTC client backend[9180] pg_regress/create_type ERROR:  type "myvarchar" is only a shell
2024-04-23 16:22:54.902 UTC client backend[9180] pg_regress/create_type STATEMENT:  ALTER TYPE myvarchar SET (storage = extended);
2024-04-23 16:22:54.902 UTC client backend[9180] pg_regress/create_type ERROR:  cannot change type's storage to PLAIN
2024-04-23 16:22:54.902 UTC client backend[9180] pg_regress/create_type STATEMENT:  ALTER TYPE myvarchar SET (storage = plain);
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type ERROR:  cannot drop function myvarcharsend(myvarchar) because other objects depend on it
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type DETAIL:  type myvarchar depends on function myvarcharsend(myvarchar)
	function myvarcharin(cstring,oid,integer) depends on type myvarchar
	function myvarcharout(myvarchar) depends on type myvarchar
	function myvarcharrecv(internal,oid,integer) depends on type myvarchar
	type myvarchardom depends on function myvarcharsend(myvarchar)
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP FUNCTION myvarcharsend(myvarchar);
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type ERROR:  cannot drop type myvarchar because other objects depend on it
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type DETAIL:  function myvarcharin(cstring,oid,integer) depends on type myvarchar
	function myvarcharout(myvarchar) depends on type myvarchar
	function myvarcharsend(myvarchar) depends on type myvarchar
	function myvarcharrecv(internal,oid,integer) depends on type myvarchar
	type myvarchardom depends on type myvarchar
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:54.904 UTC client backend[9180] pg_regress/create_type STATEMENT:  DROP TYPE myvarchar;
2024-04-23 16:22:55.143 UTC client backend[9179] pg_regress/create_table ERROR:  relation "as_select1" already exists
2024-04-23 16:22:55.143 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relkind = 'r';
2024-04-23 16:22:55.469 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure ptest9(numeric) does not exist at character 6
2024-04-23 16:22:55.469 UTC client backend[9178] pg_regress/create_procedure HINT:  No procedure matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:55.469 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL ptest9(1./0.);
2024-04-23 16:22:55.507 UTC client backend[9179] pg_regress/create_table ERROR:  relation "as_select1" already exists
2024-04-23 16:22:55.507 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE as_select1 AS EXECUTE select1;
2024-04-23 16:22:55.511 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure name "ptest10" is not unique
2024-04-23 16:22:55.511 UTC client backend[9178] pg_regress/create_procedure HINT:  Specify the argument list to select the procedure unambiguously.
2024-04-23 16:22:55.511 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  drop procedure ptest10;
2024-04-23 16:22:55.511 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure name "ptest10" is not unique
2024-04-23 16:22:55.511 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  drop procedure ptest10(int, int, int);
2024-04-23 16:22:55.514 UTC client backend[9178] pg_regress/create_procedure ERROR:  version() is not a procedure at character 6
2024-04-23 16:22:55.514 UTC client backend[9178] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2024-04-23 16:22:55.514 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL version();
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure ERROR:  sum(integer) is not a procedure at character 6
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL sum(1);
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 40
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx() LANGUAGE SQL WINDOW AS $$ INSERT INTO cp_test VALUES (1, 'a') $$;
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 40
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx() LANGUAGE SQL STRICT AS $$ INSERT INTO cp_test VALUES (1, 'a') $$;
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure ERROR:  VARIADIC parameter must be the last parameter
2024-04-23 16:22:55.516 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx(a VARIADIC int[], b OUT int) LANGUAGE SQL
	  AS $$ SELECT a[1] $$;
2024-04-23 16:22:55.517 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure OUT parameters cannot appear after one with a default value
2024-04-23 16:22:55.517 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx(a int DEFAULT 42, b OUT int) LANGUAGE SQL
	  AS $$ SELECT a $$;
2024-04-23 16:22:55.517 UTC client backend[9178] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 30
2024-04-23 16:22:55.517 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE ptest1(text) STRICT;
2024-04-23 16:22:55.518 UTC client backend[9178] pg_regress/create_procedure ERROR:  ptest1(text) is not a function
2024-04-23 16:22:55.518 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  ALTER FUNCTION ptest1(text) VOLATILE;
2024-04-23 16:22:55.519 UTC client backend[9178] pg_regress/create_procedure ERROR:  cp_testfunc1(integer) is not a procedure
2024-04-23 16:22:55.519 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE cp_testfunc1(int) VOLATILE;
2024-04-23 16:22:55.519 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist
2024-04-23 16:22:55.519 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE nonexistent() VOLATILE;
2024-04-23 16:22:55.520 UTC client backend[9178] pg_regress/create_procedure ERROR:  ptest1(text) is not a function
2024-04-23 16:22:55.520 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  DROP FUNCTION ptest1(text);
2024-04-23 16:22:55.521 UTC client backend[9178] pg_regress/create_procedure ERROR:  cp_testfunc1(integer) is not a procedure
2024-04-23 16:22:55.521 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  DROP PROCEDURE cp_testfunc1(int);
2024-04-23 16:22:55.522 UTC client backend[9178] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist
2024-04-23 16:22:55.522 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  DROP PROCEDURE nonexistent();
2024-04-23 16:22:55.525 UTC client backend[9178] pg_regress/create_procedure ERROR:  permission denied for procedure ptest1
2024-04-23 16:22:55.525 UTC client backend[9178] pg_regress/create_procedure STATEMENT:  CALL ptest1('a');
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table ERROR:  syntax error at or near "OIDS" at character 29
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH OIDS;
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table ERROR:  tables declared WITH OIDS are not supported
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH (oids);
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table ERROR:  tables declared WITH OIDS are not supported
2024-04-23 16:22:55.568 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH (oids = true);
2024-04-23 16:22:55.569 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 51
2024-04-23 16:22:55.569 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_column (id int DEFAULT (id));
2024-04-23 16:22:55.570 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 51
2024-04-23 16:22:55.570 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_column (id int DEFAULT (bar.id));
2024-04-23 16:22:55.571 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 59
2024-04-23 16:22:55.571 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg_column (id int DEFAULT (avg(id)));
2024-04-23 16:22:55.571 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 58
2024-04-23 16:22:55.571 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_non_column (a int DEFAULT (avg(non_existent)));
2024-04-23 16:22:55.572 UTC client backend[9179] pg_regress/create_table ERROR:  aggregate functions are not allowed in DEFAULT expressions at character 47
2024-04-23 16:22:55.572 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (avg(1)));
2024-04-23 16:22:55.573 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use subquery in DEFAULT expression at character 46
2024-04-23 16:22:55.573 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (select 1));
2024-04-23 16:22:55.574 UTC client backend[9179] pg_regress/create_table ERROR:  set-returning functions are not allowed in DEFAULT expressions at character 47
2024-04-23 16:22:55.574 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (generate_series(1,3)));
2024-04-23 16:22:55.578 UTC client backend[9179] pg_regress/create_table ERROR:  cannot create partitioned table as inheritance child
2024-04-23 16:22:55.578 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) INHERITS (some_table) PARTITION BY LIST (a);
2024-04-23 16:22:55.578 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use "list" partition strategy with more than one column
2024-04-23 16:22:55.578 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a1 int,
		a2 int
	) PARTITION BY LIST (a1, a2);
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition key expressions
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (retset(a));
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition key expressions
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE ((avg(a)));
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table ERROR:  window functions are not allowed in partition key expressions
2024-04-23 16:22:55.579 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE ((avg(a) OVER (PARTITION BY b)));
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use subquery in partition key expression
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY LIST ((a LIKE (SELECT 1)));
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use constant expression as partition key
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE ((42));
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use constant expression as partition key
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (const_func());
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  unrecognized partitioning strategy "magic"
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
	    a int
	) PARTITION BY MAGIC (a);
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  column "b" named in partition key does not exist at character 57
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (b);
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use system column "xmin" in partition key at character 57
2024-04-23 16:22:55.580 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (xmin);
2024-04-23 16:22:55.581 UTC client backend[9179] pg_regress/create_table ERROR:  partition key column 1 has pseudo-type record
2024-04-23 16:22:55.581 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE (((a, b)));
2024-04-23 16:22:55.581 UTC client backend[9179] pg_regress/create_table ERROR:  partition key column 2 has pseudo-type unknown
2024-04-23 16:22:55.581 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE (a, ('unknown'));
2024-04-23 16:22:55.582 UTC client backend[9179] pg_regress/create_table ERROR:  functions in partition key expression must be marked IMMUTABLE
2024-04-23 16:22:55.582 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (immut_func(a));
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table ERROR:  data type point has no default operator class for access method "btree"
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table HINT:  You must specify a btree operator class or define a default btree operator class for the data type.
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY LIST (a);
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table ERROR:  operator class "point_ops" does not exist for access method "btree"
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY LIST (a point_ops);
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table ERROR:  data type point has no default operator class for access method "btree"
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table HINT:  You must specify a btree operator class or define a default btree operator class for the data type.
2024-04-23 16:22:55.583 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY RANGE (a);
2024-04-23 16:22:55.584 UTC client backend[9179] pg_regress/create_table ERROR:  operator class "point_ops" does not exist for access method "btree"
2024-04-23 16:22:55.584 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY RANGE (a point_ops);
2024-04-23 16:22:55.584 UTC client backend[9179] pg_regress/create_table ERROR:  cannot add NO INHERIT constraint to partitioned table "partitioned"
2024-04-23 16:22:55.584 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		CONSTRAINT check_a CHECK (a > 0) NO INHERIT
	) PARTITION BY RANGE (a);
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop function plusone(integer) because other objects depend on it
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table DETAIL:  table partitioned depends on function plusone(integer)
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table STATEMENT:  DROP FUNCTION plusone(int);
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table ERROR:  cannot inherit from partitioned table "partitioned2"
2024-04-23 16:22:55.586 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail () INHERITS (partitioned2);
2024-04-23 16:22:55.597 UTC client backend[9179] pg_regress/create_table ERROR:  no partition of relation "partitioned2" found for row
2024-04-23 16:22:55.597 UTC client backend[9179] pg_regress/create_table DETAIL:  Partition key of the failing row contains ((a + 1), substr(b, 1, 5)) = (2, hello).
2024-04-23 16:22:55.597 UTC client backend[9179] pg_regress/create_table STATEMENT:  INSERT INTO partitioned2 VALUES (1, 'hello');
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table STATEMENT:  alter table partitioned drop column a;
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop type intdom1 because other objects depend on it
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table DETAIL:  table partitioned depends on type intdom1
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:55.837 UTC client backend[9179] pg_regress/create_table STATEMENT:  drop domain intdom1;
2024-04-23 16:22:55.838 UTC client backend[9179] pg_regress/create_table ERROR:  relation "partitioned" does not exist at character 7
2024-04-23 16:22:55.838 UTC client backend[9179] pg_regress/create_table STATEMENT:  table partitioned;
2024-04-23 16:22:55.840 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2024-04-23 16:22:55.840 UTC client backend[9179] pg_regress/create_table STATEMENT:  alter table partitioned drop column a;
2024-04-23 16:22:55.841 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop type intdom1 because other objects depend on it
2024-04-23 16:22:55.841 UTC client backend[9179] pg_regress/create_table DETAIL:  table partitioned depends on type intdom1
2024-04-23 16:22:55.841 UTC client backend[9179] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:55.841 UTC client backend[9179] pg_regress/create_table STATEMENT:  drop domain intdom1;
2024-04-23 16:22:55.842 UTC client backend[9179] pg_regress/create_table ERROR:  relation "partitioned" does not exist at character 7
2024-04-23 16:22:55.842 UTC client backend[9179] pg_regress/create_table STATEMENT:  table partitioned;
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename);
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename.somename);
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2024-04-23 16:22:55.852 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (a);
2024-04-23 16:22:55.853 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 79
2024-04-23 16:22:55.853 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(a));
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 79
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(somename));
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition bound at character 75
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(1));
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use subquery in partition bound at character 75
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((select 1));
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition bound at character 75
2024-04-23 16:22:55.854 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (generate_series(4, 6));
2024-04-23 16:22:55.855 UTC client backend[9179] pg_regress/create_table ERROR:  collations are not supported by type integer at character 81
2024-04-23 16:22:55.855 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((1+1) collate "POSIX");
2024-04-23 16:22:55.855 UTC client backend[9179] pg_regress/create_table ERROR:  syntax error at or near ")" at character 64
2024-04-23 16:22:55.855 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES IN ();
2024-04-23 16:22:55.856 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a list partition at character 60
2024-04-23 16:22:55.856 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES FROM (1) TO (2);
2024-04-23 16:22:55.859 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a list partition at character 60
2024-04-23 16:22:55.859 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2024-04-23 16:22:55.861 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_default_part" conflicts with existing default partition "part_default" at character 57
2024-04-23 16:22:55.861 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF list_parted DEFAULT;
2024-04-23 16:22:55.863 UTC client backend[9179] pg_regress/create_table ERROR:  specified value cannot be cast to type boolean for column "a" at character 59
2024-04-23 16:22:55.863 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE bools_true PARTITION OF bools FOR VALUES IN (1);
2024-04-23 16:22:56.081 UTC client backend[9179] pg_regress/create_table ERROR:  partition "bigintp_10_2" would overlap partition "bigintp_10" at character 63
2024-04-23 16:22:56.081 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE bigintp_10_2 PARTITION OF bigintp FOR VALUES IN ('10');
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (somename) TO ('2019-01-01');
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (somename.somename) TO ('2019-01-01');
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2024-04-23 16:22:56.083 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (a) TO ('2019-01-01');
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 84
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (max(a)) TO ('2019-01-01');
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 84
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (max(somename)) TO ('2019-01-01');
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition bound at character 80
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (max('2019-02-01'::date)) TO ('2019-01-01');
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table ERROR:  cannot use subquery in partition bound at character 80
2024-04-23 16:22:56.084 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM ((select 1)) TO ('2019-01-01');
2024-04-23 16:22:56.085 UTC client backend[9179] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition bound at character 80
2024-04-23 16:22:56.085 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (generate_series(1, 3)) TO ('2019-01-01');
2024-04-23 16:22:56.097 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2024-04-23 16:22:56.097 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES IN ('a');
2024-04-23 16:22:56.097 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2024-04-23 16:22:56.097 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table ERROR:  FROM must specify exactly one value per partitioning column
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a', 1) TO ('z');
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table ERROR:  TO must specify exactly one value per partitioning column
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a') TO ('z', 1);
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table ERROR:  cannot specify NULL in range bound
2024-04-23 16:22:56.098 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM (null) TO (maxvalue);
2024-04-23 16:22:56.099 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2024-04-23 16:22:56.099 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table DETAIL:  The new modulus 25 is not divisible by 10, the modulus of existing partition "hpart_4".
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 25, REMAINDER 3);
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table DETAIL:  The new modulus 150 is not a factor of 200, the modulus of existing partition "hpart_3".
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 150, REMAINDER 3);
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "hpart_4" at character 60
2024-04-23 16:22:56.101 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 100, REMAINDER 3);
2024-04-23 16:22:56.102 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a hash partition at character 60
2024-04-23 16:22:56.102 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES FROM ('a', 1) TO ('z');
2024-04-23 16:22:56.102 UTC client backend[9179] pg_regress/create_table ERROR:  invalid bound specification for a hash partition at character 60
2024-04-23 16:22:56.102 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES IN (1000);
2024-04-23 16:22:56.103 UTC client backend[9179] pg_regress/create_table ERROR:  a hash-partitioned table may not have a default partition
2024-04-23 16:22:56.103 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF hash_parted DEFAULT;
2024-04-23 16:22:56.103 UTC client backend[9179] pg_regress/create_table ERROR:  "unparted" is not partitioned
2024-04-23 16:22:56.103 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF unparted FOR VALUES IN ('a');
2024-04-23 16:22:56.104 UTC client backend[9179] pg_regress/create_table ERROR:  "unparted" is not partitioned
2024-04-23 16:22:56.104 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF unparted FOR VALUES WITH (MODULUS 2, REMAINDER 1);
2024-04-23 16:22:56.104 UTC client backend[9179] pg_regress/create_table ERROR:  cannot create a permanent relation as partition of temporary relation "temp_parted"
2024-04-23 16:22:56.104 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF temp_parted FOR VALUES IN ('a');
2024-04-23 16:22:56.107 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part_null_z" at character 65
2024-04-23 16:22:56.107 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN (null);
2024-04-23 16:22:56.108 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part_ab" at character 65
2024-04-23 16:22:56.108 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('b', 'c');
2024-04-23 16:22:56.109 UTC client backend[9179] pg_regress/create_table ERROR:  updated partition constraint for default partition "list_parted2_def" would be violated by some row
2024-04-23 16:22:56.109 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('W', 'X', 'Y');
2024-04-23 16:22:56.110 UTC client backend[9179] pg_regress/create_table ERROR:  empty range bound specified for partition "fail_part" at character 68
2024-04-23 16:22:56.110 UTC client backend[9179] pg_regress/create_table DETAIL:  Specified lower bound (1) is greater than or equal to upper bound (0).
2024-04-23 16:22:56.110 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (0);
2024-04-23 16:22:56.111 UTC client backend[9179] pg_regress/create_table ERROR:  empty range bound specified for partition "fail_part" at character 68
2024-04-23 16:22:56.111 UTC client backend[9179] pg_regress/create_table DETAIL:  Specified lower bound (1) is greater than or equal to upper bound (1).
2024-04-23 16:22:56.111 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (1);
2024-04-23 16:22:56.113 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part0" at character 68
2024-04-23 16:22:56.113 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (minvalue) TO (2);
2024-04-23 16:22:56.114 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part0" at character 68
2024-04-23 16:22:56.114 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (-1) TO (1);
2024-04-23 16:22:56.115 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part1" at character 68
2024-04-23 16:22:56.115 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (9) TO (maxvalue);
2024-04-23 16:22:56.209 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part2" at character 76
2024-04-23 16:22:56.209 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (30);
2024-04-23 16:22:56.210 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part2" at character 76
2024-04-23 16:22:56.210 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (50);
2024-04-23 16:22:56.211 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_default_part" conflicts with existing default partition "range2_default" at character 59
2024-04-23 16:22:56.211 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF range_parted2 DEFAULT;
2024-04-23 16:22:56.212 UTC client backend[9179] pg_regress/create_table ERROR:  updated partition constraint for default partition "range2_default" would be violated by some row
2024-04-23 16:22:56.212 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (80) TO (90);
2024-04-23 16:22:56.213 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part00" at character 68
2024-04-23 16:22:56.213 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (0, minvalue) TO (0, 1);
2024-04-23 16:22:56.214 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part12" at character 71
2024-04-23 16:22:56.214 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, 10) TO (1, 20);
2024-04-23 16:22:56.215 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part10" at character 68
2024-04-23 16:22:56.215 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, minvalue) TO (1, maxvalue);
2024-04-23 16:22:56.218 UTC client backend[9179] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "h2part_4" at character 61
2024-04-23 16:22:56.218 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 2, REMAINDER 1);
2024-04-23 16:22:56.218 UTC client backend[9179] pg_regress/create_table ERROR:  modulus for hash partition must be an integer value greater than zero
2024-04-23 16:22:56.218 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 0, REMAINDER 1);
2024-04-23 16:22:56.219 UTC client backend[9179] pg_regress/create_table ERROR:  remainder for hash partition must be less than modulus
2024-04-23 16:22:56.219 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 8, REMAINDER 8);
2024-04-23 16:22:56.221 UTC client backend[9179] pg_regress/create_table ERROR:  column "b" specified more than once
2024-04-23 16:22:56.221 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE part_b PARTITION OF parted (
		b NOT NULL,
		b DEFAULT 1,
		b CHECK (b >= 0),
		CONSTRAINT check_a CHECK (length(a) > 0)
	) FOR VALUES IN ('b');
2024-04-23 16:22:56.223 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop inherited constraint "check_a" of relation "part_b"
2024-04-23 16:22:56.223 UTC client backend[9179] pg_regress/create_table STATEMENT:  ALTER TABLE part_b DROP CONSTRAINT check_a;
2024-04-23 16:22:56.223 UTC client backend[9179] pg_regress/create_table ERROR:  cannot drop inherited constraint "check_b" of relation "part_b"
2024-04-23 16:22:56.223 UTC client backend[9179] pg_regress/create_table STATEMENT:  ALTER TABLE part_b DROP CONSTRAINT check_b;
2024-04-23 16:22:56.224 UTC client backend[9179] pg_regress/create_table ERROR:  column "c" named in partition key does not exist at character 98
2024-04-23 16:22:56.224 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part_col_not_found PARTITION OF parted FOR VALUES IN ('c') PARTITION BY RANGE (c);
2024-04-23 16:22:56.226 UTC client backend[9179] pg_regress/create_table ERROR:  null value in column "b" of relation "parted_notnull_inh_test1" violates not-null constraint
2024-04-23 16:22:56.226 UTC client backend[9179] pg_regress/create_table DETAIL:  Failing row contains (1, null).
2024-04-23 16:22:56.226 UTC client backend[9179] pg_regress/create_table STATEMENT:  insert into parted_notnull_inh_test (b) values (null);
2024-04-23 16:22:56.920 UTC client backend[9179] pg_regress/create_table ERROR:  cannot specify storage parameters for a partitioned table
2024-04-23 16:22:56.920 UTC client backend[9179] pg_regress/create_table HINT:  Specify storage parameters for its leaf partitions instead.
2024-04-23 16:22:56.920 UTC client backend[9179] pg_regress/create_table STATEMENT:  CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a) WITH (fillfactor=100);
2024-04-23 16:22:56.986 UTC client backend[9179] pg_regress/create_table ERROR:  cannot create a permanent relation as partition of temporary relation "temp_parted"
2024-04-23 16:22:56.986 UTC client backend[9179] pg_regress/create_table STATEMENT:  create table perm_part partition of temp_parted default;
2024-04-23 16:22:56.986 UTC client backend[9179] pg_regress/create_table ERROR:  cannot create a temporary relation as partition of permanent relation "perm_parted"
2024-04-23 16:22:56.986 UTC client backend[9179] pg_regress/create_table STATEMENT:  create temp table temp_part partition of perm_parted default;
2024-04-23 16:22:56.989 UTC client backend[9179] pg_regress/create_table ERROR:  cannot CREATE TABLE .. PARTITION OF "tab_part_create" because it is being used by active queries in this session
2024-04-23 16:22:56.989 UTC client backend[9179] pg_regress/create_table CONTEXT:  SQL statement "create table tab_part_create_1 partition of tab_part_create for values in (1)"
	PL/pgSQL function func_part_create() line 3 at EXECUTE
2024-04-23 16:22:56.989 UTC client backend[9179] pg_regress/create_table STATEMENT:  insert into tab_part_create values (1);
2024-04-23 16:22:57.096 UTC client backend[9179] pg_regress/create_table ERROR:  updated partition constraint for default partition "defcheck_def" would be violated by some row
2024-04-23 16:22:57.096 UTC client backend[9179] pg_regress/create_table STATEMENT:  create table defcheck_0 partition of defcheck for values in (0);
2024-04-23 16:22:58.417 UTC client backend[9390] pg_regress/create_index ERROR:  syntax error at or near "ON" at character 28
2024-04-23 16:22:58.417 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops);
2024-04-23 16:22:58.418 UTC client backend[9382] pg_regress/create_view ERROR:  relation "noview" does not exist
2024-04-23 16:22:58.418 UTC client backend[9382] pg_regress/create_view STATEMENT:  COMMENT ON VIEW noview IS 'no view';
2024-04-23 16:22:58.424 UTC client backend[9382] pg_regress/create_view ERROR:  cannot drop constraint view_base_table_pkey on table view_base_table because other objects depend on it
2024-04-23 16:22:58.424 UTC client backend[9382] pg_regress/create_view DETAIL:  view key_dependent_view depends on constraint view_base_table_pkey on table view_base_table
2024-04-23 16:22:58.424 UTC client backend[9382] pg_regress/create_view HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:58.424 UTC client backend[9382] pg_regress/create_view STATEMENT:  ALTER TABLE view_base_table DROP CONSTRAINT view_base_table_pkey;
2024-04-23 16:22:58.432 UTC client backend[9382] pg_regress/create_view ERROR:  cannot drop columns from view
2024-04-23 16:22:58.432 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a FROM viewtest_tbl WHERE a <> 20;
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view ERROR:  cannot change name of view column "a" to "?column?"
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view HINT:  Use ALTER VIEW ... RENAME COLUMN ... to change name of view column instead.
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT 1, * FROM viewtest_tbl;
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view ERROR:  cannot change data type of view column "b" from integer to numeric
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b::numeric, c, d FROM viewtest_tbl;
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view ERROR:  cannot change data type of view column "c" from numeric(10,1) to numeric(10,2)
2024-04-23 16:22:58.433 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b, c::numeric(10,2), d FROM viewtest_tbl;
2024-04-23 16:22:58.434 UTC client backend[9382] pg_regress/create_view ERROR:  cannot change collation of view column "d" from "C" to "POSIX"
2024-04-23 16:22:58.434 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b, c, d COLLATE "POSIX" FROM viewtest_tbl;
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including ERROR:  could not create unique index "tbl_include_unique2_idx_unique"
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including STATEMENT:  CREATE UNIQUE INDEX tbl_include_unique2_idx_unique ON tbl_include_unique2 using btree (c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including ERROR:  could not create unique index "tbl_include_unique2_c1_c2_c3_c4_key"
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2024-04-23 16:22:58.436 UTC client backend[9391] pg_regress/index_including STATEMENT:  ALTER TABLE tbl_include_unique2 add UNIQUE (c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.446 UTC client backend[9391] pg_regress/index_including ERROR:  could not create unique index "tbl_include_box_pk_pkey"
2024-04-23 16:22:58.446 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2024-04-23 16:22:58.446 UTC client backend[9391] pg_regress/index_including STATEMENT:  ALTER TABLE tbl_include_box_pk add PRIMARY KEY (c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.468 UTC client backend[9391] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "covering"
2024-04-23 16:22:58.468 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2024-04-23 16:22:58.468 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.471 UTC client backend[9382] pg_regress/create_view ERROR:  cannot create temporary relation in non-temporary schema
2024-04-23 16:22:58.471 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE VIEW temp_view_test.v3_temp AS SELECT * FROM temp_table;
2024-04-23 16:22:58.471 UTC client backend[9382] pg_regress/create_view ERROR:  cannot create temporary relation in non-temporary schema
2024-04-23 16:22:58.471 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE SCHEMA test_view_schema
	    CREATE TEMP VIEW testview AS SELECT 1;
2024-04-23 16:22:58.488 UTC client backend[9391] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "covering"
2024-04-23 16:22:58.488 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2024-04-23 16:22:58.488 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.532 UTC client backend[9391] pg_regress/index_including ERROR:  null value in column "c2" of relation "tbl" violates not-null constraint
2024-04-23 16:22:58.532 UTC client backend[9391] pg_regress/index_including DETAIL:  Failing row contains (1, null, 3, (4,4),(4,4)).
2024-04-23 16:22:58.532 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, NULL, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.561 UTC client backend[9382] pg_regress/create_view ERROR:  invalid value for boolean option "security_barrier": 100
2024-04-23 16:22:58.561 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview5 WITH (security_barrier=100)	-- Error
	       AS SELECT * FROM tbl1 WHERE a > 100;
2024-04-23 16:22:58.561 UTC client backend[9382] pg_regress/create_view ERROR:  unrecognized parameter "invalid_option"
2024-04-23 16:22:58.561 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview6 WITH (invalid_option)		-- Error
	       AS SELECT * FROM tbl1 WHERE a < 100;
2024-04-23 16:22:58.562 UTC client backend[9382] pg_regress/create_view ERROR:  invalid value for boolean option "security_invoker": 100
2024-04-23 16:22:58.562 UTC client backend[9382] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview10 WITH (security_invoker=100)	-- Error
	       AS SELECT * FROM tbl1 WHERE a <> 100;
2024-04-23 16:22:58.582 UTC client backend[9391] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_c1_c2_c3_c4_key"
2024-04-23 16:22:58.582 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2024-04-23 16:22:58.582 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_pkey"
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including ERROR:  null value in column "c2" of relation "tbl" violates not-null constraint
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including DETAIL:  Failing row contains (1, null, 3, (4,4),(4,4)).
2024-04-23 16:22:58.593 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, NULL, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.608 UTC client backend[9391] pg_regress/index_including ERROR:  conflicting key value violates exclusion constraint "tbl_c1_c3_c4_excl"
2024-04-23 16:22:58.608 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1)=(1) conflicts with existing key (c1)=(1).
2024-04-23 16:22:58.608 UTC client backend[9391] pg_regress/index_including STATEMENT:  INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x;
2024-04-23 16:22:58.626 UTC client backend[9390] pg_regress/create_index ERROR:  relation "six_wrong" does not exist
2024-04-23 16:22:58.626 UTC client backend[9390] pg_regress/create_index STATEMENT:  COMMENT ON INDEX six_wrong IS 'bad index';
2024-04-23 16:22:58.784 UTC client backend[9391] pg_regress/index_including ERROR:  cannot alter statistics on non-expression column "c1" of index "tbl_idx"
2024-04-23 16:22:58.784 UTC client backend[9391] pg_regress/index_including HINT:  Alter statistics on table column instead.
2024-04-23 16:22:58.784 UTC client backend[9391] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 1 SET STATISTICS 1000;
2024-04-23 16:22:58.786 UTC client backend[9391] pg_regress/index_including ERROR:  cannot alter statistics on included column "c2" of index "tbl_idx"
2024-04-23 16:22:58.786 UTC client backend[9391] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 3 SET STATISTICS 1000;
2024-04-23 16:22:58.786 UTC client backend[9391] pg_regress/index_including ERROR:  column number 4 of relation "tbl_idx" does not exist
2024-04-23 16:22:58.786 UTC client backend[9391] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 4 SET STATISTICS 1000;
2024-04-23 16:22:58.794 UTC client backend[9382] pg_regress/create_view ERROR:  cannot drop column f3 of table tt14t because other objects depend on it
2024-04-23 16:22:58.794 UTC client backend[9382] pg_regress/create_view DETAIL:  view tt14v depends on column f3 of table tt14t
2024-04-23 16:22:58.794 UTC client backend[9382] pg_regress/create_view HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:22:58.794 UTC client backend[9382] pg_regress/create_view STATEMENT:  alter table tt14t drop column f3;
2024-04-23 16:22:58.797 UTC client backend[9382] pg_regress/create_view ERROR:  attribute 3 of type record has been dropped
2024-04-23 16:22:58.797 UTC client backend[9382] pg_regress/create_view STATEMENT:  select * from tt14v;
2024-04-23 16:22:58.798 UTC client backend[9382] pg_regress/create_view ERROR:  cannot alter type of a column used by a view or rule
2024-04-23 16:22:58.798 UTC client backend[9382] pg_regress/create_view DETAIL:  rule _RETURN on view tt14v depends on column "f4"
2024-04-23 16:22:58.798 UTC client backend[9382] pg_regress/create_view STATEMENT:  alter table tt14t alter column f4 type integer using f4::integer;
2024-04-23 16:22:58.800 UTC client backend[9382] pg_regress/create_view ERROR:  attribute 4 of type record has wrong type
2024-04-23 16:22:58.800 UTC client backend[9382] pg_regress/create_view DETAIL:  Table has type integer, but query expects text.
2024-04-23 16:22:58.800 UTC client backend[9382] pg_regress/create_view STATEMENT:  select * from tt14v;
2024-04-23 16:22:58.866 UTC client backend[9382] pg_regress/create_view ERROR:  operator does not exist: text = text[] at character 20
2024-04-23 16:22:58.866 UTC client backend[9382] pg_regress/create_view HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:22:58.866 UTC client backend[9382] pg_regress/create_view STATEMENT:  select 'foo'::text = any((select array['abc','def','foo']::text[]));
2024-04-23 16:22:58.966 UTC client backend[9391] pg_regress/index_including ERROR:  relation "tbl_c1_c2_c3_c4_key" does not exist
2024-04-23 16:22:58.966 UTC client backend[9391] pg_regress/index_including STATEMENT:  REINDEX INDEX tbl_c1_c2_c3_c4_key;
2024-04-23 16:22:58.978 UTC client backend[9391] pg_regress/index_including ERROR:  access method "brin" does not support included columns
2024-04-23 16:22:58.978 UTC client backend[9391] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING brin(c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.983 UTC client backend[9391] pg_regress/index_including ERROR:  access method "gin" does not support included columns
2024-04-23 16:22:58.983 UTC client backend[9391] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING gin(c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.986 UTC client backend[9391] pg_regress/index_including ERROR:  access method "hash" does not support included columns
2024-04-23 16:22:58.986 UTC client backend[9391] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING hash(c1, c2) INCLUDE (c3, c4);
2024-04-23 16:22:58.993 UTC client backend[9384] pg_regress/index_including_gist ERROR:  conflicting key value violates exclusion constraint "tbl_gist_c4_c1_c2_c3_excl"
2024-04-23 16:22:58.993 UTC client backend[9384] pg_regress/index_including_gist DETAIL:  Key (c4)=((4,5),(2,3)) conflicts with existing key (c4)=((2,3),(1,2)).
2024-04-23 16:22:58.993 UTC client backend[9384] pg_regress/index_including_gist STATEMENT:  INSERT INTO tbl_gist SELECT x, 2*x, 3*x, box(point(x,x+1),point(2*x,2*x+1)) FROM generate_series(1,10) AS x;
2024-04-23 16:22:59.048 UTC client backend[9391] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_idx_unique"
2024-04-23 16:22:59.048 UTC client backend[9391] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2024-04-23 16:22:59.048 UTC client backend[9391] pg_regress/index_including STATEMENT:  UPDATE tbl SET c2 = 2 WHERE c1 = 1;
2024-04-23 16:22:59.156 UTC client backend[9390] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "unique_idx2"
2024-04-23 16:22:59.156 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (i)=(null) already exists.
2024-04-23 16:22:59.156 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO unique_tbl (t) VALUES ('seven');
2024-04-23 16:22:59.215 UTC client backend[9390] pg_regress/create_index ERROR:  could not create unique index "unique_idx4"
2024-04-23 16:22:59.215 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (i)=(null) is duplicated.
2024-04-23 16:22:59.215 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX unique_idx4 ON unique_tbl (i) NULLS NOT DISTINCT;
2024-04-23 16:22:59.567 UTC client backend[9390] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "func_index_index"
2024-04-23 16:22:59.567 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (textcat(f1, f2))=(ABCDEF) already exists.
2024-04-23 16:22:59.567 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO func_index_heap VALUES('ABCD', 'EF');
2024-04-23 16:22:59.591 UTC client backend[9390] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "func_index_index"
2024-04-23 16:22:59.591 UTC client backend[9390] pg_regress/create_index DETAIL:  Key ((f1 || f2))=(ABCDEF) already exists.
2024-04-23 16:22:59.591 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO func_index_heap VALUES('ABCD', 'EF');
2024-04-23 16:22:59.603 UTC client backend[9390] pg_regress/create_index ERROR:  column "row" has pseudo-type record
2024-04-23 16:22:59.603 UTC client backend[9390] pg_regress/create_index STATEMENT:  create index on func_index_heap ((f1 || f2), (row(f1, f2)));
2024-04-23 16:22:59.613 UTC client backend[9390] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "covering_index_index"
2024-04-23 16:22:59.613 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (f1, f2)=(1, 2) already exists.
2024-04-23 16:22:59.613 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO covering_index_heap VALUES(1,2,'BBB');
2024-04-23 16:22:59.646 UTC client backend[9390] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "concur_index2"
2024-04-23 16:22:59.646 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (f1)=(b) already exists.
2024-04-23 16:22:59.646 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO concur_heap VALUES ('b','x');
2024-04-23 16:22:59.647 UTC client backend[9390] pg_regress/create_index ERROR:  could not create unique index "concur_index3"
2024-04-23 16:22:59.647 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (f2)=(b) is duplicated.
2024-04-23 16:22:59.647 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2);
2024-04-23 16:22:59.653 UTC client backend[9390] pg_regress/create_index ERROR:  CREATE INDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:22:59.653 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX CONCURRENTLY concur_index7 ON concur_heap(f1);
2024-04-23 16:22:59.678 UTC client backend[9390] pg_regress/create_index ERROR:  could not create unique index "concur_index3"
2024-04-23 16:22:59.678 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (f2)=(b) is duplicated.
2024-04-23 16:22:59.678 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_heap;
2024-04-23 16:22:59.745 UTC client backend[9390] pg_regress/create_index ERROR:  CREATE INDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:22:59.745 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX CONCURRENTLY concur_temp_ind ON concur_temp(f1);
2024-04-23 16:22:59.778 UTC client backend[9390] pg_regress/create_index ERROR:  DROP INDEX CONCURRENTLY does not support dropping multiple objects
2024-04-23 16:22:59.778 UTC client backend[9390] pg_regress/create_index STATEMENT:  DROP INDEX CONCURRENTLY "concur_index2", "concur_index3";
2024-04-23 16:22:59.778 UTC client backend[9390] pg_regress/create_index ERROR:  DROP INDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:22:59.778 UTC client backend[9390] pg_regress/create_index STATEMENT:  DROP INDEX CONCURRENTLY "concur_index5";
2024-04-23 16:22:59.804 UTC client backend[9390] pg_regress/create_index ERROR:  cannot drop index cwi_replaced_pkey because constraint cwi_replaced_pkey on table cwi_test requires it
2024-04-23 16:22:59.804 UTC client backend[9390] pg_regress/create_index HINT:  You can drop constraint cwi_replaced_pkey on table cwi_test instead.
2024-04-23 16:22:59.804 UTC client backend[9390] pg_regress/create_index STATEMENT:  DROP INDEX cwi_replaced_pkey;
2024-04-23 16:22:59.805 UTC client backend[9390] pg_regress/create_index ERROR:  index "cwi_uniq3_idx" column number 1 does not have default sorting behavior at character 26
2024-04-23 16:22:59.805 UTC client backend[9390] pg_regress/create_index DETAIL:  Cannot create a primary key or unique constraint using such an index.
2024-04-23 16:22:59.805 UTC client backend[9390] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq3_idx;
2024-04-23 16:22:59.806 UTC client backend[9390] pg_regress/create_index ERROR:  index "cwi_uniq4_idx" column number 1 does not have default sorting behavior at character 26
2024-04-23 16:22:59.806 UTC client backend[9390] pg_regress/create_index DETAIL:  Cannot create a primary key or unique constraint using such an index.
2024-04-23 16:22:59.806 UTC client backend[9390] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq4_idx;
2024-04-23 16:22:59.817 UTC client backend[9390] pg_regress/create_index ERROR:  ALTER TABLE / ADD CONSTRAINT USING INDEX is not supported on partitioned tables
2024-04-23 16:22:59.817 UTC client backend[9390] pg_regress/create_index STATEMENT:  alter table cwi_test add primary key using index cwi_test_a_idx ;
2024-04-23 16:22:59.820 UTC client backend[9390] pg_regress/create_index ERROR:  primary keys cannot use NULLS NOT DISTINCT indexes
2024-04-23 16:22:59.820 UTC client backend[9390] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD PRIMARY KEY USING INDEX cwi_a_nnd;
2024-04-23 16:22:59.822 UTC client backend[9390] pg_regress/create_index ERROR:  relation "syscolcol_table" does not exist
2024-04-23 16:22:59.822 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscolcol_table (ctid);
2024-04-23 16:22:59.823 UTC client backend[9390] pg_regress/create_index ERROR:  index creation on system columns is not supported
2024-04-23 16:22:59.823 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscol_table ((ctid >= '(1000,0)'));
2024-04-23 16:22:59.824 UTC client backend[9390] pg_regress/create_index ERROR:  index creation on system columns is not supported
2024-04-23 16:22:59.824 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscol_table (a) WHERE ctid >= '(1000,0)';
2024-04-23 16:22:59.932 UTC client backend[9390] pg_regress/create_index ERROR:  concurrent index creation for exclusion constraints is not supported
2024-04-23 16:22:59.932 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY  concur_reindex_tab3_c2_excl;
2024-04-23 16:22:59.933 UTC client backend[9390] pg_regress/create_index WARNING:  cannot reindex exclusion constraint index "public.concur_reindex_tab3_c2_excl" concurrently, skipping
2024-04-23 16:22:59.935 UTC client backend[9390] pg_regress/create_index ERROR:  conflicting key value violates exclusion constraint "concur_reindex_tab3_c2_excl"
2024-04-23 16:22:59.935 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (c2)=([2,5)) conflicts with existing key (c2)=([1,3)).
2024-04-23 16:22:59.935 UTC client backend[9390] pg_regress/create_index STATEMENT:  INSERT INTO concur_reindex_tab3 VALUES  (4, '[2,4]');
2024-04-23 16:23:00.155 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_index" is not a table or materialized view
2024-04-23 16:23:00.155 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part_index;
2024-04-23 16:23:00.156 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_index" is not a table or materialized view
2024-04-23 16:23:00.156 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_part_index;
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_index_10" is not a table or materialized view
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part_index_10;
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_index_10" is not a table or materialized view
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_part_index_10;
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX INDEX cannot run inside a transaction block
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index CONTEXT:  while reindexing partitioned index "public.concur_reindex_part_index"
2024-04-23 16:23:00.157 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part_index;
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part" is not an index
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part;
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part" is not an index
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_part;
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_10" is not an index
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part_10;
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index ERROR:  "concur_reindex_part_10" is not an index
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_part_10;
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX TABLE cannot run inside a transaction block
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index CONTEXT:  while reindexing partitioned table "public.concur_reindex_part"
2024-04-23 16:23:00.169 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part;
2024-04-23 16:23:00.181 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:23:00.181 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_tab;
2024-04-23 16:23:00.182 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.182 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY pg_class;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY pg_class_oid_index;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY pg_toast.pg_toast_1260;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY pg_toast.pg_toast_1260_index;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX SYSTEM CONCURRENTLY postgres;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX (CONCURRENTLY) SYSTEM postgres;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX (CONCURRENTLY) SYSTEM;
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index WARNING:  cannot reindex system catalogs concurrently, skipping all
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index ERROR:  can only reindex the currently open database
2024-04-23 16:23:00.183 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX DATABASE not_current_database;
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index ERROR:  could not create unique index "concur_reindex_ind5"
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (c1)=(1) is duplicated.
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX CONCURRENTLY concur_reindex_ind5 ON concur_reindex_tab4 (c1);
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index ERROR:  could not create unique index "concur_reindex_ind5_ccnew"
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index DETAIL:  Key (c1)=(1) is duplicated.
2024-04-23 16:23:00.196 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_ind5;
2024-04-23 16:23:00.203 UTC client backend[9390] pg_regress/create_index WARNING:  skipping reindex of invalid index "public.concur_reindex_ind5"
2024-04-23 16:23:00.203 UTC client backend[9390] pg_regress/create_index HINT:  Use DROP INDEX or REINDEX INDEX.
2024-04-23 16:23:00.266 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:23:00.266 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_temp_ind_1;
2024-04-23 16:23:00.293 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:23:00.293 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_temp_ind_3;
2024-04-23 16:23:00.325 UTC client backend[9390] pg_regress/create_index ERROR:  schema "schema_to_reindex" does not exist
2024-04-23 16:23:00.325 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2024-04-23 16:23:00.361 UTC client backend[9390] pg_regress/create_index ERROR:  REINDEX SCHEMA cannot run inside a transaction block
2024-04-23 16:23:00.361 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index ERROR:  must be owner of schema schema_to_reindex
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index ERROR:  permission denied for table pg_toast_1260
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX TABLE pg_toast.pg_toast_1260;
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index ERROR:  permission denied for index pg_toast_1260_index
2024-04-23 16:23:00.400 UTC client backend[9390] pg_regress/create_index STATEMENT:  REINDEX INDEX pg_toast.pg_toast_1260_index;
2024-04-23 16:23:01.262 UTC client backend[9783] pg_regress/typed_table ERROR:  type "nothing" does not exist
2024-04-23 16:23:01.262 UTC client backend[9783] pg_regress/typed_table STATEMENT:  CREATE TABLE ttable1 OF nothing;
2024-04-23 16:23:01.264 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  table "test_exists" does not exist
2024-04-23 16:23:01.264 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TABLE test_exists;
2024-04-23 16:23:01.271 UTC client backend[9790] pg_regress/create_am ERROR:  function int4in(internal) does not exist
2024-04-23 16:23:01.271 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE INDEX HANDLER int4in;
2024-04-23 16:23:01.272 UTC client backend[9774] pg_regress/create_aggregate ERROR:  aggregate newavg_wrong(integer) does not exist
2024-04-23 16:23:01.272 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  COMMENT ON AGGREGATE newavg_wrong (int4) IS 'an agg comment';
2024-04-23 16:23:01.274 UTC client backend[9789] pg_regress/errors ERROR:  relation "nonesuch" does not exist at character 15
2024-04-23 16:23:01.274 UTC client backend[9789] pg_regress/errors STATEMENT:  select * from nonesuch;
2024-04-23 16:23:01.274 UTC client backend[9790] pg_regress/create_am ERROR:  function heap_tableam_handler must return type index_am_handler
2024-04-23 16:23:01.274 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE INDEX HANDLER heap_tableam_handler;
2024-04-23 16:23:01.277 UTC client backend[9789] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 8
2024-04-23 16:23:01.277 UTC client backend[9789] pg_regress/errors STATEMENT:  select nonesuch from pg_database;
2024-04-23 16:23:01.278 UTC client backend[9790] pg_regress/create_am ERROR:  data type box has no default operator class for access method "gist2"
2024-04-23 16:23:01.278 UTC client backend[9790] pg_regress/create_am HINT:  You must specify an operator class for the index or define a default operator class for the data type.
2024-04-23 16:23:01.278 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE INDEX grect2ind2 ON fast_emp4000 USING gist2 (home_base);
2024-04-23 16:23:01.278 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  view "test_view_exists" does not exist
2024-04-23 16:23:01.278 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP VIEW test_view_exists;
2024-04-23 16:23:01.280 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "from" at character 17
2024-04-23 16:23:01.280 UTC client backend[9789] pg_regress/errors STATEMENT:  select distinct from pg_database;
2024-04-23 16:23:01.282 UTC client backend[9789] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 33
2024-04-23 16:23:01.282 UTC client backend[9789] pg_regress/errors STATEMENT:  select * from pg_database where nonesuch = pg_database.datname;
2024-04-23 16:23:01.285 UTC client backend[9797] pg_regress/create_cast ERROR:  function casttestfunc(text) does not exist at character 8
2024-04-23 16:23:01.285 UTC client backend[9797] pg_regress/create_cast HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:23:01.285 UTC client backend[9797] pg_regress/create_cast STATEMENT:  SELECT casttestfunc('foo'::text);
2024-04-23 16:23:01.286 UTC client backend[9789] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 55
2024-04-23 16:23:01.286 UTC client backend[9789] pg_regress/errors STATEMENT:  select * from pg_database where pg_database.datname = nonesuch;
2024-04-23 16:23:01.290 UTC client backend[9789] pg_regress/errors ERROR:  column "foobar" does not exist at character 21
2024-04-23 16:23:01.290 UTC client backend[9789] pg_regress/errors STATEMENT:  select distinct on (foobar) * from pg_database;
2024-04-23 16:23:01.291 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  view "test_view_exists" does not exist
2024-04-23 16:23:01.291 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP VIEW test_view_exists;
2024-04-23 16:23:01.293 UTC client backend[9797] pg_regress/create_cast ERROR:  function casttestfunc(text) does not exist at character 8
2024-04-23 16:23:01.293 UTC client backend[9797] pg_regress/create_cast HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:23:01.293 UTC client backend[9797] pg_regress/create_cast STATEMENT:  SELECT casttestfunc('foo'::text);
2024-04-23 16:23:01.294 UTC client backend[9789] pg_regress/errors ERROR:  FOR UPDATE is not allowed with GROUP BY clause
2024-04-23 16:23:01.294 UTC client backend[9789] pg_regress/errors STATEMENT:  select null from pg_database group by datname for update;
2024-04-23 16:23:01.294 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  index "test_index_exists" does not exist
2024-04-23 16:23:01.294 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP INDEX test_index_exists;
2024-04-23 16:23:01.294 UTC client backend[9774] pg_regress/create_aggregate ERROR:  aggregate nosuchagg(*) does not exist
2024-04-23 16:23:01.294 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  COMMENT ON AGGREGATE nosuchagg (*) IS 'should fail';
2024-04-23 16:23:01.295 UTC client backend[9789] pg_regress/errors ERROR:  FOR UPDATE is not allowed with GROUP BY clause
2024-04-23 16:23:01.295 UTC client backend[9789] pg_regress/errors STATEMENT:  select null from pg_database group by grouping sets (()) for update;
2024-04-23 16:23:01.296 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 12
2024-04-23 16:23:01.296 UTC client backend[9789] pg_regress/errors STATEMENT:  delete from;
2024-04-23 16:23:01.299 UTC client backend[9789] pg_regress/errors ERROR:  relation "nonesuch" does not exist at character 13
2024-04-23 16:23:01.299 UTC client backend[9789] pg_regress/errors STATEMENT:  delete from nonesuch;
2024-04-23 16:23:01.302 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 11
2024-04-23 16:23:01.302 UTC client backend[9789] pg_regress/errors STATEMENT:  drop table;
2024-04-23 16:23:01.305 UTC client backend[9797] pg_regress/create_cast ERROR:  cannot cast type integer to casttesttype at character 18
2024-04-23 16:23:01.305 UTC client backend[9797] pg_regress/create_cast STATEMENT:  SELECT 1234::int4::casttesttype;
2024-04-23 16:23:01.305 UTC client backend[9789] pg_regress/errors ERROR:  table "nonesuch" does not exist
2024-04-23 16:23:01.305 UTC client backend[9789] pg_regress/errors STATEMENT:  drop table nonesuch;
2024-04-23 16:23:01.307 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 19
2024-04-23 16:23:01.307 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table rename;
2024-04-23 16:23:01.309 UTC client backend[9789] pg_regress/errors ERROR:  relation "nonesuch" does not exist
2024-04-23 16:23:01.309 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table nonesuch rename to newnonesuch;
2024-04-23 16:23:01.309 UTC client backend[9795] pg_regress/constraints ERROR:  syntax error at or near ")" at character 45
2024-04-23 16:23:01.309 UTC client backend[9795] pg_regress/constraints STATEMENT:  CREATE TABLE error_tbl (i int DEFAULT (100, ));
2024-04-23 16:23:01.310 UTC client backend[9789] pg_regress/errors ERROR:  relation "nonesuch" does not exist
2024-04-23 16:23:01.310 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table nonesuch rename to stud_emp;
2024-04-23 16:23:01.310 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot add column to typed table
2024-04-23 16:23:01.310 UTC client backend[9783] pg_regress/typed_table STATEMENT:  ALTER TABLE persons ADD COLUMN comment text;
2024-04-23 16:23:01.310 UTC client backend[9795] pg_regress/constraints ERROR:  syntax error at or near "IN" at character 43
2024-04-23 16:23:01.310 UTC client backend[9795] pg_regress/constraints STATEMENT:  CREATE TABLE error_tbl (b1 bool DEFAULT 1 IN (1, 2));
2024-04-23 16:23:01.311 UTC client backend[9788] pg_regress/hash_func ERROR:  could not identify a hash function for type bit varying
2024-04-23 16:23:01.311 UTC client backend[9788] pg_regress/hash_func STATEMENT:  SELECT v as value, hash_array(v)::bit(32) as standard
	FROM   (VALUES ('{101}'::varbit[])) x(v);
2024-04-23 16:23:01.311 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot drop column from typed table
2024-04-23 16:23:01.311 UTC client backend[9783] pg_regress/typed_table STATEMENT:  ALTER TABLE persons DROP COLUMN name;
2024-04-23 16:23:01.311 UTC client backend[9789] pg_regress/errors ERROR:  relation "student" already exists
2024-04-23 16:23:01.311 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table stud_emp rename to student;
2024-04-23 16:23:01.312 UTC client backend[9788] pg_regress/hash_func ERROR:  could not identify an extended hash function for type bit varying
2024-04-23 16:23:01.312 UTC client backend[9788] pg_regress/hash_func STATEMENT:  SELECT v as value, hash_array_extended(v, 0)::bit(32) as extended0
	FROM   (VALUES ('{101}'::varbit[])) x(v);
2024-04-23 16:23:01.313 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot rename column of typed table
2024-04-23 16:23:01.313 UTC client backend[9783] pg_regress/typed_table STATEMENT:  ALTER TABLE persons RENAME COLUMN id TO num;
2024-04-23 16:23:01.313 UTC client backend[9789] pg_regress/errors ERROR:  relation "stud_emp" already exists
2024-04-23 16:23:01.313 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table stud_emp rename to stud_emp;
2024-04-23 16:23:01.314 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot alter column type of typed table
2024-04-23 16:23:01.314 UTC client backend[9783] pg_regress/typed_table STATEMENT:  ALTER TABLE persons ALTER COLUMN name TYPE varchar;
2024-04-23 16:23:01.314 UTC client backend[9789] pg_regress/errors ERROR:  relation "nonesuchrel" does not exist
2024-04-23 16:23:01.314 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table nonesuchrel rename column nonesuchatt to newnonesuchatt;
2024-04-23 16:23:01.316 UTC client backend[9774] pg_regress/create_aggregate ERROR:  function least_accum(bigint, bigint) requires run-time type coercion
2024-04-23 16:23:01.316 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  create aggregate least_agg(int4) (
	  stype = int8, sfunc = least_accum
	);
2024-04-23 16:23:01.316 UTC client backend[9790] pg_regress/create_am ERROR:  cannot drop access method gist2 because other objects depend on it
2024-04-23 16:23:01.316 UTC client backend[9790] pg_regress/create_am DETAIL:  index grect2ind2 depends on operator class box_ops for access method gist2
2024-04-23 16:23:01.316 UTC client backend[9790] pg_regress/create_am HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:23:01.316 UTC client backend[9790] pg_regress/create_am STATEMENT:  DROP ACCESS METHOD gist2;
2024-04-23 16:23:01.316 UTC client backend[9789] pg_regress/errors ERROR:  column "nonesuchatt" does not exist
2024-04-23 16:23:01.316 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table emp rename column nonesuchatt to newnonesuchatt;
2024-04-23 16:23:01.318 UTC client backend[9789] pg_regress/errors ERROR:  column "manager" of relation "stud_emp" already exists
2024-04-23 16:23:01.318 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table emp rename column salary to manager;
2024-04-23 16:23:01.318 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot change inheritance of typed table
2024-04-23 16:23:01.318 UTC client backend[9783] pg_regress/typed_table STATEMENT:  ALTER TABLE persons INHERIT stuff;
2024-04-23 16:23:01.319 UTC client backend[9789] pg_regress/errors ERROR:  column name "ctid" conflicts with a system column name
2024-04-23 16:23:01.319 UTC client backend[9789] pg_regress/errors STATEMENT:  alter table emp rename column salary to ctid;
2024-04-23 16:23:01.319 UTC client backend[9783] pg_regress/typed_table ERROR:  column "myname" does not exist
2024-04-23 16:23:01.319 UTC client backend[9783] pg_regress/typed_table STATEMENT:  CREATE TABLE personsx OF person_type (myname WITH OPTIONS NOT NULL);
2024-04-23 16:23:01.321 UTC client backend[9789] pg_regress/errors WARNING:  there is no transaction in progress
2024-04-23 16:23:01.323 UTC client backend[9774] pg_regress/create_aggregate ERROR:  function least_accum(bigint, bigint) requires run-time type coercion
2024-04-23 16:23:01.323 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  create aggregate least_agg(int4) (
	  stype = int8, sfunc = least_accum
	);
2024-04-23 16:23:01.326 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2024-04-23 16:23:01.326 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (3).
2024-04-23 16:23:01.326 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (3);
2024-04-23 16:23:01.327 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  index "test_index_exists" does not exist
2024-04-23 16:23:01.327 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP INDEX test_index_exists;
2024-04-23 16:23:01.327 UTC client backend[9789] pg_regress/errors WARNING:  there is no transaction in progress
2024-04-23 16:23:01.331 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2024-04-23 16:23:01.331 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (2).
2024-04-23 16:23:01.331 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (2);
2024-04-23 16:23:01.331 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  sequence "test_sequence_exists" does not exist
2024-04-23 16:23:01.331 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP SEQUENCE test_sequence_exists;
2024-04-23 16:23:01.331 UTC client backend[9790] pg_regress/create_am ERROR:  invalid value for parameter "default_table_access_method": ""
2024-04-23 16:23:01.331 UTC client backend[9790] pg_regress/create_am DETAIL:  default_table_access_method cannot be empty.
2024-04-23 16:23:01.331 UTC client backend[9790] pg_regress/create_am STATEMENT:  SET default_table_access_method = '';
2024-04-23 16:23:01.332 UTC client backend[9789] pg_regress/errors ERROR:  function int2um(integer) does not exist
2024-04-23 16:23:01.332 UTC client backend[9789] pg_regress/errors STATEMENT:  create aggregate newavg2 (sfunc = int4pl,
				  basetype = int4,
				  stype = int4,
				  finalfunc = int2um,
				  initcond = '0');
2024-04-23 16:23:01.335 UTC client backend[9790] pg_regress/create_am ERROR:  invalid value for parameter "default_table_access_method": "I do not exist AM"
2024-04-23 16:23:01.335 UTC client backend[9790] pg_regress/create_am DETAIL:  Table access method "I do not exist AM" does not exist.
2024-04-23 16:23:01.335 UTC client backend[9790] pg_regress/create_am STATEMENT:  SET default_table_access_method = 'I do not exist AM';
2024-04-23 16:23:01.336 UTC client backend[9789] pg_regress/errors ERROR:  aggregate input type must be specified
2024-04-23 16:23:01.336 UTC client backend[9789] pg_regress/errors STATEMENT:  create aggregate newcnt1 (sfunc = int4inc,
				  stype = int4,
				  initcond = '0');
2024-04-23 16:23:01.338 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2024-04-23 16:23:01.338 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (1).
2024-04-23 16:23:01.338 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (1);
2024-04-23 16:23:01.338 UTC client backend[9790] pg_regress/create_am ERROR:  access method "btree" is not of type TABLE
2024-04-23 16:23:01.338 UTC client backend[9790] pg_regress/create_am STATEMENT:  SET default_table_access_method = 'btree';
2024-04-23 16:23:01.339 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 11
2024-04-23 16:23:01.339 UTC client backend[9789] pg_regress/errors STATEMENT:  drop index;
2024-04-23 16:23:01.341 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "314159" at character 12
2024-04-23 16:23:01.341 UTC client backend[9789] pg_regress/errors STATEMENT:  drop index 314159;
2024-04-23 16:23:01.342 UTC client backend[9790] pg_regress/create_am ERROR:  function int4in(internal) does not exist
2024-04-23 16:23:01.342 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE TABLE HANDLER int4in;
2024-04-23 16:23:01.342 UTC client backend[9789] pg_regress/errors ERROR:  index "nonesuch" does not exist
2024-04-23 16:23:01.342 UTC client backend[9789] pg_regress/errors STATEMENT:  drop index nonesuch;
2024-04-23 16:23:01.343 UTC client backend[9792] pg_regress/infinite_recurse ERROR:  stack depth limit exceeded
2024-04-23 16:23:01.343 UTC client backend[9792] pg_regress/infinite_recurse HINT:  Increase the configuration parameter max_stack_depth (currently 2048kB), after ensuring the platform's stack depth limit is adequate.
2024-04-23 16:23:01.343 UTC client backend[9792] pg_regress/infinite_recurse CONTEXT:  SQL function "infinite_recurse" during inlining
	SQL function "infinite_recurse" during startup
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
2024-04-23 16:23:01.343 UTC client backend[9792] pg_regress/infinite_recurse STATEMENT:  select infinite_recurse();
2024-04-23 16:23:01.344 UTC client backend[9790] pg_regress/create_am ERROR:  function bthandler must return type table_am_handler
2024-04-23 16:23:01.344 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE TABLE HANDLER bthandler;
2024-04-23 16:23:01.344 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 15
2024-04-23 16:23:01.344 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate;
2024-04-23 16:23:01.346 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 23
2024-04-23 16:23:01.346 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate newcnt1;
2024-04-23 16:23:01.347 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "314159" at character 16
2024-04-23 16:23:01.347 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate 314159 (int);
2024-04-23 16:23:01.347 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2024-04-23 16:23:01.347 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (1, x check failed, -2).
2024-04-23 16:23:01.347 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (1, 'x check failed', -2);
2024-04-23 16:23:01.348 UTC client backend[9789] pg_regress/errors ERROR:  type "nonesuch" does not exist
2024-04-23 16:23:01.348 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate newcnt (nonesuch);
2024-04-23 16:23:01.349 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2024-04-23 16:23:01.349 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (5, z check failed, 10).
2024-04-23 16:23:01.349 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (5, 'z check failed', 10);
2024-04-23 16:23:01.349 UTC client backend[9789] pg_regress/errors ERROR:  aggregate nonesuch(integer) does not exist
2024-04-23 16:23:01.349 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate nonesuch (int4);
2024-04-23 16:23:01.350 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2024-04-23 16:23:01.350 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (0, check failed, -2).
2024-04-23 16:23:01.350 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (0, 'check failed', -2);
2024-04-23 16:23:01.350 UTC client backend[9789] pg_regress/errors ERROR:  aggregate newcnt(real) does not exist
2024-04-23 16:23:01.350 UTC client backend[9789] pg_regress/errors STATEMENT:  drop aggregate newcnt (float4);
2024-04-23 16:23:01.351 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2024-04-23 16:23:01.351 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (6, check failed, 11).
2024-04-23 16:23:01.351 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (6, 'check failed', 11);
2024-04-23 16:23:01.352 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "(" at character 15
2024-04-23 16:23:01.352 UTC client backend[9789] pg_regress/errors STATEMENT:  drop function ();
2024-04-23 16:23:01.353 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "314159" at character 15
2024-04-23 16:23:01.353 UTC client backend[9789] pg_regress/errors STATEMENT:  drop function 314159();
2024-04-23 16:23:01.353 UTC client backend[9788] pg_regress/hash_func ERROR:  could not identify a hash function for type bit varying
2024-04-23 16:23:01.353 UTC client backend[9788] pg_regress/hash_func STATEMENT:  SELECT v as value, hash_record(v)::bit(32) as standard
	FROM   (VALUES (row('10'::varbit, 'aaa')::hash_test_t2)) x(v);
2024-04-23 16:23:01.353 UTC client backend[9774] pg_regress/create_aggregate ERROR:  must specify both or neither of serialization and deserialization functions
2024-04-23 16:23:01.353 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_serialize
	);
2024-04-23 16:23:01.354 UTC client backend[9790] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 41
2024-04-23 16:23:01.354 UTC client backend[9790] pg_regress/create_am STATEMENT:  SELECT INTO tableam_tblselectinto_heap2 USING heap2 FROM tableam_tbl_heap2;
2024-04-23 16:23:01.354 UTC client backend[9789] pg_regress/errors ERROR:  function nonesuch() does not exist
2024-04-23 16:23:01.354 UTC client backend[9789] pg_regress/errors STATEMENT:  drop function nonesuch();
2024-04-23 16:23:01.354 UTC client backend[9788] pg_regress/hash_func ERROR:  could not identify an extended hash function for type bit varying
2024-04-23 16:23:01.354 UTC client backend[9788] pg_regress/hash_func STATEMENT:  SELECT v as value, hash_record_extended(v, 0)::bit(32) as extended0
	FROM   (VALUES (row('11'::varbit, 'aaa')::hash_test_t2)) x(v);
2024-04-23 16:23:01.355 UTC client backend[9774] pg_regress/create_aggregate ERROR:  function numeric_avg_deserialize(internal) does not exist
2024-04-23 16:23:01.355 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_deserialize,
		deserialfunc = numeric_avg_deserialize
	);
2024-04-23 16:23:01.355 UTC client backend[9790] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 32
2024-04-23 16:23:01.355 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE VIEW tableam_view_heap2 USING heap2 AS SELECT * FROM tableam_tbl_heap2;
2024-04-23 16:23:01.355 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  sequence "test_sequence_exists" does not exist
2024-04-23 16:23:01.355 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP SEQUENCE test_sequence_exists;
2024-04-23 16:23:01.355 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 10
2024-04-23 16:23:01.355 UTC client backend[9789] pg_regress/errors STATEMENT:  drop type;
2024-04-23 16:23:01.356 UTC client backend[9774] pg_regress/create_aggregate ERROR:  function numeric_avg_serialize(bytea, internal) does not exist
2024-04-23 16:23:01.356 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_serialize,
		deserialfunc = numeric_avg_serialize
	);
2024-04-23 16:23:01.357 UTC client backend[9790] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 35
2024-04-23 16:23:01.357 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE SEQUENCE tableam_seq_heap2 USING heap2;
2024-04-23 16:23:01.357 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  schema "test_schema_exists" does not exist
2024-04-23 16:23:01.357 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP SCHEMA test_schema_exists;
2024-04-23 16:23:01.357 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "314159" at character 11
2024-04-23 16:23:01.357 UTC client backend[9789] pg_regress/errors STATEMENT:  drop type 314159;
2024-04-23 16:23:01.359 UTC client backend[9774] pg_regress/create_aggregate ERROR:  function int4larger(internal, internal) does not exist
2024-04-23 16:23:01.359 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_serialize,
		deserialfunc = numeric_avg_deserialize,
		combinefunc = int4larger
	);
2024-04-23 16:23:01.359 UTC client backend[9789] pg_regress/errors ERROR:  type "nonesuch" does not exist
2024-04-23 16:23:01.359 UTC client backend[9789] pg_regress/errors STATEMENT:  drop type nonesuch;
2024-04-23 16:23:01.359 UTC client backend[9776] pg_regress/create_function_sql ERROR:  only superuser can define a leakproof function
2024-04-23 16:23:01.359 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  ALTER FUNCTION functest_E_2(int) LEAKPROOF;
2024-04-23 16:23:01.360 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 14
2024-04-23 16:23:01.360 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator;
2024-04-23 16:23:01.360 UTC client backend[9776] pg_regress/create_function_sql ERROR:  only superuser can define a leakproof function
2024-04-23 16:23:01.360 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_E_3(int) RETURNS bool LANGUAGE 'sql'
	       LEAKPROOF AS 'SELECT $1 < 200';
2024-04-23 16:23:01.362 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 21
2024-04-23 16:23:01.362 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator equals;
2024-04-23 16:23:01.364 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.364 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (2, -NULL-, -2).
2024-04-23 16:23:01.364 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,z) VALUES (2, -2);
2024-04-23 16:23:01.364 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 18
2024-04-23 16:23:01.364 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator ===;
2024-04-23 16:23:01.364 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  schema "test_schema_exists" does not exist
2024-04-23 16:23:01.364 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP SCHEMA test_schema_exists;
2024-04-23 16:23:01.366 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  type "test_type_exists" does not exist
2024-04-23 16:23:01.366 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TYPE test_type_exists;
2024-04-23 16:23:01.366 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "," at character 19
2024-04-23 16:23:01.366 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator int4, int4;
2024-04-23 16:23:01.370 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "(" at character 15
2024-04-23 16:23:01.370 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator (int4, int4);
2024-04-23 16:23:01.372 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.372 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (2, Y, -2).
2024-04-23 16:23:01.372 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y) VALUES ('Y');
2024-04-23 16:23:01.373 UTC client backend[9783] pg_regress/typed_table ERROR:  column "name" specified more than once
2024-04-23 16:23:01.373 UTC client backend[9783] pg_regress/typed_table STATEMENT:  CREATE TABLE persons4 OF person_type (
	    name WITH OPTIONS NOT NULL,
	    name WITH OPTIONS DEFAULT ''  -- error, specified more than once
	);
2024-04-23 16:23:01.373 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ")" at character 20
2024-04-23 16:23:01.373 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator === ();
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view1"
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing DISTINCT are not automatically updatable.
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view1;
2024-04-23 16:23:01.374 UTC client backend[9789] pg_regress/errors ERROR:  missing argument at character 24
2024-04-23 16:23:01.374 UTC client backend[9789] pg_regress/errors HINT:  Use NONE to denote the missing argument of a unary operator.
2024-04-23 16:23:01.374 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator === (int4);
2024-04-23 16:23:01.374 UTC client backend[9783] pg_regress/typed_table ERROR:  cannot drop type person_type because other objects depend on it
2024-04-23 16:23:01.374 UTC client backend[9783] pg_regress/typed_table DETAIL:  table persons depends on type person_type
	function get_all_persons() depends on type person_type
	table persons2 depends on type person_type
	table persons3 depends on type person_type
2024-04-23 16:23:01.374 UTC client backend[9783] pg_regress/typed_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:23:01.374 UTC client backend[9783] pg_regress/typed_table STATEMENT:  DROP TYPE person_type RESTRICT;
2024-04-23 16:23:01.374 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_check"
2024-04-23 16:23:01.374 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (1, -NULL-, -2).
2024-04-23 16:23:01.374 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,z) VALUES (1, -2);
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view2"
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing GROUP BY are not automatically updatable.
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.374 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view2;
2024-04-23 16:23:01.374 UTC client backend[9789] pg_regress/errors ERROR:  operator does not exist: integer === integer
2024-04-23 16:23:01.374 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator === (int4, int4);
2024-04-23 16:23:01.374 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  type "test_type_exists" does not exist
2024-04-23 16:23:01.374 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TYPE test_type_exists;
2024-04-23 16:23:01.375 UTC client backend[9789] pg_regress/errors ERROR:  missing argument at character 26
2024-04-23 16:23:01.375 UTC client backend[9789] pg_regress/errors HINT:  Use NONE to denote the missing argument of a unary operator.
2024-04-23 16:23:01.375 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator = (nonesuch);
2024-04-23 16:23:01.375 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view3"
2024-04-23 16:23:01.375 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing HAVING are not automatically updatable.
2024-04-23 16:23:01.375 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.375 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view3;
2024-04-23 16:23:01.376 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  type "test_domain_exists" does not exist
2024-04-23 16:23:01.376 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP DOMAIN test_domain_exists;
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate ERROR:  cannot change return type of existing function
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate HINT:  Use DROP AGGREGATE myavg(numeric) first.
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE myavg (numeric)
	(
		stype = numeric,
		sfunc = numeric_add,
		finalfunc = numeric_out
	);
2024-04-23 16:23:01.377 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "," at character 19
2024-04-23 16:23:01.377 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator = ( , int4);
2024-04-23 16:23:01.377 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.377 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, -5).
2024-04-23 16:23:01.377 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL VALUES (5, 'check failed', -5);
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view4"
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that return aggregate functions are not automatically updatable.
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view4;
2024-04-23 16:23:01.377 UTC client backend[9783] pg_regress/typed_table ERROR:  type stuff is not a composite type
2024-04-23 16:23:01.377 UTC client backend[9783] pg_regress/typed_table STATEMENT:  CREATE TABLE persons5 OF stuff;
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate ERROR:  cannot change routine kind
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate DETAIL:  "myavg" is an ordinary aggregate function.
2024-04-23 16:23:01.377 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE myavg (order by numeric)
	(
		stype = numeric,
		sfunc = numeric_add
	);
2024-04-23 16:23:01.377 UTC client backend[9789] pg_regress/errors ERROR:  type "nonesuch" does not exist
2024-04-23 16:23:01.377 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator = (nonesuch, int4);
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view5"
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that return window functions are not automatically updatable.
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.377 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view5;
2024-04-23 16:23:01.378 UTC client backend[9789] pg_regress/errors ERROR:  type "nonesuch" does not exist
2024-04-23 16:23:01.378 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator = (int4, nonesuch);
2024-04-23 16:23:01.378 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view6"
2024-04-23 16:23:01.378 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable.
2024-04-23 16:23:01.378 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.378 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view6;
2024-04-23 16:23:01.379 UTC client backend[9774] pg_regress/create_aggregate ERROR:  cannot change routine kind
2024-04-23 16:23:01.379 UTC client backend[9774] pg_regress/create_aggregate DETAIL:  "sum3" is a function.
2024-04-23 16:23:01.379 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE sum3 (int8,int8,int8)
	(
		stype = int8,
		sfunc = sum4
	);
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ")" at character 24
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors STATEMENT:  drop operator = (int4, );
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view7"
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing WITH are not automatically updatable.
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view7 SET a=a+1;
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 10
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors STATEMENT:  drop rule;
2024-04-23 16:23:01.379 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  type "test_domain_exists" does not exist
2024-04-23 16:23:01.379 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP DOMAIN test_domain_exists;
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view8"
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.379 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view8 SET a=a+1;
2024-04-23 16:23:01.379 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_check"
2024-04-23 16:23:01.379 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, 4).
2024-04-23 16:23:01.379 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y,z) VALUES ('check failed', 4);
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "314159" at character 11
2024-04-23 16:23:01.379 UTC client backend[9789] pg_regress/errors STATEMENT:  drop rule 314159;
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view9"
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view9 SET a=a+1;
2024-04-23 16:23:01.380 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.380 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, -5).
2024-04-23 16:23:01.380 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,y) VALUES (5, 'check failed');
2024-04-23 16:23:01.380 UTC client backend[9789] pg_regress/errors ERROR:  relation "noplace" does not exist
2024-04-23 16:23:01.380 UTC client backend[9789] pg_regress/errors STATEMENT:  drop rule nonesuch on noplace;
2024-04-23 16:23:01.380 UTC client backend[9774] pg_regress/create_aggregate ERROR:  parameter "parallel" must be SAFE, RESTRICTED, or UNSAFE
2024-04-23 16:23:01.380 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE mysum (int)
	(
		stype = int,
		sfunc = int4pl,
		parallel = pear
	);
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view10"
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view10 SET a=a+1;
2024-04-23 16:23:01.380 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "tuple" at character 6
2024-04-23 16:23:01.380 UTC client backend[9789] pg_regress/errors STATEMENT:  drop tuple rule nonesuch;
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view11"
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.380 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view11 SET a=a+1;
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "instance" at character 6
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors STATEMENT:  drop instance rule nonesuch on noplace;
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view12"
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view12 SET a=a+1;
2024-04-23 16:23:01.381 UTC client backend[9774] pg_regress/create_aggregate ERROR:  strictness of aggregate's forward and inverse transition functions must match
2024-04-23 16:23:01.381 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE invalidsumdouble (float8)
	(
	    stype = float8,
	    sfunc = float8pl,
	    mstype = float8,
	    msfunc = float8pl,
	    minvfunc = float8mi_n
	);
2024-04-23 16:23:01.381 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_u2" does not exist
2024-04-23 16:23:01.381 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP USER regress_test_u2;
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view13"
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO ro_view13 VALUES (3, 'Row 3');
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "rewrite" at character 6
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors STATEMENT:  drop rewrite rule nonesuch;
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view13"
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger.
2024-04-23 16:23:01.381 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO ro_view13 AS t USING (VALUES (1, 'Row 1')) AS v(a,b) ON t.a = v.a
	  WHEN MATCHED THEN DELETE;
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.381 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0;
2024-04-23 16:23:01.382 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_u1" does not exist
2024-04-23 16:23:01.382 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP USER regress_test_u1;
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate ERROR:  return type of inverse transition function float8mi_int is not double precision
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE wrongreturntype (float8)
	(
	    stype = float8,
	    sfunc = float8pl,
	    mstype = float8,
	    msfunc = float8pl,
	    minvfunc = float8mi_int
	);
2024-04-23 16:23:01.382 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view13"
2024-04-23 16:23:01.382 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.382 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view using MERGE, provide an INSTEAD OF UPDATE trigger.
2024-04-23 16:23:01.382 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO ro_view13 AS t USING (VALUES (2, 'Row 2')) AS v(a,b) ON t.a = v.a
	  WHEN MATCHED THEN UPDATE SET b = v.b;
2024-04-23 16:23:01.382 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.382 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1::int8/0;
2024-04-23 16:23:01.382 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.382 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (8, Y, -8).
2024-04-23 16:23:01.382 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y) VALUES ('Y');
2024-04-23 16:23:01.382 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_r2" does not exist
2024-04-23 16:23:01.382 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP ROLE regress_test_r2;
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Sfunc1" not recognized
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Basetype" not recognized
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Stype1" not recognized
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Initcond1" not recognized
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Parallel" not recognized
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate ERROR:  aggregate stype must be specified
2024-04-23 16:23:01.382 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE case_agg ( -- old syntax
		"Sfunc1" = int4pl,
		"Basetype" = int4,
		"Stype1" = int4,
		"Initcond1" = '0',
		"Parallel" = safe
	);
2024-04-23 16:23:01.383 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view13"
2024-04-23 16:23:01.383 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.383 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger.
2024-04-23 16:23:01.383 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO ro_view13 AS t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a
	  WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b);
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0::int8;
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Stype" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Sfunc" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc_extra" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc_modify" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate WARNING:  aggregate attribute "Parallel" not recognized
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate ERROR:  aggregate stype must be specified
2024-04-23 16:23:01.383 UTC client backend[9774] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE case_agg(float8)
	(
		"Stype" = internal,
		"Sfunc" = ordered_set_transition,
		"Finalfunc" = percentile_disc_final,
		"Finalfunc_extra" = true,
		"Finalfunc_modify" = read_write,
		"Parallel" = safe
	);
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1::int2/0;
2024-04-23 16:23:01.383 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_r1" does not exist
2024-04-23 16:23:01.383 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP ROLE regress_test_r1;
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.383 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0::int2;
2024-04-23 16:23:01.384 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into column "ctid" of view "rw_view14"
2024-04-23 16:23:01.384 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2024-04-23 16:23:01.384 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view14 VALUES (null, 3, 'Row 3');
2024-04-23 16:23:01.384 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_g2" does not exist
2024-04-23 16:23:01.384 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP GROUP regress_test_g2;
2024-04-23 16:23:01.384 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.384 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1::numeric/0;
2024-04-23 16:23:01.385 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.385 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0::numeric;
2024-04-23 16:23:01.385 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  role "regress_test_g1" does not exist
2024-04-23 16:23:01.385 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP GROUP regress_test_g1;
2024-04-23 16:23:01.385 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update column "ctid" of view "rw_view14"
2024-04-23 16:23:01.385 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2024-04-23 16:23:01.385 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE rw_view14 SET ctid=null WHERE a=3;
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1::float8/0;
2024-04-23 16:23:01.386 UTC client backend[9776] pg_regress/create_function_sql ERROR:  duplicate function body specified
2024-04-23 16:23:01.386 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_S_xxx(x int) RETURNS int
	    LANGUAGE SQL
	    AS $$ SELECT x * 2 $$
	    RETURN x * 3;
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0::float8;
2024-04-23 16:23:01.386 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  conversion "test_conversion_exists" does not exist
2024-04-23 16:23:01.386 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP CONVERSION test_conversion_exists;
2024-04-23 16:23:01.386 UTC client backend[9776] pg_regress/create_function_sql ERROR:  SQL function with unquoted function body cannot have polymorphic arguments
2024-04-23 16:23:01.386 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_S_xx(x anyarray) RETURNS anyelement
	    LANGUAGE SQL
	    RETURN x[1];
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.386 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1::float4/0;
2024-04-23 16:23:01.386 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "sys_col_check_tbl" violates check constraint "sys_col_check_tbl_check"
2024-04-23 16:23:01.386 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (Olympia, Washington, t, 100).
2024-04-23 16:23:01.386 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO SYS_COL_CHECK_TBL VALUES ('Olympia', 'Washington', true, 100);
2024-04-23 16:23:01.387 UTC client backend[9789] pg_regress/errors ERROR:  division by zero
2024-04-23 16:23:01.387 UTC client backend[9789] pg_regress/errors STATEMENT:  select 1/0::float4;
2024-04-23 16:23:01.387 UTC client backend[9776] pg_regress/create_function_sql ERROR:  operator does not exist: date > integer at character 85
2024-04-23 16:23:01.387 UTC client backend[9776] pg_regress/create_function_sql HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:23:01.387 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_S_xx(x date) RETURNS boolean
	    LANGUAGE SQL
	    RETURN x > 1;
2024-04-23 16:23:01.387 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "xxx" at character 1
2024-04-23 16:23:01.387 UTC client backend[9789] pg_regress/errors STATEMENT:  xxx;
2024-04-23 16:23:01.387 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot merge into column "ctid" of view "rw_view14"
2024-04-23 16:23:01.387 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2024-04-23 16:23:01.387 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO rw_view14  AS t
	  USING (VALUES (2, 'Merged row 2'), (3, 'Merged row 3')) AS v(a,b) ON t.a = v.a
	  WHEN MATCHED THEN UPDATE SET b = v.b  -- should be OK, except...
	  WHEN NOT MATCHED THEN INSERT VALUES (null, v.a, v.b);
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "foo" at character 8
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE foo;
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near ";" at character 14
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE ;
2024-04-23 16:23:01.388 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  text search parser "test_tsparser_exists" does not exist
2024-04-23 16:23:01.388 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH PARSER test_tsparser_exists;
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at end of input at character 13
2024-04-23 16:23:01.388 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "foo" at character 29
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors STATEMENT:  INSERT INTO foo VALUES(123) foo;
2024-04-23 16:23:01.389 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  text search dictionary "test_tsdict_exists" does not exist
2024-04-23 16:23:01.389 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH DICTIONARY test_tsdict_exists;
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "123" at character 13
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors STATEMENT:  INSERT INTO 123
	VALUES(123);
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "123" at character 29
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors STATEMENT:  INSERT INTO foo
	VALUES(123) 123
	;
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 94
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE foo
	  (id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY,
		id3 INTEGER NOT NUL,
	   id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL);
2024-04-23 16:23:01.389 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2024-04-23 16:23:01.389 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2024-04-23 16:23:01.389 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 VALUES (3, 'ROW 3');
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 90
2024-04-23 16:23:01.389 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL,
	id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL);
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 35
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE foo(
	id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY);
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 90
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE TABLE foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL);
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 100
2024-04-23 16:23:01.390 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE
	TEMPORARY
	TABLE
	foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL,
	id4 INT4
	UNIQUE
	NOT
	NULL,
	id5 TEXT
	UNIQUE
	NOT
	NULL)
	;
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 45
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE
	TEMPORARY
	TABLE
	foo(
	id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY)
	;
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 153
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE
	TEMPORARY
	TABLE
	foo
	(id
	INT4
	UNIQUE NOT NULL, idx INT4 UNIQUE NOT NULL, idy INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL,
	idz INT4 UNIQUE NOT NULL,
	idv INT4 UNIQUE NOT NULL);
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 180
2024-04-23 16:23:01.391 UTC client backend[9789] pg_regress/errors STATEMENT:  CREATE
	TEMPORARY
	TABLE
	foo
	(id
	INT4
	UNIQUE
	NOT
	NULL
	,
	idm
	INT4
	UNIQUE
	NOT
	NULL,
	idx INT4 UNIQUE NOT NULL, idy INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL,
	idz INT4 UNIQUE NOT NULL,
	idv
	INT4
	UNIQUE
	NOT
	NULL);
2024-04-23 16:23:01.392 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2024-04-23 16:23:01.392 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2024-04-23 16:23:01.392 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 (a) VALUES (3) ON CONFLICT (a) DO UPDATE set upper = 'blarg';
2024-04-23 16:23:01.392 UTC client backend[9781] pg_regress/inherit ERROR:  null value in column "aa" of relation "z" violates not-null constraint
2024-04-23 16:23:01.392 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (null, text).
2024-04-23 16:23:01.392 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO z VALUES (NULL, 'text');
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 (a) VALUES (4);
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update column "upper" of view "rw_view15"
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2024-04-23 16:23:01.393 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE rw_view15 SET upper='ROW 3' WHERE a=3;
2024-04-23 16:23:01.394 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update column "upper" of view "rw_view15"
2024-04-23 16:23:01.394 UTC client backend[9793] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2024-04-23 16:23:01.394 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE rw_view15 SET upper=DEFAULT WHERE a=3;
2024-04-23 16:23:01.395 UTC client backend[9793] pg_regress/updatable_views ERROR:  multiple assignments to same column "a"
2024-04-23 16:23:01.395 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view16 VALUES (3, 'Row 3', 3);
2024-04-23 16:23:01.395 UTC client backend[9793] pg_regress/updatable_views ERROR:  multiple assignments to same column "a"
2024-04-23 16:23:01.395 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE rw_view16 SET a=3, aa=-3 WHERE a=3;
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view1"
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views containing DISTINCT are not automatically updatable.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO ro_view17 VALUES (3, 'ROW 3');
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view18"
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view18;
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view19"
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view19 SET last_value=1000;
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "ro_view20"
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views that return set-returning functions are not automatically updatable.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.396 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE ro_view20 SET b=upper(b);
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot insert into view "rw_view16"
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view16 (a, b) VALUES (3, 'Row 3');
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot update view "rw_view16"
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  UPDATE rw_view16 SET b='ROW 2' WHERE a=2;
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot delete from view "rw_view16"
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views HINT:  To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view16 WHERE a=2;
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot execute MERGE on relation "rw_view16"
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views DETAIL:  MERGE is not supported for relations with rules.
2024-04-23 16:23:01.398 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO rw_view16 AS t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a
	  WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b);
2024-04-23 16:23:01.409 UTC client backend[9795] pg_regress/constraints ERROR:  system column "ctid" reference in check constraint is invalid at character 138
2024-04-23 16:23:01.409 UTC client backend[9795] pg_regress/constraints STATEMENT:  CREATE TABLE SYS_COL_CHECK_TBL (city text, state text, is_capital bool,
	                  altitude int,
					  CHECK (NOT (is_capital AND ctid::text = 'sys_col_check_tbl')));
2024-04-23 16:23:01.418 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "check_fkeys2_pkey_bad" for table "fkeys2" does not exist
2024-04-23 16:23:01.418 UTC client backend[9778] pg_regress/triggers STATEMENT:  COMMENT ON TRIGGER check_fkeys2_pkey_bad ON fkeys2 IS 'wrong';
2024-04-23 16:23:01.422 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  text search template "test_tstemplate_exists" does not exist
2024-04-23 16:23:01.422 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH TEMPLATE test_tstemplate_exists;
2024-04-23 16:23:01.422 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  text search configuration "test_tsconfig_exists" does not exist
2024-04-23 16:23:01.422 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH CONFIGURATION test_tsconfig_exists;
2024-04-23 16:23:01.430 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_child_check"
2024-04-23 16:23:01.430 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (7, -NULL-, -7, 42, 6).
2024-04-23 16:23:01.430 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6);
2024-04-23 16:23:01.432 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_tbl_check"
2024-04-23 16:23:01.432 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (6, -NULL-, -7, 42, 7).
2024-04-23 16:23:01.432 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7);
2024-04-23 16:23:01.433 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  extension "test_extension_exists" does not exist
2024-04-23 16:23:01.433 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP EXTENSION test_extension_exists;
2024-04-23 16:23:01.433 UTC client backend[9778] pg_regress/triggers ERROR:  tuple references non-existent key
2024-04-23 16:23:01.433 UTC client backend[9778] pg_regress/triggers DETAIL:  Trigger "check_fkeys2_pkey_exist" found tuple referencing non-existent key in "pkeys".
2024-04-23 16:23:01.433 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into fkeys2 values (70, '5', 3);
2024-04-23 16:23:01.434 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.434 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (6, check failed, -6, 42, 7).
2024-04-23 16:23:01.434 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7);
2024-04-23 16:23:01.435 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  function test_function_exists() does not exist
2024-04-23 16:23:01.435 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_function_exists();
2024-04-23 16:23:01.438 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  function test_function_exists(integer, text, integer[]) does not exist
2024-04-23 16:23:01.438 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_function_exists(int, text, int[]);
2024-04-23 16:23:01.440 UTC client backend[9776] pg_regress/create_function_sql ERROR:  could not find a function named "functest_b_1"
2024-04-23 16:23:01.440 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  DROP FUNCTION functest_b_1;
2024-04-23 16:23:01.440 UTC client backend[9778] pg_regress/triggers ERROR:  tuple references non-existent key
2024-04-23 16:23:01.440 UTC client backend[9778] pg_regress/triggers DETAIL:  Trigger "check_fkeys_pkey_exist" found tuple referencing non-existent key in "pkeys".
2024-04-23 16:23:01.440 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into fkeys values (70, '5', 1);
2024-04-23 16:23:01.441 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  aggregate test_aggregate_exists(*) does not exist
2024-04-23 16:23:01.441 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP AGGREGATE test_aggregate_exists(*);
2024-04-23 16:23:01.441 UTC client backend[9776] pg_regress/create_function_sql ERROR:  function name "functest_b_2" is not unique
2024-04-23 16:23:01.441 UTC client backend[9776] pg_regress/create_function_sql HINT:  Specify the argument list to select the function unambiguously.
2024-04-23 16:23:01.441 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  DROP FUNCTION functest_b_2;
2024-04-23 16:23:01.441 UTC client backend[9796] pg_regress/vacuum ERROR:  ANALYZE cannot be executed from VACUUM or ANALYZE
2024-04-23 16:23:01.441 UTC client backend[9796] pg_regress/vacuum CONTEXT:  SQL function "do_analyze" statement 1
	SQL function "wrap_do_analyze" statement 1
2024-04-23 16:23:01.441 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE vaccluster;
2024-04-23 16:23:01.441 UTC client backend[9778] pg_regress/triggers ERROR:  tuple references non-existent key
2024-04-23 16:23:01.441 UTC client backend[9778] pg_regress/triggers DETAIL:  Trigger "check_fkeys_pkey2_exist" found tuple referencing non-existent key in "fkeys2".
2024-04-23 16:23:01.441 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into fkeys values (60, '6', 4);
2024-04-23 16:23:01.442 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  aggregate test_aggregate_exists(integer) does not exist
2024-04-23 16:23:01.442 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP AGGREGATE test_aggregate_exists(int);
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers ERROR:  "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys"
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers CONTEXT:  SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 "
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers STATEMENT:  delete from pkeys where pkey1 = 30 and pkey2 = '3';
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql ERROR:  cannot change routine kind
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql DETAIL:  "functest1" is a function.
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE OR REPLACE FUNCTION functest1(a int) RETURNS int LANGUAGE SQL WINDOW AS 'SELECT $1';
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql ERROR:  cannot change routine kind
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql DETAIL:  "functest1" is a function.
2024-04-23 16:23:01.442 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE OR REPLACE PROCEDURE functest1(a int) LANGUAGE SQL AS 'SELECT $1';
2024-04-23 16:23:01.442 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  operator does not exist: integer @#@ integer
2024-04-23 16:23:01.442 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR @#@ (int, int);
2024-04-23 16:23:01.442 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test_check"
2024-04-23 16:23:01.442 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (-3).
2024-04-23 16:23:01.442 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST) VALUES (-3);
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers ERROR:  "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys"
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers CONTEXT:  SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 "
2024-04-23 16:23:01.442 UTC client backend[9778] pg_regress/triggers STATEMENT:  update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 50 and pkey2 = '5';
2024-04-23 16:23:01.447 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  language "test_language_exists" does not exist
2024-04-23 16:23:01.447 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP LANGUAGE test_language_exists;
2024-04-23 16:23:01.449 UTC client backend[9790] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2024-04-23 16:23:01.449 UTC client backend[9790] pg_regress/create_am STATEMENT:  ALTER TABLE heaptable SET ACCESS METHOD heap, SET ACCESS METHOD heap2;
2024-04-23 16:23:01.449 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  cast from type text to type text does not exist
2024-04-23 16:23:01.449 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP CAST (text AS text);
2024-04-23 16:23:01.451 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "atacc2" violates check constraint "atacc1_test_check"
2024-04-23 16:23:01.451 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (-3, null).
2024-04-23 16:23:01.451 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO ATACC2 (TEST) VALUES (-3);
2024-04-23 16:23:01.451 UTC client backend[9790] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2024-04-23 16:23:01.451 UTC client backend[9790] pg_regress/create_am STATEMENT:  ALTER TABLE heaptable SET ACCESS METHOD DEFAULT, SET ACCESS METHOD heap2;
2024-04-23 16:23:01.452 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test_check"
2024-04-23 16:23:01.452 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (-3, null).
2024-04-23 16:23:01.452 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST) VALUES (-3);
2024-04-23 16:23:01.452 UTC client backend[9790] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2024-04-23 16:23:01.452 UTC client backend[9790] pg_regress/create_am STATEMENT:  ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap, SET ACCESS METHOD heap2;
2024-04-23 16:23:01.455 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test2_check"
2024-04-23 16:23:01.455 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (null, 3).
2024-04-23 16:23:01.455 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST2) VALUES (3);
2024-04-23 16:23:01.461 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  trigger "test_trigger_exists" for table "test_exists" does not exist
2024-04-23 16:23:01.461 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON test_exists;
2024-04-23 16:23:01.465 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  relation "no_such_table" does not exist
2024-04-23 16:23:01.465 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON no_such_table;
2024-04-23 16:23:01.465 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  schema "no_such_schema" does not exist
2024-04-23 16:23:01.465 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON no_such_schema.no_such_table;
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  rule "test_rule_exists" for relation "test_exists" does not exist
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON test_exists;
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  relation "no_such_table" does not exist
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON no_such_table;
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  schema "no_such_schema" does not exist
2024-04-23 16:23:01.466 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON no_such_schema.no_such_table;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  foreign-data wrapper "test_fdw_exists" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP FOREIGN DATA WRAPPER test_fdw_exists;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  server "test_server_exists" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP SERVER test_server_exists;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  operator class "test_operator_class" does not exist for access method "btree"
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS test_operator_class USING btree;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS test_operator_class USING no_such_am;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS IF EXISTS test_operator_class USING no_such_am;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  operator family "test_operator_family" does not exist for access method "btree"
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY test_operator_family USING btree;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY test_operator_family USING no_such_am;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY IF EXISTS test_operator_family USING no_such_am;
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2024-04-23 16:23:01.470 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP ACCESS METHOD no_such_am;
2024-04-23 16:23:01.471 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  table "test_exists" does not exist
2024-04-23 16:23:01.471 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP TABLE test_exists;
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  function name "test_ambiguous_funcname" is not unique
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists HINT:  Specify the argument list to select the function unambiguously.
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_ambiguous_funcname;
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  function name "test_ambiguous_funcname" is not unique
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists HINT:  Specify the argument list to select the function unambiguously.
2024-04-23 16:23:01.474 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION IF EXISTS test_ambiguous_funcname;
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  procedure name "test_ambiguous_procname" is not unique
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists HINT:  Specify the argument list to select the procedure unambiguously.
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP PROCEDURE test_ambiguous_procname;
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  procedure name "test_ambiguous_procname" is not unique
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists HINT:  Specify the argument list to select the procedure unambiguously.
2024-04-23 16:23:01.475 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP PROCEDURE IF EXISTS test_ambiguous_procname;
2024-04-23 16:23:01.476 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  routine name "test_ambiguous_procname" is not unique
2024-04-23 16:23:01.476 UTC client backend[9784] pg_regress/drop_if_exists HINT:  Specify the argument list to select the routine unambiguously.
2024-04-23 16:23:01.476 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  DROP ROUTINE IF EXISTS test_ambiguous_procname;
2024-04-23 16:23:01.497 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  database "test_database_exists" does not exist
2024-04-23 16:23:01.497 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  drop database test_database_exists (force);
2024-04-23 16:23:01.498 UTC client backend[9784] pg_regress/drop_if_exists ERROR:  database "test_database_exists" does not exist
2024-04-23 16:23:01.498 UTC client backend[9784] pg_regress/drop_if_exists STATEMENT:  drop database test_database_exists with (force);
2024-04-23 16:23:01.500 UTC client backend[9795] pg_regress/constraints ERROR:  column "a" of relation "atacc3" contains null values
2024-04-23 16:23:01.500 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE ATACC1 ADD CONSTRAINT ditto NOT NULL a;
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql ERROR:  return type mismatch in function declared to return integer
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql DETAIL:  Actual return type is text.
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql CONTEXT:  SQL function "test1"
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT ''not an integer'';';
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql ERROR:  syntax error at or near "not" at character 62
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'not even SQL';
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql ERROR:  return type mismatch in function declared to return integer
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql DETAIL:  Final statement must return exactly one column.
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql CONTEXT:  SQL function "test1"
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT 1, 2, 3;';
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql ERROR:  there is no parameter $2 at character 69
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT $2;';
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql ERROR:  only one AS item needed for language "sql"
2024-04-23 16:23:01.503 UTC client backend[9776] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'a', 'b';
2024-04-23 16:23:01.508 UTC client backend[9796] pg_regress/vacuum ERROR:  ANALYZE cannot be executed from VACUUM or ANALYZE
2024-04-23 16:23:01.508 UTC client backend[9796] pg_regress/vacuum CONTEXT:  SQL function "do_analyze" statement 1
	SQL function "wrap_do_analyze" statement 1
2024-04-23 16:23:01.508 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM FULL vaccluster;
2024-04-23 16:23:01.520 UTC client backend[9778] pg_regress/triggers ERROR:  ttdummy (tttest): you cannot change price_on and/or price_off columns (use set_ttdummy)
2024-04-23 16:23:01.520 UTC client backend[9778] pg_regress/triggers STATEMENT:  update tttest set price_on = -1 where price_id = 1;
2024-04-23 16:23:01.527 UTC client backend[9795] pg_regress/constraints ERROR:  cannot add NOT NULL constraint to column "a" of relation "atacc2" with inheritance children
2024-04-23 16:23:01.527 UTC client backend[9795] pg_regress/constraints DETAIL:  Existing constraint "a_is_not_null" is marked NO INHERIT.
2024-04-23 16:23:01.527 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE ATACC2 INHERIT ATACC1;
2024-04-23 16:23:01.570 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.570 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (8, try again, -8).
2024-04-23 16:23:01.570 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y,z) SELECT yd, -8 FROM tmp WHERE yd = 'try again';
2024-04-23 16:23:01.625 UTC client backend[9790] pg_regress/create_am ERROR:  zero-length delimited identifier at or near """" at character 37
2024-04-23 16:23:01.625 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "";
2024-04-23 16:23:01.626 UTC client backend[9790] pg_regress/create_am ERROR:  access method "i_do_not_exist_am" does not exist
2024-04-23 16:23:01.626 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING i_do_not_exist_am;
2024-04-23 16:23:01.626 UTC client backend[9790] pg_regress/create_am ERROR:  access method "I do not exist AM" does not exist
2024-04-23 16:23:01.626 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "I do not exist AM";
2024-04-23 16:23:01.627 UTC client backend[9790] pg_regress/create_am ERROR:  access method "btree" is not of type TABLE
2024-04-23 16:23:01.627 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "btree";
2024-04-23 16:23:01.627 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2024-04-23 16:23:01.627 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (-4, Y, 4).
2024-04-23 16:23:01.627 UTC client backend[9795] pg_regress/constraints STATEMENT:  UPDATE INSERT_TBL SET x = z, z = x;
2024-04-23 16:23:01.627 UTC client backend[9790] pg_regress/create_am ERROR:  "tableam_parted_a_heap2" is not partitioned
2024-04-23 16:23:01.627 UTC client backend[9790] pg_regress/create_am STATEMENT:  CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x;
2024-04-23 16:23:01.629 UTC client backend[9790] pg_regress/create_am ERROR:  cannot drop access method heap2 because other objects depend on it
2024-04-23 16:23:01.629 UTC client backend[9790] pg_regress/create_am DETAIL:  table tableam_tbl_heap2 depends on access method heap2
	table tableam_tblas_heap2 depends on access method heap2
	materialized view tableam_tblmv_heap2 depends on access method heap2
	table tableam_parted_b_heap2 depends on access method heap2
	table tableam_parted_d_heap2 depends on access method heap2
2024-04-23 16:23:01.629 UTC client backend[9790] pg_regress/create_am HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:23:01.629 UTC client backend[9790] pg_regress/create_am STATEMENT:  DROP ACCESS METHOD heap2;
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers ERROR:  duplicate trigger events specified at or near "ON" at character 63
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_upd_and_col BEFORE UPDATE OR UPDATE OF a ON main_table
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_upd_and_col');
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers ERROR:  column "a" specified more than once
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_upd_a_a BEFORE UPDATE OF a, a ON main_table
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_upd_a_a');
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers ERROR:  syntax error at or near "OF" at character 42
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_ins_a BEFORE INSERT OF a ON main_table
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_ins_a');
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers ERROR:  INSERT trigger's WHEN condition cannot reference OLD values at character 88
2024-04-23 16:23:01.833 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_ins_when BEFORE INSERT OR UPDATE ON main_table
	FOR EACH ROW WHEN (OLD.a <> NEW.a)
	EXECUTE PROCEDURE trigger_func('error_ins_old');
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers ERROR:  DELETE trigger's WHEN condition cannot reference NEW values at character 97
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_del_when BEFORE DELETE OR UPDATE ON main_table
	FOR EACH ROW WHEN (OLD.a <> NEW.a)
	EXECUTE PROCEDURE trigger_func('error_del_new');
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers ERROR:  BEFORE trigger's WHEN condition cannot reference NEW system columns at character 88
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_del_when BEFORE INSERT OR UPDATE ON main_table
	FOR EACH ROW WHEN (NEW.tableoid <> 0)
	EXECUTE PROCEDURE trigger_func('error_when_sys_column');
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers ERROR:  statement trigger's WHEN condition cannot reference column values at character 90
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER error_stmt_when BEFORE UPDATE OF a ON main_table
	FOR EACH STATEMENT WHEN (OLD.* IS DISTINCT FROM NEW.*)
	EXECUTE PROCEDURE trigger_func('error_stmt_when');
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers ERROR:  cannot drop column b of table main_table because other objects depend on it
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers DETAIL:  trigger after_upd_b_row_trig on table main_table depends on column b of table main_table
	trigger after_upd_a_b_row_trig on table main_table depends on column b of table main_table
	trigger after_upd_b_stmt_trig on table main_table depends on column b of table main_table
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:23:01.834 UTC client backend[9778] pg_regress/triggers STATEMENT:  ALTER TABLE main_table DROP COLUMN b;
2024-04-23 16:23:01.912 UTC client backend[9795] pg_regress/constraints ERROR:  new row for relation "copy_tbl" violates check constraint "copy_con"
2024-04-23 16:23:01.912 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (7, check failed, 6).
2024-04-23 16:23:01.912 UTC client backend[9795] pg_regress/constraints CONTEXT:  COPY copy_tbl, line 2: "7	check failed	6"
2024-04-23 16:23:01.912 UTC client backend[9795] pg_regress/constraints STATEMENT:  COPY COPY_TBL FROM '/Users/admin/pgsql/src/test/regress/data/constrf.data';
2024-04-23 16:23:01.923 UTC client backend[9781] pg_regress/inherit ERROR:  column "tomorrow" inherits conflicting default values
2024-04-23 16:23:01.923 UTC client backend[9781] pg_regress/inherit HINT:  To resolve the conflict, specify a default explicitly.
2024-04-23 16:23:01.923 UTC client backend[9781] pg_regress/inherit STATEMENT:  CREATE TABLE otherchild () INHERITS (firstparent, thirdparent);
2024-04-23 16:23:01.949 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "primary_tbl_pkey"
2024-04-23 16:23:01.949 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:01.949 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL VALUES (1, 'three');
2024-04-23 16:23:01.952 UTC client backend[9795] pg_regress/constraints ERROR:  null value in column "i" of relation "primary_tbl" violates not-null constraint
2024-04-23 16:23:01.952 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (null, six).
2024-04-23 16:23:01.952 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL (t) VALUES ('six');
2024-04-23 16:23:01.964 UTC client backend[9781] pg_regress/inherit ERROR:  cannot alter inherited column "f1" of relation "childtab"
2024-04-23 16:23:01.964 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table parent1 alter column f1 type bigint;
2024-04-23 16:23:01.971 UTC client backend[9796] pg_regress/vacuum ERROR:  parallel workers for vacuum must be between 0 and 1024 at character 9
2024-04-23 16:23:01.971 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL -1) pvactst;
2024-04-23 16:23:01.973 UTC client backend[9796] pg_regress/vacuum ERROR:  VACUUM FULL cannot be performed in parallel
2024-04-23 16:23:01.973 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL 2, FULL TRUE) pvactst;
2024-04-23 16:23:01.973 UTC client backend[9796] pg_regress/vacuum ERROR:  parallel option requires a value between 0 and 1024 at character 9
2024-04-23 16:23:01.973 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL) pvactst;
2024-04-23 16:23:01.974 UTC client backend[9795] pg_regress/constraints ERROR:  null value in column "i" of relation "primary_tbl" violates not-null constraint
2024-04-23 16:23:01.974 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (null, six).
2024-04-23 16:23:01.974 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL (t) VALUES ('six');
2024-04-23 16:23:01.976 UTC client backend[9796] pg_regress/vacuum WARNING:  disabling parallel option of vacuum on "tmp" --- cannot vacuum temporary tables in parallel
2024-04-23 16:23:01.986 UTC client backend[9781] pg_regress/inherit ERROR:  constraint "p2chk" conflicts with inherited constraint on relation "c2"
2024-04-23 16:23:01.986 UTC client backend[9781] pg_regress/inherit STATEMENT:  create table c2 (constraint p2chk check (ff1 > 10) no inherit) inherits (p1);
2024-04-23 16:23:02.005 UTC client backend[9793] pg_regress/updatable_views ERROR:  cannot execute MERGE on relation "rw_view1"
2024-04-23 16:23:02.005 UTC client backend[9793] pg_regress/updatable_views DETAIL:  MERGE is not supported for relations with rules.
2024-04-23 16:23:02.005 UTC client backend[9793] pg_regress/updatable_views STATEMENT:  MERGE INTO rw_view2 t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a
	  WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b);
2024-04-23 16:23:02.245 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.245 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:02.245 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'three');
2024-04-23 16:23:02.261 UTC client backend[9795] pg_regress/constraints ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2024-04-23 16:23:02.261 UTC client backend[9795] pg_regress/constraints HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2024-04-23 16:23:02.261 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'a'), (2, 'b'), (2, 'b') ON CONFLICT (i) DO UPDATE SET t = 'fails';
2024-04-23 16:23:02.292 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.292 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:02.292 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'three');
2024-04-23 16:23:02.299 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.299 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(null) already exists.
2024-04-23 16:23:02.299 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL (t) VALUES ('seven');
2024-04-23 16:23:02.299 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "ac" violates check constraint "ac_check"
2024-04-23 16:23:02.299 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (null).
2024-04-23 16:23:02.299 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into ac (aa) values (NULL);
2024-04-23 16:23:02.316 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "bc" violates check constraint "ac_check"
2024-04-23 16:23:02.316 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (null, null).
2024-04-23 16:23:02.316 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into bc (aa) values (NULL);
2024-04-23 16:23:02.319 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "ac_check" of relation "bc"
2024-04-23 16:23:02.319 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table bc drop constraint ac_check;
2024-04-23 16:23:02.335 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "ac" violates check constraint "ac_aa_check"
2024-04-23 16:23:02.335 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (null).
2024-04-23 16:23:02.335 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into ac (aa) values (NULL);
2024-04-23 16:23:02.337 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "bc" violates check constraint "ac_aa_check"
2024-04-23 16:23:02.337 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (null, null).
2024-04-23 16:23:02.337 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into bc (aa) values (NULL);
2024-04-23 16:23:02.338 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "ac_aa_check" of relation "bc"
2024-04-23 16:23:02.338 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table bc drop constraint ac_aa_check;
2024-04-23 16:23:02.339 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_t_key"
2024-04-23 16:23:02.339 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i, t)=(1, one) already exists.
2024-04-23 16:23:02.339 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'one');
TRAP: failed Assert("!TTS_EMPTY(slot)"), File: "../src/backend/executor/execTuples.c", Line: 1737, PID: 9793
2024-04-23 16:23:02.357 UTC client backend[9796] pg_regress/vacuum ERROR:  null value in column "i" of relation "vac_truncate_test" violates not-null constraint
2024-04-23 16:23:02.357 UTC client backend[9796] pg_regress/vacuum DETAIL:  Failing row contains (null, null).
2024-04-23 16:23:02.357 UTC client backend[9796] pg_regress/vacuum STATEMENT:  INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL);
2024-04-23 16:23:02.362 UTC client backend[9781] pg_regress/inherit ERROR:  check constraint "cc" of relation "c1" is violated by some row
2024-04-23 16:23:02.362 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table p2 add constraint cc check (f2>0);
2024-04-23 16:23:02.362 UTC client backend[9781] pg_regress/inherit ERROR:  check constraint "p2_f2_check" of relation "c1" is violated by some row
2024-04-23 16:23:02.362 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table p2 add check (f2>0);
2024-04-23 16:23:02.363 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "c1" violates check constraint "p2_f2_check"
2024-04-23 16:23:02.363 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (1, -1, 2).
2024-04-23 16:23:02.363 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into c1 values(1,-1,2);
0   postgres                            0x000000010449b138 ExceptionalCondition + 108
1   postgres                            0x00000001041d77f8 ExecFetchSlotMinimalTuple + 0
2   postgres                            0x00000001041a69c4 ExecIRDeleteTriggers + 200
3   postgres                            0x00000001041f781c ExecModifyTable + 2828
4   postgres                            0x00000001041d204c ExecProcNodeFirst + 56
5   postgres                            0x00000001041cb360 standard_ExecutorRun + 300
6   postgres                            0x00000001041cb22c ExecutorRun + 36
7   postgres                            0x000000010436e178 ProcessQuery + 160
8   postgres                            0x000000010436d824 PortalRunMulti + 412
9   postgres                            0x000000010436d3e8 FillPortalStore + 128
10  postgres                            0x000000010436d15c PortalRun + 436
11  postgres                            0x000000010436c118 exec_simple_query + 1208
12  postgres                            0x0000000104369e9c PostgresMain + 3484
13  postgres                            0x0000000104365608 BackendInitialize + 0
14  postgres                            0x00000001042cd2c0 PgArchShmemSize + 0
15  postgres                            0x00000001042d19ec ServerLoop + 7404
16  postgres                            0x00000001042cf44c InitProcessGlobals + 0
17  postgres                            0x0000000104220d6c help + 0
18  dyld                                0x00000001a1833f28 start + 2236
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE INSERT ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row');
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.452 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE UPDATE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row');
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE DELETE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row');
2024-04-23 16:23:02.453 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.453 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:02.453 UTC client backend[9795] pg_regress/constraints STATEMENT:  UPDATE unique_tbl SET i = 1 WHERE i = 0;
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.453 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER INSERT ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row');
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER UPDATE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row');
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER DELETE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row');
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have TRUNCATE triggers.
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE TRUNCATE ON main_view
	EXECUTE PROCEDURE trigger_func('before_tru_row');
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers ERROR:  "main_view" is a view
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers DETAIL:  Views cannot have TRUNCATE triggers.
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER TRUNCATE ON main_view
	EXECUTE PROCEDURE trigger_func('before_tru_row');
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers ERROR:  "main_table" is a table
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2024-04-23 16:23:02.454 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF INSERT ON main_table
	FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_ins');
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers ERROR:  "main_table" is a table
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_table
	FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_upd');
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers ERROR:  "main_table" is a table
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF DELETE ON main_table
	FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_del');
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers ERROR:  INSTEAD OF triggers cannot have WHEN conditions
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view
	FOR EACH ROW WHEN (OLD.a <> NEW.a) EXECUTE PROCEDURE view_trigger('instead_of_upd');
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers ERROR:  INSTEAD OF triggers cannot have column lists
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF UPDATE OF a ON main_view
	FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_upd');
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers ERROR:  INSTEAD OF triggers must be FOR EACH ROW
2024-04-23 16:23:02.455 UTC client backend[9778] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view
	EXECUTE PROCEDURE view_trigger('instead_of_upd');
2024-04-23 16:23:02.489 UTC client backend[9796] pg_regress/vacuum ERROR:  column "a" of relation "vacparted" appears more than once
2024-04-23 16:23:02.489 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM ANALYZE vacparted(a,b,a);
2024-04-23 16:23:02.489 UTC client backend[9796] pg_regress/vacuum ERROR:  column "b" of relation "vacparted" appears more than once
2024-04-23 16:23:02.489 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE vacparted(a,b,b);
2024-04-23 16:23:02.690 UTC client backend[9781] pg_regress/inherit ERROR:  cannot rename inherited column "b"
2024-04-23 16:23:02.690 UTC client backend[9781] pg_regress/inherit STATEMENT:  ALTER TABLE inht1 RENAME b TO bb;
2024-04-23 16:23:02.691 UTC client backend[9781] pg_regress/inherit ERROR:  cannot rename inherited column "aa"
2024-04-23 16:23:02.691 UTC client backend[9781] pg_regress/inherit STATEMENT:  ALTER TABLE inhts RENAME aa TO aaa;
2024-04-23 16:23:02.712 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.712 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2024-04-23 16:23:02.712 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMIT;
2024-04-23 16:23:02.713 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.713 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2024-04-23 16:23:02.713 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO unique_tbl VALUES (3, 'Three');
2024-04-23 16:23:02.714 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.714 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2024-04-23 16:23:02.714 UTC client backend[9795] pg_regress/constraints STATEMENT:  SET CONSTRAINTS ALL IMMEDIATE;
2024-04-23 16:23:02.714 UTC client backend[9778] pg_regress/triggers ERROR:  No such country: "Japon"
2024-04-23 16:23:02.714 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function city_update() line 9 at RAISE
2024-04-23 16:23:02.714 UTC client backend[9778] pg_regress/triggers STATEMENT:  UPDATE city_view SET country_name = 'Japon' WHERE city_name = 'Tokyo';
2024-04-23 16:23:02.720 UTC client backend[9781] pg_regress/inherit ERROR:  cannot rename inherited column "b"
2024-04-23 16:23:02.720 UTC client backend[9781] pg_regress/inherit STATEMENT:  ALTER TABLE inht1 RENAME b TO bb;
2024-04-23 16:23:02.729 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key"
2024-04-23 16:23:02.729 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:02.729 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO parted_uniq_tbl VALUES (1);
2024-04-23 16:23:02.753 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key"
2024-04-23 16:23:02.753 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2024-04-23 16:23:02.753 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMIT;
2024-04-23 16:23:02.754 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.754 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM vacparted, does_not_exist;
2024-04-23 16:23:02.757 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.757 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (FREEZE) does_not_exist, vaccluster;
2024-04-23 16:23:02.759 UTC client backend[9796] pg_regress/vacuum ERROR:  column "does_not_exist" of relation "vactst" does not exist
2024-04-23 16:23:02.759 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM ANALYZE vactst (does_not_exist), vacparted (b);
2024-04-23 16:23:02.765 UTC client backend[9796] pg_regress/vacuum ERROR:  ANALYZE option must be specified when a column list is provided
2024-04-23 16:23:02.765 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM FULL vactst, vacparted (a, b), vaccluster (i);
2024-04-23 16:23:02.772 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.772 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE vactst, does_not_exist, vacparted;
2024-04-23 16:23:02.773 UTC client backend[9796] pg_regress/vacuum ERROR:  column "does_not_exist" of relation "vacparted" does not exist
2024-04-23 16:23:02.773 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE vactst (i), vacparted (does_not_exist);
2024-04-23 16:23:02.779 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.779 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE (VERBOSE) does_not_exist;
2024-04-23 16:23:02.780 UTC client backend[9796] pg_regress/vacuum ERROR:  syntax error at or near "arg" at character 22
2024-04-23 16:23:02.780 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE (nonexistent-arg) does_not_exist;
2024-04-23 16:23:02.781 UTC client backend[9796] pg_regress/vacuum ERROR:  unrecognized ANALYZE option "nonexistentarg" at character 10
2024-04-23 16:23:02.781 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE (nonexistentarg) does_not_exit;
2024-04-23 16:23:02.784 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.784 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE (SKIP_LOCKED, VERBOSE) does_not_exist;
2024-04-23 16:23:02.784 UTC client backend[9796] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2024-04-23 16:23:02.784 UTC client backend[9796] pg_regress/vacuum STATEMENT:  ANALYZE (VERBOSE, SKIP_LOCKED) does_not_exist;
2024-04-23 16:23:02.793 UTC client backend[9795] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2024-04-23 16:23:02.793 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2024-04-23 16:23:02.793 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMIT;
2024-04-23 16:23:02.827 UTC client backend[9778] pg_regress/triggers ERROR:  U9999
2024-04-23 16:23:02.827 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function depth_c_tf() line 5 at RAISE
	SQL statement "insert into depth_c values (1)"
	PL/pgSQL function depth_b_tf() line 12 at EXECUTE
	SQL statement "insert into depth_b values (new.id)"
	PL/pgSQL function depth_a_tf() line 4 at SQL statement
2024-04-23 16:23:02.827 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into depth_a values (1);
2024-04-23 16:23:02.828 UTC client backend[9795] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "circles_c1_c2_excl"
2024-04-23 16:23:02.828 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (c1, (c2::circle))=(<(20,20),10>, <(0,0),4>) conflicts with existing key (c1, (c2::circle))=(<(10,10),10>, <(0,0),5>).
2024-04-23 16:23:02.828 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>');
2024-04-23 16:23:02.831 UTC client backend[9795] pg_regress/constraints ERROR:  ON CONFLICT DO UPDATE not supported with exclusion constraints
2024-04-23 16:23:02.831 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>')
	  ON CONFLICT ON CONSTRAINT circles_c1_c2_excl DO UPDATE SET c2 = EXCLUDED.c2;
2024-04-23 16:23:02.834 UTC client backend[9795] pg_regress/constraints ERROR:  could not create exclusion constraint "circles_c1_c2_excl1"
2024-04-23 16:23:02.834 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (c1, (c2::circle))=(<(0,0),5>, <(0,0),5>) conflicts with key (c1, (c2::circle))=(<(0,0),5>, <(0,0),4>).
2024-04-23 16:23:02.834 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE circles ADD EXCLUDE USING gist
	  (c1 WITH &&, (c2::circle) WITH &&);
2024-04-23 16:23:02.835 UTC client backend[9796] pg_regress/vacuum ERROR:  PROCESS_TOAST required with VACUUM FULL
2024-04-23 16:23:02.835 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (PROCESS_TOAST FALSE, FULL) vac_option_tab;
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (f1)=(1) conflicts with existing key (f1)=(1).
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO deferred_excl VALUES(1);
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints ERROR:  ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints STATEMENT:  INSERT INTO deferred_excl VALUES(1) ON CONFLICT ON CONSTRAINT deferred_excl_con DO NOTHING;
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (f1)=(2) conflicts with existing key (f1)=(2).
2024-04-23 16:23:02.857 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMIT;
2024-04-23 16:23:02.861 UTC client backend[9795] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2024-04-23 16:23:02.861 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (f1)=(3) conflicts with existing key (f1)=(3).
2024-04-23 16:23:02.861 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMIT;
2024-04-23 16:23:02.867 UTC client backend[9795] pg_regress/constraints ERROR:  could not create exclusion constraint "deferred_excl_f1_excl"
2024-04-23 16:23:02.867 UTC client backend[9795] pg_regress/constraints DETAIL:  Key (f1)=(3) conflicts with key (f1)=(3).
2024-04-23 16:23:02.867 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE deferred_excl ADD EXCLUDE (f1 WITH =);
2024-04-23 16:23:02.874 UTC client backend[9795] pg_regress/constraints ERROR:  constraint "notnull_tbl1_a_not_null" for relation "notnull_tbl1" already exists
2024-04-23 16:23:02.874 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE notnull_tbl1 ADD COLUMN b INT CONSTRAINT notnull_tbl1_a_not_null NOT NULL;
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 16777220) vac_option_tab;
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 120) vac_option_tab;
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum HINT:  Value exceeds integer range.
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 10000000000) vac_option_tab;
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT cannot be specified for VACUUM FULL
2024-04-23 16:23:02.876 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT '512 kB', FULL) vac_option_tab;
2024-04-23 16:23:02.877 UTC client backend[9796] pg_regress/vacuum ERROR:  ONLY_DATABASE_STATS cannot be specified with a list of tables
2024-04-23 16:23:02.877 UTC client backend[9796] pg_regress/vacuum STATEMENT:  VACUUM (ONLY_DATABASE_STATS) vactst;
2024-04-23 16:23:02.882 UTC client backend[9795] pg_regress/constraints ERROR:  constraint "blah" for relation "notnull_tbl2" already exists
2024-04-23 16:23:02.882 UTC client backend[9795] pg_regress/constraints STATEMENT:  CREATE TABLE notnull_tbl2 (a INTEGER CONSTRAINT blah NOT NULL, b INTEGER CONSTRAINT blah NOT NULL);
2024-04-23 16:23:02.882 UTC client backend[9795] pg_regress/constraints ERROR:  column "a" is in a primary key
2024-04-23 16:23:02.882 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE notnull_tbl2 ALTER a DROP NOT NULL;
2024-04-23 16:23:02.908 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned", skipping it
2024-04-23 16:23:02.909 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned", skipping it
2024-04-23 16:23:02.911 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned", skipping it
2024-04-23 16:23:02.912 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_class", skipping it
2024-04-23 16:23:02.913 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "pg_class", skipping it
2024-04-23 16:23:02.914 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_class", skipping it
2024-04-23 16:23:02.914 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_authid", skipping it
2024-04-23 16:23:02.915 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "pg_authid", skipping it
2024-04-23 16:23:02.915 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_authid", skipping it
2024-04-23 16:23:02.916 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2024-04-23 16:23:02.916 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.916 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.917 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.917 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.918 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_parted", skipping it
2024-04-23 16:23:02.918 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2024-04-23 16:23:02.918 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.919 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2024-04-23 16:23:02.919 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.919 UTC client backend[9795] pg_regress/constraints ERROR:  column "c1" is in index used as replica identity
2024-04-23 16:23:02.919 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE  notnull_tbl1 ALTER c1 DROP NOT NULL;
2024-04-23 16:23:02.920 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2024-04-23 16:23:02.920 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.920 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.920 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.920 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.923 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.923 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.924 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.925 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.925 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.929 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.930 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2024-04-23 16:23:02.931 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.932 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.932 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_parted", skipping it
2024-04-23 16:23:02.932 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.933 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.933 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2024-04-23 16:23:02.933 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.934 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.936 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.936 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.937 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.937 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.937 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2024-04-23 16:23:02.937 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.938 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2024-04-23 16:23:02.938 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2024-04-23 16:23:02.938 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.938 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.939 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2024-04-23 16:23:02.939 UTC client backend[9796] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers ERROR:  tuple to be updated was already modified by an operation triggered by the current command
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers STATEMENT:  update parent set val1 = 'b' where aid = 1;
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers ERROR:  tuple to be updated or deleted was already modified by an operation triggered by the current command
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2024-04-23 16:23:02.988 UTC client backend[9778] pg_regress/triggers STATEMENT:  merge into parent p using (values (1)) as v(id) on p.aid = v.id
	  when matched then update set val1 = 'b';
2024-04-23 16:23:02.991 UTC client backend[9778] pg_regress/triggers ERROR:  tuple to be deleted was already modified by an operation triggered by the current command
2024-04-23 16:23:02.991 UTC client backend[9778] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2024-04-23 16:23:02.991 UTC client backend[9778] pg_regress/triggers STATEMENT:  delete from parent where aid = 1;
2024-04-23 16:23:02.992 UTC client backend[9778] pg_regress/triggers ERROR:  tuple to be updated or deleted was already modified by an operation triggered by the current command
2024-04-23 16:23:02.992 UTC client backend[9778] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2024-04-23 16:23:02.992 UTC client backend[9778] pg_regress/triggers STATEMENT:  merge into parent p using (values (1)) as v(id) on p.aid = v.id
	  when matched then delete;
2024-04-23 16:23:03.658 UTC client backend[9778] pg_regress/triggers ERROR:  tuple to be updated was already modified by an operation triggered by the current command
2024-04-23 16:23:03.658 UTC client backend[9778] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2024-04-23 16:23:03.658 UTC client backend[9778] pg_regress/triggers STATEMENT:  delete from self_ref_trigger;
2024-04-23 16:23:03.658 UTC client backend[9795] pg_regress/constraints ERROR:  multiple primary keys for table "cnn_parent" are not allowed
2024-04-23 16:23:03.658 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE cnn_parent ADD PRIMARY KEY (b);
2024-04-23 16:23:04.411 UTC client backend[9795] pg_regress/constraints ERROR:  constraint "cnn_parent_pkey" of relation "cnn_parent" does not exist
2024-04-23 16:23:04.411 UTC client backend[9795] pg_regress/constraints STATEMENT:  ALTER TABLE cnn_parent DROP CONSTRAINT cnn_parent_pkey;
2024-04-23 16:23:05.607 UTC client backend[9778] pg_regress/triggers ERROR:  cannot ALTER TABLE "trigger_ddl_table" because it is being used by active queries in this session
2024-04-23 16:23:05.607 UTC client backend[9778] pg_regress/triggers CONTEXT:  SQL statement "alter table trigger_ddl_table add primary key (col1)"
	PL/pgSQL function trigger_ddl_func() line 3 at SQL statement
2024-04-23 16:23:05.607 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into trigger_ddl_table values (1, 42);
2024-04-23 16:23:05.844 UTC client backend[9778] pg_regress/triggers ERROR:  cannot CREATE INDEX "trigger_ddl_table" because it is being used by active queries in this session
2024-04-23 16:23:05.844 UTC client backend[9778] pg_regress/triggers CONTEXT:  SQL statement "create index on trigger_ddl_table (col2)"
	PL/pgSQL function trigger_ddl_func() line 3 at SQL statement
2024-04-23 16:23:05.844 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into trigger_ddl_table values (1, 42);
2024-04-23 16:23:05.861 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c1"
2024-04-23 16:23:05.861 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table p1_c1 drop constraint f1_pos;
2024-04-23 16:23:05.880 UTC client backend[9795] pg_regress/constraints ERROR:  null value in column "a" of relation "cnn2_part1" violates not-null constraint
2024-04-23 16:23:05.880 UTC client backend[9795] pg_regress/constraints DETAIL:  Failing row contains (null).
2024-04-23 16:23:05.880 UTC client backend[9795] pg_regress/constraints STATEMENT:  insert into cnn2_part1 values (null);
2024-04-23 16:23:05.900 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (1,black)
2024-04-23 16:23:05.900 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.900 UTC client backend[9778] pg_regress/triggers WARNING:  after insert (new): (1,black)
2024-04-23 16:23:05.900 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2024-04-23 16:23:05.903 UTC client backend[9795] pg_regress/constraints ERROR:  column "a" in child table must be marked NOT NULL
2024-04-23 16:23:05.903 UTC client backend[9795] pg_regress/constraints STATEMENT:  alter table cnn2_parted attach partition cnn2_part1 for values in (1);
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (2,red)
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new, modified): (3,"red trig modified")
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers WARNING:  after insert (new): (3,"red trig modified")
2024-04-23 16:23:05.904 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (3,orange)
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  before update (old): (3,"red trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  before update (new): (3,"updated red trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  after update (old): (3,"red trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  after update (new): (3,"updated red trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (4,green)
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new, modified): (5,"green trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers WARNING:  after insert (new): (5,"green trig modified")
2024-04-23 16:23:05.905 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (5,purple)
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers WARNING:  before update (old): (5,"green trig modified")
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers WARNING:  before update (new): (5,"updated green trig modified")
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers WARNING:  after update (old): (5,"green trig modified")
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers WARNING:  after update (new): (5,"updated green trig modified")
2024-04-23 16:23:05.906 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (6,white)
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new, modified): (7,"white trig modified")
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers WARNING:  after insert (new): (7,"white trig modified")
2024-04-23 16:23:05.911 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2024-04-23 16:23:05.911 UTC client backend[9795] pg_regress/constraints ERROR:  column "a" of relation "cnn_part1" contains null values
2024-04-23 16:23:05.911 UTC client backend[9795] pg_regress/constraints STATEMENT:  alter table cnn2_parted add primary key (a);
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (7,pink)
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers WARNING:  before update (old): (7,"white trig modified")
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers WARNING:  before update (new): (7,"updated white trig modified")
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers WARNING:  after update (old): (7,"white trig modified")
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers WARNING:  after update (new): (7,"updated white trig modified")
2024-04-23 16:23:05.916 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new): (8,yellow)
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers WARNING:  before insert (new, modified): (9,"yellow trig modified")
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers WARNING:  after insert (new): (9,"yellow trig modified")
2024-04-23 16:23:05.923 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2024-04-23 16:23:06.039 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c2"
2024-04-23 16:23:06.039 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table p1_c2 drop constraint f1_pos;
2024-04-23 16:23:06.039 UTC client backend[9778] pg_regress/triggers ERROR:  "my_view" is a view
2024-04-23 16:23:06.039 UTC client backend[9778] pg_regress/triggers DETAIL:  Triggers on views cannot have transition tables.
2024-04-23 16:23:06.039 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger my_trigger after update on my_view referencing old table as old_table
	   for each statement execute procedure my_trigger_function();
2024-04-23 16:23:06.039 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c1c2"
2024-04-23 16:23:06.039 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table p1_c1c2 drop constraint f1_pos;
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers ERROR:  "parted_trig" is a table
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger failed instead of update on parted_trig
	  for each row execute procedure trigger_nothing();
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers ERROR:  "parted_trig" is a partitioned table
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported on partitioned tables.
2024-04-23 16:23:06.080 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger failed after update on parted_trig
	  referencing old table as old_table
	  for each row execute procedure trigger_nothing();
2024-04-23 16:23:06.087 UTC client backend[9781] pg_regress/inherit ERROR:  constraint "inh_check_constraint" conflicts with NOT VALID constraint on relation "invalid_check_con_child"
2024-04-23 16:23:06.087 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table invalid_check_con add constraint inh_check_constraint check(f1 > 0);
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "invalid_check_con" violates check constraint "inh_check_constraint"
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0).
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into invalid_check_con values(0);
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "invalid_check_con_child" violates check constraint "inh_check_constraint"
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0).
2024-04-23 16:23:06.094 UTC client backend[9781] pg_regress/inherit STATEMENT:  insert into invalid_check_con_child values(0);
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints ERROR:  constraint "no_constraint" for table "constraint_comments_tbl" does not exist
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT no_constraint ON constraint_comments_tbl IS 'yes, the comment';
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints ERROR:  constraint "no_constraint" for domain constraint_comments_dom does not exist
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT no_constraint ON DOMAIN constraint_comments_dom IS 'yes, another comment';
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints ERROR:  relation "no_comments_tbl" does not exist
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON no_comments_tbl IS 'bad comment';
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints ERROR:  type "no_comments_dom" does not exist
2024-04-23 16:23:06.106 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON DOMAIN no_comments_dom IS 'another bad comment';
2024-04-23 16:23:06.114 UTC client backend[9795] pg_regress/constraints ERROR:  must be owner of relation constraint_comments_tbl
2024-04-23 16:23:06.114 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON constraint_comments_tbl IS 'no, the comment';
2024-04-23 16:23:06.114 UTC client backend[9795] pg_regress/constraints ERROR:  must be owner of type constraint_comments_dom
2024-04-23 16:23:06.114 UTC client backend[9795] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON DOMAIN constraint_comments_dom IS 'no, another comment';
2024-04-23 16:23:06.135 UTC client backend[9778] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart1 because trigger trg1 on table trigpart requires it
2024-04-23 16:23:06.135 UTC client backend[9778] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2024-04-23 16:23:06.135 UTC client backend[9778] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart1;
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart2 because trigger trg1 on table trigpart requires it
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart2;
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart3 because trigger trg1 on table trigpart requires it
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2024-04-23 16:23:06.136 UTC client backend[9778] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart3;
2024-04-23 16:23:06.165 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "trg1" for table "trigpart3" does not exist
2024-04-23 16:23:06.165 UTC client backend[9778] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart3;
2024-04-23 16:23:06.174 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "trg1" for table "trigpart41" does not exist
2024-04-23 16:23:06.174 UTC client backend[9778] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart41;
2024-04-23 16:23:06.221 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "trg1" for relation "trigpart3" already exists
2024-04-23 16:23:06.221 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter table trigpart attach partition trigpart3 FOR VALUES FROM (2000) to (3000);
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit ERROR:  cannot define not-null constraint on column "a2" with NO INHERIT
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit DETAIL:  The column has an inherited not-null constraint.
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit STATEMENT:  create table cc3 (a2 int not null no inherit) inherits (cc1);
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit ERROR:  cannot change NO INHERIT status of inherited NOT NULL constraint "nn" on relation "cc2"
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table cc2 add not null a2 no inherit;
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "nn" of relation "cc2"
2024-04-23 16:23:06.976 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table cc2 alter column a2 drop not null;
2024-04-23 16:23:06.979 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "pp1_f1_not_null" of relation "cc2"
2024-04-23 16:23:06.979 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table cc2 alter column f1 drop not null;
2024-04-23 16:23:06.985 UTC client backend[9781] pg_regress/inherit ERROR:  cannot drop inherited constraint "pp1_f1_not_null" of relation "cc1"
2024-04-23 16:23:06.985 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table cc1 alter column f1 drop not null;
2024-04-23 16:23:07.074 UTC client backend[9781] pg_regress/inherit ERROR:  column "f1" in child table must be marked NOT NULL
2024-04-23 16:23:07.074 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table inh_child2 inherit inh_child1;
2024-04-23 16:23:07.098 UTC client backend[9778] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2024-04-23 16:23:07.098 UTC client backend[9778] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1_1".
2024-04-23 16:23:07.098 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'uno uno v2');
2024-04-23 16:23:07.099 UTC client backend[9778] pg_regress/triggers ERROR:  no partition of relation "parted" found for row
2024-04-23 16:23:07.099 UTC client backend[9778] pg_regress/triggers DETAIL:  Partition key of the failing row contains (a) = (2).
2024-04-23 16:23:07.099 UTC client backend[9778] pg_regress/triggers STATEMENT:  update parted set c = c || 'v3';
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1_1".
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'uno uno v4');
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers ERROR:  no partition of relation "parted_1" found for row
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers DETAIL:  Partition key of the failing row contains (b) = (2).
2024-04-23 16:23:07.103 UTC client backend[9778] pg_regress/triggers STATEMENT:  update parted set c = c || 'v5';
2024-04-23 16:23:07.110 UTC client backend[9781] pg_regress/inherit ERROR:  column "a" in child table must be marked NOT NULL
2024-04-23 16:23:07.110 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table inh_child inherit inh_parent;
2024-04-23 16:23:07.258 UTC client backend[9778] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2024-04-23 16:23:07.258 UTC client backend[9778] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1".
2024-04-23 16:23:07.258 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'one fail');
2024-04-23 16:23:07.259 UTC client backend[9778] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2024-04-23 16:23:07.259 UTC client backend[9778] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_2".
2024-04-23 16:23:07.259 UTC client backend[9778] pg_regress/triggers STATEMENT:  insert into parted values (1, 2, 'two fail');
2024-04-23 16:23:07.286 UTC client backend[9781] pg_regress/inherit ERROR:  must be owner of table inh_child
2024-04-23 16:23:07.286 UTC client backend[9781] pg_regress/inherit STATEMENT:  alter table inh_parent alter a drop not null;
2024-04-23 16:23:07.298 UTC client backend[9781] pg_regress/inherit ERROR:  cannot inherit from temporary relation "inh_temp_parent"
2024-04-23 16:23:07.298 UTC client backend[9781] pg_regress/inherit STATEMENT:  create table inh_perm_child () inherits (inh_temp_parent);
2024-04-23 16:23:10.692 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2024-04-23 16:23:10.692 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 10).
2024-04-23 16:23:10.692 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', '10');
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 10).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', '10');
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 10).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', '10');
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_fastdef" violates not-null constraint
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0, 1, null).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', NULL);
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_plaindef" violates not-null constraint
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 1, null).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', NULL);
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_reorder" violates not-null constraint
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 1, null).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', NULL);
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "shdata_small"
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0, 5, 5).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '5', '5');
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "shdata_small"
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 5, 5).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '5', '5');
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "shdata_small"
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 5, 5).
2024-04-23 16:23:10.693 UTC client backend[9781] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '5', '5');
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 15).
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 0;
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 15).
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 10;
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 15).
2024-04-23 16:23:10.694 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 20;
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates partition constraint
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 5).
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_child_fastdef SET partid = partid + 10 WHERE partid = 0;
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates partition constraint
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 5).
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_child_plaindef SET partid = partid + 10 WHERE partid = 10;
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates partition constraint
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (5, 1, 30).
2024-04-23 16:23:10.695 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_child_reorder SET partid = partid + 10 WHERE partid = 20;
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 15).
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 10, data = data + 10 WHERE partid = 0;
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 15).
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 20, data = data + 10 WHERE partid = 10;
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 15).
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 0, data = data + 10 WHERE partid = 20;
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit ERROR:  no partition of relation "errtst_parent" found for row
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit DETAIL:  Partition key of the failing row contains (partid) = (30).
2024-04-23 16:23:10.696 UTC client backend[9781] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 30, data = data + 10 WHERE partid = 20;
2024-04-23 16:23:10.730 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:10.730 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:10.730 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (1);
2024-04-23 16:23:11.804 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:11.804 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:11.804 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (1);
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (11);
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (21);
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:11.811 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (30);
2024-04-23 16:23:11.812 UTC client backend[9778] pg_regress/triggers ERROR:  except
2024-04-23 16:23:11.812 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2024-04-23 16:23:11.812 UTC client backend[9778] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (40);
2024-04-23 16:23:12.670 UTC client backend[9778] pg_regress/triggers ERROR:  ROW triggers with transition tables are not supported on partitions
2024-04-23 16:23:12.670 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger child_row_trig
	  after insert on child referencing new table as new_table
	  for each row execute procedure dump_insert();
2024-04-23 16:23:12.672 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "child_row_trig" prevents table "child" from becoming a partition
2024-04-23 16:23:12.672 UTC client backend[9778] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported on partitions.
2024-04-23 16:23:12.672 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter table parent attach partition child for values in ('AAA');
2024-04-23 16:23:13.032 UTC client backend[9778] pg_regress/triggers ERROR:  ROW triggers with transition tables are not supported on inheritance children
2024-04-23 16:23:13.032 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger child_row_trig
	  after insert on child referencing new table as new_table
	  for each row execute procedure dump_insert();
2024-04-23 16:23:13.035 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "child_row_trig" prevents table "child" from becoming an inheritance child
2024-04-23 16:23:13.035 UTC client backend[9778] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported in inheritance hierarchies.
2024-04-23 16:23:13.035 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter table child inherit parent;
2024-04-23 16:23:13.229 UTC client backend[9778] pg_regress/triggers ERROR:  transition tables cannot be specified for triggers with more than one event
2024-04-23 16:23:13.229 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger my_table_multievent_trig
	  after insert or update on my_table referencing new table as new_table
	  for each statement execute procedure dump_insert();
2024-04-23 16:23:13.229 UTC client backend[9778] pg_regress/triggers ERROR:  transition tables cannot be specified for triggers with column lists
2024-04-23 16:23:13.229 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger my_table_col_update_trig
	  after update of b on my_table referencing new table as new_table
	  for each statement execute procedure dump_insert();
2024-04-23 16:23:13.385 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "my_trig" for relation "my_table" already exists
2024-04-23 16:23:13.385 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger my_trig
	  before insert on my_table
	  for each row execute procedure funcB();
2024-04-23 16:23:13.423 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "my_trig" for relation "parted_trig_1" is an internal or a child trigger
2024-04-23 16:23:13.423 UTC client backend[9778] pg_regress/triggers STATEMENT:  create or replace trigger my_trig
	  after insert on parted_trig_1
	  for each row execute procedure funcB();
2024-04-23 16:23:13.433 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "my_trig" for relation "parted_trig_1" already exists
2024-04-23 16:23:13.433 UTC client backend[9778] pg_regress/triggers STATEMENT:  create trigger my_trig
	  after insert on parted_trig
	  for each row execute procedure funcB();
2024-04-23 16:23:13.544 UTC client backend[9778] pg_regress/triggers ERROR:  BOOM!
2024-04-23 16:23:13.544 UTC client backend[9778] pg_regress/triggers CONTEXT:  PL/pgSQL function convslot_trig4() line 1 at RAISE
2024-04-23 16:23:13.544 UTC client backend[9778] pg_regress/triggers STATEMENT:  update convslot_test_parent set val = 3;
2024-04-23 16:23:13.802 UTC client backend[9778] pg_regress/triggers ERROR:  syntax error at or near "only" at character 20
2024-04-23 16:23:13.802 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter trigger a on only grandparent rename to b;
2024-04-23 16:23:13.803 UTC client backend[9778] pg_regress/triggers ERROR:  cannot rename trigger "b" on table "middle"
2024-04-23 16:23:13.803 UTC client backend[9778] pg_regress/triggers HINT:  Rename the trigger on the partitioned table "grandparent" instead.
2024-04-23 16:23:13.803 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter trigger b on middle rename to c;
2024-04-23 16:23:13.804 UTC client backend[9778] pg_regress/triggers ERROR:  trigger "c" for relation "middle" already exists
2024-04-23 16:23:13.804 UTC client backend[9778] pg_regress/triggers STATEMENT:  alter trigger b on grandparent rename to c;
2024-04-23 16:23:35.416 UTC autovacuum worker[11618] LOG:  automatic vacuum of table "postgres.pg_catalog.pg_authid": index scans: 1
	pages: 0 removed, 1 remain, 1 scanned (100.00% of total)
	tuples: 36 removed, 22 remain, 6 are dead but not yet removable
	removable cutoff: 4678, which was 1293 XIDs old when operation ended
	new relfrozenxid: 4678, which is 3948 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 1 pages from table (100.00% of total) had 32 dead item identifiers removed
	index "pg_authid_rolname_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_authid_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 145.214 MB/s
	buffer usage: 37 hits, 0 misses, 5 dirtied
	WAL usage: 7 records, 2 full page images, 15924 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:23:35.943 UTC autovacuum worker[11618] LOG:  automatic analyze of table "postgres.pg_catalog.pg_authid"
	avg read rate: 0.612 MB/s, avg write rate: 0.090 MB/s
	buffer usage: 496 hits, 41 misses, 6 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.52 s
2024-04-23 16:23:35.952 UTC autovacuum worker[11618] LOG:  automatic analyze of table "postgres.pg_catalog.pg_shdepend"
	avg read rate: 0.000 MB/s, avg write rate: 7.812 MB/s
	buffer usage: 111 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:16.050 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_type"
	avg read rate: 1.259 MB/s, avg write rate: 0.217 MB/s
	buffer usage: 1020 hits, 58 misses, 10 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.35 s
2024-04-23 16:24:16.113 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_attribute"
	avg read rate: 3.627 MB/s, avg write rate: 0.977 MB/s
	buffer usage: 490 hits, 26 misses, 7 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.05 s
2024-04-23 16:24:16.155 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_class"
	avg read rate: 1.519 MB/s, avg write rate: 1.085 MB/s
	buffer usage: 534 hits, 7 misses, 5 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s
2024-04-23 16:24:16.299 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_constraint"
	avg read rate: 0.292 MB/s, avg write rate: 0.117 MB/s
	buffer usage: 532 hits, 5 misses, 2 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.13 s
2024-04-23 16:24:16.352 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_rewrite"
	avg read rate: 2.358 MB/s, avg write rate: 0.147 MB/s
	buffer usage: 111 hits, 16 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.05 s
2024-04-23 16:24:17.325 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_description"
	avg read rate: 0.435 MB/s, avg write rate: 0.071 MB/s
	buffer usage: 84 hits, 49 misses, 8 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.88 s
2024-04-23 16:24:17.373 UTC autovacuum worker[13417] LOG:  automatic aggressive vacuum of table "template1.pg_catalog.pg_depend": index scans: 0
	pages: 0 removed, 13 remain, 13 scanned (100.00% of total)
	tuples: 0 removed, 1709 remain, 0 are dead but not yet removable
	removable cutoff: 5978, which was 0 XIDs old when operation ended
	new relfrozenxid: 5978, which is 5248 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 5.853 MB/s, avg write rate: 0.308 MB/s
	buffer usage: 52 hits, 19 misses, 1 dirtied
	WAL usage: 1 records, 1 full page images, 8001 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s
2024-04-23 16:24:17.420 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_depend"
	avg read rate: 3.906 MB/s, avg write rate: 3.906 MB/s
	buffer usage: 105 hits, 1 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:17.536 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_ts_config_map"
	avg read rate: 0.565 MB/s, avg write rate: 0.188 MB/s
	buffer usage: 52 hits, 6 misses, 2 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.08 s
2024-04-23 16:24:17.639 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_init_privs"
	avg read rate: 0.326 MB/s, avg write rate: 0.081 MB/s
	buffer usage: 85 hits, 4 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.09 s
2024-04-23 16:24:17.888 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.pg_catalog.pg_collation"
	avg read rate: 0.690 MB/s, avg write rate: 0.031 MB/s
	buffer usage: 143 hits, 22 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.24 s
2024-04-23 16:24:18.605 UTC autovacuum worker[13417] LOG:  automatic analyze of table "template1.information_schema.sql_features"
	avg read rate: 0.965 MB/s, avg write rate: 0.096 MB/s
	buffer usage: 178 hits, 10 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.08 s
2024-04-23 16:24:35.372 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.tenk1": index scans: 0
	pages: 0 removed, 345 remain, 1 scanned (0.29% of total)
	tuples: 0 removed, 10000 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1305 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 84 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.352 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.tenk1"
	avg read rate: 0.000 MB/s, avg write rate: 0.332 MB/s
	buffer usage: 659 hits, 0 misses, 2 dirtied
	system usage: CPU: user: 0.03 s, system: 0.00 s, elapsed: 0.04 s
2024-04-23 16:24:36.594 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.tenk2": index scans: 0
	pages: 0 removed, 345 remain, 1 scanned (0.29% of total)
	tuples: 0 removed, 10000 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1306 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.161 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 47 hits, 3 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.14 s
2024-04-23 16:24:36.638 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.tenk2"
	avg read rate: 0.000 MB/s, avg write rate: 0.178 MB/s
	buffer usage: 537 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.03 s, system: 0.00 s, elapsed: 0.04 s
2024-04-23 16:24:36.653 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.road": index scans: 0
	pages: 0 removed, 71 remain, 1 scanned (1.41% of total)
	tuples: 0 removed, 5124 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1307 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.587 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 28 hits, 1 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:36.731 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.road"
	avg read rate: 0.000 MB/s, avg write rate: 0.099 MB/s
	buffer usage: 287 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.02 s, system: 0.00 s, elapsed: 0.07 s
2024-04-23 16:24:36.788 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.road"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 138 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.04 s, system: 0.00 s, elapsed: 0.05 s
2024-04-23 16:24:36.844 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.ihighway"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 54 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.848 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_type": index scans: 1
	pages: 0 removed, 76 remain, 76 scanned (100.00% of total)
	tuples: 296 removed, 1718 remain, 762 are dead but not yet removable
	removable cutoff: 4678, which was 1309 XIDs old when operation ended
	new relfrozenxid: 742, which is 12 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 44 pages from table (57.89% of total) had 1653 dead item identifiers removed
	index "pg_type_oid_index": pages: 11 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_type_typname_nsp_index": pages: 17 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 1.776 MB/s
	buffer usage: 243 hits, 0 misses, 1 dirtied
	WAL usage: 140 records, 0 full page images, 15947 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.862 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_type"
	avg read rate: 0.000 MB/s, avg write rate: 0.558 MB/s
	buffer usage: 947 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:36.862 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.shighway"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 58 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.863 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.num_exp_sub"
	avg read rate: 0.000 MB/s, avg write rate: 7.812 MB/s
	buffer usage: 133 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.863 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.num_exp_div"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 48 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.863 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.num_exp_mul"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 52 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.864 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.num_result": index scans: 0
	pages: 0 removed, 5 remain, 5 scanned (100.00% of total)
	tuples: 460 removed, 8 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1314 XIDs old when operation ended
	new relfrozenxid: 1136, which is 275 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 78.649 MB/s
	buffer usage: 18 hits, 0 misses, 3 dirtied
	WAL usage: 11 records, 1 full page images, 10522 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.864 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.num_result"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 36 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.869 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.test_range_spgist": index scans: 0
	pages: 0 removed, 33 remain, 33 scanned (100.00% of total)
	tuples: 0 removed, 6200 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1315 XIDs old when operation ended
	new relfrozenxid: 1142, which is 2 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "test_range_spgist_idx": pages: 43 in total, 1 newly deleted, 1 currently deleted, 1 reusable
	avg read rate: 0.000 MB/s, avg write rate: 10.580 MB/s
	buffer usage: 155 hits, 0 misses, 7 dirtied
	WAL usage: 65 records, 1 full page images, 12068 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.872 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.test_range_spgist"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 52 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.883 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.test_range_gist": index scans: 0
	pages: 0 removed, 33 remain, 33 scanned (100.00% of total)
	tuples: 0 removed, 6200 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1316 XIDs old when operation ended
	new relfrozenxid: 1099, which is 5 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "test_range_gist_idx": pages: 35 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 13.014 MB/s
	buffer usage: 132 hits, 0 misses, 3 dirtied
	WAL usage: 34 records, 1 full page images, 10332 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.888 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.test_range_gist"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 52 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.905 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.quad_box_tbl": index scans: 0
	pages: 0 removed, 92 remain, 92 scanned (100.00% of total)
	tuples: 0 removed, 11005 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1317 XIDs old when operation ended
	new relfrozenxid: 1408, which is 5 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "quad_box_tbl_idx": pages: 112 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 4.180 MB/s
	buffer usage: 329 hits, 0 misses, 4 dirtied
	WAL usage: 135 records, 1 full page images, 16165 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.909 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.quad_box_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 192 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.922 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.quad_box_tbl_ord_seq1": index scans: 0
	pages: 57 removed, 71 remain, 128 scanned (100.00% of total)
	tuples: 0 removed, 11005 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1319 XIDs old when operation ended
	new relfrozenxid: 1547, which is 59 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 2.806 MB/s
	buffer usage: 382 hits, 0 misses, 4 dirtied
	WAL usage: 74 records, 1 full page images, 12662 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:36.932 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.quad_box_tbl_ord_seq1"
	avg read rate: 0.000 MB/s, avg write rate: 0.977 MB/s
	buffer usage: 208 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.932 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.timestamptz_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 88 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:36.949 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_attribute": index scans: 1
	pages: 0 removed, 308 remain, 271 scanned (87.99% of total)
	tuples: 1729 removed, 10624 remain, 4281 are dead but not yet removable
	removable cutoff: 4678, which was 1321 XIDs old when operation ended
	new relfrozenxid: 742, which is 12 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 159 pages from table (51.62% of total) had 8343 dead item identifiers removed
	index "pg_attribute_relid_attnam_index": pages: 72 in total, 10 newly deleted, 10 currently deleted, 0 reusable
	index "pg_attribute_relid_attnum_index": pages: 50 in total, 5 newly deleted, 5 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 948 hits, 0 misses, 0 dirtied
	WAL usage: 518 records, 0 full page images, 79339 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:36.988 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_attribute"
	avg read rate: 0.000 MB/s, avg write rate: 0.504 MB/s
	buffer usage: 766 hits, 0 misses, 2 dirtied
	system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.03 s
2024-04-23 16:24:37.067 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_proc"
	avg read rate: 0.000 MB/s, avg write rate: 0.396 MB/s
	buffer usage: 809 hits, 0 misses, 4 dirtied
	system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.07 s
2024-04-23 16:24:37.068 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_attrdef": index scans: 1
	pages: 0 removed, 4 remain, 4 scanned (100.00% of total)
	tuples: 8 removed, 30 remain, 15 are dead but not yet removable
	removable cutoff: 4678, which was 1323 XIDs old when operation ended
	new relfrozenxid: 1088, which is 358 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 4 pages from table (100.00% of total) had 46 dead item identifiers removed
	index "pg_attrdef_adrelid_adnum_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_attrdef_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 59.037 MB/s
	buffer usage: 67 hits, 0 misses, 3 dirtied
	WAL usage: 13 records, 1 full page images, 9616 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.068 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_attrdef"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 65 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.069 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_constraint": index scans: 1
	pages: 0 removed, 19 remain, 19 scanned (100.00% of total)
	tuples: 27 removed, 470 remain, 303 are dead but not yet removable
	removable cutoff: 4678, which was 1324 XIDs old when operation ended
	new relfrozenxid: 1191, which is 461 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 8 pages from table (42.11% of total) had 172 dead item identifiers removed
	index "pg_constraint_conparentid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_constraint_conname_nsp_index": pages: 6 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_constraint_conrelid_contypid_conname_index": pages: 5 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_constraint_contypid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_constraint_oid_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 12.999 MB/s
	buffer usage: 154 hits, 0 misses, 1 dirtied
	WAL usage: 30 records, 0 full page images, 3802 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.074 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_constraint"
	avg read rate: 0.000 MB/s, avg write rate: 2.604 MB/s
	buffer usage: 474 hits, 0 misses, 2 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.197 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_inherits": index scans: 1
	pages: 0 removed, 4 remain, 4 scanned (100.00% of total)
	tuples: 4 removed, 341 remain, 290 are dead but not yet removable
	removable cutoff: 4678, which was 1325 XIDs old when operation ended
	new relfrozenxid: 774, which is 44 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 4 pages from table (100.00% of total) had 215 dead item identifiers removed
	index "pg_inherits_parent_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_inherits_relid_seqno_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 17.536 MB/s
	buffer usage: 49 hits, 0 misses, 2 dirtied
	WAL usage: 12 records, 0 full page images, 1495 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.197 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_inherits"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 64 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.198 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_index": index scans: 1
	pages: 0 removed, 18 remain, 18 scanned (100.00% of total)
	tuples: 21 removed, 506 remain, 215 are dead but not yet removable
	removable cutoff: 4678, which was 1326 XIDs old when operation ended
	new relfrozenxid: 754, which is 24 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 10 pages from table (55.56% of total) had 451 dead item identifiers removed
	index "pg_index_indrelid_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_index_indexrelid_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 73 hits, 0 misses, 0 dirtied
	WAL usage: 32 records, 0 full page images, 3436 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.201 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_index"
	avg read rate: 0.000 MB/s, avg write rate: 1.953 MB/s
	buffer usage: 327 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.532 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_rewrite": index scans: 1
	pages: 0 removed, 40 remain, 40 scanned (100.00% of total)
	tuples: 108 removed, 162 remain, 9 are dead but not yet removable
	removable cutoff: 4678, which was 1327 XIDs old when operation ended
	new relfrozenxid: 2984, which is 2254 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 27 pages from table (67.50% of total) had 151 dead item identifiers removed
	index "pg_rewrite_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_rewrite_rel_rulename_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 153 hits, 0 misses, 0 dirtied
	WAL usage: 82 records, 0 full page images, 5902 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.534 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_rewrite"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 154 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.601 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_trigger": index scans: 1
	pages: 0 removed, 10 remain, 10 scanned (100.00% of total)
	tuples: 2 removed, 350 remain, 330 are dead but not yet removable
	removable cutoff: 4678, which was 1328 XIDs old when operation ended
	new relfrozenxid: 4404, which is 3674 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 2 pages from table (20.00% of total) had 56 dead item identifiers removed
	index "pg_trigger_tgconstraint_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_trigger_tgrelid_tgname_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_trigger_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 17.246 MB/s
	buffer usage: 76 hits, 0 misses, 2 dirtied
	WAL usage: 10 records, 0 full page images, 1433 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.605 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_trigger"
	avg read rate: 0.000 MB/s, avg write rate: 1.953 MB/s
	buffer usage: 240 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.622 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_enum": index scans: 1
	pages: 1 removed, 1 remain, 2 scanned (100.00% of total)
	tuples: 35 removed, 44 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1330 XIDs old when operation ended
	new relfrozenxid: 793, which is 63 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 2 pages from table (100.00% of total) had 59 dead item identifiers removed
	index "pg_enum_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_enum_typid_label_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_enum_typid_sortorder_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 1.343 MB/s
	buffer usage: 61 hits, 0 misses, 3 dirtied
	WAL usage: 15 records, 1 full page images, 10092 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:37.623 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_enum"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 84 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.624 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_namespace"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 64 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.632 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_depend": index scans: 1
	pages: 0 removed, 93 remain, 93 scanned (100.00% of total)
	tuples: 2178 removed, 6239 remain, 3245 are dead but not yet removable
	removable cutoff: 4678, which was 1332 XIDs old when operation ended
	new relfrozenxid: 742, which is 12 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 62 pages from table (66.67% of total) had 5486 dead item identifiers removed
	index "pg_depend_depender_index": pages: 61 in total, 3 newly deleted, 3 currently deleted, 0 reusable
	index "pg_depend_reference_index": pages: 40 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 426 hits, 0 misses, 0 dirtied
	WAL usage: 250 records, 0 full page images, 40766 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.634 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_depend"
	avg read rate: 0.000 MB/s, avg write rate: 2.604 MB/s
	buffer usage: 201 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.639 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_partitioned_table": index scans: 1
	pages: 0 removed, 3 remain, 3 scanned (100.00% of total)
	tuples: 0 removed, 78 remain, 71 are dead but not yet removable
	removable cutoff: 4678, which was 1333 XIDs old when operation ended
	new relfrozenxid: 2301, which is 1571 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 1 pages from table (33.33% of total) had 80 dead item identifiers removed
	index "pg_partitioned_table_partrelid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 76.344 MB/s
	buffer usage: 23 hits, 0 misses, 3 dirtied
	WAL usage: 4 records, 0 full page images, 833 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.639 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_partitioned_table"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 91 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.639 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.num_exp_add"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 60 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.652 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.quad_poly_tbl": index scans: 0
	pages: 0 removed, 349 remain, 349 scanned (100.00% of total)
	tuples: 0 removed, 11003 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1335 XIDs old when operation ended
	new relfrozenxid: 1359, which is 11 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "quad_poly_tbl_idx": pages: 98 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 2.483 MB/s
	buffer usage: 829 hits, 0 misses, 4 dirtied
	WAL usage: 387 records, 1 full page images, 31048 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s
2024-04-23 16:24:37.658 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.quad_poly_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 451 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.659 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.timestamp_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 87 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.665 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.quad_box_tbl_ord_seq2": index scans: 0
	pages: 3 removed, 13 remain, 16 scanned (100.00% of total)
	tuples: 0 removed, 1900 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1338 XIDs old when operation ended
	new relfrozenxid: 1554, which is 66 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 4.805 MB/s
	buffer usage: 50 hits, 0 misses, 4 dirtied
	WAL usage: 16 records, 1 full page images, 9240 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.666 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.quad_box_tbl_ord_seq2"
	avg read rate: 0.000 MB/s, avg write rate: 7.812 MB/s
	buffer usage: 46 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.666 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.ramp"
	avg read rate: 0.000 MB/s, avg write rate: 7.812 MB/s
	buffer usage: 31 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.670 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.quad_point_tbl": index scans: 0
	pages: 0 removed, 69 remain, 69 scanned (100.00% of total)
	tuples: 0 removed, 11003 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1340 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "sp_quad_ind": pages: 72 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 7.868 MB/s
	buffer usage: 251 hits, 0 misses, 4 dirtied
	WAL usage: 93 records, 1 full page images, 13720 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.674 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.quad_point_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 161 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.680 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.kd_point_tbl": index scans: 0
	pages: 4 removed, 60 remain, 64 scanned (100.00% of total)
	tuples: 0 removed, 11003 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1342 XIDs old when operation ended
	new relfrozenxid: 3066, which is 86 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "sp_kd_ind": pages: 97 in total, 1 newly deleted, 1 currently deleted, 1 reusable
	avg read rate: 0.000 MB/s, avg write rate: 9.358 MB/s
	buffer usage: 270 hits, 0 misses, 7 dirtied
	WAL usage: 105 records, 1 full page images, 14365 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.683 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.kd_point_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 76 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.686 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.slow_emp4000": index scans: 0
	pages: 8 removed, 24 remain, 32 scanned (100.00% of total)
	tuples: 0 removed, 3378 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1344 XIDs old when operation ended
	new relfrozenxid: 3154, which is 25 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 2.773 MB/s
	buffer usage: 85 hits, 0 misses, 1 dirtied
	WAL usage: 27 records, 1 full page images, 9889 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.686 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.slow_emp4000"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 42 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.687 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.fast_emp4000": index scans: 0
	pages: 0 removed, 24 remain, 24 scanned (100.00% of total)
	tuples: 0 removed, 3378 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1345 XIDs old when operation ended
	new relfrozenxid: 3186, which is 47 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "grect2ind": pages: 29 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 43.323 MB/s
	buffer usage: 106 hits, 0 misses, 3 dirtied
	WAL usage: 25 records, 1 full page images, 9801 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.690 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.fast_emp4000"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 43 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.693 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.array_index_op_test"
	avg read rate: 0.000 MB/s, avg write rate: 1.953 MB/s
	buffer usage: 195 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.699 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.radix_text_tbl": index scans: 0
	pages: 0 removed, 70 remain, 70 scanned (100.00% of total)
	tuples: 0 removed, 6251 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1347 XIDs old when operation ended
	new relfrozenxid: 3129, which is 13 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "sp_radix_ind": pages: 58 in total, 2 newly deleted, 2 currently deleted, 2 reusable
	avg read rate: 0.000 MB/s, avg write rate: 11.781 MB/s
	buffer usage: 251 hits, 0 misses, 7 dirtied
	WAL usage: 75 records, 1 full page images, 12682 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.723 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.radix_text_tbl"
	avg read rate: 0.000 MB/s, avg write rate: 0.312 MB/s
	buffer usage: 91 hits, 0 misses, 1 dirtied
	system usage: CPU: user: 0.02 s, system: 0.00 s, elapsed: 0.02 s
2024-04-23 16:24:37.959 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.public.dupindexcols": index scans: 0
	pages: 9 removed, 55 remain, 64 scanned (100.00% of total)
	tuples: 0 removed, 10000 remain, 0 are dead but not yet removable
	removable cutoff: 4678, which was 1349 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.132 MB/s
	buffer usage: 183 hits, 0 misses, 4 dirtied
	WAL usage: 58 records, 1 full page images, 11718 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.23 s
2024-04-23 16:24:37.963 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.public.dupindexcols"
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 88 hits, 0 misses, 0 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:37.967 UTC autovacuum worker[14425] LOG:  automatic vacuum of table "regression.pg_catalog.pg_class": index scans: 1
	pages: 0 removed, 68 remain, 68 scanned (100.00% of total)
	tuples: 35 removed, 2129 remain, 1371 are dead but not yet removable
	removable cutoff: 4678, which was 1350 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 14 pages from table (20.59% of total) had 271 dead item identifiers removed
	index "pg_class_oid_index": pages: 7 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_class_relname_nsp_index": pages: 14 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	index "pg_class_tblspc_relfilenode_index": pages: 7 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 16.209 MB/s
	buffer usage: 216 hits, 0 misses, 8 dirtied
	WAL usage: 62 records, 1 full page images, 13869 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:24:38.056 UTC autovacuum worker[14425] LOG:  automatic analyze of table "regression.pg_catalog.pg_class"
	avg read rate: 0.000 MB/s, avg write rate: 0.176 MB/s
	buffer usage: 559 hits, 0 misses, 2 dirtied
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.08 s
2024-04-23 16:25:15.362 UTC autovacuum worker[16184] LOG:  automatic aggressive vacuum of table "template1.pg_catalog.pg_statistic": index scans: 1
	pages: 0 removed, 27 remain, 27 scanned (100.00% of total)
	tuples: 134 removed, 411 remain, 0 are dead but not yet removable
	removable cutoff: 6029, which was 0 XIDs old when operation ended
	new relfrozenxid: 6029, which is 5299 XIDs ahead of previous value
	frozen: 15 pages from table (55.56% of total) had 165 tuples frozen
	index scan needed: 16 pages from table (59.26% of total) had 152 dead item identifiers removed
	index "pg_statistic_relid_att_inh_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 9.555 MB/s, avg write rate: 6.370 MB/s
	buffer usage: 97 hits, 3 misses, 2 dirtied
	WAL usage: 68 records, 3 full page images, 22217 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.456 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_statistic": index scans: 1
	pages: 0 removed, 53 remain, 53 scanned (100.00% of total)
	tuples: 9 removed, 932 remain, 302 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	new relfrozenxid: 760, which is 30 XIDs ahead of previous value
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan needed: 5 pages from table (9.43% of total) had 25 dead item identifiers removed
	index "pg_statistic_relid_att_inh_index": pages: 5 in total, 0 newly deleted, 0 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 144 hits, 0 misses, 0 dirtied
	WAL usage: 14 records, 0 full page images, 1172 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.458 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_type": index scans: 0
	pages: 0 removed, 76 remain, 30 scanned (39.47% of total)
	tuples: 0 removed, 1447 remain, 762 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 72 hits, 0 misses, 0 dirtied
	WAL usage: 1 records, 0 full page images, 225 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.463 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_attribute": index scans: 0
	pages: 0 removed, 308 remain, 114 scanned (37.01% of total)
	tuples: 0 removed, 8924 remain, 4281 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	index "pg_attribute_relid_attnam_index": pages: 72 in total, 0 newly deleted, 10 currently deleted, 0 reusable
	index "pg_attribute_relid_attnum_index": pages: 50 in total, 0 newly deleted, 5 currently deleted, 0 reusable
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 362 hits, 0 misses, 0 dirtied
	WAL usage: 1 records, 0 full page images, 225 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.465 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_constraint": index scans: 0
	pages: 0 removed, 19 remain, 19 scanned (100.00% of total)
	tuples: 0 removed, 470 remain, 303 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 113 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.467 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_inherits": index scans: 0
	pages: 0 removed, 4 remain, 4 scanned (100.00% of total)
	tuples: 0 removed, 341 remain, 290 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 46 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.468 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_index": index scans: 0
	pages: 0 removed, 18 remain, 18 scanned (100.00% of total)
	tuples: 0 removed, 506 remain, 215 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 47 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.477 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_trigger": index scans: 0
	pages: 0 removed, 10 remain, 10 scanned (100.00% of total)
	tuples: 0 removed, 350 remain, 330 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 56 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.478 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_depend": index scans: 0
	pages: 0 removed, 93 remain, 40 scanned (43.01% of total)
	tuples: 0 removed, 5443 remain, 3245 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 128 hits, 0 misses, 0 dirtied
	WAL usage: 1 records, 0 full page images, 225 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.480 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_partitioned_table": index scans: 0
	pages: 0 removed, 3 remain, 3 scanned (100.00% of total)
	tuples: 0 removed, 78 remain, 71 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 16 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:35.481 UTC autovacuum worker[16668] LOG:  automatic vacuum of table "regression.pg_catalog.pg_class": index scans: 0
	pages: 0 removed, 68 remain, 68 scanned (100.00% of total)
	tuples: 0 removed, 2129 remain, 1371 are dead but not yet removable
	removable cutoff: 4678, which was 1351 XIDs old when operation ended
	frozen: 0 pages from table (0.00% of total) had 0 tuples frozen
	index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	buffer usage: 164 hits, 0 misses, 0 dirtied
	WAL usage: 0 records, 0 full page images, 0 bytes
	system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 16:25:57.836 UTC postmaster[7550] LOG:  server process (PID 9793) was terminated by signal 6: Abort trap: 6
2024-04-23 16:25:57.836 UTC postmaster[7550] DETAIL:  Failed process was running: MERGE INTO rw_view2 t
	  USING (SELECT x, 'R'||x FROM generate_series(0,3) x) AS s(a,b) ON t.a = s.a
	  WHEN MATCHED AND t.a <= 1 THEN DELETE
	  WHEN MATCHED THEN UPDATE SET b = s.b
	  WHEN NOT MATCHED AND s.a > 0 THEN INSERT VALUES (s.a, s.b)
	  RETURNING merge_action(), s.*, t.*;
2024-04-23 16:25:57.836 UTC postmaster[7550] LOG:  terminating any other active server processes
2024-04-23 16:25:57.838 UTC postmaster[7550] LOG:  all server processes terminated; reinitializing
2024-04-23 16:26:04.206 UTC startup[17544] LOG:  database system was interrupted; last known up at 2024-04-23 16:22:35 UTC
2024-04-23 16:26:04.415 UTC startup[17544] LOG:  database system was not properly shut down; automatic recovery in progress
2024-04-23 16:26:04.461 UTC startup[17544] LOG:  redo starts at 0/1506700
2024-04-23 16:26:06.115 UTC client backend[17688] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.115 UTC client backend[17688] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.221 UTC client backend[17738] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.221 UTC client backend[17738] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.227 UTC client backend[17742] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.227 UTC client backend[17742] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.233 UTC client backend[17746] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.233 UTC client backend[17746] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.240 UTC client backend[17748] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.240 UTC client backend[17748] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.254 UTC client backend[17751] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.254 UTC client backend[17751] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.259 UTC client backend[17754] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.259 UTC client backend[17754] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.268 UTC client backend[17757] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.268 UTC client backend[17757] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.275 UTC client backend[17760] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.275 UTC client backend[17760] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.279 UTC client backend[17762] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.279 UTC client backend[17762] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.285 UTC client backend[17765] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.285 UTC client backend[17765] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.291 UTC client backend[17767] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.291 UTC client backend[17767] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.294 UTC client backend[17769] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.294 UTC client backend[17769] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.301 UTC client backend[17772] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.301 UTC client backend[17772] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.303 UTC client backend[17774] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.303 UTC client backend[17774] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.339 UTC client backend[17780] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.339 UTC client backend[17780] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.343 UTC client backend[17781] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.343 UTC client backend[17781] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.344 UTC client backend[17782] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.344 UTC client backend[17782] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.347 UTC client backend[17783] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.347 UTC client backend[17783] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.348 UTC client backend[17784] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.348 UTC client backend[17784] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:06.350 UTC client backend[17787] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:06.350 UTC client backend[17787] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.612 UTC client backend[18148] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.612 UTC client backend[18148] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.613 UTC client backend[18152] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.613 UTC client backend[18152] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.621 UTC client backend[18156] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.621 UTC client backend[18156] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.632 UTC client backend[18157] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.632 UTC client backend[18157] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.635 UTC client backend[18158] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.635 UTC client backend[18158] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.639 UTC client backend[18159] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.639 UTC client backend[18159] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.640 UTC client backend[18162] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.640 UTC client backend[18162] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.639 UTC client backend[18160] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.639 UTC client backend[18160] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.640 UTC client backend[18163] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.640 UTC client backend[18163] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.640 UTC client backend[18164] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.640 UTC client backend[18164] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.641 UTC client backend[18165] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.641 UTC client backend[18165] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.640 UTC client backend[18161] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.640 UTC client backend[18161] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.702 UTC client backend[18166] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.702 UTC client backend[18166] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.703 UTC client backend[18167] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.703 UTC client backend[18167] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.704 UTC client backend[18168] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.704 UTC client backend[18168] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.705 UTC client backend[18169] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.705 UTC client backend[18169] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.721 UTC client backend[18170] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.721 UTC client backend[18170] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.722 UTC client backend[18172] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.722 UTC client backend[18172] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.724 UTC client backend[18173] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.724 UTC client backend[18173] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:12.725 UTC client backend[18174] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:12.725 UTC client backend[18174] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:14.545 UTC startup[17544] LOG:  redo in progress, elapsed time: 10.08 s, current LSN: 0/3FFFFC0
2024-04-23 16:26:16.217 UTC client backend[18442] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.217 UTC client backend[18442] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.217 UTC client backend[18445] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.217 UTC client backend[18445] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.464 UTC client backend[18523] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.464 UTC client backend[18523] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.474 UTC client backend[18524] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.474 UTC client backend[18524] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.477 UTC client backend[18525] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.477 UTC client backend[18525] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.490 UTC client backend[18526] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.490 UTC client backend[18526] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.499 UTC client backend[18527] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.499 UTC client backend[18527] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.500 UTC client backend[18528] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.500 UTC client backend[18528] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.503 UTC client backend[18529] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.503 UTC client backend[18529] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.504 UTC client backend[18530] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.504 UTC client backend[18530] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.507 UTC client backend[18531] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.507 UTC client backend[18531] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.510 UTC client backend[18532] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.510 UTC client backend[18532] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.511 UTC client backend[18533] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.511 UTC client backend[18533] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.512 UTC client backend[18534] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.512 UTC client backend[18534] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.514 UTC client backend[18536] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.514 UTC client backend[18536] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.515 UTC client backend[18537] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.515 UTC client backend[18537] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.516 UTC client backend[18538] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.516 UTC client backend[18538] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.517 UTC client backend[18539] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.517 UTC client backend[18539] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.518 UTC client backend[18542] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.518 UTC client backend[18542] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:16.519 UTC client backend[18543] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:16.519 UTC client backend[18543] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.330 UTC client backend[18795] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.330 UTC client backend[18795] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.331 UTC client backend[18796] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.331 UTC client backend[18796] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.332 UTC client backend[18797] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.332 UTC client backend[18797] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.333 UTC client backend[18799] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.333 UTC client backend[18799] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.335 UTC client backend[18800] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.335 UTC client backend[18800] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.340 UTC client backend[18802] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.340 UTC client backend[18802] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.347 UTC client backend[18804] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.347 UTC client backend[18804] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:17.557 UTC startup[17544] LOG:  invalid record length at 0/4FB8610: expected at least 24, got 0
2024-04-23 16:26:17.558 UTC startup[17544] LOG:  redo done at 0/4FB85D8 system usage: CPU: user: 0.17 s, system: 0.22 s, elapsed: 13.09 s
2024-04-23 16:26:17.596 UTC checkpointer[17545] LOG:  checkpoint starting: end-of-recovery immediate wait
2024-04-23 16:26:17.825 UTC client backend[18903] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:17.825 UTC client backend[18903] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.630 UTC client backend[18923] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.630 UTC client backend[18923] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.681 UTC client backend[18939] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.681 UTC client backend[18939] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.711 UTC client backend[18959] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.711 UTC client backend[18959] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.717 UTC client backend[18961] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.717 UTC client backend[18961] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.916 UTC client backend[19039] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.916 UTC client backend[19039] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.924 UTC client backend[19040] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.924 UTC client backend[19040] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.928 UTC client backend[19041] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.928 UTC client backend[19041] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.953 UTC client backend[19042] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.953 UTC client backend[19042] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.954 UTC client backend[19043] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.954 UTC client backend[19043] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.956 UTC client backend[19044] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.956 UTC client backend[19044] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.958 UTC client backend[19045] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.958 UTC client backend[19045] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.959 UTC client backend[19046] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.959 UTC client backend[19046] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.960 UTC client backend[19047] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.960 UTC client backend[19047] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.961 UTC client backend[19048] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.961 UTC client backend[19048] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.963 UTC client backend[19049] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.963 UTC client backend[19049] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19050] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19050] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19051] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19051] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19052] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19052] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19053] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19053] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19054] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19054] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:19.964 UTC client backend[19055] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:19.964 UTC client backend[19055] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.520 UTC client backend[19296] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.520 UTC client backend[19296] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.521 UTC client backend[19297] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.521 UTC client backend[19297] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.522 UTC client backend[19298] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.522 UTC client backend[19298] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.523 UTC client backend[19299] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.523 UTC client backend[19299] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.524 UTC client backend[19300] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.524 UTC client backend[19300] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.526 UTC client backend[19301] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.526 UTC client backend[19301] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.527 UTC client backend[19302] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.527 UTC client backend[19302] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.528 UTC client backend[19305] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.528 UTC client backend[19305] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:21.529 UTC client backend[19306] [unknown] FATAL:  the database system is not yet accepting connections
2024-04-23 16:26:21.529 UTC client backend[19306] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2024-04-23 16:26:22.337 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 4697 buffers (28.7%); 0 WAL file(s) added, 0 removed, 3 recycled; write=4.554 s, sync=0.001 s, total=4.741 s; sync files=0, longest=0.000 s, average=0.000 s; distance=60103 kB, estimate=60103 kB; lsn=0/4FB8610, redo lsn=0/4FB8610
2024-04-23 16:26:22.345 UTC postmaster[7550] LOG:  database system is ready to accept connections
2024-04-23 16:26:23.026 UTC client backend[19554] pg_regress/with ERROR:  could not implement recursive UNION
2024-04-23 16:26:23.026 UTC client backend[19554] pg_regress/with DETAIL:  All column datatypes must be hashable.
2024-04-23 16:26:23.026 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE t(n) AS (
	    VALUES ('01'::varbit)
	UNION
	    SELECT n || '10'::varbit FROM t WHERE n < '100'::varbit
	)
	SELECT n FROM t;
2024-04-23 16:26:23.026 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 32
2024-04-23 16:26:23.026 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Couldn't find end of Start Tag wrong line 1
	<wrong
	      ^
2024-04-23 16:26:23.026 UTC client backend[19550] pg_regress/xml STATEMENT:  INSERT INTO xmltest VALUES (3, '<wrong');
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML comment
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlcomment('test-');
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML comment
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlcomment('--test');
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml ERROR:  argument of XMLCONCAT must be type xml, not type integer at character 18
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlconcat(1, 2);
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 25
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Couldn't find end of Start Tag syntax line 1
	<syntax
	       ^
2024-04-23 16:26:23.027 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlconcat('bad', '<syntax');
2024-04-23 16:26:23.028 UTC client backend[19550] pg_regress/xml ERROR:  unnamed XML attribute value must be a column reference at character 66
2024-04-23 16:26:23.028 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlelement(name element,
	                  xmlattributes ('unnamed and wrong'));
2024-04-23 16:26:23.028 UTC client backend[19550] pg_regress/xml ERROR:  XML attribute name "a" appears more than once at character 65
2024-04-23 16:26:23.028 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlelement(name duplicate, xmlattributes(1 as a, 2 as b, 3 as a));
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml ERROR:  timestamp out of range
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml DETAIL:  XML does not support infinite timestamp values.
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlelement(name foo, xmlattributes('infinity'::timestamp as bar));
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: xmlParseEntityRef: no name
	<invalidentity>&</invalidentity>
	                ^
	line 1: chunk is not well balanced
	<invalidentity>&</invalidentity>
	                                ^
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<invalidentity>&</invalidentity>');
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<undefinedentity>&idontexist;</undefinedentity>
	                             ^
	line 1: chunk is not well balanced
	<undefinedentity>&idontexist;</undefinedentity>
	                                               ^
2024-04-23 16:26:23.029 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<undefinedentity>&idontexist;</undefinedentity>');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<twoerrors>&idontexist;</unbalanced>
	                       ^
	line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
	<twoerrors>&idontexist;</unbalanced>
	                                    ^
	line 1: chunk is not well balanced
	<twoerrors>&idontexist;</unbalanced>
	                                    ^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<twoerrors>&idontexist;</unbalanced>');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	   
	   ^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(document '   ');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	abc
	^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(document 'abc');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: xmlParseEntityRef: no name
	<invalidentity>&</abc>
	                ^
	line 1: Opening and ending tag mismatch: invalidentity line 1 and abc
	<invalidentity>&</abc>
	                      ^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<invalidentity>&</abc>');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<undefinedentity>&idontexist;</abc>
	                             ^
	line 1: Opening and ending tag mismatch: undefinedentity line 1 and abc
	<undefinedentity>&idontexist;</abc>
	                                   ^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<undefinedentity>&idontexist;</abc>');
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<twoerrors>&idontexist;</unbalanced>
	                       ^
	line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
	<twoerrors>&idontexist;</unbalanced>
	                                    ^
2024-04-23 16:26:23.030 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<twoerrors>&idontexist;</unbalanced>');
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML processing instruction
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml DETAIL:  XML processing instruction target name cannot be "xml".
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlpi(name xml);
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML processing instruction
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml DETAIL:  XML processing instruction cannot contain "?>".
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlpi(name foo, 'in?>valid');
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML processing instruction
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml DETAIL:  XML processing instruction target name cannot be "xml".
2024-04-23 16:26:23.031 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlpi(name xml, null);
2024-04-23 16:26:23.032 UTC client backend[19554] pg_regress/with ERROR:  operator does not exist: text + integer at character 63
2024-04-23 16:26:23.032 UTC client backend[19554] pg_regress/with HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.032 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE t(n) AS (
	    SELECT '7'
	UNION ALL
	    SELECT n+1 FROM t WHERE n < 10
	)
	SELECT n, pg_typeof(n) FROM t;
2024-04-23 16:26:23.032 UTC client backend[19550] pg_regress/xml ERROR:  not an XML document
2024-04-23 16:26:23.032 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlserialize(document 'bad' as text);
2024-04-23 16:26:23.033 UTC client backend[19550] pg_regress/xml ERROR:  not an XML document
2024-04-23 16:26:23.033 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '<foo>73</foo><bar><val x="y">42</val></bar>' AS text INDENT);
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml ERROR:  not an XML document
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT 'text node<foo>73</foo>text node<bar><val x="y">42</val></bar>' AS text INDENT);
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml ERROR:  not an XML document
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '' AS text INDENT);
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml ERROR:  not an XML document
2024-04-23 16:26:23.034 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '  ' AS text INDENT);
2024-04-23 16:26:23.038 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 8
2024-04-23 16:26:23.038 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<>
	 ^
2024-04-23 16:26:23.038 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT '<>' IS NOT DOCUMENT;
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document at character 14
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	bad
	^
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml STATEMENT:  EXECUTE foo ('bad');
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML document at character 12
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Extra content at the end of the document
	<!DOCTYPE a><a/><b/>
	                ^
2024-04-23 16:26:23.039 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xml '<!DOCTYPE a><a/><b/>';
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 12
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<!-- hi--> oops <!DOCTYPE a><a/>
	                 ^
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xml '<!-- hi--> oops <!DOCTYPE a><a/>';
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 12
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<!-- hi--> <oops/> <!DOCTYPE a><a/>
	                    ^
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xml '<!-- hi--> <oops/> <!DOCTYPE a><a/>';
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml ERROR:  invalid XML content at character 12
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Extra content at the end of the document
	<!DOCTYPE a><a/><b/>
	                ^
2024-04-23 16:26:23.040 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xml '<!DOCTYPE a><a/><b/>';
2024-04-23 16:26:23.045 UTC client backend[19550] pg_regress/xml ERROR:  empty XPath expression
2024-04-23 16:26:23.045 UTC client backend[19550] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2024-04-23 16:26:23.045 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xpath('', '<!-- error -->');
2024-04-23 16:26:23.056 UTC client backend[19543] pg_regress/plancache ERROR:  relation "pcachetest" does not exist at character 35
2024-04-23 16:26:23.056 UTC client backend[19543] pg_regress/plancache STATEMENT:  EXECUTE prepstmt;
2024-04-23 16:26:23.057 UTC client backend[19543] pg_regress/plancache ERROR:  relation "pcachetest" does not exist at character 44
2024-04-23 16:26:23.057 UTC client backend[19543] pg_regress/plancache STATEMENT:  EXECUTE prepstmt2(123);
2024-04-23 16:26:23.061 UTC client backend[19543] pg_regress/plancache ERROR:  cached plan must not change result type
2024-04-23 16:26:23.061 UTC client backend[19543] pg_regress/plancache STATEMENT:  EXECUTE prepstmt;
2024-04-23 16:26:23.061 UTC client backend[19543] pg_regress/plancache ERROR:  cached plan must not change result type
2024-04-23 16:26:23.061 UTC client backend[19543] pg_regress/plancache STATEMENT:  EXECUTE prepstmt2(123);
2024-04-23 16:26:23.065 UTC client backend[19554] pg_regress/with ERROR:  search column "foo" not in WITH query column list at character 146
2024-04-23 16:26:23.065 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by foo, tar set seq
	select * from search_graph;
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with ERROR:  search sequence column name "label" already used in WITH query column list at character 146
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set label
	select * from search_graph;
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with ERROR:  search column "f" specified more than once at character 146
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t, f set seq
	select * from search_graph;
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the left side of the UNION must be a SELECT
2024-04-23 16:26:23.066 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set seq
	select * from search_graph order by seq;
2024-04-23 16:26:23.067 UTC client backend[19554] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the right side of the UNION must be a SELECT
2024-04-23 16:26:23.067 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		(select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t)
	) search depth first by f, t set seq
	select * from search_graph order by seq;
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml ERROR:  could not parse XML document
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: xmlns: '<' is not a valid URI
	<invalidns xmlns='&lt;'/>
	                       ^
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xpath('/*', '<invalidns xmlns=''&lt;''/>');
2024-04-23 16:26:23.067 UTC client backend[19554] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the recursive reference to WITH query "x" must be at the top level of its right-hand SELECT
2024-04-23 16:26:23.067 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive x(col) as (
		select 1
		union
		(with x as (select * from x)
		 select * from x)
	) search depth first by col set seq
	select * from x;
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml ERROR:  could not parse XML document
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml DETAIL:  line 1: Namespace prefix nosuchprefix on tag is not defined
	<nosuchprefix:tag/>
	                 ^
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2024-04-23 16:26:23.067 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT xpath('/*', '<nosuchprefix:tag/>');
2024-04-23 16:26:23.072 UTC client backend[19550] pg_regress/xml WARNING:  line 1: xmlns: URI relative is not absolute
	<relativens xmlns='relative'/>
	                            ^
2024-04-23 16:26:23.072 UTC client backend[19550] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2024-04-23 16:26:23.074 UTC client backend[19557] pg_regress/returning ERROR:  cannot perform INSERT RETURNING on relation "voo"
2024-04-23 16:26:23.074 UTC client backend[19557] pg_regress/returning HINT:  You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause.
2024-04-23 16:26:23.074 UTC client backend[19557] pg_regress/returning STATEMENT:  INSERT INTO voo VALUES(12,'zoo') RETURNING *, f1*2;
2024-04-23 16:26:23.074 UTC client backend[19557] pg_regress/returning ERROR:  RETURNING list has too many entries
2024-04-23 16:26:23.074 UTC client backend[19557] pg_regress/returning STATEMENT:  CREATE OR REPLACE RULE voo_i AS ON INSERT TO voo DO INSTEAD
	  INSERT INTO foo VALUES(new.*, 57) RETURNING *;
2024-04-23 16:26:23.078 UTC client backend[19558] pg_regress/sequence ERROR:  INCREMENT must not be zero
2024-04-23 16:26:23.078 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 0;
2024-04-23 16:26:23.078 UTC client backend[19558] pg_regress/sequence ERROR:  MINVALUE (20) must be less than MAXVALUE (-1)
2024-04-23 16:26:23.078 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY -1 MINVALUE 20;
2024-04-23 16:26:23.079 UTC client backend[19558] pg_regress/sequence ERROR:  MINVALUE (1) must be less than MAXVALUE (-20)
2024-04-23 16:26:23.079 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 1 MAXVALUE -20;
2024-04-23 16:26:23.079 UTC client backend[19558] pg_regress/sequence ERROR:  START value (10) cannot be greater than MAXVALUE (-1)
2024-04-23 16:26:23.079 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY -1 START 10;
2024-04-23 16:26:23.080 UTC client backend[19558] pg_regress/sequence ERROR:  START value (-10) cannot be less than MINVALUE (1)
2024-04-23 16:26:23.080 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 1 START -10;
2024-04-23 16:26:23.080 UTC client backend[19558] pg_regress/sequence ERROR:  CACHE (0) must be greater than zero
2024-04-23 16:26:23.080 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx CACHE 0;
2024-04-23 16:26:23.082 UTC client backend[19558] pg_regress/sequence ERROR:  invalid OWNED BY option
2024-04-23 16:26:23.082 UTC client backend[19558] pg_regress/sequence HINT:  Specify OWNED BY table.column or OWNED BY NONE.
2024-04-23 16:26:23.082 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY nobody;
2024-04-23 16:26:23.083 UTC client backend[19558] pg_regress/sequence ERROR:  sequence cannot be owned by relation "pg_class_oid_index"
2024-04-23 16:26:23.083 UTC client backend[19558] pg_regress/sequence DETAIL:  This operation is not supported for indexes.
2024-04-23 16:26:23.083 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY pg_class_oid_index.oid;
2024-04-23 16:26:23.084 UTC client backend[19550] pg_regress/xml ERROR:  XMLTABLE function has 1 columns available but 2 columns specified
2024-04-23 16:26:23.084 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT * FROM XMLTABLE (ROW () PASSING null COLUMNS v1 timestamp) AS f (v1, v2);
2024-04-23 16:26:23.084 UTC client backend[19558] pg_regress/sequence ERROR:  sequence must be in same schema as table it is linked to
2024-04-23 16:26:23.084 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY pg_class.relname;
2024-04-23 16:26:23.086 UTC client backend[19550] pg_regress/xml ERROR:  DEFAULT namespace is not supported
2024-04-23 16:26:23.086 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT * FROM XMLTABLE(XMLNAMESPACES(DEFAULT 'http://x.y'),
	                      '/rows/row'
	                      PASSING '<rows xmlns="http://x.y"><row><a>10</a></row></rows>'
	                      COLUMNS a int PATH 'a');
2024-04-23 16:26:23.086 UTC client backend[19554] pg_regress/with ERROR:  cycle column "foo" not in WITH query column list at character 144
2024-04-23 16:26:23.086 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle foo, tar set is_cycle using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19558] pg_regress/sequence ERROR:  column "b" of relation "sequence_test_table" does not exist
2024-04-23 16:26:23.087 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY sequence_test_table.b;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  CYCLE types boolean and integer cannot be matched at character 184
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to true default 55 using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  could not identify an equality operator for type point
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to point '(1,1)' default point '(0,0)' using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  cycle mark column name "label" already used in WITH query column list at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set label to true default false using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  cycle path column name "label" already used in WITH query column list at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to true default false using label
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  cycle mark column name and cycle path column name are the same at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set foo to true default false using foo
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  cycle column "f" specified more than once at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t, f set is_cycle to true default false using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  search sequence column name and cycle mark column name are the same at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set foo
	  cycle f, t set foo to true default false using path
	select * from search_graph;
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with ERROR:  search sequence column name and cycle path column name are the same at character 144
2024-04-23 16:26:23.087 UTC client backend[19554] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set foo
	  cycle f, t set is_cycle to true default false using foo
	select * from search_graph;
2024-04-23 16:26:23.088 UTC client backend[19550] pg_regress/xml ERROR:  more than one value returned by column XPath expression
2024-04-23 16:26:23.088 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT * FROM xmltable('/root' passing '<root><element>a1a<!-- aaaa -->a2a<?aaaaa?> <!--z-->  bbbb<x>xxx</x>cccc</element></root>' COLUMNS element text PATH 'element/text()');
2024-04-23 16:26:23.090 UTC client backend[19557] pg_regress/returning ERROR:  invalid reference to FROM-clause entry for table "foo" at character 49
2024-04-23 16:26:23.090 UTC client backend[19557] pg_regress/returning HINT:  Perhaps you meant to reference the table alias "bar".
2024-04-23 16:26:23.090 UTC client backend[19557] pg_regress/returning STATEMENT:  INSERT INTO foo AS bar DEFAULT VALUES RETURNING foo.*;
2024-04-23 16:26:23.096 UTC client backend[19550] pg_regress/xml ERROR:  null is not allowed in column "size"
2024-04-23 16:26:23.096 UTC client backend[19550] pg_regress/xml STATEMENT:  SELECT  xmltable.*
	   FROM (SELECT data FROM xmldata) x,
	        LATERAL XMLTABLE('/ROWS/ROW'
	                         PASSING data
	                         COLUMNS id int PATH '@id',
	                                  _id FOR ORDINALITY,
	                                  country_name text PATH 'COUNTRY_NAME' NOT NULL,
	                                  country_id text PATH 'COUNTRY_ID',
	                                  region_id int PATH 'REGION_ID',
	                                  size float PATH 'SIZE' NOT NULL,
	                                  unit text PATH 'SIZE/@unit',
	                                  premier_name text PATH 'PREMIER_NAME' DEFAULT 'not specified');
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence ERROR:  sequence type must be smallint, integer, or bigint
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS text;
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence ERROR:  type "nosuchtype" does not exist at character 35
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS nosuchtype;
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence ERROR:  MAXVALUE (100000) is out of range for sequence data type smallint
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS smallint MAXVALUE 100000;
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence ERROR:  MINVALUE (-100000) is out of range for sequence data type smallint
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS smallint MINVALUE -100000;
2024-04-23 16:26:23.100 UTC client backend[19554] pg_regress/with ERROR:  WITH query "x" has 1 columns available but 2 columns specified at character 6
2024-04-23 16:26:23.100 UTC client backend[19554] pg_regress/with STATEMENT:  WITH x(n, b) AS (SELECT 1)
	SELECT * FROM x;
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence ERROR:  MAXVALUE (100000) is out of range for sequence data type smallint
2024-04-23 16:26:23.100 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test8 AS smallint;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT SELECT n+1 FROM x)
		SELECT * FROM x;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT ALL SELECT n+1 FROM x)
		SELECT * FROM x;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT SELECT n+1 FROM x)
		SELECT * FROM x;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT ALL SELECT n+1 FROM x)
		SELECT * FROM x;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT n FROM x)
		SELECT * FROM x;
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within its non-recursive term at character 39
2024-04-23 16:26:23.101 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT n FROM x UNION ALL SELECT 1)
		SELECT * FROM x;
2024-04-23 16:26:23.103 UTC client backend[19558] pg_regress/sequence ERROR:  MINVALUE (-100000) is out of range for sequence data type smallint
2024-04-23 16:26:23.103 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test10 AS smallint;
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 95
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM y LEFT JOIN x ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 83
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM x RIGHT JOIN y ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 83
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM x FULL JOIN y ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within a subquery at character 114
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x
	                          WHERE n IN (SELECT * FROM x))
	  SELECT * FROM x;
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with ERROR:  aggregate functions are not allowed in a recursive query's recursive term at character 51
2024-04-23 16:26:23.103 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT count(*) FROM x)
	  SELECT * FROM x;
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with ERROR:  aggregate functions are not allowed in a recursive query's recursive term at character 51
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT sum(n) FROM x)
	  SELECT * FROM x;
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with ERROR:  ORDER BY in a recursive query is not implemented at character 71
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x ORDER BY 1)
	  SELECT * FROM x;
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with ERROR:  OFFSET in a recursive query is not implemented at character 78
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x LIMIT 10 OFFSET 1)
	  SELECT * FROM x;
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with ERROR:  FOR UPDATE/SHARE in a recursive query is not implemented
2024-04-23 16:26:23.104 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x FOR UPDATE)
	  SELECT * FROM x;
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "x" must not appear within a subquery at character 77
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE x(id) AS (values (1)
	    UNION ALL
	    SELECT (SELECT * FROM x) FROM x WHERE id < 5
	) SELECT * FROM x;
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with ERROR:  mutual recursion between WITH items is not implemented at character 18
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE
	  x (id) AS (SELECT 1 UNION ALL SELECT id+1 FROM y WHERE id < 5),
	  y (id) AS (SELECT 1 UNION ALL SELECT id+1 FROM x WHERE id < 5)
	SELECT * FROM x;
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 140
2024-04-23 16:26:23.105 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          UNION ALL
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 158
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
		   SELECT * FROM
	       (SELECT i+1 FROM foo WHERE i < 10
	          UNION ALL
	       SELECT i+1 FROM foo WHERE i < 5) AS t
	) SELECT * FROM foo;
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "foo" must not appear within EXCEPT at character 137
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          EXCEPT
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 140
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          INTERSECT
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with ERROR:  recursive query "foo" column 1 has type integer in non-recursive term but type numeric overall at character 37
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with HINT:  Cast the output of the non-recursive term to the correct type.
2024-04-23 16:26:23.106 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	   (SELECT i FROM (VALUES(1),(2)) t(i)
	   UNION ALL
	   SELECT (i+1)::numeric(10,0) FROM foo WHERE i < 10)
	SELECT * FROM foo;
2024-04-23 16:26:23.106 UTC client backend[19543] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2024-04-23 16:26:23.106 UTC client backend[19543] pg_regress/plancache DETAIL:  Failing row contains (null).
2024-04-23 16:26:23.106 UTC client backend[19543] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(null);
2024-04-23 16:26:23.107 UTC client backend[19554] pg_regress/with ERROR:  recursive query "foo" column 1 has type numeric(3,0) in non-recursive term but type numeric overall at character 37
2024-04-23 16:26:23.107 UTC client backend[19554] pg_regress/with HINT:  Cast the output of the non-recursive term to the correct type.
2024-04-23 16:26:23.107 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	   (SELECT i::numeric(3,0) FROM (VALUES(1),(2)) t(i)
	   UNION ALL
	   SELECT (i+1)::numeric(10,0) FROM foo WHERE i < 10)
	SELECT * FROM foo;
2024-04-23 16:26:23.107 UTC client backend[19543] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2024-04-23 16:26:23.107 UTC client backend[19543] pg_regress/plancache DETAIL:  Failing row contains (1).
2024-04-23 16:26:23.107 UTC client backend[19543] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(1);
2024-04-23 16:26:23.108 UTC client backend[19554] pg_regress/with ERROR:  cannot refer to OLD within WITH query
2024-04-23 16:26:23.108 UTC client backend[19554] pg_regress/with STATEMENT:  CREATE RULE r2 AS ON UPDATE TO x DO INSTEAD
	    WITH t AS (SELECT OLD.*) UPDATE y SET a = t.n FROM t;
2024-04-23 16:26:23.108 UTC client backend[19543] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2024-04-23 16:26:23.108 UTC client backend[19543] pg_regress/plancache DETAIL:  Failing row contains (2).
2024-04-23 16:26:23.108 UTC client backend[19543] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(2);
2024-04-23 16:26:23.110 UTC client backend[19558] pg_regress/sequence ERROR:  null value in column "f2" of relation "serialtest1" violates not-null constraint
2024-04-23 16:26:23.110 UTC client backend[19558] pg_regress/sequence DETAIL:  Failing row contains (wrong, null).
2024-04-23 16:26:23.110 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest1 VALUES ('wrong', NULL);
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with ERROR:  relation "outermost" does not exist at character 96
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with DETAIL:  There is a WITH item named "outermost", but it cannot be referenced from this part of the query.
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with HINT:  Use WITH RECURSIVE, or re-order the WITH items to remove forward references.
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with STATEMENT:  WITH outermost(x) AS (
	  SELECT 1
	  UNION (WITH innermost as (SELECT 2)
	         SELECT * FROM outermost  -- fail
	         UNION SELECT * FROM innermost)
	)
	SELECT * FROM outermost ORDER BY 1;
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with ERROR:  recursive reference to query "outermost" must not appear within a subquery at character 69
2024-04-23 16:26:23.111 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE outermost(x) AS (
	  WITH innermost as (SELECT 2 FROM outermost) -- fail
	    SELECT * FROM innermost
	    UNION SELECT * from outermost
	)
	SELECT * FROM outermost ORDER BY 1;
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain ERROR:  cannot drop type domaindroptest because other objects depend on it
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain DETAIL:  type dependenttypetest depends on type domaindroptest
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain STATEMENT:  drop domain domaindroptest;
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain ERROR:  type "domaindroptest" does not exist
2024-04-23 16:26:23.123 UTC client backend[19561] pg_regress/domain STATEMENT:  drop domain domaindroptest cascade;
2024-04-23 16:26:23.127 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(5)
2024-04-23 16:26:23.127 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO basictest values ('88', 'haha', 'short text', '123.12');
2024-04-23 16:26:23.127 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(5)
2024-04-23 16:26:23.127 UTC client backend[19561] pg_regress/domain CONTEXT:  COPY basictest, line 1, column testvarchar: "notsoshorttext"
2024-04-23 16:26:23.127 UTC client backend[19561] pg_regress/domain STATEMENT:  COPY basictest (testvarchar) FROM stdin;
2024-04-23 16:26:23.128 UTC client backend[19564] pg_regress/prepare ERROR:  prepared statement "q1" already exists
2024-04-23 16:26:23.128 UTC client backend[19564] pg_regress/prepare STATEMENT:  PREPARE q1 AS SELECT 2;
2024-04-23 16:26:23.131 UTC client backend[19565] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2024-04-23 16:26:23.131 UTC client backend[19565] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare ERROR:  wrong number of parameters for prepared statement "q3"
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare DETAIL:  Expected 5 parameters but got 1.
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare STATEMENT:  EXECUTE q3('bool');
2024-04-23 16:26:23.132 UTC client backend[19563] pg_regress/conversion ERROR:  conversion "myconv" already exists
2024-04-23 16:26:23.132 UTC client backend[19563] pg_regress/conversion STATEMENT:  CREATE CONVERSION myconv FOR 'LATIN1' TO 'UTF8' FROM iso8859_1_to_utf8;
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare ERROR:  wrong number of parameters for prepared statement "q3"
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare DETAIL:  Expected 5 parameters but got 6.
2024-04-23 16:26:23.132 UTC client backend[19564] pg_regress/prepare STATEMENT:  EXECUTE q3('bytea', 5::smallint, 10.5::float, false, 4::bigint, true);
2024-04-23 16:26:23.133 UTC client backend[19564] pg_regress/prepare ERROR:  parameter $3 of type boolean cannot be coerced to the expected type double precision at character 38
2024-04-23 16:26:23.133 UTC client backend[19564] pg_regress/prepare HINT:  You will need to rewrite or cast the expression.
2024-04-23 16:26:23.133 UTC client backend[19564] pg_regress/prepare STATEMENT:  EXECUTE q3(5::smallint, 10.5::float, false, 4::bigint, 'bytea');
2024-04-23 16:26:23.133 UTC client backend[19563] pg_regress/conversion ERROR:  default conversion for LATIN1 to UTF8 already exists
2024-04-23 16:26:23.133 UTC client backend[19563] pg_regress/conversion STATEMENT:  CREATE DEFAULT CONVERSION public.mydef2 FOR 'LATIN1' TO 'UTF8' FROM iso8859_1_to_utf8;
2024-04-23 16:26:23.133 UTC client backend[19564] pg_regress/prepare ERROR:  type "nonexistenttype" does not exist at character 12
2024-04-23 16:26:23.133 UTC client backend[19564] pg_regress/prepare STATEMENT:  PREPARE q4(nonexistenttype) AS SELECT $1;
2024-04-23 16:26:23.133 UTC client backend[19563] pg_regress/conversion ERROR:  conversion "myconv_bad" does not exist
2024-04-23 16:26:23.133 UTC client backend[19563] pg_regress/conversion STATEMENT:  COMMENT ON CONVERSION myconv_bad IS 'foo';
2024-04-23 16:26:23.133 UTC client backend[19561] pg_regress/domain ERROR:  division by zero
2024-04-23 16:26:23.133 UTC client backend[19561] pg_regress/domain STATEMENT:  select * from pg_input_error_info('0', 'weirdfloat');
2024-04-23 16:26:23.138 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(4)
2024-04-23 16:26:23.138 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO domarrtest values (NULL, '{{"toolong","b","c"},{"d","e","f"}}');
2024-04-23 16:26:23.142 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(4)
2024-04-23 16:26:23.142 UTC client backend[19561] pg_regress/domain CONTEXT:  COPY domarrtest, line 1, column testchar4arr: "{qwerty,w,e}"
2024-04-23 16:26:23.142 UTC client backend[19561] pg_regress/domain STATEMENT:  COPY domarrtest FROM stdin;
2024-04-23 16:26:23.142 UTC client backend[19565] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2024-04-23 16:26:23.142 UTC client backend[19565] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2024-04-23 16:26:23.143 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "attmp_wrong" does not exist
2024-04-23 16:26:23.143 UTC client backend[19566] pg_regress/alter_table STATEMENT:  COMMENT ON TABLE attmp_wrong IS 'table comment';
2024-04-23 16:26:23.143 UTC client backend[19566] pg_regress/alter_table ERROR:  column name "xmin" conflicts with a system column name
2024-04-23 16:26:23.143 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp ADD COLUMN xmin integer;
2024-04-23 16:26:23.144 UTC client backend[19565] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2024-04-23 16:26:23.144 UTC client backend[19565] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp ERROR:  ON COMMIT can only be used on temporary tables
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp STATEMENT:  CREATE TABLE temptest(col int) ON COMMIT DELETE ROWS;
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp ERROR:  ON COMMIT can only be used on temporary tables
2024-04-23 16:26:23.147 UTC client backend[19565] pg_regress/temp STATEMENT:  CREATE TABLE temptest(col) ON COMMIT DELETE ROWS AS SELECT 1;
2024-04-23 16:26:23.149 UTC client backend[19544] pg_regress/copy2 ERROR:  column "xyz" of relation "x" does not exist
2024-04-23 16:26:23.149 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x (xyz) from stdin;
2024-04-23 16:26:23.149 UTC client backend[19561] pg_regress/domain ERROR:  duplicate key value violates unique constraint "dcomptable_d1_key"
2024-04-23 16:26:23.149 UTC client backend[19561] pg_regress/domain DETAIL:  Key (d1)=((1,2)) already exists.
2024-04-23 16:26:23.149 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable values (row(1,2)::dcomptype);
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (format CSV, FORMAT CSV);
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (freeze off, freeze on);
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 35
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (delimiter ',', delimiter ',');
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 30
2024-04-23 16:26:23.150 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (null ' ', null ' ');
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (header off, header on);
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 31
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (quote ':', quote ':');
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (escape ':', escape ':');
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 37
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_quote (a), force_quote *);
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 40
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_not_null (a), force_not_null (b));
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 36
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_null (a), force_null (b));
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 45
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (convert_selectively (a), convert_selectively (b));
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 42
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (encoding 'sql_ascii', encoding 'sql_ascii');
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 37
2024-04-23 16:26:23.151 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (on_error ignore, on_error ignore);
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 43
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (log_verbosity default, log_verbosity verbose);
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot specify DELIMITER in BINARY mode
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format BINARY, delimiter ',');
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot specify NULL in BINARY mode
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format BINARY, null 'x');
2024-04-23 16:26:23.152 UTC client backend[19561] pg_regress/domain ERROR:  column "d1" of table "dcomptable" contains values that violate the new constraint
2024-04-23 16:26:23.152 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain dcomptype add constraint c2 check ((value).r > (value).i);
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 ERROR:  only ON_ERROR STOP is allowed in BINARY mode
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (format BINARY, on_error ignore);
2024-04-23 16:26:23.152 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.152 UTC client backend[19561] pg_regress/domain STATEMENT:  select row(2,1)::dcomptype;
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY ON_ERROR "unsupported" not recognized at character 20
2024-04-23 16:26:23.152 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (on_error unsupported);
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE requires CSV mode
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format TEXT, force_quote(a));
2024-04-23 16:26:23.153 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.153 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable values (row(2,1)::comptype);
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE cannot be used with COPY FROM
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin (format CSV, force_quote(a));
2024-04-23 16:26:23.153 UTC client backend[19565] pg_regress/temp ERROR:  unsupported ON COMMIT and foreign key combination
2024-04-23 16:26:23.153 UTC client backend[19565] pg_regress/temp DETAIL:  Table "temptest4" references "temptest3", but they do not have the same ON COMMIT setting.
2024-04-23 16:26:23.153 UTC client backend[19565] pg_regress/temp STATEMENT:  COMMIT;
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL requires CSV mode
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdout (format TEXT, force_not_null(a));
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL cannot be used with COPY TO
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format CSV, force_not_null(a));
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_NULL requires CSV mode
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdout (format TEXT, force_null(a));
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY FORCE_NULL cannot be used with COPY TO
2024-04-23 16:26:23.153 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format CSV, force_null(a));
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY ON_ERROR cannot be used with COPY TO at character 33
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdin (format BINARY, on_error unsupported);
2024-04-23 16:26:23.154 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.154 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable (d1.r, d1.i) values(100, 99);
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY LOG_VERBOSITY "unsupported" not recognized at character 19
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x to stdout (log_verbosity unsupported);
2024-04-23 16:26:23.154 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.154 UTC client backend[19561] pg_regress/domain STATEMENT:  update dcomptable set d1.r = (d1).r + 1 where (d1).i > 0;
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 ERROR:  column "d" specified more than once
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x (a, b, c, d, e, d, c) from stdin;
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 ERROR:  invalid input syntax for type integer: ""
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY x, line 1, column a: ""
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 ERROR:  missing data for column "e"
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2000	230	23	23"
2024-04-23 16:26:23.154 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 ERROR:  missing data for column "e"
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2001	231	\N	\N"
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 ERROR:  extra data after last expected column
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2002	232	40	50	60	70	80"
2024-04-23 16:26:23.155 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2024-04-23 16:26:23.157 UTC client backend[19544] pg_regress/copy2 ERROR:  WHERE clause not allowed with COPY TO at character 18
2024-04-23 16:26:23.157 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x TO stdout WHERE a = 1;
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 ERROR:  column "f" does not exist at character 25
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE f > 60003;
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 ERROR:  aggregate functions are not allowed in COPY FROM WHERE conditions at character 29
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a = max(x.b);
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot use subquery in COPY FROM WHERE condition at character 27
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a IN (SELECT 1 FROM x);
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 ERROR:  set-returning functions are not allowed in COPY FROM WHERE conditions at character 31
2024-04-23 16:26:23.158 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a IN (generate_series(1,5));
2024-04-23 16:26:23.159 UTC client backend[19544] pg_regress/copy2 ERROR:  window functions are not allowed in COPY FROM WHERE conditions at character 29
2024-04-23 16:26:23.159 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a = row_number() over(b);
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a;
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_e" references "truncate_a".
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.162 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a,trunc_b;
2024-04-23 16:26:23.163 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.163 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2024-04-23 16:26:23.163 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.163 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a,trunc_e;
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_d" references "trunc_c".
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_d" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c;
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_e" references "trunc_c".
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.164 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,trunc_d;
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp ERROR:  function nonempty(unknown) does not exist at character 8
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp STATEMENT:  select nonempty('');
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp ERROR:  value for domain nonempty violates check constraint "nonempty_check"
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp STATEMENT:  select pg_temp.nonempty('');
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp ERROR:  value for domain nonempty violates check constraint "nonempty_check"
2024-04-23 16:26:23.165 UTC client backend[19565] pg_regress/temp STATEMENT:  select ''::nonempty;
2024-04-23 16:26:23.165 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.165 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2024-04-23 16:26:23.165 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.165 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,trunc_d,trunc_e,truncate_a;
2024-04-23 16:26:23.166 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.166 UTC client backend[19561] pg_regress/domain STATEMENT:  select makedcomp(2,1);
2024-04-23 16:26:23.167 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.167 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2024-04-23 16:26:23.167 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.167 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a RESTRICT;
2024-04-23 16:26:23.171 UTC client backend[19566] pg_regress/alter_table ERROR:  column number must be in range from 1 to 32767 at character 36
2024-04-23 16:26:23.171 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 0 SET STATISTICS 1000;
2024-04-23 16:26:23.171 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter statistics on non-expression column "a" of index "attmp_idx"
2024-04-23 16:26:23.171 UTC client backend[19566] pg_regress/alter_table HINT:  Alter statistics on table column instead.
2024-04-23 16:26:23.171 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 1 SET STATISTICS 1000;
2024-04-23 16:26:23.173 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2024-04-23 16:26:23.173 UTC client backend[19561] pg_regress/domain STATEMENT:  select row(0,1)::dcomptype;
2024-04-23 16:26:23.175 UTC client backend[19561] pg_regress/domain ERROR:  operator does not exist: character varying > double precision
2024-04-23 16:26:23.175 UTC client backend[19561] pg_regress/domain HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.175 UTC client backend[19561] pg_regress/domain STATEMENT:  alter type comptype alter attribute r type varchar;
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "truncate_a" references "trunc_c".
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "truncate_a" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c;
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_d" references "trunc_c".
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_d" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.175 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a;
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_e" references "trunc_c".
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a,trunc_d;
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.176 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a,trunc_d,trunc_e;
2024-04-23 16:26:23.178 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter statistics on non-expression column "b" of index "attmp_idx"
2024-04-23 16:26:23.178 UTC client backend[19566] pg_regress/alter_table HINT:  Alter statistics on table column instead.
2024-04-23 16:26:23.178 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 3 SET STATISTICS 1000;
2024-04-23 16:26:23.178 UTC client backend[19566] pg_regress/alter_table ERROR:  column number 4 of relation "attmp_idx" does not exist
2024-04-23 16:26:23.178 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 4 SET STATISTICS 1000;
2024-04-23 16:26:23.185 UTC client backend[19561] pg_regress/domain ERROR:  cannot drop column r of composite type comptype because other objects depend on it
2024-04-23 16:26:23.185 UTC client backend[19561] pg_regress/domain DETAIL:  constraint c1 depends on column r of composite type comptype
2024-04-23 16:26:23.185 UTC client backend[19561] pg_regress/domain HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:23.185 UTC client backend[19561] pg_regress/domain STATEMENT:  alter type comptype drop attribute r;
2024-04-23 16:26:23.340 UTC client backend[19541] pg_regress/limit ERROR:  SKIP LOCKED and WITH TIES options cannot be used together
2024-04-23 16:26:23.340 UTC client backend[19541] pg_regress/limit STATEMENT:  SELECT  thousand
			FROM onek WHERE thousand < 5
			ORDER BY thousand FETCH FIRST 1 ROW WITH TIES FOR UPDATE SKIP LOCKED;
2024-04-23 16:26:23.340 UTC client backend[19541] pg_regress/limit ERROR:  WITH TIES cannot be specified without ORDER BY clause
2024-04-23 16:26:23.340 UTC client backend[19541] pg_regress/limit STATEMENT:  SELECT ''::text AS two, unique1, unique2, stringu1
			FROM onek WHERE unique1 > 50
			FETCH FIRST 2 ROW WITH TIES;
2024-04-23 16:26:23.343 UTC client backend[19573] pg_regress/polymorphism ERROR:  operator does not exist: point + integer at character 13
2024-04-23 16:26:23.343 UTC client backend[19573] pg_regress/polymorphism HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.343 UTC client backend[19573] pg_regress/polymorphism QUERY:  
	  select x + 1
	
2024-04-23 16:26:23.343 UTC client backend[19573] pg_regress/polymorphism CONTEXT:  SQL function "polyf" during inlining
2024-04-23 16:26:23.343 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(point(3,4));
2024-04-23 16:26:23.366 UTC client backend[19558] pg_regress/sequence ERROR:  smallint out of range
2024-04-23 16:26:23.366 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f3)
	  VALUES ('bogus', -32769);
2024-04-23 16:26:23.367 UTC client backend[19558] pg_regress/sequence ERROR:  smallint out of range
2024-04-23 16:26:23.367 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f4)
	  VALUES ('bogus', -32769);
2024-04-23 16:26:23.368 UTC client backend[19558] pg_regress/sequence ERROR:  smallint out of range
2024-04-23 16:26:23.368 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f3)
	  VALUES ('bogus', 32768);
2024-04-23 16:26:23.369 UTC client backend[19558] pg_regress/sequence ERROR:  smallint out of range
2024-04-23 16:26:23.369 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f4)
	  VALUES ('bogus', 32768);
2024-04-23 16:26:23.370 UTC client backend[19558] pg_regress/sequence ERROR:  bigint out of range
2024-04-23 16:26:23.370 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f5)
	  VALUES ('bogus', -9223372036854775809);
2024-04-23 16:26:23.372 UTC client backend[19558] pg_regress/sequence ERROR:  bigint out of range
2024-04-23 16:26:23.372 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f6)
	  VALUES ('bogus', -9223372036854775809);
2024-04-23 16:26:23.373 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine element type of "anyarray" argument
2024-04-23 16:26:23.373 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(stavalues1) from pg_statistic;
2024-04-23 16:26:23.374 UTC client backend[19558] pg_regress/sequence ERROR:  bigint out of range
2024-04-23 16:26:23.374 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f5)
	  VALUES ('bogus', 9223372036854775808);
2024-04-23 16:26:23.374 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "attmp" does not exist at character 15
2024-04-23 16:26:23.374 UTC client backend[19566] pg_regress/alter_table STATEMENT:  SELECT * FROM attmp;
2024-04-23 16:26:23.374 UTC client backend[19545] pg_regress/plpgsql ERROR:  function tg_hub_adjustslots_wrong(character, integer, integer) does not exist
2024-04-23 16:26:23.374 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  COMMENT ON FUNCTION tg_hub_adjustslots_wrong(bpchar, integer, integer) IS 'function with args';
2024-04-23 16:26:23.375 UTC client backend[19558] pg_regress/sequence ERROR:  bigint out of range
2024-04-23 16:26:23.375 UTC client backend[19558] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f6)
	  VALUES ('bogus', 9223372036854775808);
2024-04-23 16:26:23.376 UTC client backend[19571] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe)" at character 8
2024-04-23 16:26:23.376 UTC client backend[19571] pg_regress/rowtypes DETAIL:  Too few columns.
2024-04-23 16:26:23.376 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select '(Joe)'::fullname;
2024-04-23 16:26:23.380 UTC client backend[19571] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe,,)" at character 8
2024-04-23 16:26:23.380 UTC client backend[19571] pg_regress/rowtypes DETAIL:  Too many columns.
2024-04-23 16:26:23.380 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select '(Joe,,)'::fullname;
2024-04-23 16:26:23.381 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2024-04-23 16:26:23.381 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2024-04-23 16:26:23.382 UTC client backend[19571] pg_regress/rowtypes ERROR:  malformed record literal: "[]" at character 8
2024-04-23 16:26:23.382 UTC client backend[19571] pg_regress/rowtypes DETAIL:  Missing left parenthesis.
2024-04-23 16:26:23.382 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select '[]'::fullname;
2024-04-23 16:26:23.382 UTC client backend[19573] pg_regress/polymorphism ERROR:  return type anyarray is not supported for SQL functions
2024-04-23 16:26:23.382 UTC client backend[19573] pg_regress/polymorphism CONTEXT:  SQL function "polyf" during inlining
2024-04-23 16:26:23.382 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(stavalues1) from pg_statistic;
2024-04-23 16:26:23.385 UTC client backend[19571] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe,Blow) /" at character 8
2024-04-23 16:26:23.385 UTC client backend[19571] pg_regress/rowtypes DETAIL:  Junk after right parenthesis.
2024-04-23 16:26:23.385 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select '(Joe,Blow) /'::fullname;
2024-04-23 16:26:23.386 UTC client backend[19561] pg_regress/domain ERROR:  duplicate key value violates unique constraint "dcomptable_d1_key"
2024-04-23 16:26:23.386 UTC client backend[19561] pg_regress/domain DETAIL:  Key (d1)=({"(1,2)"}) already exists.
2024-04-23 16:26:23.386 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable values (array[row(1,2)]::dcomptypea);
2024-04-23 16:26:23.387 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine result data type
2024-04-23 16:26:23.387 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:26:23.387 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function polyf(x anyelement) returns anyrange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2024-04-23 16:26:23.387 UTC client backend[19541] pg_regress/limit ERROR:  row count cannot be null in FETCH FIRST ... WITH TIES clause
2024-04-23 16:26:23.387 UTC client backend[19541] pg_regress/limit STATEMENT:  CREATE VIEW limit_thousand_v_3 AS SELECT thousand FROM onek WHERE thousand < 995
			ORDER BY thousand FETCH FIRST NULL ROWS WITH TIES;
2024-04-23 16:26:23.388 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2024-04-23 16:26:23.388 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2024-04-23 16:26:23.411 UTC client backend[19571] pg_regress/rowtypes ERROR:  missing FROM-clause entry for table "q" at character 12
2024-04-23 16:26:23.411 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select f1, q.c1 from quadtable;
2024-04-23 16:26:23.429 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2024-04-23 16:26:23.429 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2024-04-23 16:26:23.444 UTC client backend[19561] pg_regress/domain ERROR:  column "d1" of table "dcomptable" contains values that violate the new constraint
2024-04-23 16:26:23.444 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain dcomptypea add constraint c2 check (value[1].r > value[1].i);
2024-04-23 16:26:23.444 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot alter table "fullname" because column "people.fn" uses its row type
2024-04-23 16:26:23.444 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  alter table fullname add column suffix text default '';
2024-04-23 16:26:23.445 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2024-04-23 16:26:23.445 UTC client backend[19561] pg_regress/domain STATEMENT:  select array[row(2,1)]::dcomptypea;
2024-04-23 16:26:23.446 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of index part_attmp_index
2024-04-23 16:26:23.446 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX part_attmp_index RENAME TO fail;
2024-04-23 16:26:23.447 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of index part_attmp1_index
2024-04-23 16:26:23.447 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX part_attmp1_index RENAME TO fail;
2024-04-23 16:26:23.447 UTC client backend[19573] pg_regress/polymorphism ERROR:  function polyf(int4range, integer, numeric) does not exist at character 8
2024-04-23 16:26:23.447 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.447 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(int4range(42, 49), 11, 4.5) as fail;
2024-04-23 16:26:23.448 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of table part_at2tmp
2024-04-23 16:26:23.448 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_at2tmp RENAME TO fail;
2024-04-23 16:26:23.448 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2024-04-23 16:26:23.448 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable values (array[row(2,1)]::comptype[]);
2024-04-23 16:26:23.449 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.449 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_func';
2024-04-23 16:26:23.450 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of table part_at2tmp1
2024-04-23 16:26:23.450 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_at2tmp1 RENAME TO fail;
2024-04-23 16:26:23.452 UTC client backend[19573] pg_regress/polymorphism ERROR:  function polyf(int4multirange, integer, numeric) does not exist at character 8
2024-04-23 16:26:23.452 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.452 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(multirange(int4range(42, 49)), 11, 4.5) as fail;
2024-04-23 16:26:23.452 UTC client backend[19558] pg_regress/sequence ERROR:  currval of sequence "sequence_test" is not yet defined in this session
2024-04-23 16:26:23.452 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT currval('sequence_test'::regclass);
2024-04-23 16:26:23.452 UTC client backend[19571] pg_regress/rowtypes ERROR:  subfield "c1" is of type complex but expression is of type integer at character 22
2024-04-23 16:26:23.452 UTC client backend[19571] pg_regress/rowtypes HINT:  You will need to rewrite or cast the expression.
2024-04-23 16:26:23.452 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  update quadtable set q.c1 = 12;
2024-04-23 16:26:23.452 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.452 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_func';
2024-04-23 16:26:23.453 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine result data type
2024-04-23 16:26:23.453 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:26:23.453 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function polyf(x anycompatible) returns anycompatiblerange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2024-04-23 16:26:23.453 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2024-04-23 16:26:23.453 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dcomptable (d1[1].r, d1[1].i) values(100, 99);
2024-04-23 16:26:23.454 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2024-04-23 16:26:23.454 UTC client backend[19561] pg_regress/domain STATEMENT:  update dcomptable set d1[1].r = d1[1].r + 1 where d1[1].i > 0;
2024-04-23 16:26:23.454 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.454 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_operator';
2024-04-23 16:26:23.455 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.455 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_type';
2024-04-23 16:26:23.458 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.458 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_view';
2024-04-23 16:26:23.461 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.461 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_sequence';
2024-04-23 16:26:23.464 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine result data type
2024-04-23 16:26:23.464 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anycompatiblemultirange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:26:23.464 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function polyf(x anycompatible) returns anycompatiblemultirange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2024-04-23 16:26:23.464 UTC client backend[19544] pg_regress/copy2 ERROR:  null value in column "b" of relation "forcetest" violates not-null constraint
2024-04-23 16:26:23.464 UTC client backend[19544] pg_regress/copy2 DETAIL:  Failing row contains (3, null, , null, null).
2024-04-23 16:26:23.464 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY forcetest, line 1: "3,,"""
2024-04-23 16:26:23.464 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b), FORCE_NOT_NULL(c));
2024-04-23 16:26:23.469 UTC client backend[19544] pg_regress/copy2 ERROR:  FORCE_NOT_NULL column "b" not referenced by COPY
2024-04-23 16:26:23.469 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL(b));
2024-04-23 16:26:23.470 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.470 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2024-04-23 16:26:23.472 UTC client backend[19544] pg_regress/copy2 ERROR:  FORCE_NULL column "b" not referenced by COPY
2024-04-23 16:26:23.472 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b));
2024-04-23 16:26:23.473 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.473 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2024-04-23 16:26:23.475 UTC client backend[19573] pg_regress/polymorphism ERROR:  function polyf(integer, numeric[], integer, numeric) does not exist at character 48
2024-04-23 16:26:23.475 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.475 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x), y, pg_typeof(y)
	  from polyf(11, array[1, 2.2], 42, 34.5);
2024-04-23 16:26:23.477 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.477 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2024-04-23 16:26:23.479 UTC client backend[19558] pg_regress/sequence ERROR:  cannot drop sequence t1_f1_seq because other objects depend on it
2024-04-23 16:26:23.479 UTC client backend[19558] pg_regress/sequence DETAIL:  default value for column f1 of table t1 depends on sequence t1_f1_seq
2024-04-23 16:26:23.479 UTC client backend[19558] pg_regress/sequence HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:23.479 UTC client backend[19558] pg_regress/sequence STATEMENT:  DROP SEQUENCE t1_f1_seq;
2024-04-23 16:26:23.480 UTC client backend[19558] pg_regress/sequence ERROR:  cannot drop sequence myseq2 because other objects depend on it
2024-04-23 16:26:23.480 UTC client backend[19558] pg_regress/sequence DETAIL:  default value for column f2 of table t1 depends on sequence myseq2
2024-04-23 16:26:23.480 UTC client backend[19558] pg_regress/sequence HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:23.480 UTC client backend[19558] pg_regress/sequence STATEMENT:  DROP SEQUENCE myseq2;
2024-04-23 16:26:23.481 UTC client backend[19565] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.481 UTC client backend[19565] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2024-04-23 16:26:23.481 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2024-04-23 16:26:23.481 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.487 UTC client backend[19610] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2024-04-23 16:26:23.487 UTC client backend[19610] pg_regress/temp STATEMENT:  PREPARE TRANSACTION 'twophase_search';
2024-04-23 16:26:23.488 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 73
2024-04-23 16:26:23.488 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL *, FORCE_NOT_NULL(b));
2024-04-23 16:26:23.488 UTC client backend[19544] pg_regress/copy2 ERROR:  conflicting or redundant options at character 69
2024-04-23 16:26:23.488 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL *, FORCE_NULL(b));
2024-04-23 16:26:23.488 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not determine interpretation of row comparison operator ~~ at character 25
2024-04-23 16:26:23.488 UTC client backend[19571] pg_regress/rowtypes HINT:  Row comparison operators must be associated with btree operator families.
2024-04-23 16:26:23.488 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select ROW('ABC','DEF') ~~ ROW('DEF','ABC') as fail;
2024-04-23 16:26:23.495 UTC client backend[19558] pg_regress/sequence ERROR:  sequence "t1_f1_seq" does not exist
2024-04-23 16:26:23.495 UTC client backend[19558] pg_regress/sequence STATEMENT:  DROP SEQUENCE t1_f1_seq;
2024-04-23 16:26:23.495 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2024-04-23 16:26:23.495 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.497 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of index onek_unique1
2024-04-23 16:26:23.497 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER INDEX onek_unique1 RENAME TO fail;
2024-04-23 16:26:23.503 UTC client backend[19561] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check"
2024-04-23 16:26:23.503 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into pitable values(array[-1]);
2024-04-23 16:26:23.503 UTC client backend[19558] pg_regress/sequence ERROR:  cannot open relation "serialtest1"
2024-04-23 16:26:23.503 UTC client backend[19558] pg_regress/sequence DETAIL:  This operation is not supported for tables.
2024-04-23 16:26:23.503 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE serialTest1 CYCLE;
2024-04-23 16:26:23.503 UTC client backend[19561] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check" at character 28
2024-04-23 16:26:23.503 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into pitable values('{0}');
2024-04-23 16:26:23.503 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2024-04-23 16:26:23.503 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.504 UTC client backend[19561] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check"
2024-04-23 16:26:23.504 UTC client backend[19561] pg_regress/domain STATEMENT:  update pitable set f1[1] = 0;
2024-04-23 16:26:23.508 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2024-04-23 16:26:23.508 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.509 UTC client backend[19558] pg_regress/sequence ERROR:  RESTART value (0) cannot be less than MINVALUE (1)
2024-04-23 16:26:23.509 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test2 RESTART WITH 0;
2024-04-23 16:26:23.509 UTC client backend[19558] pg_regress/sequence ERROR:  RESTART value (40) cannot be greater than MAXVALUE (-1)
2024-04-23 16:26:23.509 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test4 RESTART WITH 40;
2024-04-23 16:26:23.509 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2024-04-23 16:26:23.509 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.510 UTC client backend[19554] pg_regress/with ERROR:  INSERT ... SELECT rule actions are not supported for queries having data-modifying statements in WITH
2024-04-23 16:26:23.510 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t1 AS ( DELETE FROM bug6051 RETURNING * )
	INSERT INTO bug6051 SELECT * FROM t1;
2024-04-23 16:26:23.511 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(4)
2024-04-23 16:26:23.511 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into vc4table values(array['too long']);
2024-04-23 16:26:23.512 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblemultirange because input has type unknown
2024-04-23 16:26:23.512 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select polyf(null);
2024-04-23 16:26:23.517 UTC client backend[19558] pg_regress/sequence ERROR:  nextval: reached maximum value of sequence "sequence_test2" (36)
2024-04-23 16:26:23.517 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2024-04-23 16:26:23.517 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of view attmp_view_new
2024-04-23 16:26:23.517 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER VIEW attmp_view_new RENAME TO fail;
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain ERROR:  column "f1" is of type dposinta[] but expression is of type integer[] at character 34
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain HINT:  You will need to rewrite or cast the expression.
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dposintatable values(array[array[42]]);
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain ERROR:  column "f1" is of type dposinta[] but expression is of type posint[] at character 34
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain HINT:  You will need to rewrite or cast the expression.
2024-04-23 16:26:23.518 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dposintatable values(array[array[42]::posint[]]);
2024-04-23 16:26:23.521 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.521 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.521 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp02a(*) (SFUNC = stfnp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.529 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types bigint and integer at record column 1
2024-04-23 16:26:23.529 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select * from int8_tbl i8 where i8 in (row(123,456));
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify column "nosuch" in record data type at character 9
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select (row(1, 2.0)).nosuch;
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify column "f3" in record data type at character 9
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select (r).f3 from (select row(1, 2.0) as r) ss;
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare rows of zero length at character 14
2024-04-23 16:26:23.530 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select ROW() = ROW();
2024-04-23 16:26:23.576 UTC client backend[19561] pg_regress/domain ERROR:  wrong number of array subscripts
2024-04-23 16:26:23.576 UTC client backend[19561] pg_regress/domain STATEMENT:  update dposintatable set f1[2][1] = array[97];
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp04a(*) (SFUNC = stfp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.576 UTC client backend[19561] pg_regress/domain ERROR:  syntax error at or near "[" at character 33
2024-04-23 16:26:23.576 UTC client backend[19561] pg_regress/domain STATEMENT:  update dposintatable set (f1[2])[1] = array[98];
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.576 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp04b(*) (SFUNC = stfp, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.576 UTC client backend[19558] pg_regress/sequence ERROR:  nextval: reached minimum value of sequence "sequence_test2" (-36)
2024-04-23 16:26:23.576 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2024-04-23 16:26:23.579 UTC client backend[19558] pg_regress/sequence ERROR:  setval: value -100 is out of bounds for sequence "sequence_test2" (5..36)
2024-04-23 16:26:23.579 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', -100);
2024-04-23 16:26:23.580 UTC client backend[19558] pg_regress/sequence ERROR:  setval: value 100 is out of bounds for sequence "sequence_test2" (5..36)
2024-04-23 16:26:23.580 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', 100);
2024-04-23 16:26:23.580 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2024-04-23 16:26:23.580 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.586 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2024-04-23 16:26:23.586 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.586 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop index onek_unique1_constraint because constraint onek_unique1_constraint on table onek requires it
2024-04-23 16:26:23.586 UTC client backend[19566] pg_regress/alter_table HINT:  You can drop constraint onek_unique1_constraint on table onek instead.
2024-04-23 16:26:23.586 UTC client backend[19566] pg_regress/alter_table STATEMENT:  DROP INDEX onek_unique1_constraint;
2024-04-23 16:26:23.587 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2024-04-23 16:26:23.587 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp11b(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  INITCOND = '{}');
2024-04-23 16:26:23.587 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "dcomptype_check"
2024-04-23 16:26:23.587 UTC client backend[19561] pg_regress/domain STATEMENT:  update dcomptable set f1[1].cf1 = -1;
2024-04-23 16:26:23.588 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2024-04-23 16:26:23.588 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.588 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop index onek_unique1_constraint_foo because constraint onek_unique1_constraint_foo on table onek requires it
2024-04-23 16:26:23.588 UTC client backend[19566] pg_regress/alter_table HINT:  You can drop constraint onek_unique1_constraint_foo on table onek instead.
2024-04-23 16:26:23.588 UTC client backend[19566] pg_regress/alter_table STATEMENT:  DROP INDEX onek_unique1_constraint_foo;
2024-04-23 16:26:23.588 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2024-04-23 16:26:23.588 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp12b(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  INITCOND = '{}');
2024-04-23 16:26:23.589 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.589 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.589 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.590 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.590 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.590 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.591 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2024-04-23 16:26:23.591 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp15a(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.592 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.592 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp16a(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.592 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.592 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.592 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.593 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.593 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.593 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp17b(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.594 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp18b(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.595 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.595 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp19a(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2024-04-23 16:26:23.596 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.596 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp19b(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, INITCOND = '{}');
2024-04-23 16:26:23.600 UTC client backend[19558] pg_regress/sequence ERROR:  relation "asdf" does not exist
2024-04-23 16:26:23.600 UTC client backend[19558] pg_regress/sequence STATEMENT:  COMMENT ON SEQUENCE asdf IS 'won''t work';
2024-04-23 16:26:23.602 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.602 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO nulltest DEFAULT VALUES;
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn02a(*) (SFUNC = stfnp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.602 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn02b(*) (SFUNC = stfnp, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.602 UTC client backend[19561] pg_regress/domain ERROR:  domain dcheck does not allow null values
2024-04-23 16:26:23.602 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into nulltest values ('a', 'b', 'c', 'd', NULL);
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain ERROR:  new row for relation "nulltest" violates check constraint "nulltest_col5_check"
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (a, b, c, d, a).
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into nulltest values ('a', 'b', 'c', 'd', 'a');
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO nulltest values (NULL, 'b', 'c', 'd', 'd');
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO nulltest values ('a', NULL, 'c', 'd', 'c');
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain ERROR:  null value in column "col3" of relation "nulltest" violates not-null constraint
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (a, b, null, d, c).
2024-04-23 16:26:23.603 UTC client backend[19561] pg_regress/domain STATEMENT:  INSERT INTO nulltest values ('a', 'b', NULL, 'd', 'c');
2024-04-23 16:26:23.604 UTC client backend[19544] pg_regress/copy2 ERROR:  new row for relation "check_con_tbl" violates check constraint "check_con_tbl_check"
2024-04-23 16:26:23.604 UTC client backend[19544] pg_regress/copy2 DETAIL:  Failing row contains (0).
2024-04-23 16:26:23.604 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY check_con_tbl, line 1: "0"
2024-04-23 16:26:23.604 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy check_con_tbl from stdin;
2024-04-23 16:26:23.604 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot rename inherited constraint "con1"
2024-04-23 16:26:23.604 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE constraint_rename_test2 RENAME CONSTRAINT con1 TO con1foo;
2024-04-23 16:26:23.604 UTC client backend[19566] pg_regress/alter_table ERROR:  inherited constraint "con1" must be renamed in child tables too
2024-04-23 16:26:23.604 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY constraint_rename_test RENAME CONSTRAINT con1 TO con1foo;
2024-04-23 16:26:23.607 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.607 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.607 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn04a(*) (SFUNC = stfp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain ERROR:  null value in column "col3" of relation "nulltest" violates not-null constraint
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (a, b, null, d, d).
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain CONTEXT:  COPY nulltest, line 1: "a	b	\N	d	d"
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain ERROR:  domain dcheck does not allow null values
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain CONTEXT:  COPY nulltest, line 1, column col5: null input
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2024-04-23 16:26:23.608 UTC client backend[19558] pg_regress/sequence ERROR:  lastval is not yet defined in this session
2024-04-23 16:26:23.608 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT lastval();
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain ERROR:  new row for relation "nulltest" violates check constraint "nulltest_col5_check"
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (a, b, c, null, a).
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain CONTEXT:  COPY nulltest, line 3: "a	b	c	\N	a"
2024-04-23 16:26:23.608 UTC client backend[19561] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2024-04-23 16:26:23.608 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2024-04-23 16:26:23.608 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.609 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2024-04-23 16:26:23.609 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn07b(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  INITCOND = '{}');
2024-04-23 16:26:23.610 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.610 UTC client backend[19561] pg_regress/domain STATEMENT:  SELECT cast(NULL as dnotnull);
2024-04-23 16:26:23.610 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.610 UTC client backend[19561] pg_regress/domain STATEMENT:  SELECT cast(cast(NULL as dnull) as dnotnull);
2024-04-23 16:26:23.611 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2024-04-23 16:26:23.611 UTC client backend[19561] pg_regress/domain STATEMENT:  SELECT cast(col4 as dnotnull) from nulltest;
2024-04-23 16:26:23.612 UTC client backend[19558] pg_regress/sequence ERROR:  lastval is not yet defined in this session
2024-04-23 16:26:23.612 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT lastval();
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn13b(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.613 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn14b(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  INITCOND = '{}');
2024-04-23 16:26:23.614 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2024-04-23 16:26:23.614 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn15a(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn15b(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn16a(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn16b(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine transition data type
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn19a(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism ERROR:  function ffnp(anyarray) does not exist
2024-04-23 16:26:23.616 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn20a(BASETYPE = anyelement, SFUNC = tfp,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2024-04-23 16:26:23.617 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify an ordering operator for type cantcompare at character 27
2024-04-23 16:26:23.617 UTC client backend[19571] pg_regress/rowtypes HINT:  Use an explicit ordering operator or modify the query.
2024-04-23 16:26:23.617 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select * from cc order by f1;
2024-04-23 16:26:23.719 UTC client backend[19555] pg_regress/largeobject ERROR:  large object read request is too large
2024-04-23 16:26:23.719 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_get(25526);
2024-04-23 16:26:23.741 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2024-04-23 16:26:23.741 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 < row(1, 'abc')::testtype3;
2024-04-23 16:26:23.741 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2024-04-23 16:26:23.741 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 <> row(1, 'abc')::testtype3;
2024-04-23 16:26:23.743 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2024-04-23 16:26:23.743 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 < row(1)::testtype5;
2024-04-23 16:26:23.744 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2024-04-23 16:26:23.744 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 <> row(1)::testtype5;
2024-04-23 16:26:23.752 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify a comparison function for type point
2024-04-23 16:26:23.752 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, '(1,2)')::testtype6 < row(1, '(1,3)')::testtype6;
2024-04-23 16:26:23.752 UTC client backend[19558] pg_regress/sequence ERROR:  cannot execute nextval() in a read-only transaction
2024-04-23 16:26:23.752 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2024-04-23 16:26:23.752 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify an equality operator for type point
2024-04-23 16:26:23.752 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, '(1,2)')::testtype6 <> row(1, '(1,3)')::testtype6;
2024-04-23 16:26:23.754 UTC client backend[19558] pg_regress/sequence ERROR:  cannot execute setval() in a read-only transaction
2024-04-23 16:26:23.754 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', 1);
2024-04-23 16:26:23.758 UTC client backend[19558] pg_regress/sequence ERROR:  permission denied for sequence seq3
2024-04-23 16:26:23.758 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT nextval('seq3');
2024-04-23 16:26:23.790 UTC client backend[19544] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2024-04-23 16:26:23.790 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY rls_t1 TO stdout;
2024-04-23 16:26:23.791 UTC client backend[19561] pg_regress/domain ERROR:  null value in column "col5" of relation "defaulttest" violates not-null constraint
2024-04-23 16:26:23.791 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12).
2024-04-23 16:26:23.791 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into defaulttest(col4) values(0);
2024-04-23 16:26:23.791 UTC client backend[19544] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2024-04-23 16:26:23.791 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY rls_t1 (a, b, c) TO stdout;
2024-04-23 16:26:23.791 UTC client backend[19544] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2024-04-23 16:26:23.791 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY rls_t1 (c) TO stdout;
2024-04-23 16:26:23.792 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_open(INV_WRITE) in a read-only transaction
2024-04-23 16:26:23.792 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_open(2121, x'20000'::int);
2024-04-23 16:26:23.797 UTC client backend[19573] pg_regress/polymorphism ERROR:  function add_group(smallint[], bigint, integer) does not exist
2024-04-23 16:26:23.797 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create aggregate build_group(int8, integer) (
	  SFUNC = add_group,
	  STYPE = int2[]
	);
2024-04-23 16:26:23.799 UTC client backend[19554] pg_regress/with ERROR:  WITH RECURSIVE is not supported for MERGE statement
2024-04-23 16:26:23.799 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE cte_basic AS (SELECT 1 a, 'cte_basic val' b)
	MERGE INTO m USING (select 0 k, 'merge source SubPlan' v) o ON m.k=o.k
	WHEN MATCHED THEN UPDATE SET v = (SELECT b || ' merge update' FROM cte_basic WHERE cte_basic.a = m.k LIMIT 1)
	WHEN NOT MATCHED THEN INSERT VALUES(o.k, o.v);
2024-04-23 16:26:23.799 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_create() in a read-only transaction
2024-04-23 16:26:23.799 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_create(42);
2024-04-23 16:26:23.800 UTC client backend[19561] pg_regress/domain ERROR:  null value in column "col5" of relation "defaulttest" violates not-null constraint
2024-04-23 16:26:23.800 UTC client backend[19561] pg_regress/domain DETAIL:  Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12).
2024-04-23 16:26:23.800 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into defaulttest(col4) values(0);
2024-04-23 16:26:23.802 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_creat() in a read-only transaction
2024-04-23 16:26:23.802 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_creat(42);
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_unlink() in a read-only transaction
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_unlink(42);
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lowrite() in a read-only transaction
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lowrite(42, 'x');
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_import() in a read-only transaction
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_import('/Users/admin/pgsql/build/testrun/regress/regress/results/lotest.txt');
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_truncate() in a read-only transaction
2024-04-23 16:26:23.803 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_truncate(42, 0);
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_truncate64() in a read-only transaction
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_truncate64(42, 0);
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_from_bytea() in a read-only transaction
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_from_bytea(0, 'x');
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject ERROR:  cannot execute lo_put() in a read-only transaction
2024-04-23 16:26:23.804 UTC client backend[19555] pg_regress/largeobject STATEMENT:  SELECT lo_put(42, 0, 'x');
2024-04-23 16:26:23.833 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2024-04-23 16:26:23.833 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *< row(1, 'abc')::testtype3;
2024-04-23 16:26:23.833 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2024-04-23 16:26:23.833 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *<> row(1, 'abc')::testtype3;
2024-04-23 16:26:23.852 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2024-04-23 16:26:23.852 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *< row(1)::testtype5;
2024-04-23 16:26:23.852 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot copy to view "instead_of_insert_tbl_view"
2024-04-23 16:26:23.852 UTC client backend[19544] pg_regress/copy2 HINT:  To enable copying to a view, provide an INSTEAD OF INSERT trigger.
2024-04-23 16:26:23.852 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY instead_of_insert_tbl_view FROM stdin;
2024-04-23 16:26:23.852 UTC client backend[19571] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2024-04-23 16:26:23.852 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *<> row(1)::testtype5;
2024-04-23 16:26:23.855 UTC client backend[19558] pg_regress/sequence ERROR:  permission denied for sequence seq3
2024-04-23 16:26:23.855 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT currval('seq3');
2024-04-23 16:26:23.861 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot compare arrays of different element types
2024-04-23 16:26:23.861 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select max(histogram_bounds) from pg_stats where tablename = 'pg_am';
2024-04-23 16:26:23.867 UTC client backend[19573] pg_regress/polymorphism ERROR:  function "array_in" in FROM has unsupported return type anyarray at character 15
2024-04-23 16:26:23.867 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from array_in('{1,2,3}','int4'::regtype,-1);
2024-04-23 16:26:23.868 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot accept a value of type anyrange
2024-04-23 16:26:23.868 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select anyrange_in('[10,20)','int4range'::regtype,-1);
2024-04-23 16:26:23.873 UTC client backend[19573] pg_regress/polymorphism ERROR:  function myleast() does not exist at character 8
2024-04-23 16:26:23.873 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.873 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select myleast();
2024-04-23 16:26:23.875 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function result type must be integer because of OUT parameters
2024-04-23 16:26:23.875 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int) RETURNS float
	AS 'select $1+1' LANGUAGE sql;
2024-04-23 16:26:23.877 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function result type must be record because of OUT parameters
2024-04-23 16:26:23.877 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int, out f3 text) RETURNS int
	AS 'select $1+1' LANGUAGE sql;
2024-04-23 16:26:23.878 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot change return type of existing function
2024-04-23 16:26:23.878 UTC client backend[19562] pg_regress/rangefuncs HINT:  Use DROP FUNCTION rngfunc(integer) first.
2024-04-23 16:26:23.878 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int, out f3 text)
	RETURNS record
	AS 'select $1+1' LANGUAGE sql;
2024-04-23 16:26:23.880 UTC client backend[19544] pg_regress/copy2 ERROR:  invalid input syntax for type integer: "a"
2024-04-23 16:26:23.880 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 2, column n: "a"
2024-04-23 16:26:23.880 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error stop);
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism ERROR:  function formarray(numeric, numeric[]) does not exist at character 8
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select formarray(1.1, array[1.2,55.5]);
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism ERROR:  function formarray(integer, text) does not exist at character 8
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.884 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select formarray(1, 'x'::text);
2024-04-23 16:26:23.885 UTC client backend[19573] pg_regress/polymorphism ERROR:  function formarray(integer, text[]) does not exist at character 8
2024-04-23 16:26:23.885 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.885 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select formarray(1, variadic array['x'::text]);
2024-04-23 16:26:23.891 UTC client backend[19562] pg_regress/rangefuncs ERROR:  could not determine polymorphic type because input has type unknown
2024-04-23 16:26:23.891 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  SELECT dup('xyz');
2024-04-23 16:26:23.891 UTC client backend[19544] pg_regress/copy2 ERROR:  invalid input syntax for type widget: "1"
2024-04-23 16:26:23.891 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY hard_err, line 1, column foo: "1"
2024-04-23 16:26:23.891 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY hard_err FROM STDIN WITH (on_error ignore);
2024-04-23 16:26:23.892 UTC client backend[19544] pg_regress/copy2 ERROR:  missing data for column "k"
2024-04-23 16:26:23.892 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 1: "1	{1}"
2024-04-23 16:26:23.892 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error ignore);
2024-04-23 16:26:23.892 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot change name of input parameter "f1"
2024-04-23 16:26:23.892 UTC client backend[19562] pg_regress/rangefuncs HINT:  Use DROP FUNCTION dup(anyelement) first.
2024-04-23 16:26:23.892 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION dup (inout f2 anyelement, out f3 anyarray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2024-04-23 16:26:23.893 UTC client backend[19544] pg_regress/copy2 ERROR:  extra data after last expected column
2024-04-23 16:26:23.893 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 1: "1	{1}	3	abc"
2024-04-23 16:26:23.893 UTC client backend[19544] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error ignore);
2024-04-23 16:26:23.898 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot determine result data type
2024-04-23 16:26:23.898 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  A result of type anyelement requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2024-04-23 16:26:23.898 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE FUNCTION bad (f1 int, out f2 anyelement, out f3 anyarray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2024-04-23 16:26:23.898 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer, integer, integer) does not exist at character 8
2024-04-23 16:26:23.898 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.898 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc(10, 20, 30);
2024-04-23 16:26:23.899 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc() does not exist
2024-04-23 16:26:23.899 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  drop function dfunc();
2024-04-23 16:26:23.901 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer) does not exist
2024-04-23 16:26:23.901 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  drop function dfunc(int);
2024-04-23 16:26:23.901 UTC client backend[19567] pg_regress/truncate ERROR:  relation "truncate_a_id1" does not exist at character 16
2024-04-23 16:26:23.901 UTC client backend[19567] pg_regress/truncate STATEMENT:  SELECT nextval('truncate_a_id1');
2024-04-23 16:26:23.902 UTC client backend[19573] pg_regress/polymorphism ERROR:  input parameters after one with a default value must also have defaults
2024-04-23 16:26:23.902 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function dfunc(a int = 1, b int) returns int as $$
	  select $1 + $2;
	$$ language sql;
2024-04-23 16:26:23.904 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate only a partitioned table
2024-04-23 16:26:23.904 UTC client backend[19567] pg_regress/truncate HINT:  Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly.
2024-04-23 16:26:23.904 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE ONLY truncparted;
2024-04-23 16:26:23.906 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate only a partitioned table
2024-04-23 16:26:23.906 UTC client backend[19567] pg_regress/truncate HINT:  Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly.
2024-04-23 16:26:23.906 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE ONLY truncparted;
2024-04-23 16:26:23.908 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot determine result data type
2024-04-23 16:26:23.908 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  A result of type anycompatible requires at least one input of type anycompatible, anycompatiblearray, anycompatiblenonarray, anycompatiblerange, or anycompatiblemultirange.
2024-04-23 16:26:23.908 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  CREATE FUNCTION bad (f1 anyarray, out f2 anycompatible, out f3 anycompatiblearray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2024-04-23 16:26:23.910 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc() is not unique at character 8
2024-04-23 16:26:23.910 UTC client backend[19573] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2024-04-23 16:26:23.910 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc();
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with ERROR:  recursive query "t" must not contain data-modifying statements at character 16
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE t AS (
		INSERT INTO y
			SELECT * FROM t
	)
	VALUES(FALSE);
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with ERROR:  WITH query "t" does not have a RETURNING clause at character 54
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	SELECT * FROM t;
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with ERROR:  recursive query "t" must not contain data-modifying statements at character 16
2024-04-23 16:26:23.912 UTC client backend[19554] pg_regress/with STATEMENT:  WITH RECURSIVE t(action, a) AS (
		MERGE INTO y USING (VALUES (11)) v(a) ON y.a = v.a
			WHEN NOT MATCHED THEN INSERT VALUES (v.a)
			RETURNING merge_action(), (SELECT a FROM t)
	)
	SELECT * FROM t;
2024-04-23 16:26:23.913 UTC client backend[19554] pg_regress/with ERROR:  WITH clause containing a data-modifying statement must be at the top level at character 23
2024-04-23 16:26:23.913 UTC client backend[19554] pg_regress/with STATEMENT:  SELECT * FROM (
		WITH t AS (UPDATE y SET a=a+1 RETURNING *)
		SELECT * FROM t
	) ss;
2024-04-23 16:26:23.915 UTC client backend[19554] pg_regress/with ERROR:  conditional DO INSTEAD rules are not supported for data-modifying statements in WITH
2024-04-23 16:26:23.915 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2024-04-23 16:26:23.918 UTC client backend[19554] pg_regress/with ERROR:  DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH
2024-04-23 16:26:23.918 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2024-04-23 16:26:23.919 UTC client backend[19554] pg_regress/with ERROR:  DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH
2024-04-23 16:26:23.919 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc() is not unique at character 8
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc();
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer) is not unique at character 8
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc(1);
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer, integer) is not unique at character 8
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2024-04-23 16:26:23.919 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc(1, 2);
2024-04-23 16:26:23.922 UTC client backend[19554] pg_regress/with ERROR:  DO ALSO rules are not supported for data-modifying statements in WITH
2024-04-23 16:26:23.922 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2024-04-23 16:26:23.923 UTC client backend[19573] pg_regress/polymorphism ERROR:  only input parameters can have default values
2024-04-23 16:26:23.923 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function dfunc(out int = 20) returns int as $$
	  select 1;
	$$ language sql;
2024-04-23 16:26:23.923 UTC client backend[19567] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2024-04-23 16:26:23.923 UTC client backend[19567] pg_regress/truncate DETAIL:  Table "truncpart" references "truncprim".
2024-04-23 16:26:23.923 UTC client backend[19567] pg_regress/truncate HINT:  Truncate table "truncpart" at the same time, or use TRUNCATE ... CASCADE.
2024-04-23 16:26:23.923 UTC client backend[19567] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncprim;
2024-04-23 16:26:23.923 UTC client backend[19554] pg_regress/with ERROR:  multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH
2024-04-23 16:26:23.923 UTC client backend[19554] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2024-04-23 16:26:23.924 UTC client backend[19554] pg_regress/with ERROR:  syntax error at or near "with" at character 19
2024-04-23 16:26:23.924 UTC client backend[19554] pg_regress/with STATEMENT:  create table foo (with baz);
2024-04-23 16:26:23.925 UTC client backend[19554] pg_regress/with ERROR:  syntax error at or near "with" at character 19
2024-04-23 16:26:23.925 UTC client backend[19554] pg_regress/with STATEMENT:  create table foo (with ordinality);
2024-04-23 16:26:23.928 UTC client backend[19544] pg_regress/copy2 ERROR:  cannot specify DEFAULT in BINARY mode
2024-04-23 16:26:23.928 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format binary, default '\D');
2024-04-23 16:26:23.929 UTC client backend[19554] pg_regress/with ERROR:  relation "with_test" does not exist at character 43
2024-04-23 16:26:23.929 UTC client backend[19554] pg_regress/with STATEMENT:  WITH with_test AS (SELECT 42) INSERT INTO with_test VALUES (1);
2024-04-23 16:26:23.929 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY default representation cannot use newline or carriage return
2024-04-23 16:26:23.929 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default E'\n');
2024-04-23 16:26:23.930 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY default representation cannot use newline or carriage return
2024-04-23 16:26:23.930 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default E'\r');
2024-04-23 16:26:23.931 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY delimiter must not appear in the DEFAULT specification
2024-04-23 16:26:23.931 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (delimiter ';', default 'test;test');
2024-04-23 16:26:23.932 UTC client backend[19544] pg_regress/copy2 ERROR:  CSV quote character must not appear in the DEFAULT specification
2024-04-23 16:26:23.932 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format csv, quote '"', default 'test"test');
2024-04-23 16:26:23.933 UTC client backend[19544] pg_regress/copy2 ERROR:  NULL specification and DEFAULT specification cannot be the same
2024-04-23 16:26:23.933 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default '\N');
2024-04-23 16:26:23.934 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc() does not exist at character 8
2024-04-23 16:26:23.934 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.934 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc();
2024-04-23 16:26:23.935 UTC client backend[19544] pg_regress/copy2 ERROR:  unexpected default marker in COPY data
2024-04-23 16:26:23.935 UTC client backend[19544] pg_regress/copy2 DETAIL:  Column "id" has no default value.
2024-04-23 16:26:23.935 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY copy_default, line 1: "\D	value	'2022-07-04'"
2024-04-23 16:26:23.935 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default '\D');
2024-04-23 16:26:23.939 UTC client backend[19544] pg_regress/copy2 ERROR:  unexpected default marker in COPY data
2024-04-23 16:26:23.939 UTC client backend[19544] pg_regress/copy2 DETAIL:  Column "id" has no default value.
2024-04-23 16:26:23.939 UTC client backend[19544] pg_regress/copy2 CONTEXT:  COPY copy_default, line 1: "\D,value,2022-07-04"
2024-04-23 16:26:23.939 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format csv, default '\D');
2024-04-23 16:26:23.943 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot remove parameter defaults from existing function
2024-04-23 16:26:23.943 UTC client backend[19573] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(integer[]) first.
2024-04-23 16:26:23.943 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a variadic int[]) returns int as
	$$ select array_upper($1, 1) $$ language sql;
2024-04-23 16:26:23.951 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer) is not unique at character 8
2024-04-23 16:26:23.951 UTC client backend[19573] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2024-04-23 16:26:23.951 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select dfunc(1);
2024-04-23 16:26:23.952 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer) does not exist at character 15
2024-04-23 16:26:23.952 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.952 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(0);
2024-04-23 16:26:23.953 UTC client backend[19573] pg_regress/polymorphism ERROR:  argument name "x" used more than once at character 39
2024-04-23 16:26:23.953 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(x := 20, b := 10, x := 30);
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism ERROR:  positional argument cannot follow named argument at character 34
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(10, b := 20, 30);
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(x => integer, b => integer, c => integer) does not exist at character 15
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(x := 10, b := 20, c := 30);
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer, integer, a => integer) does not exist at character 15
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(10, 10, a := 20);
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(integer, c => integer, d => integer) does not exist at character 15
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:23.954 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc(1,c := 2,d := 3);
2024-04-23 16:26:24.004 UTC client backend[19562] pg_regress/rangefuncs LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp19562.0", size 140000
2024-04-23 16:26:24.004 UTC client backend[19562] pg_regress/rangefuncs CONTEXT:  SQL function "rngfunc1" statement 1
2024-04-23 16:26:24.004 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select t.a, t, t.a from rngfunc1(10000) t limit 1;
2024-04-23 16:26:24.005 UTC client backend[19573] pg_regress/polymorphism ERROR:  function dfunc(unknown, c => integer, b => date) does not exist at character 15
2024-04-23 16:26:24.005 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.005 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select * from dfunc('Hello World', c := 20, b := '2009-07-25'::date);
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot change name of input parameter "c"
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(character varying,numeric) first.
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a varchar = 'def a', out _a varchar, x numeric = NULL, out _c numeric)
	returns record as $$
	  select $1, $2;
	$$ language sql;
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot change name of input parameter "c"
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(character varying,numeric) first.
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a varchar = 'def a', out _a varchar, numeric = NULL, out _c numeric)
	returns record as $$
	  select $1, $2;
	$$ language sql;
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  parameter name "a" used more than once
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function testpolym(a int, a int) returns int as $$ select 1;$$ language sql;
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  parameter name "a" used more than once
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function testpolym(int, out a int, out a int) returns int as $$ select 1;$$ language sql;
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  parameter name "a" used more than once
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function testpolym(out a int, inout a int) returns int as $$ select 1;$$ language sql;
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism ERROR:  parameter name "a" used more than once
2024-04-23 16:26:24.006 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function testpolym(a int, inout a int) returns int as $$ select 1;$$ language sql;
2024-04-23 16:26:24.010 UTC client backend[19562] pg_regress/rangefuncs LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp19562.1", size 277788
2024-04-23 16:26:24.010 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select t.a, t, t.a from rngfunc1(10000) t limit 1;
2024-04-23 16:26:24.025 UTC client backend[19561] pg_regress/domain ERROR:  column "col1" of table "domnotnull" contains null values
2024-04-23 16:26:24.025 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain dnotnulltest set not null;
2024-04-23 16:26:24.026 UTC client backend[19561] pg_regress/domain ERROR:  column "col2" of table "domnotnull" contains null values
2024-04-23 16:26:24.026 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain dnotnulltest set not null;
2024-04-23 16:26:24.026 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2024-04-23 16:26:24.026 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']);
2024-04-23 16:26:24.027 UTC client backend[19562] pg_regress/rangefuncs ERROR:  return type mismatch in function declared to return record
2024-04-23 16:26:24.027 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Final statement returns integer instead of point at column 1.
2024-04-23 16:26:24.027 UTC client backend[19562] pg_regress/rangefuncs CONTEXT:  SQL function "array_to_set" during startup
2024-04-23 16:26:24.027 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text);
2024-04-23 16:26:24.042 UTC client backend[19561] pg_regress/domain ERROR:  domain dnotnulltest does not allow null values
2024-04-23 16:26:24.042 UTC client backend[19561] pg_regress/domain STATEMENT:  update domnotnull set col1 = null;
2024-04-23 16:26:24.043 UTC client backend[19562] pg_regress/rangefuncs ERROR:  return type mismatch in function declared to return record
2024-04-23 16:26:24.043 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Final statement returns integer instead of point at column 1.
2024-04-23 16:26:24.043 UTC client backend[19562] pg_regress/rangefuncs CONTEXT:  SQL function "array_to_set" during inlining
2024-04-23 16:26:24.043 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text);
2024-04-23 16:26:24.045 UTC client backend[19571] pg_regress/rowtypes ERROR:  column "f1" is of type integer but expression is of type compos at character 82
2024-04-23 16:26:24.045 UTC client backend[19571] pg_regress/rowtypes HINT:  You will need to rewrite or cast the expression.
2024-04-23 16:26:24.045 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  create function fcompos1(v compos) returns void as $$
	insert into compos values (v);  -- fail
	$$ language sql;
2024-04-23 16:26:24.050 UTC client backend[19544] pg_regress/copy2 ERROR:  COPY DEFAULT only available using COPY FROM
2024-04-23 16:26:24.050 UTC client backend[19544] pg_regress/copy2 STATEMENT:  copy (select 1 as test) TO stdout with (default '\D');
2024-04-23 16:26:24.050 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2024-04-23 16:26:24.050 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc();
2024-04-23 16:26:24.054 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c" referenced in foreign key constraint does not exist
2024-04-23 16:26:24.054 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key(c) references attmp2 match full;
2024-04-23 16:26:24.055 UTC client backend[19558] pg_regress/sequence ERROR:  permission denied for sequence seq3
2024-04-23 16:26:24.055 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT lastval();
2024-04-23 16:26:24.056 UTC client backend[19566] pg_regress/alter_table ERROR:  column "b" referenced in foreign key constraint does not exist
2024-04-23 16:26:24.056 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key(a) references attmp2(b) match full;
2024-04-23 16:26:24.057 UTC client backend[19566] pg_regress/alter_table ERROR:  insert or update on table "attmp3" violates foreign key constraint "attmpconstr"
2024-04-23 16:26:24.057 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (a)=(5) is not present in table "attmp2".
2024-04-23 16:26:24.057 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key (a) references attmp2 match full;
2024-04-23 16:26:24.059 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2024-04-23 16:26:24.059 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc();
2024-04-23 16:26:24.059 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, point) does not exist at character 29
2024-04-23 16:26:24.059 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.059 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, point(1,2)) x;
2024-04-23 16:26:24.060 UTC client backend[19571] pg_regress/rowtypes ERROR:  function text(fullname) does not exist at character 8
2024-04-23 16:26:24.060 UTC client backend[19571] pg_regress/rowtypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.060 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select text(fullname) from fullname;
2024-04-23 16:26:24.062 UTC client backend[19571] pg_regress/rowtypes ERROR:  column fullname.text does not exist at character 8
2024-04-23 16:26:24.062 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select fullname.text from fullname;
2024-04-23 16:26:24.070 UTC client backend[19571] pg_regress/rowtypes ERROR:  function text(record) does not exist at character 8
2024-04-23 16:26:24.070 UTC client backend[19571] pg_regress/rowtypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.070 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select text(row('Jim', 'Beam'));
2024-04-23 16:26:24.071 UTC client backend[19571] pg_regress/rowtypes ERROR:  could not identify column "text" in record data type at character 9
2024-04-23 16:26:24.071 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  select (row('Jim', 'Beam')).text;
2024-04-23 16:26:24.074 UTC client backend[19566] pg_regress/alter_table ERROR:  insert or update on table "attmp3" violates foreign key constraint "attmpconstr"
2024-04-23 16:26:24.074 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (a)=(5) is not present in table "attmp2".
2024-04-23 16:26:24.074 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 validate constraint attmpconstr;
2024-04-23 16:26:24.074 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, integer[]) does not exist at character 29
2024-04-23 16:26:24.074 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.074 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[1,2]) x;
2024-04-23 16:26:24.079 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row
2024-04-23 16:26:24.079 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 ADD CONSTRAINT b_greater_than_ten CHECK (b > 10);
2024-04-23 16:26:24.080 UTC client backend[19561] pg_regress/domain ERROR:  column "col1" of table "domcontest" contains values that violate the new constraint
2024-04-23 16:26:24.080 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain con add constraint t check (VALUE < 1);
2024-04-23 16:26:24.080 UTC client backend[19558] pg_regress/sequence ERROR:  permission denied for sequence seq3
2024-04-23 16:26:24.080 UTC client backend[19558] pg_regress/sequence STATEMENT:  SELECT setval('seq3', 5);
2024-04-23 16:26:24.080 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row
2024-04-23 16:26:24.080 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 VALIDATE CONSTRAINT b_greater_than_ten;
2024-04-23 16:26:24.083 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, point[]) does not exist at character 29
2024-04-23 16:26:24.083 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.083 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[point(1,2)]) x;
2024-04-23 16:26:24.084 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2024-04-23 16:26:24.084 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.084 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2024-04-23 16:26:24.090 UTC client backend[19561] pg_regress/domain ERROR:  value for domain con violates check constraint "con_check"
2024-04-23 16:26:24.090 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into domcontest values (-5);
2024-04-23 16:26:24.090 UTC client backend[19558] pg_regress/sequence ERROR:  must be owner of sequence sequence_test2
2024-04-23 16:26:24.090 UTC client backend[19558] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test2 START WITH 1;
2024-04-23 16:26:24.090 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2024-04-23 16:26:24.090 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.090 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2024-04-23 16:26:24.092 UTC client backend[19561] pg_regress/domain ERROR:  value for domain con violates check constraint "t"
2024-04-23 16:26:24.092 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into domcontest values (42);
2024-04-23 16:26:24.093 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(numeric, int4range) does not exist at character 29
2024-04-23 16:26:24.093 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.093 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, int4range(4,7)) x;
2024-04-23 16:26:24.094 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2024-04-23 16:26:24.094 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, '[4,7)') x;
2024-04-23 16:26:24.096 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "b_le_20" of relation "attmp6" is violated by some row
2024-04-23 16:26:24.096 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 VALIDATE CONSTRAINT b_le_20;
2024-04-23 16:26:24.100 UTC client backend[19561] pg_regress/domain ERROR:  value for domain con violates check constraint "con_check"
2024-04-23 16:26:24.100 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into domcontest values (-5);
2024-04-23 16:26:24.101 UTC client backend[19561] pg_regress/domain ERROR:  constraint "nonexistent" of domain "con" does not exist
2024-04-23 16:26:24.101 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain con drop constraint nonexistent;
2024-04-23 16:26:24.101 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(int4range, numrange) does not exist at character 29
2024-04-23 16:26:24.101 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.101 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(int4range(11,12), numrange(4,7)) x;
2024-04-23 16:26:24.103 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine result data type
2024-04-23 16:26:24.103 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:26:24.103 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function anyctest(anycompatible)
	returns anycompatiblerange as $$
	  select $1
	$$ language sql;
2024-04-23 16:26:24.104 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is redundant for a function returning a named composite type at character 34
2024-04-23 16:26:24.104 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc() as t(f1 int8,f2 int8);
2024-04-23 16:26:24.105 UTC client backend[19561] pg_regress/domain ERROR:  column "col1" of table "domconnotnulltest" contains null values
2024-04-23 16:26:24.105 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain connotnull add not null;
2024-04-23 16:26:24.105 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is redundant for a function with OUT parameters at character 38
2024-04-23 16:26:24.105 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from pg_get_keywords() as t(f1 int8,f2 int8);
2024-04-23 16:26:24.107 UTC client backend[19562] pg_regress/rangefuncs ERROR:  a column definition list is only allowed for functions returning "record" at character 27
2024-04-23 16:26:24.107 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from sin(3) as t(f1 int8,f2 int8);
2024-04-23 16:26:24.110 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2024-04-23 16:26:24.110 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.110 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2024-04-23 16:26:24.112 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(numeric, int4multirange) does not exist at character 29
2024-04-23 16:26:24.112 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.112 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, multirange(int4range(4,7))) x;
2024-04-23 16:26:24.112 UTC client backend[19561] pg_regress/domain ERROR:  column "col2" of table "domconnotnulltest" contains null values
2024-04-23 16:26:24.112 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain connotnull add not null;
2024-04-23 16:26:24.112 UTC client backend[19573] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblemultirange because input has type unknown
2024-04-23 16:26:24.112 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, '{[4,7)}') x;
2024-04-23 16:26:24.154 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(int4multirange, nummultirange) does not exist at character 29
2024-04-23 16:26:24.154 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.154 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(multirange(int4range(11,12)), multirange(numrange(4,7))) x;
2024-04-23 16:26:24.220 UTC client backend[19573] pg_regress/polymorphism ERROR:  cannot determine result data type
2024-04-23 16:26:24.220 UTC client backend[19573] pg_regress/polymorphism DETAIL:  A result of type anycompatiblemultirange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:26:24.220 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  create function anyctest(anycompatible)
	returns anycompatiblemultirange as $$
	  select $1
	$$ language sql;
2024-04-23 16:26:24.220 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "check_a_is_2" of relation "parent_noinh_convalid" is violated by some row
2024-04-23 16:26:24.220 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table parent_noinh_convalid validate constraint check_a_is_2;
2024-04-23 16:26:24.221 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer[], integer[]) does not exist at character 29
2024-04-23 16:26:24.221 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.221 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(array[11], array[1,2]) x;
2024-04-23 16:26:24.221 UTC client backend[19561] pg_regress/domain ERROR:  domain connotnull does not allow null values
2024-04-23 16:26:24.221 UTC client backend[19561] pg_regress/domain STATEMENT:  update domconnotnulltest set col1 = null;
2024-04-23 16:26:24.329 UTC client backend[19571] pg_regress/rowtypes ERROR:  missing FROM-clause entry for table "d" at character 8
2024-04-23 16:26:24.329 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  SELECT d.a FROM (SELECT compositetable AS d FROM compositetable) s;
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes ERROR:  column "ctid" not found in data type compositetable at character 9
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  SELECT (d).ctid FROM (SELECT compositetable AS d FROM compositetable) s;
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes ERROR:  column "nonexistent" not found in data type compositetable at character 9
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  SELECT (NULL::compositetable).nonexistent;
2024-04-23 16:26:24.330 UTC client backend[19573] pg_regress/polymorphism ERROR:  function anyctest(integer, numeric[], integer, numeric) does not exist at character 29
2024-04-23 16:26:24.330 UTC client backend[19573] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.330 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[1, 2.2], 42, 34.5) x;
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes ERROR:  column "oid" not found in data type compositetable at character 9
2024-04-23 16:26:24.330 UTC client backend[19571] pg_regress/rowtypes STATEMENT:  SELECT (NULL::compositetable).oid;
2024-04-23 16:26:24.462 UTC client backend[19566] pg_regress/alter_table ERROR:  there is no unique constraint matching given keys for referenced table "attmp4"
2024-04-23 16:26:24.462 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp5 add constraint attmpconstr foreign key(a) references attmp4(a) match full;
2024-04-23 16:26:24.466 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot drop column moredrop of table users because other objects depend on it
2024-04-23 16:26:24.466 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  view usersview depends on column moredrop of table users
2024-04-23 16:26:24.466 UTC client backend[19562] pg_regress/rangefuncs HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:24.466 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  alter table users drop column moredrop;
2024-04-23 16:26:24.467 UTC client backend[19573] pg_regress/polymorphism ERROR:  invalid input syntax for type integer: "12.2" at character 42
2024-04-23 16:26:24.467 UTC client backend[19573] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, '12.2') x;
2024-04-23 16:26:24.469 UTC client backend[19562] pg_regress/rangefuncs ERROR:  attribute 5 of type record has been dropped
2024-04-23 16:26:24.469 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from usersview;
2024-04-23 16:26:24.470 UTC client backend[19562] pg_regress/rangefuncs ERROR:  cannot alter type of a column used by a view or rule
2024-04-23 16:26:24.470 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  rule _RETURN on view usersview depends on column "seq"
2024-04-23 16:26:24.470 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  alter table users alter column seq type numeric;
2024-04-23 16:26:24.474 UTC client backend[19562] pg_regress/rangefuncs ERROR:  attribute 2 of type record has wrong type
2024-04-23 16:26:24.474 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Table has type numeric, but query expects integer.
2024-04-23 16:26:24.474 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from usersview;
2024-04-23 16:26:24.483 UTC client backend[19561] pg_regress/domain ERROR:  column "stuff" of table "thethings" contains values that violate the new constraint
2024-04-23 16:26:24.483 UTC client backend[19561] pg_regress/domain STATEMENT:  ALTER DOMAIN things ADD CONSTRAINT meow CHECK (VALUE < 11);
2024-04-23 16:26:24.486 UTC client backend[19561] pg_regress/domain ERROR:  column "stuff" of table "thethings" contains values that violate the new constraint
2024-04-23 16:26:24.486 UTC client backend[19561] pg_regress/domain STATEMENT:  ALTER DOMAIN things VALIDATE CONSTRAINT meow;
2024-04-23 16:26:24.508 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.508 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned type integer at ordinal position 2, but query expects numeric.
2024-04-23 16:26:24.508 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from rngfuncbar();
2024-04-23 16:26:24.509 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.509 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 2.
2024-04-23 16:26:24.509 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from rngfuncbar();
2024-04-23 16:26:24.606 UTC client backend[19561] pg_regress/domain ERROR:  domain dom does not allow null values
2024-04-23 16:26:24.606 UTC client backend[19561] pg_regress/domain STATEMENT:  select * from domview;
2024-04-23 16:26:24.627 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dom violates check constraint "domchkgt6"
2024-04-23 16:26:24.627 UTC client backend[19561] pg_regress/domain STATEMENT:  select * from domview;
2024-04-23 16:26:24.629 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.629 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 2.
2024-04-23 16:26:24.629 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int);
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 4.
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int, f int, g int);
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned type integer at ordinal position 3, but query expects double precision.
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int, f float);
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs DETAIL:  Returned row contains 1 attribute, but query expects 2.
2024-04-23 16:26:24.630 UTC client backend[19562] pg_regress/rangefuncs STATEMENT:  select * from int8_tbl, coalesce(row(1)) as (a int, b int);
2024-04-23 16:26:24.732 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2024-04-23 16:26:24.732 UTC client backend[19561] pg_regress/domain STATEMENT:  select 'y1234'::dtop;
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain STATEMENT:  select 'y123'::dtop;
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain STATEMENT:  select 'yz23'::dtop;
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dtop_check"
2024-04-23 16:26:24.733 UTC client backend[19561] pg_regress/domain STATEMENT:  select 'xz23'::dtop;
2024-04-23 16:26:24.866 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(4)
2024-04-23 16:26:24.866 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dtest values('x1234');
2024-04-23 16:26:24.867 UTC client backend[19561] pg_regress/domain ERROR:  value too long for type character varying(4)
2024-04-23 16:26:24.867 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dtest values('y1234');
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest1" are of incompatible types: inet and integer.
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
2024-04-23 16:26:24.867 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2024-04-23 16:26:24.867 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dtest values('y123');
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest1" are of incompatible types: inet and integer.
2024-04-23 16:26:24.867 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable(ptest1);
2024-04-23 16:26:24.868 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2024-04-23 16:26:24.868 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dtest values('yz23');
2024-04-23 16:26:24.868 UTC client backend[19561] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dtop_check"
2024-04-23 16:26:24.868 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dtest values('xz23');
2024-04-23 16:26:24.869 UTC client backend[19545] pg_regress/plpgsql ERROR:  duplicate key value violates unique constraint "pfield_name"
2024-04-23 16:26:24.869 UTC client backend[19545] pg_regress/plpgsql DETAIL:  Key (name)=(PF1_1) already exists.
2024-04-23 16:26:24.869 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  insert into PField values ('PF1_1', 'should fail due to unique index');
2024-04-23 16:26:24.870 UTC client backend[19545] pg_regress/plpgsql ERROR:  WS.not.there         does not exist
2024-04-23 16:26:24.870 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_backlink_set(character,character) line 30 at RAISE
	PL/pgSQL function tg_backlink_a() line 17 at assignment
2024-04-23 16:26:24.870 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  update PSlot set backlink = 'WS.not.there' where slotname = 'PS.base.a1';
2024-04-23 16:26:24.871 UTC client backend[19545] pg_regress/plpgsql ERROR:  illegal backlink beginning with XX
2024-04-23 16:26:24.871 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_backlink_set(character,character) line 47 at RAISE
	PL/pgSQL function tg_backlink_a() line 17 at assignment
2024-04-23 16:26:24.871 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  update PSlot set backlink = 'XX.illegal' where slotname = 'PS.base.a1';
2024-04-23 16:26:24.872 UTC client backend[19545] pg_regress/plpgsql ERROR:  PS.not.there         does not exist
2024-04-23 16:26:24.872 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_slotlink_set(character,character) line 30 at RAISE
	PL/pgSQL function tg_slotlink_a() line 17 at assignment
2024-04-23 16:26:24.872 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  update PSlot set slotlink = 'PS.not.there' where slotname = 'PS.base.a1';
2024-04-23 16:26:24.873 UTC client backend[19566] pg_regress/alter_table ERROR:  insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey"
2024-04-23 16:26:24.873 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (ftest1)=(43) is not present in table "pktable".
2024-04-23 16:26:24.873 UTC client backend[19566] pg_regress/alter_table STATEMENT:  INSERT INTO FKTABLE VALUES(43);
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql ERROR:  illegal slotlink beginning with XX
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_slotlink_set(character,character) line 77 at RAISE
	PL/pgSQL function tg_slotlink_a() line 17 at assignment
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  update PSlot set slotlink = 'XX.illegal' where slotname = 'PS.base.a1';
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql ERROR:  duplicate key value violates unique constraint "hslot_name"
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql DETAIL:  Key (slotname)=(HS.base.hub1.1      ) already exists.
2024-04-23 16:26:24.873 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  insert into HSlot values ('HS', 'base.hub1', 1, '');
2024-04-23 16:26:24.875 UTC client backend[19545] pg_regress/plpgsql ERROR:  no manual manipulation of HSlot
2024-04-23 16:26:24.875 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_hslot_biu() line 12 at RAISE
2024-04-23 16:26:24.875 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  insert into HSlot values ('HS', 'base.hub1', 20, '');
2024-04-23 16:26:24.876 UTC client backend[19545] pg_regress/plpgsql ERROR:  no manual manipulation of HSlot
2024-04-23 16:26:24.876 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_hslot_bd() line 12 at RAISE
2024-04-23 16:26:24.876 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  delete from HSlot;
2024-04-23 16:26:24.876 UTC client backend[19561] pg_regress/domain ERROR:  domain str_domain does not allow null values
2024-04-23 16:26:24.876 UTC client backend[19561] pg_regress/domain STATEMENT:  alter table domain_test add column c str_domain;
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql ERROR:  system "notthere" does not exist
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_iface_biu() line 8 at RAISE
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  insert into IFace values ('IF', 'notthere', 'eth0', '');
2024-04-23 16:26:24.878 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2024-04-23 16:26:24.878 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest1" are of incompatible types: numeric and integer.
2024-04-23 16:26:24.878 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql ERROR:  IFace slotname "IF.orion.ethernet_interface_name_too_long" too long (20 char max)
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_iface_biu() line 14 at RAISE
2024-04-23 16:26:24.878 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  insert into IFace values ('IF', 'orion', 'ethernet_interface_name_too_long', '');
2024-04-23 16:26:24.879 UTC client backend[19561] pg_regress/domain ERROR:  value for domain str_domain2 violates check constraint "str_domain2_check"
2024-04-23 16:26:24.879 UTC client backend[19561] pg_regress/domain STATEMENT:  alter table domain_test add column d str_domain2;
2024-04-23 16:26:24.884 UTC client backend[19561] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2024-04-23 16:26:24.884 UTC client backend[19561] pg_regress/domain STATEMENT:  execute s1(0);
2024-04-23 16:26:24.884 UTC client backend[19561] pg_regress/domain ERROR:  domain pos_int does not allow null values
2024-04-23 16:26:24.884 UTC client backend[19561] pg_regress/domain STATEMENT:  execute s1(NULL);
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain ERROR:  domain pos_int does not allow null values
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(3);
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(3);
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain ERROR:  domain pos_int does not allow null values
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(null);
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(0);
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 4 at assignment
2024-04-23 16:26:24.885 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(1);
2024-04-23 16:26:24.886 UTC client backend[19561] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2024-04-23 16:26:24.886 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) while casting return value to function's return type
2024-04-23 16:26:24.886 UTC client backend[19561] pg_regress/domain STATEMENT:  select doubledecrement(2);
2024-04-23 16:26:24.925 UTC client backend[19561] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2024-04-23 16:26:24.925 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2024-04-23 16:26:24.932 UTC client backend[19561] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2024-04-23 16:26:24.932 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2024-04-23 16:26:24.932 UTC client backend[19566] pg_regress/alter_table ERROR:  insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey"
2024-04-23 16:26:24.932 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (ftest1)=(43) is not present in table "pktable".
2024-04-23 16:26:24.932 UTC client backend[19566] pg_regress/alter_table STATEMENT:  INSERT INTO FKTABLE VALUES(43);
2024-04-23 16:26:24.936 UTC client backend[19561] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2024-04-23 16:26:24.936 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2024-04-23 16:26:24.941 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2024-04-23 16:26:24.941 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest1" are of incompatible types: cidr and integer.
2024-04-23 16:26:24.941 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable;
2024-04-23 16:26:24.944 UTC client backend[19561] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2024-04-23 16:26:24.944 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2024-04-23 16:26:24.946 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2024-04-23 16:26:24.946 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest1" are of incompatible types: cidr and integer.
2024-04-23 16:26:24.946 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
	     references pktable(ptest1, ptest2);
2024-04-23 16:26:24.947 UTC client backend[19545] pg_regress/plpgsql ERROR:  operator does not exist: point + integer at character 3
2024-04-23 16:26:24.947 UTC client backend[19545] pg_regress/plpgsql HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.947 UTC client backend[19545] pg_regress/plpgsql QUERY:  x + 1
2024-04-23 16:26:24.947 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function f1(anyelement) line 3 at RETURN
2024-04-23 16:26:24.947 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select f1(point(3,4));
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest1" and "ptest2" are of incompatible types: integer and inet.
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
	     references pktable(ptest2, ptest1);
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "ftest2" and "ptest1" are of incompatible types: inet and integer.
2024-04-23 16:26:24.952 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1)
	     references pktable(ptest1, ptest2);
2024-04-23 16:26:24.954 UTC client backend[19561] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2024-04-23 16:26:24.954 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2024-04-23 16:26:24.958 UTC client backend[19545] pg_regress/plpgsql ERROR:  cannot determine element type of "anyarray" argument
2024-04-23 16:26:24.958 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select f1(stavalues1) from pg_statistic;
2024-04-23 16:26:24.959 UTC client backend[19561] pg_regress/domain ERROR:  value for domain posint2 violates check constraint "posint2_check"
2024-04-23 16:26:24.959 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into ddtest2 values(11);
2024-04-23 16:26:24.959 UTC client backend[19561] pg_regress/domain ERROR:  value for domain posint2 violates check constraint "c1"
2024-04-23 16:26:24.959 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into ddtest2 values(-2);
2024-04-23 16:26:24.960 UTC client backend[19561] pg_regress/domain ERROR:  column "f1" of table "ddtest2" contains values that violate the new constraint
2024-04-23 16:26:24.960 UTC client backend[19561] pg_regress/domain STATEMENT:  alter domain posint add constraint c2 check(value >= 10);
2024-04-23 16:26:24.960 UTC client backend[19545] pg_regress/plpgsql ERROR:  PL/pgSQL functions cannot accept type anyarray
2024-04-23 16:26:24.960 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "f1" near line 1
2024-04-23 16:26:24.960 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select f1(stavalues1) from pg_statistic;
2024-04-23 16:26:24.964 UTC client backend[19545] pg_regress/plpgsql ERROR:  cannot determine result data type
2024-04-23 16:26:24.964 UTC client backend[19545] pg_regress/plpgsql DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2024-04-23 16:26:24.964 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function f1(x anyelement) returns anyrange as $$
	begin
	  return array[x + 1, x + 2];
	end$$ language plpgsql;
2024-04-23 16:26:24.970 UTC client backend[19561] pg_regress/domain ERROR:  numeric field overflow
2024-04-23 16:26:24.970 UTC client backend[19561] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2024-04-23 16:26:24.970 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2024-04-23 16:26:24.970 UTC client backend[19561] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2024-04-23 16:26:24.971 UTC client backend[19545] pg_regress/plpgsql ERROR:  function f1(int4range, integer, numeric) does not exist at character 8
2024-04-23 16:26:24.971 UTC client backend[19545] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.971 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select f1(int4range(42, 49), 11, 4.5) as fail;
2024-04-23 16:26:24.971 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc_test1"
2024-04-23 16:26:24.971 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (2).
2024-04-23 16:26:24.971 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2024-04-23 16:26:24.972 UTC client backend[19545] pg_regress/plpgsql ERROR:  cannot determine result data type
2024-04-23 16:26:24.972 UTC client backend[19545] pg_regress/plpgsql DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2024-04-23 16:26:24.972 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function f1(x anycompatible) returns anycompatiblerange as $$
	begin
	  return array[x + 1, x + 2];
	end$$ language plpgsql;
2024-04-23 16:26:24.974 UTC client backend[19561] pg_regress/domain ERROR:  numeric field overflow
2024-04-23 16:26:24.974 UTC client backend[19561] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2024-04-23 16:26:24.974 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2024-04-23 16:26:24.974 UTC client backend[19561] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2024-04-23 16:26:24.976 UTC client backend[19561] pg_regress/domain ERROR:  numeric field overflow
2024-04-23 16:26:24.976 UTC client backend[19561] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2024-04-23 16:26:24.976 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2024-04-23 16:26:24.976 UTC client backend[19561] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2024-04-23 16:26:24.977 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "atacc_test1" of relation "atacc1" is violated by some row
2024-04-23 16:26:24.977 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 check (test>3);
2024-04-23 16:26:24.978 UTC client backend[19545] pg_regress/plpgsql ERROR:  function f1(integer, numeric[], integer, numeric) does not exist at character 48
2024-04-23 16:26:24.978 UTC client backend[19545] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:24.978 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select x, pg_typeof(x), y, pg_typeof(y)
	  from f1(11, array[1, 2.2], 42, 34.5);
2024-04-23 16:26:24.979 UTC client backend[19561] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2024-04-23 16:26:24.979 UTC client backend[19561] pg_regress/domain STATEMENT:  select array[2,1]::orderedpair;
2024-04-23 16:26:24.979 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test1" does not exist
2024-04-23 16:26:24.979 UTC client backend[19566] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "atacc1.test".
2024-04-23 16:26:24.979 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 check (test1>3);
2024-04-23 16:26:24.979 UTC client backend[19545] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function with OUT parameters at character 74
2024-04-23 16:26:24.979 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function f1(in i int, out j int) returns int as $$
	begin
	  return i+1;
	end$$ language plpgsql;
2024-04-23 16:26:24.980 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc_test1"
2024-04-23 16:26:24.980 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (4, 4, 2).
2024-04-23 16:26:24.980 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2,test3) values (4,4,2);
2024-04-23 16:26:24.981 UTC client backend[19561] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2024-04-23 16:26:24.981 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into op values (array[2,1]);
2024-04-23 16:26:24.981 UTC client backend[19561] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2024-04-23 16:26:24.981 UTC client backend[19561] pg_regress/domain STATEMENT:  update op set f1[2] = 0;
2024-04-23 16:26:24.983 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_check"
2024-04-23 16:26:24.983 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (4, 3).
2024-04-23 16:26:24.983 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (3, 4);
2024-04-23 16:26:24.984 UTC client backend[19561] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2024-04-23 16:26:24.984 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(integer) line 5 at assignment
2024-04-23 16:26:24.984 UTC client backend[19561] pg_regress/domain STATEMENT:  select array_elem_check(-1);
2024-04-23 16:26:24.986 UTC client backend[19561] pg_regress/domain ERROR:  value for domain di violates check constraint "pos"
2024-04-23 16:26:24.986 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function dom_check(integer) line 4 at assignment
2024-04-23 16:26:24.986 UTC client backend[19561] pg_regress/domain STATEMENT:  select dom_check(0);
2024-04-23 16:26:24.987 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc2" violates check constraint "foo"
2024-04-23 16:26:24.987 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (-3).
2024-04-23 16:26:24.987 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc2 (test2) values (-3);
2024-04-23 16:26:24.989 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc3" violates check constraint "foo"
2024-04-23 16:26:24.989 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, -3, null).
2024-04-23 16:26:24.989 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc3 (test2) values (-3);
2024-04-23 16:26:24.990 UTC client backend[19561] pg_regress/domain ERROR:  value for domain di violates check constraint "pos"
2024-04-23 16:26:24.990 UTC client backend[19561] pg_regress/domain CONTEXT:  PL/pgSQL function dom_check(integer) line 4 at assignment
2024-04-23 16:26:24.990 UTC client backend[19561] pg_regress/domain STATEMENT:  select dom_check(0);
2024-04-23 16:26:24.994 UTC client backend[19561] pg_regress/domain ERROR:  value for domain inotnull violates check constraint "inotnull_check"
2024-04-23 16:26:24.994 UTC client backend[19561] pg_regress/domain STATEMENT:  select null::inotnull;
2024-04-23 16:26:24.995 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "atacc2" is not a parent of relation "atacc3"
2024-04-23 16:26:24.995 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc3 no inherit atacc2;
2024-04-23 16:26:24.996 UTC client backend[19561] pg_regress/domain ERROR:  value for domain inotnull violates check constraint "inotnull_check"
2024-04-23 16:26:24.996 UTC client backend[19561] pg_regress/domain STATEMENT:  insert into dom_table values (null);
2024-04-23 16:26:25.002 UTC client backend[19566] pg_regress/alter_table ERROR:  child table is missing constraint "foo"
2024-04-23 16:26:25.002 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2024-04-23 16:26:25.027 UTC client backend[19566] pg_regress/alter_table ERROR:  child table is missing column "test2"
2024-04-23 16:26:25.027 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2024-04-23 16:26:25.051 UTC client backend[19566] pg_regress/alter_table ERROR:  child table "atacc3" has different type for column "test2"
2024-04-23 16:26:25.051 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2024-04-23 16:26:25.071 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "atacc2" would be inherited from more than once
2024-04-23 16:26:25.071 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table ERROR:  circular inheritance not allowed
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table DETAIL:  "atacc3" is already a child of "atacc2".
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc2 inherit atacc3;
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table ERROR:  circular inheritance not allowed
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table DETAIL:  "atacc2" is already a child of "atacc2".
2024-04-23 16:26:25.072 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc2 inherit atacc2;
2024-04-23 16:26:25.079 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "foo"
2024-04-23 16:26:25.079 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (-3).
2024-04-23 16:26:25.079 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (-3);
2024-04-23 16:26:25.081 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "foo" of relation "atacc2" is violated by some row
2024-04-23 16:26:25.081 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc2 add constraint foo check (test>0) no inherit;
2024-04-23 16:26:25.086 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2024-04-23 16:26:25.086 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(2) already exists.
2024-04-23 16:26:25.086 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2024-04-23 16:26:25.087 UTC client backend[19566] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2024-04-23 16:26:25.087 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(0) is duplicated.
2024-04-23 16:26:25.087 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter column test type integer using 0;
2024-04-23 16:26:25.102 UTC client backend[19566] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2024-04-23 16:26:25.102 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(2) is duplicated.
2024-04-23 16:26:25.102 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 unique (test);
2024-04-23 16:26:25.186 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test1" named in key does not exist
2024-04-23 16:26:25.186 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 unique (test1);
2024-04-23 16:26:25.193 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2024-04-23 16:26:25.193 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test, test2)=(4, 4) already exists.
2024-04-23 16:26:25.193 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (4,4);
2024-04-23 16:26:25.196 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc1_test_key"
2024-04-23 16:26:25.196 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(3) already exists.
2024-04-23 16:26:25.196 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (2, 3);
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(2) already exists.
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (4, null).
2024-04-23 16:26:25.199 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values(NULL);
2024-04-23 16:26:25.200 UTC client backend[19566] pg_regress/alter_table ERROR:  multiple primary keys for table "atacc1" are not allowed
2024-04-23 16:26:25.200 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_oid1 primary key(id);
2024-04-23 16:26:25.203 UTC client backend[19566] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2024-04-23 16:26:25.203 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(2) is duplicated.
2024-04-23 16:26:25.203 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test);
2024-04-23 16:26:25.206 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test" of relation "atacc1" contains null values
2024-04-23 16:26:25.206 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test);
2024-04-23 16:26:25.206 UTC client backend[19545] pg_regress/plpgsql ERROR:  cursor "test1" does not exist
2024-04-23 16:26:25.206 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  fetch next from test1;
2024-04-23 16:26:25.207 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test1" of relation "atacc1" does not exist
2024-04-23 16:26:25.207 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test1);
2024-04-23 16:26:25.210 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test2" of relation "atacc1" contains null values
2024-04-23 16:26:25.210 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add column test2 int primary key;
2024-04-23 16:26:25.224 UTC client backend[19545] pg_regress/plpgsql ERROR:  variable "rc" is declared CONSTANT
2024-04-23 16:26:25.224 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function constant_refcursor() line 5 at OPEN
2024-04-23 16:26:25.224 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select constant_refcursor();
2024-04-23 16:26:25.229 UTC client backend[19566] pg_regress/alter_table ERROR:  check constraint "atacc1_chk" of relation "atacc1" is violated by some row
2024-04-23 16:26:25.229 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 validate constraint atacc1_chk, alter a type int;
2024-04-23 16:26:25.230 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for parameter "param2" of cursor "c1" specified more than once at character 198
2024-04-23 16:26:25.230 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test3() returns void as $$
	declare
	    c1 cursor (param1 int, param2 int) for select * from rc_test where a > param1 and b > param2;
	begin
	    open c1(param2 := 20, 21);
	end
	$$ language plpgsql;
2024-04-23 16:26:25.231 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for parameter "param1" of cursor "c1" specified more than once at character 188
2024-04-23 16:26:25.231 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test4() returns void as $$
	declare
	    c1 cursor (param1 int, param2 int) for select * from rc_test where a > param1 and b > param2;
	begin
	    open c1(20, param1 := 21);
	end
	$$ language plpgsql;
2024-04-23 16:26:25.231 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for parameter "p2" of cursor "c1" specified more than once at character 191
2024-04-23 16:26:25.231 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test5() returns void as $$
	declare
	  c1 cursor (p1 int, p2 int) for
	    select * from tenk1 where thousand = p1 and tenthous = p2;
	begin
	  open c1 (p2 := 77, p2 := 42);
	end
	$$ language plpgsql;
2024-04-23 16:26:25.232 UTC client backend[19545] pg_regress/plpgsql ERROR:  not enough arguments for cursor "c1" at character 189
2024-04-23 16:26:25.232 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test6() returns void as $$
	declare
	  c1 cursor (p1 int, p2 int) for
	    select * from tenk1 where thousand = p1 and tenthous = p2;
	begin
	  open c1 (p2 := 77);
	end
	$$ language plpgsql;
2024-04-23 16:26:25.233 UTC client backend[19566] pg_regress/alter_table ERROR:  multiple primary keys for table "atacc1" are not allowed
2024-04-23 16:26:25.233 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test2 primary key (test);
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test, test2)=(4, 4) already exists.
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (4,4);
2024-04-23 16:26:25.234 UTC client backend[19545] pg_regress/plpgsql ERROR:  division by zero
2024-04-23 16:26:25.234 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL expression "42/0 AS p1, 77 AS p2"
	PL/pgSQL function namedparmcursor_test7() line 6 at OPEN
2024-04-23 16:26:25.234 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select namedparmcursor_test7();
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, 3).
2024-04-23 16:26:25.234 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (NULL,3);
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "test2" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (3, null).
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (3, NULL);
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, null).
2024-04-23 16:26:25.235 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (NULL,NULL);
2024-04-23 16:26:25.238 UTC client backend[19545] pg_regress/plpgsql ERROR:  too many parameters specified for RAISE
2024-04-23 16:26:25.238 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "raise_test1" near line 3
2024-04-23 16:26:25.238 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function raise_test1(int) returns int as $$
	begin
	    raise notice 'This message has too many parameters!', $1;
	    return $1;
	end;
	$$ language plpgsql;
2024-04-23 16:26:25.239 UTC client backend[19545] pg_regress/plpgsql ERROR:  too few parameters specified for RAISE
2024-04-23 16:26:25.239 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "raise_test2" near line 3
2024-04-23 16:26:25.239 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function raise_test2(int) returns int as $$
	begin
	    raise notice 'This message has too few parameters: %, %, %', $1, $1;
	    return $1;
	end;
	$$ language plpgsql;
2024-04-23 16:26:25.276 UTC client backend[19545] pg_regress/plpgsql ERROR:  syntax error at or near "Johnny" at character 83
2024-04-23 16:26:25.276 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function bad_sql1() returns int as $$
	declare a int;
	begin
	    a := 5;
	    Johnny Yuma;
	    a := 10;
	    return a;
	end$$ language plpgsql;
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql ERROR:  syntax error at or near "the" at character 99
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function bad_sql2() returns int as $$
	declare r record;
	begin
	    for r in select I fought the law, the law won LOOP
	        raise notice 'in loop';
	    end loop;
	    return 5;
	end;$$ language plpgsql;
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql ERROR:  missing expression at or near ";" at character 74
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function missing_return_expr() returns int as $$
	begin
	    return ;
	end;$$ language plpgsql;
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function returning void at character 72
2024-04-23 16:26:25.277 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create function void_return_expr() returns void as $$
	begin
	    return 5;
	end;$$ language plpgsql;
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc1_pkey"
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key (test)=(3) already exists.
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (2, 3);
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, 1).
2024-04-23 16:26:25.345 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (1, NULL);
2024-04-23 16:26:25.347 UTC client backend[19545] pg_regress/plpgsql ERROR:  control reached end of function without RETURN
2024-04-23 16:26:25.347 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function missing_return_expr()
2024-04-23 16:26:25.347 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select missing_return_expr();
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table pg_class alter column relname drop not null;
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table pg_class alter relname set not null;
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "non_existent" does not exist
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table non_existent alter column bar set not null;
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "non_existent" does not exist
2024-04-23 16:26:25.399 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table non_existent alter column bar drop not null;
2024-04-23 16:26:25.404 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "sqlstate" does not exist at character 1
2024-04-23 16:26:25.404 UTC client backend[19545] pg_regress/plpgsql QUERY:  sqlstate
2024-04-23 16:26:25.404 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function excpt_test1() line 3 at RAISE
2024-04-23 16:26:25.404 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select excpt_test1();
2024-04-23 16:26:25.405 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "sqlstate" does not exist at character 1
2024-04-23 16:26:25.405 UTC client backend[19545] pg_regress/plpgsql QUERY:  sqlstate
2024-04-23 16:26:25.405 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function excpt_test2() line 5 at RAISE
2024-04-23 16:26:25.405 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select excpt_test2();
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test" of relation "atacc1" contains null values
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test set not null;
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter bar set not null;
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2024-04-23 16:26:25.413 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter bar drop not null;
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table ERROR:  ALTER action ALTER COLUMN ... DROP NOT NULL cannot be performed on relation "myview"
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table myview alter column test drop not null;
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table ERROR:  ALTER action ALTER COLUMN ... SET NOT NULL cannot be performed on relation "myview"
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2024-04-23 16:26:25.414 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table myview alter column test set not null;
2024-04-23 16:26:25.424 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test_a" of relation "atacc1" contains null values
2024-04-23 16:26:25.424 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null;
2024-04-23 16:26:25.424 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test_a" of relation "atacc1" contains null values
2024-04-23 16:26:25.424 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null;
2024-04-23 16:26:25.432 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.432 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.432 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2024-04-23 16:26:25.432 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.436 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test_b" of relation "atacc1" contains null values
2024-04-23 16:26:25.436 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null, alter test_b set not null;
2024-04-23 16:26:25.437 UTC client backend[19566] pg_regress/alter_table ERROR:  column "test_b" of relation "atacc1" contains null values
2024-04-23 16:26:25.437 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_b set not null, alter test_a set not null;
2024-04-23 16:26:25.450 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned no rows
2024-04-23 16:26:25.450 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2024-04-23 16:26:25.450 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.450 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "a" of relation "parent" violates not-null constraint
2024-04-23 16:26:25.450 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null).
2024-04-23 16:26:25.450 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into parent values (NULL);
2024-04-23 16:26:25.451 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.451 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.451 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2024-04-23 16:26:25.451 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.451 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "a" of relation "child" violates not-null constraint
2024-04-23 16:26:25.451 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, foo).
2024-04-23 16:26:25.451 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into child (a, b) values (NULL, 'foo');
2024-04-23 16:26:25.452 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "parent" contains null values
2024-04-23 16:26:25.452 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table only parent alter a set not null;
2024-04-23 16:26:25.452 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "child" contains null values
2024-04-23 16:26:25.452 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table child alter a set not null;
2024-04-23 16:26:25.452 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned no rows
2024-04-23 16:26:25.452 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2024-04-23 16:26:25.452 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.453 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.453 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2024-04-23 16:26:25.453 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.462 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned no rows
2024-04-23 16:26:25.462 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2024-04-23 16:26:25.462 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2024-04-23 16:26:25.462 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned no rows
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = '''Valame Dios!'' dijo Sancho; ''no le dije yo a vuestra merced que mirase bien lo que hacia?'''
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2024-04-23 16:26:25.463 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.463 UTC client backend[19566] pg_regress/alter_table ERROR:  invalid input syntax for type integer: "wrong_datatype"
2024-04-23 16:26:25.463 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table def_test alter column c1 set default 'wrong_datatype';
2024-04-23 16:26:25.464 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c3" of relation "def_test" does not exist
2024-04-23 16:26:25.464 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table def_test alter column c3 set default 30;
2024-04-23 16:26:25.464 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.464 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.464 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2024-04-23 16:26:25.464 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.465 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned no rows
2024-04-23 16:26:25.465 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: $1 = '0', $2 = 'foo'
2024-04-23 16:26:25.465 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2024-04-23 16:26:25.465 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.468 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.468 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: $1 = '1'
2024-04-23 16:26:25.468 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2024-04-23 16:26:25.468 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.470 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.470 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2024-04-23 16:26:25.470 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.471 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.471 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.471 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 10 at SQL statement
2024-04-23 16:26:25.471 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.472 UTC client backend[19566] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2024-04-23 16:26:25.472 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table pg_class drop column relname;
2024-04-23 16:26:25.474 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "nosuchtable" does not exist
2024-04-23 16:26:25.474 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table nosuchtable drop column bar;
2024-04-23 16:26:25.474 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.474 UTC client backend[19545] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2024-04-23 16:26:25.474 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.474 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 10 at SQL statement
2024-04-23 16:26:25.474 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stricttest();
2024-04-23 16:26:25.476 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.476 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 drop a;
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 order by a;
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 order by "........pg.dropped.1........";
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 group by a;
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2024-04-23 16:26:25.477 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 group by "........pg.dropped.1........";
2024-04-23 16:26:25.477 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 88
2024-04-23 16:26:25.477 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "out1" shadows a previously defined variable at character 97
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 8
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select a from atacc1;
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column atacc1.a does not exist at character 8
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select atacc1.a from atacc1;
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 8
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select a,b,c,d from atacc1;
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 28
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 where a = 1;
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 8
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select "........pg.dropped.1........" from atacc1;
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table ERROR:  column atacc1.........pg.dropped.1........ does not exist at character 8
2024-04-23 16:26:25.478 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select atacc1."........pg.dropped.1........" from atacc1;
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 8
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select "........pg.dropped.1........",b,c,d from atacc1;
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 28
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select * from atacc1 where "........pg.dropped.1........" = 1;
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 19
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table STATEMENT:  update atacc1 set a = 3;
2024-04-23 16:26:25.479 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 88
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2024-04-23 16:26:25.479 UTC client backend[19566] pg_regress/alter_table STATEMENT:  update atacc1 set b = 2 where a = 3;
2024-04-23 16:26:25.479 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "out1" shadows a previously defined variable at character 97
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 19
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  update atacc1 set "........pg.dropped.1........" = 3;
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  update atacc1 set b = 2 where "........pg.dropped.1........" = 3;
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  INSERT has more expressions than target columns at character 40
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 values (10, 11, 12, 13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  INSERT has more expressions than target columns at character 45
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 values (default, 11, 12, 13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (a) values (10);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (a) values (default);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (a,b,c,d) values (10,11,12,13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 (a,b,c,d) values (default,11,12,13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........") values (10);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........") values (default);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........",b,c,d) values (10,11,12,13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........",b,c,d) values (default,11,12,13);
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist at character 26
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  delete from atacc1 where a = 3;
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 26
2024-04-23 16:26:25.480 UTC client backend[19566] pg_regress/alter_table STATEMENT:  delete from atacc1 where "........pg.dropped.1........" = 3;
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 drop bar;
2024-04-23 16:26:25.481 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "f1" shadows a previously defined variable at character 93
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table ERROR:  syntax error at or near "WITH" at character 24
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 SET WITH OIDS;
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop system column "xmin"
2024-04-23 16:26:25.481 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 drop xmin;
2024-04-23 16:26:25.482 UTC client backend[19566] pg_regress/alter_table ERROR:  ALTER action DROP COLUMN cannot be performed on relation "myview"
2024-04-23 16:26:25.482 UTC client backend[19566] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2024-04-23 16:26:25.482 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table myview drop d;
2024-04-23 16:26:25.482 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 76
2024-04-23 16:26:25.482 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 101
2024-04-23 16:26:25.483 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.483 UTC client backend[19566] pg_regress/alter_table STATEMENT:  analyze atacc1(a);
2024-04-23 16:26:25.483 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.483 UTC client backend[19566] pg_regress/alter_table STATEMENT:  analyze atacc1("........pg.dropped.1........");
2024-04-23 16:26:25.484 UTC client backend[19545] pg_regress/plpgsql WARNING:  variable "f1" shadows a previously defined variable at character 88
2024-04-23 16:26:25.484 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.484 UTC client backend[19566] pg_regress/alter_table STATEMENT:  vacuum analyze atacc1(a);
2024-04-23 16:26:25.486 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.486 UTC client backend[19566] pg_regress/alter_table STATEMENT:  vacuum analyze atacc1("........pg.dropped.1........");
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  comment on column atacc1.a is 'testing';
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  comment on column atacc1."........pg.dropped.1........" is 'testing';
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set storage plain;
2024-04-23 16:26:25.487 UTC client backend[19545] pg_regress/plpgsql ERROR:  variable "f1" shadows a previously defined variable at character 78
2024-04-23 16:26:25.487 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create or replace function shadowtest(f1 int)
		returns boolean as $$
	declare f1 int; begin return 1; end $$ language plpgsql;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set storage plain;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set statistics 0;
2024-04-23 16:26:25.487 UTC client backend[19545] pg_regress/plpgsql ERROR:  function shadowtest(integer) does not exist at character 8
2024-04-23 16:26:25.487 UTC client backend[19545] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:25.487 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select shadowtest(1);
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set statistics 0;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set default 3;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set default 3;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a drop default;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" drop default;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set not null;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set not null;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a drop not null;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" drop not null;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 rename a to x;
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2024-04-23 16:26:25.487 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 rename "........pg.dropped.1........" to x;
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add primary key(a);
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add primary key("........pg.dropped.1........");
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" named in key does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add unique(a);
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" named in key does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add unique("........pg.dropped.1........");
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add check (a > 3);
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2024-04-23 16:26:25.488 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add check ("........pg.dropped.1........" > 3);
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" referenced in foreign key constraint does not exist
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add foreign key (a) references atacc2(id);
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" referenced in foreign key constraint does not exist
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc1 add foreign key ("........pg.dropped.1........") references atacc2(id);
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" referenced in foreign key constraint does not exist
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc2 add foreign key (id) references atacc1(a);
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" referenced in foreign key constraint does not exist
2024-04-23 16:26:25.489 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table atacc2 add foreign key (id) references atacc1("........pg.dropped.1........");
2024-04-23 16:26:25.490 UTC client backend[19545] pg_regress/plpgsql WARNING:  query returned more than one row
2024-04-23 16:26:25.490 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.490 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at SQL statement
2024-04-23 16:26:25.490 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist
2024-04-23 16:26:25.490 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create index "testing_idx" on atacc1(a);
2024-04-23 16:26:25.490 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2024-04-23 16:26:25.490 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create index "testing_idx" on atacc1("........pg.dropped.1........");
2024-04-23 16:26:25.491 UTC client backend[19545] pg_regress/plpgsql ERROR:  query returned more than one row
2024-04-23 16:26:25.491 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2024-04-23 16:26:25.491 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at SQL statement
2024-04-23 16:26:25.491 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare x int;
	begin
	  select v from generate_series(1,2) g(v) into x;
	end;
	$$;
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql WARNING:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_warnings is active.
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 6 at SQL statement
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql WARNING:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_warnings is active.
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.493 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 8 at SQL statement
2024-04-23 16:26:25.494 UTC client backend[19545] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.494 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2024-04-23 16:26:25.494 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.494 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 6 at SQL statement
2024-04-23 16:26:25.494 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  x int;
	  y int;
	begin
	  select 1 into x, y;
	  select 1,2 into x, y;
	  select 1,2,3 into x, y;
	end
	$$;
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 8 at SQL statement
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  x int;
	  y int;
	begin
	  select * from test_01 into x, y; -- should be ok
	  raise notice 'ok';
	  select * from test_01 into x;    -- should to fail
	end;
	$$;
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 7 at SQL statement
2024-04-23 16:26:25.495 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  t test_01;
	begin
	  select 1, 2 into t;  -- should be ok
	  raise notice 'ok';
	  select 1, 2, 3 into t; -- should fail;
	end;
	$$;
2024-04-23 16:26:25.496 UTC client backend[19545] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2024-04-23 16:26:25.496 UTC client backend[19545] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2024-04-23 16:26:25.496 UTC client backend[19545] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2024-04-23 16:26:25.496 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 5 at SQL statement
2024-04-23 16:26:25.496 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  t test_01;
	begin
	  select 1 into t; -- should fail;
	end;
	$$;
2024-04-23 16:26:25.499 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_value_check"
2024-04-23 16:26:25.499 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (1, 100).
2024-04-23 16:26:25.499 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1(value) values (100);
2024-04-23 16:26:25.501 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_value_check"
2024-04-23 16:26:25.501 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (2, 100).
2024-04-23 16:26:25.501 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1(value) values (100);
2024-04-23 16:26:25.504 UTC client backend[19566] pg_regress/alter_table ERROR:  null value in column "id" of relation "atacc1" violates not-null constraint
2024-04-23 16:26:25.504 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null, 0).
2024-04-23 16:26:25.504 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into atacc1(id, value) values (null, 0);
2024-04-23 16:26:25.504 UTC client backend[19545] pg_regress/plpgsql ERROR:  cursor can only scan forward
2024-04-23 16:26:25.504 UTC client backend[19545] pg_regress/plpgsql HINT:  Declare it with SCROLL option to enable backward scan.
2024-04-23 16:26:25.504 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function sc_test() line 7 at FETCH
2024-04-23 16:26:25.504 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from sc_test();
2024-04-23 16:26:25.572 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" has a type conflict
2024-04-23 16:26:25.572 UTC client backend[19566] pg_regress/alter_table DETAIL:  double precision versus real
2024-04-23 16:26:25.572 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create table child (a float4) inherits (parent);
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table ERROR:  column "b" has a type conflict
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table DETAIL:  numeric(10,4) versus numeric(10,7)
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create table child (b decimal(10,7)) inherits (parent);
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c" has a collation conflict
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table DETAIL:  "C" versus "POSIX"
2024-04-23 16:26:25.573 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create table child (c text collate "POSIX") inherits (parent);
2024-04-23 16:26:25.592 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "attest" does not exist
2024-04-23 16:26:25.592 UTC client backend[19566] pg_regress/alter_table STATEMENT:  copy attest(a) to stdout;
2024-04-23 16:26:25.595 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "attest" does not exist
2024-04-23 16:26:25.595 UTC client backend[19566] pg_regress/alter_table STATEMENT:  copy attest("........pg.dropped.1........") to stdout;
2024-04-23 16:26:25.597 UTC client backend[19566] pg_regress/alter_table ERROR:  extra data after last expected column
2024-04-23 16:26:25.597 UTC client backend[19566] pg_regress/alter_table CONTEXT:  COPY attest, line 1: "10	11	12"
2024-04-23 16:26:25.597 UTC client backend[19566] pg_regress/alter_table STATEMENT:  copy attest from stdin;
2024-04-23 16:26:25.601 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" of relation "attest" does not exist
2024-04-23 16:26:25.601 UTC client backend[19566] pg_regress/alter_table STATEMENT:  copy attest(a) from stdin;
2024-04-23 16:26:25.602 UTC client backend[19566] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "attest" does not exist
2024-04-23 16:26:25.602 UTC client backend[19566] pg_regress/alter_table STATEMENT:  copy attest("........pg.dropped.1........") from stdin;
2024-04-23 16:26:25.647 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "a"
2024-04-23 16:26:25.647 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table dropColumnchild drop column a;
2024-04-23 16:26:25.648 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "b"
2024-04-23 16:26:25.648 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table only dropColumnChild drop column b;
2024-04-23 16:26:25.651 UTC client backend[19545] pg_regress/plpgsql ERROR:  cursor FOR loop must use a bound cursor variable at character 98
2024-04-23 16:26:25.651 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  create or replace function forc_bad() returns void as $$
	declare
	  c refcursor;
	begin
	  for r in c loop
	    raise notice '%', r.i;
	  end loop;
	end;
	$$ language plpgsql;
2024-04-23 16:26:25.670 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot rename inherited column "a"
2024-04-23 16:26:25.670 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table renameColumnChild rename column a to d;
2024-04-23 16:26:25.671 UTC client backend[19566] pg_regress/alter_table ERROR:  inherited column "a" must be renamed in child tables too
2024-04-23 16:26:25.671 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table only renameColumnChild rename column a to d;
2024-04-23 16:26:25.672 UTC client backend[19566] pg_regress/alter_table ERROR:  inherited column "a" must be renamed in child tables too
2024-04-23 16:26:25.672 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table only renameColumn rename column a to d;
2024-04-23 16:26:25.676 UTC client backend[19566] pg_regress/alter_table ERROR:  column must be added to child tables too
2024-04-23 16:26:25.676 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table only renameColumn add column x int;
2024-04-23 16:26:25.681 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2024-04-23 16:26:25.681 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2024-04-23 16:26:25.683 UTC client backend[19566] pg_regress/alter_table ERROR:  column "f1" does not exist at character 8
2024-04-23 16:26:25.683 UTC client backend[19566] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "c1.f2".
2024-04-23 16:26:25.683 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select f1 from c1;
2024-04-23 16:26:25.689 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2024-04-23 16:26:25.689 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2024-04-23 16:26:25.690 UTC client backend[19566] pg_regress/alter_table ERROR:  column "f1" does not exist at character 8
2024-04-23 16:26:25.690 UTC client backend[19566] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "c1.f2".
2024-04-23 16:26:25.690 UTC client backend[19566] pg_regress/alter_table STATEMENT:  select f1 from c1;
2024-04-23 16:26:25.693 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2024-04-23 16:26:25.693 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2024-04-23 16:26:25.696 UTC client backend[19545] pg_regress/plpgsql ERROR:  returned record type does not match expected record type
2024-04-23 16:26:25.696 UTC client backend[19545] pg_regress/plpgsql DETAIL:  Returned type unknown does not match expected type character varying in column 2.
2024-04-23 16:26:25.696 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2024-04-23 16:26:25.696 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select compos();
2024-04-23 16:26:25.697 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2024-04-23 16:26:25.697 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2024-04-23 16:26:25.708 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "name"
2024-04-23 16:26:25.708 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table gc1 drop column name;
2024-04-23 16:26:25.709 UTC client backend[19545] pg_regress/plpgsql ERROR:  cannot return non-composite value from function returning composite type
2024-04-23 16:26:25.709 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() line 3 at RETURN
2024-04-23 16:26:25.709 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select compos();
2024-04-23 16:26:25.709 UTC client backend[19566] pg_regress/alter_table ERROR:  column "name" of relation "gc1" does not exist
2024-04-23 16:26:25.709 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table gc1 drop column name;
2024-04-23 16:26:25.712 UTC client backend[19545] pg_regress/plpgsql ERROR:  cannot return non-composite value from function returning composite type
2024-04-23 16:26:25.712 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() line 4 at RETURN
2024-04-23 16:26:25.712 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from compos();
2024-04-23 16:26:25.749 UTC client backend[19566] pg_regress/alter_table ERROR:  column "non_existing" of relation "dropcolumnexists" does not exist
2024-04-23 16:26:25.749 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table dropColumnExists drop column non_existing;
2024-04-23 16:26:25.750 UTC client backend[19545] pg_regress/plpgsql ERROR:  invalid input syntax for type integer: "(1,hello)"
2024-04-23 16:26:25.750 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2024-04-23 16:26:25.750 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select compos();
2024-04-23 16:26:25.751 UTC client backend[19545] pg_regress/plpgsql ERROR:  invalid input syntax for type integer: "(1,hello)"
2024-04-23 16:26:25.751 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2024-04-23 16:26:25.751 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select compos();
2024-04-23 16:26:25.790 UTC client backend[19545] pg_regress/plpgsql ERROR:  1 2 3
2024-04-23 16:26:25.790 UTC client backend[19545] pg_regress/plpgsql DETAIL:  some detail info
2024-04-23 16:26:25.790 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 5 at RAISE
2024-04-23 16:26:25.790 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.794 UTC client backend[19545] pg_regress/plpgsql ERROR:  check me
2024-04-23 16:26:25.794 UTC client backend[19545] pg_regress/plpgsql DETAIL:  some detail info
2024-04-23 16:26:25.794 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.794 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql ERROR:  check me
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql DETAIL:  some detail info
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql ERROR:  check me
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql DETAIL:  some detail info
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.795 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql ERROR:  division_by_zero
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql DETAIL:  some detail info
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql ERROR:  division_by_zero
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.796 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql ERROR:  1234F
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql ERROR:  custom message
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.797 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.805 UTC client backend[19545] pg_regress/plpgsql ERROR:  custom message
2024-04-23 16:26:25.805 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.805 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.806 UTC client backend[19545] pg_regress/plpgsql ERROR:  RAISE option already specified: MESSAGE
2024-04-23 16:26:25.806 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.806 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.807 UTC client backend[19545] pg_regress/plpgsql ERROR:  RAISE option already specified: ERRCODE
2024-04-23 16:26:25.807 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.807 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.811 UTC client backend[19545] pg_regress/plpgsql ERROR:  RAISE without parameters cannot be used outside an exception handler
2024-04-23 16:26:25.811 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2024-04-23 16:26:25.811 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.811 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "c1" violates check constraint "p1_a1_check"
2024-04-23 16:26:25.811 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (11, xyz, 33, 0).
2024-04-23 16:26:25.811 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into c1 values(11,'xyz',33,0);
2024-04-23 16:26:25.828 UTC client backend[19545] pg_regress/plpgsql ERROR:  GET STACKED DIAGNOSTICS cannot be used outside an exception handler
2024-04-23 16:26:25.828 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stacked_diagnostics_test() line 6 at GET STACKED DIAGNOSTICS
2024-04-23 16:26:25.828 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select stacked_diagnostics_test();
2024-04-23 16:26:25.829 UTC client backend[19566] pg_regress/alter_table ERROR:  column "f1" cannot be cast automatically to type integer
2024-04-23 16:26:25.829 UTC client backend[19566] pg_regress/alter_table HINT:  You might need to specify "USING f1::integer".
2024-04-23 16:26:25.829 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table foo alter f1 TYPE integer;
2024-04-23 16:26:25.852 UTC client backend[19545] pg_regress/plpgsql ERROR:  substitute message
2024-04-23 16:26:25.852 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 7 at RAISE
2024-04-23 16:26:25.852 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select raise_test();
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table ERROR:  column "atcol1" cannot be cast automatically to type boolean
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table HINT:  You might need to specify "USING atcol1::boolean".
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean;
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table ERROR:  result of USING clause for column "atcol1" cannot be cast automatically to type boolean
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table HINT:  You might need to add an explicit cast.
2024-04-23 16:26:25.855 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean using atcol1::int;
2024-04-23 16:26:25.866 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "anothertab" violates check constraint "anothertab_chk"
2024-04-23 16:26:25.866 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (45, null).
2024-04-23 16:26:25.866 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into anothertab (atcol1, atcol2) values (45, null);
2024-04-23 16:26:25.895 UTC client backend[19566] pg_regress/alter_table ERROR:  default for column "atcol1" cannot be cast automatically to type boolean
2024-04-23 16:26:25.895 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean
	        using case when atcol1 % 2 = 0 then true else false end;
2024-04-23 16:26:25.896 UTC client backend[19566] pg_regress/alter_table ERROR:  operator does not exist: boolean <= integer
2024-04-23 16:26:25.896 UTC client backend[19566] pg_regress/alter_table HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-04-23 16:26:25.896 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean
	        using case when atcol1 % 2 = 0 then true else false end;
2024-04-23 16:26:25.897 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint "anothertab_chk" of relation "anothertab" does not exist
2024-04-23 16:26:25.897 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table anothertab drop constraint anothertab_chk;
2024-04-23 16:26:25.934 UTC client backend[19545] pg_regress/plpgsql ERROR:  SELECT INTO query does not return tuples
2024-04-23 16:26:25.934 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL statement "select 10 into no_such_table"
	PL/pgSQL function rttest() line 3 at RETURN QUERY
2024-04-23 16:26:25.934 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from rttest();
2024-04-23 16:26:25.935 UTC client backend[19545] pg_regress/plpgsql ERROR:  SELECT INTO query does not return tuples
2024-04-23 16:26:25.935 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL statement "select 10 into no_such_table"
	PL/pgSQL function rttest() line 3 at RETURN QUERY
2024-04-23 16:26:25.935 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from rttest();
2024-04-23 16:26:25.936 UTC client backend[19545] pg_regress/plpgsql ERROR:  relation "no_such_table" does not exist at character 15
2024-04-23 16:26:25.936 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from no_such_table;
2024-04-23 16:26:25.967 UTC client backend[19545] pg_regress/plpgsql ERROR:  schema "nonexistent" does not exist
2024-04-23 16:26:25.967 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL function "error1" statement 1
	PL/pgSQL function error2(text) line 3 at RETURN
2024-04-23 16:26:25.967 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select error2('nonexistent.stuffs');
2024-04-23 16:26:25.980 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter table "at_tab1" because column "at_tab2.y" uses its row type
2024-04-23 16:26:25.980 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table at_tab1 alter column b type varchar;
2024-04-23 16:26:25.982 UTC client backend[19545] pg_regress/plpgsql ERROR:  invalid input syntax for type date: "-1"
2024-04-23 16:26:25.982 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL function "sql_to_date" statement 1
	PL/pgSQL function cast_invoker(integer) while casting return value to function's return type
2024-04-23 16:26:25.982 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select cast_invoker(-1);
2024-04-23 16:26:25.982 UTC client backend[19566] pg_regress/alter_table ERROR:  ROW() column has type text instead of type character varying
2024-04-23 16:26:25.982 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into at_tab2 values(1,'42');
2024-04-23 16:26:25.987 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter table "at_tab1" because column "at_tab2.y" uses its row type
2024-04-23 16:26:25.987 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table at_tab1 alter column b type varchar;
2024-04-23 16:26:25.992 UTC client backend[19545] pg_regress/plpgsql ERROR:  division by zero
2024-04-23 16:26:25.992 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL expression "1/0"
	PL/pgSQL function fail() line 3 at RETURN
2024-04-23 16:26:25.992 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select fail();
2024-04-23 16:26:25.993 UTC client backend[19545] pg_regress/plpgsql ERROR:  division by zero
2024-04-23 16:26:25.993 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL expression "1/0"
	PL/pgSQL function fail() line 3 at RETURN
2024-04-23 16:26:25.993 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select fail();
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 78
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 106
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 106
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 1
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql QUERY:  'foo\\bar\041baz'
2024-04-23 16:26:25.995 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function strtest() line 4 at RETURN
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function returning void at character 36
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  DO LANGUAGE plpgsql $$begin return 1; end$$;
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "foo" does not exist at character 33
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql QUERY:  SELECT rtrim(roomno) AS roomno, foo FROM Room ORDER BY roomno
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows
2024-04-23 16:26:26.004 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  DO $$
	DECLARE r record;
	BEGIN
	    FOR r IN SELECT rtrim(roomno) AS roomno, foo FROM Room ORDER BY roomno
	    LOOP
	        RAISE NOTICE '%, %', r.roomno, r.comment;
	    END LOOP;
	END$$;
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "x" does not exist at character 1
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql QUERY:  x + 1
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare x int := x + 1;  -- error
	begin
	  raise notice 'x = %', x;
	end;
	$$;
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "x" does not exist at character 1
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql QUERY:  x + 1
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2024-04-23 16:26:26.005 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare y int := x + 1;  -- error
	        x int := 42;
	begin
	  raise notice 'x = %, y = %', x, y;
	end;
	$$;
2024-04-23 16:26:26.007 UTC client backend[19545] pg_regress/plpgsql ERROR:  column reference "q1" is ambiguous at character 8
2024-04-23 16:26:26.007 UTC client backend[19545] pg_regress/plpgsql DETAIL:  It could refer to either a PL/pgSQL variable or a table column.
2024-04-23 16:26:26.007 UTC client backend[19545] pg_regress/plpgsql QUERY:  select q1,q2 from int8_tbl
2024-04-23 16:26:26.007 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function conflict_test() line 5 at FOR over SELECT rows
2024-04-23 16:26:26.007 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select * from conflict_test();
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql ERROR:  FOREACH ... SLICE loop variable must be of an array type
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[1,2,3,4]);
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql ERROR:  FOREACH ... SLICE loop variable must be of an array type
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2024-04-23 16:26:26.030 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[[1,2],[3,4]]);
2024-04-23 16:26:26.039 UTC client backend[19545] pg_regress/plpgsql ERROR:  slice dimension (2) is out of the valid range 0..1
2024-04-23 16:26:26.039 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2024-04-23 16:26:26.039 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[1,2,3,4]);
2024-04-23 16:26:26.103 UTC client backend[19566] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2024-04-23 16:26:26.103 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur1;
2024-04-23 16:26:26.103 UTC client backend[19566] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2024-04-23 16:26:26.103 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur1[];
2024-04-23 16:26:26.105 UTC client backend[19566] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2024-04-23 16:26:26.105 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 array_of_recur1;
2024-04-23 16:26:26.106 UTC client backend[19566] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2024-04-23 16:26:26.106 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur2;
2024-04-23 16:26:26.106 UTC client backend[19566] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2024-04-23 16:26:26.106 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table recur1 alter column f2 type recur2;
2024-04-23 16:26:26.108 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2024-04-23 16:26:26.108 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select '{2,1}'::orderedarray;
2024-04-23 16:26:26.113 UTC client backend[19566] pg_regress/alter_table ERROR:  column data type integer can only have storage PLAIN
2024-04-23 16:26:26.113 UTC client backend[19566] pg_regress/alter_table STATEMENT:  create table test_storage_failed (a text, b int storage extended);
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function testoa(integer,integer,integer) line 4 at assignment
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select testoa(2,1,3);
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function testoa(integer,integer,integer) line 5 at assignment
2024-04-23 16:26:26.114 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  select testoa(1,2,1);
2024-04-23 16:26:26.141 UTC client backend[19545] pg_regress/plpgsql ERROR:  assertion failed
2024-04-23 16:26:26.141 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2024-04-23 16:26:26.141 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert 1=0;  -- should fail
	end;
	$$;
2024-04-23 16:26:26.142 UTC client backend[19545] pg_regress/plpgsql ERROR:  assertion failed
2024-04-23 16:26:26.142 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2024-04-23 16:26:26.142 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert NULL;  -- should fail
	end;
	$$;
2024-04-23 16:26:26.145 UTC client backend[19545] pg_regress/plpgsql ERROR:  assertion failed, var = "some value"
2024-04-23 16:26:26.145 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at ASSERT
2024-04-23 16:26:26.145 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare var text := 'some value';
	begin
	  assert 1=0, format('assertion failed, var = "%s"', var);
	end;
	$$;
2024-04-23 16:26:26.146 UTC client backend[19545] pg_regress/plpgsql ERROR:  unhandled assertion
2024-04-23 16:26:26.146 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2024-04-23 16:26:26.146 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert 1=0, 'unhandled assertion';
	exception when others then
	  null; -- do nothing
	end;
	$$;
2024-04-23 16:26:26.157 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for domain plpgsql_domain violates check constraint "plpgsql_domain_check"
2024-04-23 16:26:26.157 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at assignment
2024-04-23 16:26:26.157 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare v_test plpgsql_domain := 1;
	begin
	  v_test := 0;  -- fail
	end;
	$$;
2024-04-23 16:26:26.163 UTC client backend[19545] pg_regress/plpgsql ERROR:  value for domain plpgsql_arr_domain violates check constraint "plpgsql_arr_domain_check"
2024-04-23 16:26:26.163 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at assignment
2024-04-23 16:26:26.163 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  do $$
	declare v_test plpgsql_arr_domain := array[1];
	begin
	  v_test := 0 || v_test;  -- fail
	end;
	$$;
2024-04-23 16:26:26.216 UTC client backend[19545] pg_regress/plpgsql ERROR:  OLD TABLE can only be specified for a DELETE or UPDATE trigger
2024-04-23 16:26:26.216 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  CREATE TRIGGER transition_table_base_ins_trig
	  AFTER INSERT ON transition_table_base
	  REFERENCING OLD TABLE AS oldtable NEW TABLE AS newtable
	  FOR EACH STATEMENT
	  EXECUTE PROCEDURE transition_table_base_ins_func();
2024-04-23 16:26:26.293 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot convert whole-row table reference
2024-04-23 16:26:26.293 UTC client backend[19566] pg_regress/alter_table DETAIL:  USING expression contains a whole-row table reference.
2024-04-23 16:26:26.293 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE test_type_diff2 ALTER COLUMN int_four TYPE int4 USING (pg_column_size(test_type_diff2));
2024-04-23 16:26:26.606 UTC client backend[19545] pg_regress/plpgsql ERROR:  relation "dx" cannot be the target of a modifying statement
2024-04-23 16:26:26.606 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  SQL statement "INSERT INTO dx VALUES (1000000, 1000000, 'x')"
	PL/pgSQL function transition_table_level2_bad_usage_func() line 3 at SQL statement
2024-04-23 16:26:26.606 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  DELETE FROM transition_table_level2
	  WHERE level2_no BETWEEN 301 AND 305;
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql ERROR:  RI error
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level1_ri_parent_del_func() line 6 at RAISE
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  DELETE FROM transition_table_level1
	  WHERE level1_no = 25;
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql ERROR:  RI error
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level1_ri_parent_upd_func() line 15 at RAISE
2024-04-23 16:26:26.608 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  UPDATE transition_table_level1 SET level1_no = -1
	  WHERE level1_no = 30;
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql ERROR:  RI error
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  INSERT INTO transition_table_level2 (level2_no, parent_no)
	  VALUES (10000, 10000);
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql ERROR:  RI error
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE
2024-04-23 16:26:26.609 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  UPDATE transition_table_level2 SET parent_no = 2000
	  WHERE level2_no = 40;
2024-04-23 16:26:26.691 UTC client backend[19545] pg_regress/plpgsql ERROR:  TRUNCATE triggers with transition tables are not supported
2024-04-23 16:26:26.691 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  CREATE TRIGGER alter_table_under_transition_tables_upd_trigger
	  AFTER TRUNCATE OR UPDATE ON alter_table_under_transition_tables
	  REFERENCING OLD TABLE AS d NEW TABLE AS i
	  FOR EACH STATEMENT EXECUTE PROCEDURE
	    alter_table_under_transition_tables_upd_func();
2024-04-23 16:26:26.693 UTC client backend[19545] pg_regress/plpgsql WARNING:  old table = 1=1,2=2,3=3, new table = 1=11,2=22,3=33
2024-04-23 16:26:26.693 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2024-04-23 16:26:26.826 UTC client backend[19566] pg_regress/alter_table ERROR:  type "lockmodes" does not exist
2024-04-23 16:26:26.826 UTC client backend[19566] pg_regress/alter_table STATEMENT:  drop type lockmodes;
2024-04-23 16:26:26.829 UTC client backend[19545] pg_regress/plpgsql WARNING:  old table = 1=11,2=22,3=33, new table = 1=1111,2=2222,3=3333
2024-04-23 16:26:26.829 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2024-04-23 16:26:26.833 UTC client backend[19566] pg_regress/alter_table ERROR:  view "my_locks" does not exist
2024-04-23 16:26:26.833 UTC client backend[19566] pg_regress/alter_table STATEMENT:  drop view my_locks;
2024-04-23 16:26:26.835 UTC client backend[19545] pg_regress/plpgsql ERROR:  column "name" does not exist at character 33
2024-04-23 16:26:26.835 UTC client backend[19545] pg_regress/plpgsql QUERY:  (SELECT string_agg(id || '=' || name, ',') FROM d)
2024-04-23 16:26:26.835 UTC client backend[19545] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2024-04-23 16:26:26.835 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  UPDATE alter_table_under_transition_tables
	  SET id = id;
2024-04-23 16:26:26.875 UTC client backend[19545] pg_regress/plpgsql ERROR:  "x" is not a scalar variable at character 72
2024-04-23 16:26:26.875 UTC client backend[19545] pg_regress/plpgsql STATEMENT:  CREATE FUNCTION fx(x WSlot) RETURNS void AS $$
	BEGIN
	  GET DIAGNOSTICS x = ROW_COUNT;
	  RETURN;
	END; $$ LANGUAGE plpgsql;
2024-04-23 16:26:26.887 UTC client backend[19566] pg_regress/alter_table ERROR:  unrecognized parameter "autovacuum_enabled"
2024-04-23 16:26:26.887 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table my_locks set (autovacuum_enabled = false);
2024-04-23 16:26:26.887 UTC client backend[19566] pg_regress/alter_table ERROR:  unrecognized parameter "autovacuum_enabled"
2024-04-23 16:26:26.887 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter view my_locks set (autovacuum_enabled = false);
2024-04-23 16:26:26.924 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "nosuchtype" does not exist
2024-04-23 16:26:26.924 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE nosuchtype ADD ATTRIBUTE b text;
2024-04-23 16:26:26.925 UTC client backend[19566] pg_regress/alter_table ERROR:  column "b" of relation "test_type" already exists
2024-04-23 16:26:26.925 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type ADD ATTRIBUTE b text;
2024-04-23 16:26:26.930 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c" of relation "test_type" does not exist
2024-04-23 16:26:26.930 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type DROP ATTRIBUTE c;
2024-04-23 16:26:26.932 UTC client backend[19566] pg_regress/alter_table ERROR:  column "a" does not exist
2024-04-23 16:26:26.932 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type RENAME ATTRIBUTE a TO aa;
2024-04-23 16:26:26.935 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type1" because column "test_tbl1.y" uses it
2024-04-23 16:26:26.935 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar;
2024-04-23 16:26:26.940 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type1" because column "test_tbl1_idx.row" uses it
2024-04-23 16:26:26.940 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar;
2024-04-23 16:26:26.954 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2024-04-23 16:26:26.954 UTC client backend[19566] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2024-04-23 16:26:26.954 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 ADD ATTRIBUTE c text;
2024-04-23 16:26:26.962 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2024-04-23 16:26:26.962 UTC client backend[19566] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2024-04-23 16:26:26.962 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 ALTER ATTRIBUTE b TYPE varchar;
2024-04-23 16:26:26.965 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2024-04-23 16:26:26.965 UTC client backend[19566] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2024-04-23 16:26:26.965 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 DROP ATTRIBUTE b;
2024-04-23 16:26:26.968 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2024-04-23 16:26:26.968 UTC client backend[19566] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2024-04-23 16:26:26.968 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 RENAME ATTRIBUTE a TO aa;
2024-04-23 16:26:26.990 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop column a of composite type test_typex because other objects depend on it
2024-04-23 16:26:26.990 UTC client backend[19566] pg_regress/alter_table DETAIL:  constraint test_tblx_y_check on table test_tblx depends on column a of composite type test_typex
2024-04-23 16:26:26.990 UTC client backend[19566] pg_regress/alter_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2024-04-23 16:26:26.990 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TYPE test_typex DROP ATTRIBUTE a;
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table ERROR:  table "tt1" has different type for column "y"
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt1 OF tt_t0;
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table ERROR:  table "tt2" has different type for column "y"
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt2 OF tt_t0;
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table ERROR:  table has column "y" where type requires "x"
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt3 OF tt_t0;
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table ERROR:  table is missing column "y"
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt4 OF tt_t0;
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table ERROR:  table has extra column "z"
2024-04-23 16:26:27.019 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt5 OF tt_t0;
2024-04-23 16:26:27.020 UTC client backend[19566] pg_regress/alter_table ERROR:  typed tables cannot inherit
2024-04-23 16:26:27.020 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt6 OF tt_t0;
2024-04-23 16:26:27.085 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "test_drop_constr_child" violates check constraint "test_drop_constr_parent_c_check"
2024-04-23 16:26:27.085 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (null).
2024-04-23 16:26:27.085 UTC client backend[19566] pg_regress/alter_table STATEMENT:  INSERT INTO test_drop_constr_child (c) VALUES (NULL);
2024-04-23 16:26:27.320 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint "foo" for relation "tt9" already exists
2024-04-23 16:26:27.320 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT foo CHECK(c > 4);
2024-04-23 16:26:27.325 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "tt9_c_key" already exists
2024-04-23 16:26:27.325 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key UNIQUE(c);
2024-04-23 16:26:27.325 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint "foo" for relation "tt9" already exists
2024-04-23 16:26:27.325 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT foo UNIQUE(c);
2024-04-23 16:26:27.326 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint "tt9_c_key" for relation "tt9" already exists
2024-04-23 16:26:27.326 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key CHECK(c > 5);
2024-04-23 16:26:27.428 UTC client backend[19566] pg_regress/alter_table ERROR:  foreign key constraint "comment_test_child_fk" cannot be implemented
2024-04-23 16:26:27.428 UTC client backend[19566] pg_regress/alter_table DETAIL:  Key columns "id" and "id" are of incompatible types: text and integer.
2024-04-23 16:26:27.428 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE int USING id::integer;
2024-04-23 16:26:27.439 UTC client backend[19566] pg_regress/alter_table ERROR:  permission denied to create "pg_catalog.new_system_table"
2024-04-23 16:26:27.439 UTC client backend[19566] pg_regress/alter_table DETAIL:  System catalog modifications are currently disallowed.
2024-04-23 16:26:27.439 UTC client backend[19566] pg_regress/alter_table STATEMENT:  CREATE TABLE pg_catalog.new_system_table();
2024-04-23 16:26:27.982 UTC client backend[19566] pg_regress/alter_table ERROR:  could not change table "unlogged2" to logged because it references unlogged table "unlogged1"
2024-04-23 16:26:27.982 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE unlogged2 SET LOGGED;
2024-04-23 16:26:28.163 UTC client backend[19566] pg_regress/alter_table ERROR:  could not change table "logged1" to unlogged because it references logged table "logged2"
2024-04-23 16:26:28.163 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE logged1 SET UNLOGGED;
2024-04-23 16:26:28.231 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2024-04-23 16:26:28.231 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE test_add_column
		ADD COLUMN c2 integer;
2024-04-23 16:26:28.231 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2024-04-23 16:26:28.231 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY test_add_column
		ADD COLUMN c2 integer;
2024-04-23 16:26:28.239 UTC client backend[19566] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2024-04-23 16:26:28.239 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE test_add_column
		ADD COLUMN c2 integer, -- fail because c2 already exists
		ADD COLUMN c3 integer primary key;
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned DROP COLUMN a;
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter column "a" because it is part of the partition key of relation "partitioned"
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ALTER COLUMN a TYPE char(5);
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop column "b" because it is part of the partition key of relation "partitioned"
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned DROP COLUMN b;
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter column "b" because it is part of the partition key of relation "partitioned"
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ALTER COLUMN b TYPE char(5);
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot specify storage parameters for a partitioned table
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table HINT:  Specify storage parameters for its leaf partitions instead.
2024-04-23 16:26:29.224 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned SET (fillfactor=100);
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot change inheritance of partitioned table
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned INHERIT nonpartitioned;
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot inherit from partitioned table "partitioned"
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE nonpartitioned INHERIT partitioned;
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot add NO INHERIT constraint to partitioned table "partitioned"
2024-04-23 16:26:29.230 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ADD CONSTRAINT chk_a CHECK (a > 0) NO INHERIT;
2024-04-23 16:26:29.232 UTC client backend[19566] pg_regress/alter_table ERROR:  table "unparted" is not partitioned
2024-04-23 16:26:29.232 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE unparted ATTACH PARTITION fail_part FOR VALUES IN ('a');
2024-04-23 16:26:29.234 UTC client backend[19566] pg_regress/alter_table ERROR:  invalid bound specification for a list partition at character 63
2024-04-23 16:26:29.234 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES FROM (1) TO (10);
2024-04-23 16:26:29.235 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "nonexistent" does not exist
2024-04-23 16:26:29.235 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION nonexistent FOR VALUES IN (1);
2024-04-23 16:26:29.237 UTC client backend[19566] pg_regress/alter_table ERROR:  must be owner of table not_owned_by_me
2024-04-23 16:26:29.237 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE owned_by_me ATTACH PARTITION not_owned_by_me FOR VALUES IN (1);
2024-04-23 16:26:29.241 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach inheritance child as partition
2024-04-23 16:26:29.241 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION child FOR VALUES IN (1);
2024-04-23 16:26:29.241 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach inheritance parent as partition
2024-04-23 16:26:29.241 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION parent FOR VALUES IN (1);
2024-04-23 16:26:29.243 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach a permanent relation as partition of temporary relation "temp_parted"
2024-04-23 16:26:29.243 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE temp_parted ATTACH PARTITION perm_part FOR VALUES IN (1);
2024-04-23 16:26:29.244 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach a typed table as partition
2024-04-23 16:26:29.244 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.246 UTC client backend[19566] pg_regress/alter_table ERROR:  table "fail_part" contains column "c" not found in parent "list_parted"
2024-04-23 16:26:29.246 UTC client backend[19566] pg_regress/alter_table DETAIL:  The new partition may contain only the columns present in parent.
2024-04-23 16:26:29.246 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.247 UTC client backend[19566] pg_regress/alter_table ERROR:  child table is missing column "b"
2024-04-23 16:26:29.247 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.248 UTC client backend[19566] pg_regress/alter_table ERROR:  child table "fail_part" has different type for column "b"
2024-04-23 16:26:29.248 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.249 UTC client backend[19566] pg_regress/alter_table ERROR:  child table "fail_part" has different collation for column "b"
2024-04-23 16:26:29.249 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.249 UTC client backend[19566] pg_regress/alter_table ERROR:  child table is missing constraint "check_a"
2024-04-23 16:26:29.249 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.250 UTC client backend[19566] pg_regress/alter_table ERROR:  child table "fail_part" has different definition for check constraint "check_a"
2024-04-23 16:26:29.250 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.252 UTC client backend[19566] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "part_1" at character 67
2024-04-23 16:26:29.252 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2024-04-23 16:26:29.256 UTC client backend[19566] pg_regress/alter_table ERROR:  partition "fail_def_part" conflicts with existing default partition "def_part" at character 56
2024-04-23 16:26:29.256 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_def_part DEFAULT;
2024-04-23 16:26:29.257 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "part_2" is violated by some row
2024-04-23 16:26:29.257 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2);
2024-04-23 16:26:29.265 UTC client backend[19566] pg_regress/alter_table ERROR:  updated partition constraint for default partition "list_parted2_def" would be violated by some row
2024-04-23 16:26:29.265 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_3 FOR VALUES IN (11);
2024-04-23 16:26:29.282 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "part1" is violated by some row
2024-04-23 16:26:29.282 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH PARTITION part1 FOR VALUES FROM (1, 1) TO (1, 10);
2024-04-23 16:26:29.290 UTC client backend[19566] pg_regress/alter_table ERROR:  partition "partr_def2" conflicts with existing default partition "partr_def1" at character 54
2024-04-23 16:26:29.290 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH PARTITION partr_def2 DEFAULT;
2024-04-23 16:26:29.291 UTC client backend[19566] pg_regress/alter_table ERROR:  updated partition constraint for default partition "partr_def1" would be violated by some row
2024-04-23 16:26:29.291 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH partition part3 FOR VALUES FROM (2, 10) TO (2, 20);
2024-04-23 16:26:29.295 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "part_5_a" is violated by some row
2024-04-23 16:26:29.295 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_5 FOR VALUES IN (5);
2024-04-23 16:26:29.326 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "part_7_a_null" is violated by some row
2024-04-23 16:26:29.326 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_7 FOR VALUES IN (7);
2024-04-23 16:26:29.492 UTC client backend[19566] pg_regress/alter_table ERROR:  updated partition constraint for default partition "part5_def_p1" would be violated by some row
2024-04-23 16:26:29.492 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_5 ATTACH PARTITION part5_p1 FOR VALUES IN ('y');
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table ERROR:  "part_2" is already a partition
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2);
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table ERROR:  circular inheritance not allowed
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table DETAIL:  "part_5" is already a child of "list_parted2".
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_5 ATTACH PARTITION list_parted2 FOR VALUES IN ('b');
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table ERROR:  circular inheritance not allowed
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table DETAIL:  "list_parted2" is already a child of "list_parted2".
2024-04-23 16:26:29.493 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION list_parted2 FOR VALUES IN (0);
2024-04-23 16:26:29.598 UTC client backend[19566] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "hpart_1" at character 63
2024-04-23 16:26:29.598 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 4);
2024-04-23 16:26:29.598 UTC client backend[19566] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "hpart_1" at character 63
2024-04-23 16:26:29.598 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 0);
2024-04-23 16:26:29.599 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "hpart_2" is violated by some row
2024-04-23 16:26:29.599 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION hpart_2 FOR VALUES WITH (MODULUS 4, REMAINDER 1);
2024-04-23 16:26:29.634 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "hpart_5_a" is violated by some row
2024-04-23 16:26:29.634 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION hpart_5 FOR VALUES WITH (MODULUS 4, REMAINDER 2);
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table ERROR:  modulus for hash partition must be an integer value greater than zero
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 0, REMAINDER 1);
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table ERROR:  remainder for hash partition must be less than modulus
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 8);
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table DETAIL:  The new modulus 3 is not a factor of 4, the modulus of existing partition "hpart_1".
2024-04-23 16:26:29.644 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 3, REMAINDER 2);
2024-04-23 16:26:29.645 UTC client backend[19566] pg_regress/alter_table ERROR:  table "regular_table" is not partitioned
2024-04-23 16:26:29.645 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE regular_table DETACH PARTITION any_name;
2024-04-23 16:26:29.645 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "part_4" does not exist
2024-04-23 16:26:29.645 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION part_4;
2024-04-23 16:26:29.646 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "hpart_4" does not exist
2024-04-23 16:26:29.646 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted DETACH PARTITION hpart_4;
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "not_a_part" is not a partition of relation "list_parted2"
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION not_a_part;
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "part_1" is not a partition of relation "list_parted2"
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION part_1;
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table ERROR:  relation "not_a_part" is not a partition of relation "hash_parted"
2024-04-23 16:26:29.647 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted DETACH PARTITION not_a_part;
2024-04-23 16:26:29.658 UTC client backend[19566] pg_regress/alter_table ERROR:  ALTER TABLE ... DETACH CONCURRENTLY cannot run inside a transaction block
2024-04-23 16:26:29.658 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY;
2024-04-23 16:26:29.661 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot detach partitions concurrently when a default partition exists
2024-04-23 16:26:29.661 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY;
2024-04-23 16:26:29.664 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot detach partitions concurrently when a default partition exists
2024-04-23 16:26:29.664 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rpd CONCURRENTLY;
2024-04-23 16:26:29.684 UTC client backend[19566] pg_regress/alter_table ERROR:  column must be added to child tables too
2024-04-23 16:26:29.684 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ADD COLUMN c int;
2024-04-23 16:26:29.686 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop column from only the partitioned table when partitions exist
2024-04-23 16:26:29.686 UTC client backend[19566] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2024-04-23 16:26:29.686 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 DROP COLUMN b;
2024-04-23 16:26:29.686 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot add column to a partition
2024-04-23 16:26:29.686 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ADD COLUMN c text;
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited column "b"
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 DROP COLUMN b;
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot rename inherited column "b"
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 RENAME COLUMN b to c;
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter inherited column "b"
2024-04-23 16:26:29.687 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ALTER COLUMN b TYPE text;
2024-04-23 16:26:29.688 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint must be added to child tables too
2024-04-23 16:26:29.688 UTC client backend[19566] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2024-04-23 16:26:29.688 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ALTER b SET NOT NULL;
2024-04-23 16:26:29.688 UTC client backend[19566] pg_regress/alter_table ERROR:  constraint must be added to child tables too
2024-04-23 16:26:29.688 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ADD CONSTRAINT check_b CHECK (b <> 'zz');
2024-04-23 16:26:29.693 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot remove constraint from only the partitioned table when partitions exist
2024-04-23 16:26:29.693 UTC client backend[19566] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2024-04-23 16:26:29.693 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ALTER b DROP NOT NULL;
2024-04-23 16:26:29.696 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot remove constraint from only the partitioned table when partitions exist
2024-04-23 16:26:29.696 UTC client backend[19566] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2024-04-23 16:26:29.696 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 DROP CONSTRAINT check_b;
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table ERROR:  column "b" is marked NOT NULL in parent table
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ALTER b DROP NOT NULL;
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop inherited constraint "check_a2" of relation "part_2"
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 DROP CONSTRAINT check_a2;
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot add NO INHERIT constraint to partitioned table "list_parted2"
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 add constraint check_b2 check (b <> 'zz') NO INHERIT;
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot inherit from partition "part_2"
2024-04-23 16:26:29.751 UTC client backend[19566] pg_regress/alter_table STATEMENT:  CREATE TABLE inh_test () INHERITS (part_2);
2024-04-23 16:26:29.760 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot inherit from a partition
2024-04-23 16:26:29.760 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE inh_test INHERIT part_2;
2024-04-23 16:26:29.760 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot change inheritance of a partition
2024-04-23 16:26:29.760 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 INHERIT inh_test;
2024-04-23 16:26:29.761 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot drop column "b" because it is part of the partition key of relation "part_5"
2024-04-23 16:26:29.761 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DROP COLUMN b;
2024-04-23 16:26:29.761 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot alter column "b" because it is part of the partition key of relation "part_5"
2024-04-23 16:26:29.761 UTC client backend[19566] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ALTER COLUMN b TYPE text;
2024-04-23 16:26:29.786 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "p11" is violated by some row
2024-04-23 16:26:29.786 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table p attach partition p1 for values from (1, 2) to (1, 10);
2024-04-23 16:26:29.811 UTC client backend[19566] pg_regress/alter_table ERROR:  partition constraint of relation "defpart_attach_test_d" is violated by some row
2024-04-23 16:26:29.811 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table defpart_attach_test attach partition defpart_attach_test_d default;
2024-04-23 16:26:29.813 UTC client backend[19566] pg_regress/alter_table ERROR:  updated partition constraint for default partition "defpart_attach_test_d" would be violated by some row
2024-04-23 16:26:29.813 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table defpart_attach_test attach partition defpart_attach_test_2 for values in (2);
2024-04-23 16:26:29.816 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach a permanent relation as partition of temporary relation "temp_part_parent"
2024-04-23 16:26:29.816 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table temp_part_parent attach partition perm_part_child default;
2024-04-23 16:26:29.817 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot attach a temporary relation as partition of permanent relation "perm_part_parent"
2024-04-23 16:26:29.817 UTC client backend[19566] pg_regress/alter_table STATEMENT:  alter table perm_part_parent attach partition temp_part_child default;
2024-04-23 16:26:29.821 UTC client backend[19566] pg_regress/alter_table ERROR:  cannot ALTER TABLE "tab_part_attach" because it is being used by active queries in this session
2024-04-23 16:26:29.821 UTC client backend[19566] pg_regress/alter_table CONTEXT:  SQL statement "alter table tab_part_attach attach partition tab_part_attach_1 for values in (1)"
	PL/pgSQL function func_part_attach() line 4 at EXECUTE
2024-04-23 16:26:29.821 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into tab_part_attach values (1);
2024-04-23 16:26:30.086 UTC client backend[19566] pg_regress/alter_table ERROR:  new row for relation "attach_parted_part1" violates partition constraint
2024-04-23 16:26:30.086 UTC client backend[19566] pg_regress/alter_table DETAIL:  Failing row contains (2, 1).
2024-04-23 16:26:30.086 UTC client backend[19566] pg_regress/alter_table STATEMENT:  insert into attach_parted_part1 values (2, 1);
2024-04-23 16:26:30.097 UTC client backend[19566] pg_regress/alter_table WARNING:  wal_level is insufficient to publish logical changes
2024-04-23 16:26:30.097 UTC client backend[19566] pg_regress/alter_table HINT:  Set wal_level to "logical" before creating subscriptions.
2024-04-23 16:26:32.154 UTC client backend[20608] pg_regress/partition_split ERROR:  relation "sales_xxx" does not exist
2024-04-23 16:26:32.154 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_xxx INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.158 UTC client backend[20621] pg_regress/reloptions ERROR:  value 2 out of bounds for option "fillfactor"
2024-04-23 16:26:32.158 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2024-04-23 16:26:32.158 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=2);
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions ERROR:  value 110 out of bounds for option "fillfactor"
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=110);
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions ERROR:  value -10.0 out of bounds for option "autovacuum_analyze_scale_factor"
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "0.000000" and "100.000000".
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = -10.0);
2024-04-23 16:26:32.442 UTC client backend[20608] pg_regress/partition_split ERROR:  relation "sales_jan2022" already exists
2024-04-23 16:26:32.442 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_jan2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions ERROR:  value 110.0 out of bounds for option "autovacuum_analyze_scale_factor"
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "0.000000" and "100.000000".
2024-04-23 16:26:32.442 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = 110.0);
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  invalid bound specification for a range partition at character 106
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_jan2022 FOR VALUES IN ('2022-05-01', '2022-06-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (not_existing_option=2);
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  unrecognized parameter namespace "not_existing_namespace"
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (not_existing_namespace.fillfactor=2);
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  empty range bound specified for partition "sales_mar2022" at character 189
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split DETAIL:  Specified lower bound ('03-01-2022') is greater than or equal to upper bound ('02-01-2022').
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-02-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  value -30.1 out of bounds for option "fillfactor"
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=-30.1);
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": string
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor='string');
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  list of new partitions should contain at least two items
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-10-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": true
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=true);
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": 12
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=12);
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_feb2022" is less than lower bound of split partition at character 112
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-01-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": 30.5
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=30.5);
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": string
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled='string');
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  name "sales_feb_mar_apr2022" is already used at character 166
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb_mar_apr2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_feb_mar_apr2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for floating point option "autovacuum_analyze_scale_factor": string
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor='string');
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for floating point option "autovacuum_analyze_scale_factor": true
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor=true);
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  name "sales_feb2022" is already used at character 158
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_feb2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  parameter "fillfactor" specified more than once
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=30, fillfactor=40);
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": true
2024-04-23 16:26:32.443 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor);
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  "sales_feb_mar_apr2022" is not a partitioned table
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_feb_mar_apr2022 SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_jan2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_feb2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  upper bound of partition "sales_apr2022" is greater than upper bound of split partition at character 284
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-06-01'));
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_mar2022" conflicts with upper bound of previous partition "sales_feb2022" at character 189
2024-04-23 16:26:32.443 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-01') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-02-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.450 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_feb2022" is not equal to lower bound of split partition at character 112
2024-04-23 16:26:32.450 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_feb_mar_apr2022 INTO
	  (PARTITION sales_feb2022 FOR VALUES FROM ('2022-02-02') TO ('2022-03-01'),
	   PARTITION sales_mar2022 FOR VALUES FROM ('2022-03-01') TO ('2022-04-01'),
	   PARTITION sales_apr2022 FOR VALUES FROM ('2022-04-01') TO ('2022-05-01'));
2024-04-23 16:26:32.457 UTC client backend[20614] pg_regress/explain ERROR:  EXPLAIN options ANALYZE and GENERIC_PLAN cannot be used together
2024-04-23 16:26:32.457 UTC client backend[20614] pg_regress/explain CONTEXT:  PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement
2024-04-23 16:26:32.457 UTC client backend[20614] pg_regress/explain STATEMENT:  select explain_filter('explain (analyze, generic_plan) select unique1 from tenk1 where thousand = $1');
2024-04-23 16:26:32.512 UTC client backend[20611] pg_regress/hash_part ERROR:  could not open relation with OID 0
2024-04-23 16:26:32.512 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition(0, 4, 0, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  "tenk1" is not a hash partitioned table
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('tenk1'::regclass, 4, 0, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  "mchash1" is not a hash partitioned table
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash1'::regclass, 4, 0, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  modulus for hash partition must be an integer value greater than zero
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 0, 0, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  remainder for hash partition must be an integer value greater than or equal to zero
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 1, -1, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  remainder for hash partition must be less than modulus
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 1, 1, NULL);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (3)
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, NULL::int, NULL::text, NULL::json);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (1)
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int);
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part ERROR:  column 2 of the partition key has type text, but supplied value is of type integer
2024-04-23 16:26:32.513 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int);
2024-04-23 16:26:32.514 UTC client backend[20611] pg_regress/hash_part ERROR:  column 2 of the partition key has type "text", but supplied value is of type "integer"
2024-04-23 16:26:32.514 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 2, 1,
									variadic array[1,2]::int[]);
2024-04-23 16:26:32.538 UTC client backend[20611] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (0)
2024-04-23 16:26:32.538 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0,
									variadic array[]::int[]);
2024-04-23 16:26:32.540 UTC client backend[20611] pg_regress/hash_part ERROR:  column 1 of the partition key has type "integer", but supplied value is of type "timestamp with time zone"
2024-04-23 16:26:32.540 UTC client backend[20611] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0,
									variadic array[now(), now()]);
2024-04-23 16:26:32.541 UTC client backend[20609] pg_regress/partition_merge ERROR:  partition with name "sales_feb2022" is already used at character 73
2024-04-23 16:26:32.541 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_range MERGE PARTITIONS (sales_feb2022, sales_mar2022, sales_feb2022) INTO sales_feb_mar_apr2022;
2024-04-23 16:26:32.546 UTC client backend[20609] pg_regress/partition_merge ERROR:  "sales_apr2022" is not a table
2024-04-23 16:26:32.546 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_range MERGE PARTITIONS (sales_feb2022, sales_mar2022, sales_apr2022) INTO sales_feb_mar_apr2022;
2024-04-23 16:26:32.551 UTC client backend[20609] pg_regress/partition_merge ERROR:  lower bound of partition "sales_mar2022" conflicts with upper bound of previous partition "sales_jan2022"
2024-04-23 16:26:32.551 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_range MERGE PARTITIONS (sales_jan2022, sales_mar2022) INTO sales_jan_mar2022;
2024-04-23 16:26:32.558 UTC client backend[20621] pg_regress/reloptions ERROR:  RESET must not include values for parameters
2024-04-23 16:26:32.558 UTC client backend[20621] pg_regress/reloptions STATEMENT:  ALTER TABLE reloptions_test RESET (fillfactor=12);
2024-04-23 16:26:32.558 UTC client backend[20609] pg_regress/partition_merge ERROR:  lower bound of partition "sales_jan2022" conflicts with upper bound of previous partition "sales_dec2021"
2024-04-23 16:26:32.558 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_range MERGE PARTITIONS (sales_dec2021, sales_jan2022, sales_feb2022) INTO sales_dec_jan_feb2022;
2024-04-23 16:26:32.646 UTC client backend[20615] pg_regress/indexing ERROR:  cannot create index on partitioned table "idxpart" concurrently
2024-04-23 16:26:32.646 UTC client backend[20615] pg_regress/indexing STATEMENT:  create index concurrently on idxpart (a);
2024-04-23 16:26:32.647 UTC client backend[20621] pg_regress/reloptions ERROR:  null value in column "i" of relation "reloptions_test" violates not-null constraint
2024-04-23 16:26:32.647 UTC client backend[20621] pg_regress/reloptions DETAIL:  Failing row contains (null, null).
2024-04-23 16:26:32.647 UTC client backend[20621] pg_regress/reloptions STATEMENT:  INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL);
2024-04-23 16:26:32.658 UTC client backend[20621] pg_regress/reloptions ERROR:  null value in column "i" of relation "reloptions_test" violates not-null constraint
2024-04-23 16:26:32.658 UTC client backend[20621] pg_regress/reloptions DETAIL:  Failing row contains (null, null).
2024-04-23 16:26:32.658 UTC client backend[20621] pg_regress/reloptions STATEMENT:  INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL);
2024-04-23 16:26:32.683 UTC client backend[20617] pg_regress/compression ERROR:  column data type integer does not support compression
2024-04-23 16:26:32.683 UTC client backend[20617] pg_regress/compression STATEMENT:  CREATE TABLE cmdata2 (f1 int COMPRESSION pglz);
2024-04-23 16:26:32.683 UTC client backend[20621] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2024-04-23 16:26:32.683 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2 (i int) WITH (toast.not_existing_option = 42);
2024-04-23 16:26:32.697 UTC client backend[20621] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2024-04-23 16:26:32.697 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx ON reloptions_test (s)
		WITH (not_existing_option=2);
2024-04-23 16:26:32.699 UTC client backend[20621] pg_regress/reloptions ERROR:  unrecognized parameter namespace "not_existing_ns"
2024-04-23 16:26:32.699 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx ON reloptions_test (s)
		WITH (not_existing_ns.fillfactor=2);
2024-04-23 16:26:32.700 UTC client backend[20621] pg_regress/reloptions ERROR:  value 1 out of bounds for option "fillfactor"
2024-04-23 16:26:32.700 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2024-04-23 16:26:32.700 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=1);
2024-04-23 16:26:32.702 UTC client backend[20621] pg_regress/reloptions ERROR:  value 130 out of bounds for option "fillfactor"
2024-04-23 16:26:32.702 UTC client backend[20621] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2024-04-23 16:26:32.702 UTC client backend[20621] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=130);
2024-04-23 16:26:32.903 UTC client backend[20615] pg_regress/indexing ERROR:  "idxpart_c" is not a partitioned table
2024-04-23 16:26:32.903 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart_c attach partition idxpart1_c for values from (10) to (20);
2024-04-23 16:26:32.909 UTC client backend[20615] pg_regress/indexing ERROR:  ALTER action DETACH PARTITION cannot be performed on relation "idxpart_c"
2024-04-23 16:26:32.909 UTC client backend[20615] pg_regress/indexing DETAIL:  This operation is not supported for partitioned indexes.
2024-04-23 16:26:32.909 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart_c detach partition idxpart1_c;
2024-04-23 16:26:32.962 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop index idxpart1_a_idx because index idxpart_a_idx requires it
2024-04-23 16:26:32.962 UTC client backend[20615] pg_regress/indexing HINT:  You can drop index idxpart_a_idx instead.
2024-04-23 16:26:32.962 UTC client backend[20615] pg_regress/indexing STATEMENT:  drop index idxpart1_a_idx;
2024-04-23 16:26:32.962 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop partitioned index "idxpart_a_idx" concurrently
2024-04-23 16:26:32.962 UTC client backend[20615] pg_regress/indexing STATEMENT:  drop index concurrently idxpart_a_idx;
2024-04-23 16:26:33.020 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop index idxpart1_temp_a_idx because index idxpart_temp_a_idx requires it
2024-04-23 16:26:33.020 UTC client backend[20615] pg_regress/indexing HINT:  You can drop index idxpart_temp_a_idx instead.
2024-04-23 16:26:33.020 UTC client backend[20615] pg_regress/indexing STATEMENT:  drop index idxpart1_temp_a_idx;
2024-04-23 16:26:33.045 UTC client backend[20617] pg_regress/compression ERROR:  column "f1" has a compression method conflict
2024-04-23 16:26:33.045 UTC client backend[20617] pg_regress/compression DETAIL:  pglz versus lz4
2024-04-23 16:26:33.045 UTC client backend[20617] pg_regress/compression STATEMENT:  CREATE TABLE cminh() INHERITS(cmdata, cmdata1);
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression ERROR:  column "f1" has a compression method conflict
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression DETAIL:  pglz versus lz4
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression STATEMENT:  CREATE TABLE cminh(f1 TEXT COMPRESSION lz4) INHERITS(cmdata);
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression ERROR:  invalid value for parameter "default_toast_compression": ""
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression HINT:  Available values: pglz, lz4.
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression STATEMENT:  SET default_toast_compression = '';
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression ERROR:  invalid value for parameter "default_toast_compression": "I do not exist compression"
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression HINT:  Available values: pglz, lz4.
2024-04-23 16:26:33.046 UTC client backend[20617] pg_regress/compression STATEMENT:  SET default_toast_compression = 'I do not exist compression';
2024-04-23 16:26:33.050 UTC client backend[20608] pg_regress/partition_split ERROR:  relation "sales_jan_feb2022" does not exist at character 15
2024-04-23 16:26:33.050 UTC client backend[20608] pg_regress/partition_split STATEMENT:  SELECT * FROM sales_jan_feb2022;
2024-04-23 16:26:33.278 UTC client backend[20615] pg_regress/indexing ERROR:  "idxpart" is not an index
2024-04-23 16:26:33.278 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart attach partition idxpart1;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  "idxpart1" is not an index
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart_a_b_idx" as a partition of index "idxpart_a_b_idx"
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing DETAIL:  Index "idxpart_a_b_idx" is not an index on any partition of table "idxpart".
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart_a_b_idx;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  relation "idxpart1_b_idx" does not exist
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_b_idx;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst1" as a partition of index "idxpart_a_b_idx"
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst1;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst2" as a partition of index "idxpart_a_b_idx"
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst2;
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst3" as a partition of index "idxpart_a_b_idx"
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:33.280 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst3;
2024-04-23 16:26:33.336 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.0", size 499712
2024-04-23 16:26:33.336 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  COMMIT;
2024-04-23 16:26:33.362 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2_a_b" as a partition of index "idxpart_a_b_idx"
2024-04-23 16:26:33.362 UTC client backend[20615] pg_regress/indexing DETAIL:  Another index is already attached for partition "idxpart1".
2024-04-23 16:26:33.362 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_2_a_b;
2024-04-23 16:26:33.459 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170
2024-04-23 16:26:33.459 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_others INTO
	  (PARTITION sales_dec2022 FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_error FOR VALUES FROM (20211230) TO (20220201),
	   PARTITION sales_feb2022 FOR VALUES FROM (20220201) TO (20220301),
	   PARTITION sales_others DEFAULT);
2024-04-23 16:26:33.470 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_feb2022" conflicts with upper bound of previous partition "sales_error" at character 239
2024-04-23 16:26:33.470 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_others INTO
	  (PARTITION sales_dec2022 FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_error FOR VALUES FROM (20220101) TO (20220202),
	   PARTITION sales_feb2022 FOR VALUES FROM (20220201) TO (20220301),
	   PARTITION sales_others DEFAULT);
2024-04-23 16:26:33.470 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170
2024-04-23 16:26:33.470 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_others INTO
	  (PARTITION sales_dec2022 FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_error FOR VALUES FROM (20211210) TO (20211220),
	   PARTITION sales_feb2022 FOR VALUES FROM (20220201) TO (20220301),
	   PARTITION sales_others DEFAULT);
2024-04-23 16:26:33.482 UTC client backend[20608] pg_regress/partition_split ERROR:  lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170
2024-04-23 16:26:33.482 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_others INTO
	  (PARTITION sales_dec2022 FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_error FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_feb2022 FOR VALUES FROM (20220201) TO (20220301),
	   PARTITION sales_others DEFAULT);
2024-04-23 16:26:33.482 UTC client backend[20608] pg_regress/partition_split ERROR:  one partition in the list should be DEFAULT because split partition is DEFAULT at character 72
2024-04-23 16:26:33.482 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_range SPLIT PARTITION sales_others INTO
	  (PARTITION sales_dec2022 FOR VALUES FROM (20211201) TO (20220101),
	   PARTITION sales_jan2022 FOR VALUES FROM (20220101) TO (20220201),
	   PARTITION sales_feb2022 FOR VALUES FROM (20220201) TO (20220301));
2024-04-23 16:26:33.576 UTC client backend[20617] pg_regress/compression ERROR:  invalid compression method "i_do_not_exist_compression"
2024-04-23 16:26:33.576 UTC client backend[20617] pg_regress/compression STATEMENT:  CREATE TABLE badcompresstbl (a text COMPRESSION I_Do_Not_Exist_Compression);
2024-04-23 16:26:33.603 UTC client backend[20617] pg_regress/compression ERROR:  invalid compression method "i_do_not_exist_compression"
2024-04-23 16:26:33.603 UTC client backend[20617] pg_regress/compression STATEMENT:  ALTER TABLE badcompresstbl ALTER a SET COMPRESSION I_Do_Not_Exist_Compression;
2024-04-23 16:26:34.354 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:34.407 UTC client backend[20608] pg_regress/partition_split ERROR:  new row for relation "sales_mar2022" violates check constraint "sales_range_sales_amount_check"
2024-04-23 16:26:34.407 UTC client backend[20608] pg_regress/partition_split DETAIL:  Failing row contains (1, 0, 03-11-2022).
2024-04-23 16:26:34.407 UTC client backend[20608] pg_regress/partition_split STATEMENT:  INSERT INTO sales_range VALUES (1, 0, '2022-03-11');
2024-04-23 16:26:34.408 UTC client backend[20608] pg_regress/partition_split ERROR:  insert or update on table "sales_mar2022" violates foreign key constraint "sales_range_salesman_id_fkey"
2024-04-23 16:26:34.408 UTC client backend[20608] pg_regress/partition_split DETAIL:  Key (salesman_id)=(-1) is not present in table "salesmans".
2024-04-23 16:26:34.408 UTC client backend[20608] pg_regress/partition_split STATEMENT:  INSERT INTO sales_range VALUES (-1, 10, '2022-03-11');
2024-04-23 16:26:34.498 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.3", size 425984
2024-04-23 16:26:34.498 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.558 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.4", size 270336
2024-04-23 16:26:34.558 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.833 UTC client backend[20619] pg_regress/partition_prune ERROR:  table "part_rev" contains column "c" not found in parent "part"
2024-04-23 16:26:34.833 UTC client backend[20619] pg_regress/partition_prune DETAIL:  The new partition may contain only the columns present in parent.
2024-04-23 16:26:34.833 UTC client backend[20619] pg_regress/partition_prune STATEMENT:  ALTER TABLE part ATTACH PARTITION part_rev FOR VALUES IN (3);
2024-04-23 16:26:34.852 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.2", size 876544
2024-04-23 16:26:34.852 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.881 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.6", size 270336
2024-04-23 16:26:34.881 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.897 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.7", size 425984
2024-04-23 16:26:34.897 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.919 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.5", size 344064
2024-04-23 16:26:34.919 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:34.940 UTC client backend[20618] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp20618.1", size 974848
2024-04-23 16:26:34.940 UTC client backend[20618] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2024-04-23 16:26:35.250 UTC client backend[20608] pg_regress/partition_split ERROR:  insert or update on table "sales" violates foreign key constraint "sales_salesman_id_fkey"
2024-04-23 16:26:35.250 UTC client backend[20608] pg_regress/partition_split DETAIL:  Key (salesman_id)=(40) is not present in table "salesmans".
2024-04-23 16:26:35.250 UTC client backend[20608] pg_regress/partition_split STATEMENT:  INSERT INTO sales VALUES (40, 50,  '2022-03-04');
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge ERROR:  "sales_external" is not a partition
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_east, sales_external) INTO sales_all;
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge ERROR:  "sales_external2" is not a partition
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_east, sales_external2) INTO sales_all;
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge ERROR:  relation "sales_nord2" is not a partition of relation "sales_list"
2024-04-23 16:26:35.386 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_nord2, sales_east) INTO sales_all;
2024-04-23 16:26:35.686 UTC client backend[20609] pg_regress/partition_merge ERROR:  relation "t1p1" is not a partition of relation "t2"
2024-04-23 16:26:35.686 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE t2 MERGE PARTITIONS (t1p1, t2pa) INTO t2p;
2024-04-23 16:26:35.686 UTC client backend[20609] pg_regress/partition_merge ERROR:  "t3" is not a partition
2024-04-23 16:26:35.686 UTC client backend[20609] pg_regress/partition_merge STATEMENT:  ALTER TABLE t2 MERGE PARTITIONS (t2pa, t3) INTO t2p;
2024-04-23 16:26:35.718 UTC client backend[20608] pg_regress/partition_split ERROR:  new partition "sales_east" would overlap with another (not split) partition "sales_nord" at character 200
2024-04-23 16:26:35.718 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_list SPLIT PARTITION sales_all INTO
	  (PARTITION sales_west FOR VALUES IN ('Lisbon', 'New York', 'Madrid'),
	   PARTITION sales_east FOR VALUES IN ('Bejing', 'Delhi', 'Vladivostok', 'Helsinki'),
	   PARTITION sales_central FOR VALUES IN ('Warsaw', 'Berlin', 'Kyiv'));
2024-04-23 16:26:35.719 UTC client backend[20608] pg_regress/partition_split ERROR:  new partition "sales_west" would overlap with another new partition "sales_central" at character 94
2024-04-23 16:26:35.719 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_list SPLIT PARTITION sales_all INTO
	  (PARTITION sales_west FOR VALUES IN ('Lisbon', 'New York', 'Madrid'),
	   PARTITION sales_east FOR VALUES IN ('Bejing', 'Delhi', 'Vladivostok'),
	   PARTITION sales_central FOR VALUES IN ('Warsaw', 'Berlin', 'Lisbon', 'Kyiv'));
2024-04-23 16:26:35.719 UTC client backend[20608] pg_regress/partition_split ERROR:  new partition "sales_west" cannot have NULL value because split partition does not have at character 126
2024-04-23 16:26:35.719 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_list SPLIT PARTITION sales_all INTO
	  (PARTITION sales_west FOR VALUES IN ('Lisbon', 'New York', 'Madrid', NULL),
	   PARTITION sales_east FOR VALUES IN ('Bejing', 'Delhi', 'Vladivostok'),
	   PARTITION sales_central FOR VALUES IN ('Warsaw', 'Berlin', 'Kyiv'));
2024-04-23 16:26:35.722 UTC client backend[20608] pg_regress/partition_split ERROR:  new partitions do not have value NULL but split partition does
2024-04-23 16:26:35.722 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_list SPLIT PARTITION sales_all INTO
	  (PARTITION sales_west FOR VALUES IN ('Lisbon', 'New York', 'Madrid'),
	   PARTITION sales_east FOR VALUES IN ('Bejing', 'Delhi', 'Vladivostok'),
	   PARTITION sales_central FOR VALUES IN ('Warsaw', 'Berlin', 'Kyiv'));
2024-04-23 16:26:35.722 UTC client backend[20608] pg_regress/partition_split ERROR:  new partitions do not have value 'Kyiv' but split partition does
2024-04-23 16:26:35.722 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE sales_list SPLIT PARTITION sales_all INTO
	  (PARTITION sales_west FOR VALUES IN ('Lisbon', 'New York', 'Madrid'),
	   PARTITION sales_east FOR VALUES IN ('Bejing', 'Delhi', 'Vladivostok'),
	   PARTITION sales_central FOR VALUES IN ('Warsaw', 'Berlin', NULL));
2024-04-23 16:26:35.779 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart2_a_idx" as a partition of index "idxpart_a_idx"
2024-04-23 16:26:35.779 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:35.779 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_a_idx attach partition idxpart2_a_idx;
2024-04-23 16:26:36.553 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_1b_idx" as a partition of index "idxpart_1_idx"
2024-04-23 16:26:36.553 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:36.553 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_1_idx attach partition idxpart1_1b_idx;
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2b_idx" as a partition of index "idxpart_2_idx"
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_2_idx attach partition idxpart1_2b_idx;
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2c_idx" as a partition of index "idxpart_2_idx"
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing DETAIL:  The index definitions do not match.
2024-04-23 16:26:36.611 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_2_idx attach partition idxpart1_2c_idx;
2024-04-23 16:26:37.939 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 2356 buffers (14.4%); 0 WAL file(s) added, 0 removed, 2 recycled; write=2.638 s, sync=0.001 s, total=3.586 s; sync files=0, longest=0.000 s, average=0.000 s; distance=23007 kB, estimate=56394 kB; lsn=0/6AAE4B0, redo lsn=0/66303C0
2024-04-23 16:26:37.944 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:38.745 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 298 buffers (1.8%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.695 s, sync=0.001 s, total=0.801 s; sync files=0, longest=0.000 s, average=0.000 s; distance=4708 kB, estimate=51225 kB; lsn=0/6B209C8, redo lsn=0/6AC94B8
2024-04-23 16:26:38.783 UTC client backend[20731] pg_regress/stats ERROR:  unrecognized reset target: "unknown"
2024-04-23 16:26:38.783 UTC client backend[20731] pg_regress/stats HINT:  Target must be "archiver", "bgwriter", "checkpointer", "io", "recovery_prefetch", "slru", or "wal".
2024-04-23 16:26:38.783 UTC client backend[20731] pg_regress/stats STATEMENT:  SELECT pg_stat_reset_shared('unknown');
2024-04-23 16:26:38.785 UTC client backend[20731] pg_regress/stats ERROR:  invalid statistics kind: "zaphod"
2024-04-23 16:26:38.785 UTC client backend[20731] pg_regress/stats STATEMENT:  SELECT pg_stat_have_stats('zaphod', 0, 0);
2024-04-23 16:26:39.121 UTC client backend[20608] pg_regress/partition_split ERROR:  relation "t1pa" is not a partition of relation "t2"
2024-04-23 16:26:39.121 UTC client backend[20608] pg_regress/partition_split STATEMENT:  ALTER TABLE t2 SPLIT PARTITION t1pa INTO
	   (PARTITION t2a FOR VALUES FROM ('A') TO ('B'),
	    PARTITION t2b FOR VALUES FROM ('B') TO ('C'));
2024-04-23 16:26:39.132 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:39.321 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 128 buffers (0.8%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.063 s, sync=0.001 s, total=0.190 s; sync files=0, longest=0.000 s, average=0.000 s; distance=774 kB, estimate=46180 kB; lsn=0/6BC1060, redo lsn=0/6B8AEE0
2024-04-23 16:26:39.323 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:39.365 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 54 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.043 s; sync files=0, longest=0.000 s, average=0.000 s; distance=261 kB, estimate=41588 kB; lsn=0/6BFE7D8, redo lsn=0/6BCC358
2024-04-23 16:26:39.641 UTC client backend[20615] pg_regress/indexing ERROR:  multiple primary keys for table "failpart" are not allowed
2024-04-23 16:26:39.641 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table failpart partition of idxpart (b primary key) for values from (0) to (100);
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int unique, b int) partition by range (a, b);
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2024-04-23 16:26:39.697 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int, b int unique) partition by range (a, b);
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int primary key, b int) partition by range (b, a);
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "a" which is part of the partition key.
2024-04-23 16:26:39.698 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int, b int primary key) partition by range (b, a);
2024-04-23 16:26:39.730 UTC client backend[21061] pg_regress/stats LOG:  wait_for_hot_stats delayed 0.000203 seconds
2024-04-23 16:26:39.730 UTC client backend[21061] pg_regress/stats CONTEXT:  PL/pgSQL function wait_for_hot_stats() line 17 at RAISE
2024-04-23 16:26:39.730 UTC client backend[21061] pg_regress/stats STATEMENT:  SELECT wait_for_hot_stats();
2024-04-23 16:26:39.744 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.744 UTC client backend[20615] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.744 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, b int4range, exclude USING GIST (a with = )) partition by range (a, b);
2024-04-23 16:26:39.744 UTC client backend[20615] pg_regress/indexing ERROR:  cannot match partition key to index on column "a" using non-equal operator "-|-"
2024-04-23 16:26:39.744 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, exclude USING GIST (a with -|- )) partition by range (a);
2024-04-23 16:26:39.746 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.746 UTC client backend[20615] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2024-04-23 16:26:39.746 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, b int4range, c int4range, exclude USING GIST (b with =, c with &&)) partition by range (a);
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing ERROR:  unsupported PRIMARY KEY constraint with partition key definition
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing DETAIL:  PRIMARY KEY constraints cannot be used when partition keys include expressions.
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int primary key, b int) partition by range ((b + a));
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing ERROR:  unsupported UNIQUE constraint with partition key definition
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraints cannot be used when partition keys include expressions.
2024-04-23 16:26:39.749 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart (a int unique, b int) partition by range ((b + a));
2024-04-23 16:26:39.750 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.750 UTC client backend[20615] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.750 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart add primary key (a);
2024-04-23 16:26:39.780 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.780 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.780 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart add unique (a);
2024-04-23 16:26:39.804 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.804 UTC client backend[20615] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.804 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (a with =);
2024-04-23 16:26:39.812 UTC client backend[20615] pg_regress/indexing ERROR:  cannot match partition key to index on column "a" using non-equal operator "-|-"
2024-04-23 16:26:39.812 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (a with -|-);
2024-04-23 16:26:39.819 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.819 UTC client backend[20615] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2024-04-23 16:26:39.819 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (b with =, c with &&);
2024-04-23 16:26:39.837 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.837 UTC client backend[20615] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart2" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.837 UTC client backend[20615] pg_regress/indexing STATEMENT:  create table idxpart2 partition of idxpart
	for values from (0) to (1000) partition by range (b);
2024-04-23 16:26:39.840 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:39.840 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart1" lacks column "b" which is part of the partition key.
2024-04-23 16:26:39.840 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart attach partition idxpart1 for values from (1) to (1000);
2024-04-23 16:26:39.951 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop index idxpart0_pkey because index idxpart_pkey requires it
2024-04-23 16:26:39.951 UTC client backend[20615] pg_regress/indexing HINT:  You can drop index idxpart_pkey instead.
2024-04-23 16:26:39.951 UTC client backend[20615] pg_regress/indexing STATEMENT:  drop index idxpart0_pkey;
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop index idxpart1_pkey because index idxpart_pkey requires it
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing HINT:  You can drop index idxpart_pkey instead.
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing STATEMENT:  drop index idxpart1_pkey;
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop inherited constraint "idxpart0_pkey" of relation "idxpart0"
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart0 drop constraint idxpart0_pkey;
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop inherited constraint "idxpart1_pkey" of relation "idxpart1"
2024-04-23 16:26:39.952 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart1 drop constraint idxpart1_pkey;
2024-04-23 16:26:39.965 UTC client backend[20615] pg_regress/indexing ERROR:  multiple primary keys for table "idxpart1" are not allowed
2024-04-23 16:26:39.965 UTC client backend[20615] pg_regress/indexing STATEMENT:  ALTER TABLE idxpart ATTACH PARTITION idxpart1 FOR VALUES FROM (100) TO (200);
2024-04-23 16:26:39.975 UTC client backend[20615] pg_regress/indexing ERROR:  multiple primary keys for table "idxpart11" are not allowed
2024-04-23 16:26:39.975 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart attach partition idxpart1 for values from (0) to (10000);
2024-04-23 16:26:40.007 UTC client backend[20615] pg_regress/indexing ERROR:  invalid primary key definition
2024-04-23 16:26:40.007 UTC client backend[20615] pg_regress/indexing DETAIL:  Column "a" of relation "idxpart0" is not marked NOT NULL.
2024-04-23 16:26:40.007 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_pkey attach partition idxpart0_a_key;
2024-04-23 16:26:40.342 UTC client backend[20615] pg_regress/indexing ERROR:  column "a" is marked NOT NULL in parent table
2024-04-23 16:26:40.342 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table idxpart0 alter column a drop not null;
2024-04-23 16:26:40.874 UTC client backend[20615] pg_regress/indexing ERROR:  cannot attach index "idxpart1_a_idx" as a partition of index "idxpart_pkey"
2024-04-23 16:26:40.874 UTC client backend[20615] pg_regress/indexing DETAIL:  The index "idxpart_pkey" belongs to a constraint in table "idxpart" but no constraint exists for index "idxpart1_a_idx".
2024-04-23 16:26:40.874 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter index idxpart_pkey attach partition idxpart1_a_idx;
2024-04-23 16:26:40.934 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart1_a_idx"
2024-04-23 16:26:40.934 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(65536) already exists.
2024-04-23 16:26:40.934 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into idxpart select 2^g, format('two to power of %s', g) from generate_series(15, 17) g;
2024-04-23 16:26:40.939 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart2_a_idx"
2024-04-23 16:26:40.939 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(285714) already exists.
2024-04-23 16:26:40.939 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into idxpart select a * 2, b || b from idxpart where a between 2^16 and 2^19;
2024-04-23 16:26:40.940 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart2_a_idx"
2024-04-23 16:26:40.940 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(572814) already exists.
2024-04-23 16:26:40.940 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into idxpart values (572814, 'five');
2024-04-23 16:26:41.330 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart1_a_b_idx"
2024-04-23 16:26:41.330 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(1) already exists.
2024-04-23 16:26:41.330 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into covidxpart values (1, 1);
2024-04-23 16:26:41.339 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart3_a_b_idx"
2024-04-23 16:26:41.339 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(3) already exists.
2024-04-23 16:26:41.339 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into covidxpart values (3, 1);
2024-04-23 16:26:41.348 UTC client backend[20615] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart4_a_b_idx"
2024-04-23 16:26:41.348 UTC client backend[20615] pg_regress/indexing DETAIL:  Key (a)=(4) already exists.
2024-04-23 16:26:41.348 UTC client backend[20615] pg_regress/indexing STATEMENT:  insert into covidxpart values (4, 1);
2024-04-23 16:26:41.349 UTC client backend[20615] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2024-04-23 16:26:41.349 UTC client backend[20615] pg_regress/indexing DETAIL:  UNIQUE constraint on table "covidxpart" lacks column "a" which is part of the partition key.
2024-04-23 16:26:41.349 UTC client backend[20615] pg_regress/indexing STATEMENT:  create unique index on covidxpart (b) include (a);
2024-04-23 16:26:41.354 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop inherited constraint "parted_pk_detach_test1_pkey" of relation "parted_pk_detach_test1"
2024-04-23 16:26:41.354 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table parted_pk_detach_test1 drop constraint parted_pk_detach_test1_pkey;
2024-04-23 16:26:41.366 UTC client backend[20615] pg_regress/indexing ERROR:  cannot drop inherited constraint "parted_uniq_detach_test1_a_key" of relation "parted_uniq_detach_test1"
2024-04-23 16:26:41.366 UTC client backend[20615] pg_regress/indexing STATEMENT:  alter table parted_uniq_detach_test1 drop constraint parted_uniq_detach_test1_a_key;
2024-04-23 16:26:41.672 UTC client backend[20615] pg_regress/indexing ERROR:  division by zero
2024-04-23 16:26:41.672 UTC client backend[20615] pg_regress/indexing STATEMENT:  create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b));
2024-04-23 16:26:41.861 UTC client backend[21260] pg_regress/event_trigger ERROR:  function pg_backend_pid must return type event_trigger
2024-04-23 16:26:41.861 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger
	   on ddl_command_start
	   execute procedure pg_backend_pid();
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger ERROR:  trigger functions can only be called as triggers
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger CONTEXT:  compilation of PL/pgSQL function "test_event_trigger" near line 1
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  SELECT test_event_trigger();
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger ERROR:  event trigger functions cannot have declared arguments
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger CONTEXT:  compilation of PL/pgSQL function "test_event_trigger_arg" near line 1
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create function test_event_trigger_arg(name text)
	returns event_trigger as $$ BEGIN RETURN 1; END $$ language plpgsql;
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger ERROR:  SQL functions cannot return type event_trigger
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create function test_event_trigger_sql() returns event_trigger as $$
	SELECT 1 $$ language sql;
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger ERROR:  unrecognized event name "elephant_bootstrap"
2024-04-23 16:26:41.863 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger on elephant_bootstrap
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  unrecognized filter variable "food"
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when food in ('sandwich')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  filter value "sandwich" not recognized for filter variable "tag"
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('sandwich')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  filter value "create skunkcabbage" not recognized for filter variable "tag"
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('create table', 'create skunkcabbage')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  event triggers are not supported for DROP EVENT TRIGGER
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('DROP EVENT TRIGGER')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE ROLE
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE ROLE')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE DATABASE
2024-04-23 16:26:41.975 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE DATABASE')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE TABLESPACE
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE TABLESPACE')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger ERROR:  filter variable "tag" specified more than once
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('create table') and tag in ('CREATE FUNCTION')
	   execute procedure test_event_trigger();
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger ERROR:  syntax error at or near "'argument not allowed'" at character 106
2024-04-23 16:26:41.976 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   execute procedure test_event_trigger('argument not allowed');
2024-04-23 16:26:41.979 UTC client backend[21260] pg_regress/event_trigger ERROR:  permission denied to create event trigger "regress_event_trigger_noperms"
2024-04-23 16:26:41.979 UTC client backend[21260] pg_regress/event_trigger HINT:  Must be superuser to create an event trigger.
2024-04-23 16:26:41.979 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger_noperms on ddl_command_start
	   execute procedure test_event_trigger();
2024-04-23 16:26:42.061 UTC client backend[21260] pg_regress/event_trigger ERROR:  permission denied to change owner of event trigger "regress_event_trigger"
2024-04-23 16:26:42.061 UTC client backend[21260] pg_regress/event_trigger HINT:  The owner of an event trigger must be a superuser.
2024-04-23 16:26:42.061 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  alter event trigger regress_event_trigger owner to regress_evt_user;
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger ERROR:  event trigger "regress_event_trigger2" already exists
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  alter event trigger regress_event_trigger rename to regress_event_trigger2;
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger ERROR:  event trigger "regress_event_trigger" does not exist
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  drop event trigger regress_event_trigger;
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger ERROR:  role "regress_evt_user" cannot be dropped because some objects depend on it
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger DETAIL:  owner of event trigger regress_event_trigger3
	owner of user mapping for regress_evt_user on server useless_server
	owner of default privileges on new relations belonging to role regress_evt_user
2024-04-23 16:26:42.062 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  drop role regress_evt_user;
2024-04-23 16:26:42.085 UTC client backend[21260] pg_regress/event_trigger ERROR:  object audit_tbls.schema_two_table_three of type table cannot be dropped
2024-04-23 16:26:42.085 UTC client backend[21260] pg_regress/event_trigger CONTEXT:  PL/pgSQL function undroppable() line 14 at RAISE
	SQL statement "DROP TABLE IF EXISTS audit_tbls.schema_two_table_three"
	PL/pgSQL function test_evtrig_dropped_objects() line 8 at EXECUTE
2024-04-23 16:26:42.085 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  DROP SCHEMA schema_one, schema_two CASCADE;
2024-04-23 16:26:42.089 UTC client backend[21260] pg_regress/event_trigger ERROR:  object schema_one.table_three of type table cannot be dropped
2024-04-23 16:26:42.089 UTC client backend[21260] pg_regress/event_trigger CONTEXT:  PL/pgSQL function undroppable() line 14 at RAISE
2024-04-23 16:26:42.089 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  DROP SCHEMA schema_one, schema_two CASCADE;
2024-04-23 16:26:42.135 UTC client backend[21260] pg_regress/event_trigger ERROR:  pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function
2024-04-23 16:26:42.135 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  select pg_event_trigger_table_rewrite_oid();
2024-04-23 16:26:42.152 UTC client backend[21260] pg_regress/event_trigger ERROR:  rewrites not allowed
2024-04-23 16:26:42.152 UTC client backend[21260] pg_regress/event_trigger CONTEXT:  PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE
2024-04-23 16:26:42.152 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  alter table rewriteme alter column foo type numeric;
2024-04-23 16:26:42.168 UTC client backend[21260] pg_regress/event_trigger ERROR:  cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it
2024-04-23 16:26:42.168 UTC client backend[21260] pg_regress/event_trigger STATEMENT:  alter type rewritetype alter attribute a type varchar cascade;
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace ERROR:  tablespace location must be an absolute path
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspace LOCATION 'relative';
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace ERROR:  tablespace location must be an absolute path
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspace LOCATION '';
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace ERROR:  unrecognized parameter "some_nonexistent_parameter"
2024-04-23 16:26:42.904 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspacewith LOCATION '' WITH (some_nonexistent_parameter = true);
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace ERROR:  unrecognized parameter "some_nonexistent_parameter"
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace STATEMENT:  ALTER TABLESPACE regress_tblspace SET (some_nonexistent_parameter = true);
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace ERROR:  RESET must not include values for parameters
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace STATEMENT:  ALTER TABLESPACE regress_tblspace RESET (random_page_cost = 2.0);
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move system relation "pg_am_name_index"
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_am;
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_am;
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move system relation "pg_authid_rolname_index"
2024-04-23 16:26:42.922 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_authid;
2024-04-23 16:26:42.930 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:26:42.930 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_authid;
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move system relation "pg_toast_1260_index"
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) INDEX pg_toast.pg_toast_1260_index;
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) INDEX CONCURRENTLY pg_toast.pg_toast_1260_index;
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move system relation "pg_toast_1260_index"
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_toast.pg_toast_1260;
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_toast.pg_toast_1260;
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move system relation "pg_authid_rolname_index"
2024-04-23 16:26:42.931 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) TABLE pg_authid;
2024-04-23 16:26:42.939 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2024-04-23 16:26:42.939 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) TABLE CONCURRENTLY pg_authid;
2024-04-23 16:26:42.946 UTC client backend[21376] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2024-04-23 16:26:42.946 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) INDEX regress_tblspace_test_tbl_idx;
2024-04-23 16:26:42.946 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot move non-shared relation to tablespace "pg_global"
2024-04-23 16:26:42.946 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) INDEX CONCURRENTLY regress_tblspace_test_tbl_idx;
2024-04-23 16:26:42.995 UTC client backend[21376] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2024-04-23 16:26:42.995 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_1 PARTITION OF testschema.part FOR VALUES IN (1);
2024-04-23 16:26:43.002 UTC client backend[21376] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2024-04-23 16:26:43.002 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_3 PARTITION OF testschema.part FOR VALUES IN (3);
2024-04-23 16:26:43.022 UTC client backend[21376] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2024-04-23 16:26:43.022 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_78 PARTITION OF testschema.part FOR VALUES IN (7, 8)
	  PARTITION BY LIST (a);
2024-04-23 16:26:43.078 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2024-04-23 16:26:43.078 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE pg_default;
2024-04-23 16:26:43.078 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2024-04-23 16:26:43.078 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE pg_default) PARTITION BY LIST (a);
2024-04-23 16:26:43.079 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2024-04-23 16:26:43.079 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE regress_tblspace;
2024-04-23 16:26:43.079 UTC client backend[21376] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2024-04-23 16:26:43.079 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE regress_tblspace) PARTITION BY LIST (a);
2024-04-23 16:26:43.374 UTC client backend[21376] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2024-04-23 16:26:43.374 UTC client backend[21376] pg_regress/tablespace STATEMENT:  ALTER INDEX testschema.part_a_idx SET TABLESPACE pg_global;
2024-04-23 16:26:43.376 UTC client backend[21376] pg_regress/tablespace ERROR:  duplicate key value violates unique constraint "anindex"
2024-04-23 16:26:43.376 UTC client backend[21376] pg_regress/tablespace DETAIL:  Key (column1)=(1) already exists.
2024-04-23 16:26:43.376 UTC client backend[21376] pg_regress/tablespace STATEMENT:  INSERT INTO testschema.atable VALUES(1);
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace ERROR:  directory "/no/such/location" does not exist
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_badspace LOCATION '/no/such/location';
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace ERROR:  tablespace "regress_nosuchspace" does not exist
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE bar (i int) TABLESPACE regress_nosuchspace;
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace ERROR:  tablespace "regress_tblspace" cannot be dropped because some objects depend on it
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace DETAIL:  tablespace for index testschema.part_a_idx
2024-04-23 16:26:43.382 UTC client backend[21376] pg_regress/tablespace STATEMENT:  DROP TABLESPACE regress_tblspace;
2024-04-23 16:26:43.382 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:43.516 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 1001 buffers (6.1%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.118 s, sync=0.001 s, total=0.134 s; sync files=0, longest=0.000 s, average=0.000 s; distance=7884 kB, estimate=38218 kB; lsn=0/737F638, redo lsn=0/737F5E0
2024-04-23 16:26:43.520 UTC client backend[21376] pg_regress/tablespace ERROR:  tablespace "regress_tblspace" is not empty
2024-04-23 16:26:43.520 UTC client backend[21376] pg_regress/tablespace STATEMENT:  DROP TABLESPACE regress_tblspace;
2024-04-23 16:26:43.600 UTC client backend[21376] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2024-04-23 16:26:43.600 UTC client backend[21376] pg_regress/tablespace STATEMENT:  CREATE TABLE tablespace_table (i int) TABLESPACE regress_tblspace;
2024-04-23 16:26:43.601 UTC client backend[21376] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2024-04-23 16:26:43.601 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE tablespace_table;
2024-04-23 16:26:43.601 UTC client backend[21376] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2024-04-23 16:26:43.601 UTC client backend[21376] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace, CONCURRENTLY) TABLE tablespace_table;
2024-04-23 16:26:43.611 UTC checkpointer[17545] LOG:  checkpoint starting: immediate force wait
2024-04-23 16:26:43.613 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 41 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=320 kB, estimate=34428 kB; lsn=0/73CF8E0, redo lsn=0/73CF888
2024-04-23 16:26:43.645 UTC postmaster[7550] LOG:  received fast shutdown request
2024-04-23 16:26:43.645 UTC postmaster[7550] LOG:  aborting any active transactions
2024-04-23 16:26:43.646 UTC postmaster[7550] LOG:  background worker "logical replication launcher" (PID 19387) exited with exit code 1
2024-04-23 16:26:43.646 UTC checkpointer[17545] LOG:  shutting down
2024-04-23 16:26:43.646 UTC checkpointer[17545] LOG:  checkpoint starting: shutdown immediate
2024-04-23 16:26:43.705 UTC checkpointer[17545] LOG:  checkpoint complete: wrote 26 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.059 s; sync files=0, longest=0.000 s, average=0.000 s; distance=115 kB, estimate=30997 kB; lsn=0/73EC728, redo lsn=0/73EC728
2024-04-23 16:26:43.760 UTC postmaster[7550] LOG:  database system is shut down