2024-05-05 02:19:46.973 UTC postmaster[19619] LOG: starting PostgreSQL 17devel on x86_64-linux, compiled by gcc-10.2.1, 64-bit 2024-05-05 02:19:46.974 UTC postmaster[19619] LOG: listening on Unix socket "/tmp/pg_regress-XUBfqB/.s.PGSQL.40051" 2024-05-05 02:19:46.986 UTC startup[19623] LOG: database system was shut down at 2024-05-05 02:19:46 UTC 2024-05-05 02:19:46.989 UTC postmaster[19619] LOG: database system is ready to accept connections 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "34.5" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('34.5'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: value "100000" is out of range for type smallint at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('100000'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "asdf" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('asdf'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: " " at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (' '); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "- 1234" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('- 1234'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "4 444" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('4 444'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "123 dt" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('123 dt'); 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "" at character 34 2024-05-05 02:19:47.548 UTC client backend[19809] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (''); 2024-05-05 02:19:47.552 UTC client backend[19809] pg_regress/int2 ERROR: table "f" has 1 columns available but 2 columns specified 2024-05-05 02:19:47.552 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT * FROM INT2_TBL AS f(a, b); 2024-05-05 02:19:47.552 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "test" at character 13 2024-05-05 02:19:47.552 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'test' AS error; 2024-05-05 02:19:47.553 UTC client backend[19809] pg_regress/int2 ERROR: table "s" has 1 columns available but 2 columns specified 2024-05-05 02:19:47.553 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT * FROM (TABLE int2_tbl) AS s (a, b); 2024-05-05 02:19:47.553 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "foo" at character 13 2024-05-05 02:19:47.553 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'foo' AS error; 2024-05-05 02:19:47.554 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "yeah" at character 13 2024-05-05 02:19:47.554 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'yeah' AS error; 2024-05-05 02:19:47.557 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "nay" at character 13 2024-05-05 02:19:47.557 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'nay' AS error; 2024-05-05 02:19:47.560 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "o" at character 13 2024-05-05 02:19:47.560 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'o' AS error; 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "on_" at character 13 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'on_' AS error; 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "off_" at character 13 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool 'off_' AS error; 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "11" at character 13 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool '11' AS error; 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "000" at character 13 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool '000' AS error; 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" at character 13 2024-05-05 02:19:47.565 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT bool '' AS error; 2024-05-05 02:19:47.572 UTC client backend[19814] pg_regress/bit ERROR: bit string length 2 does not match type bit(11) 2024-05-05 02:19:47.572 UTC client backend[19814] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'10'); 2024-05-05 02:19:47.572 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38 2024-05-05 02:19:47.572 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F'); 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}'); 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "G/0" at character 32 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('G/0'); 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111'); 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "-1/0" at character 32 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('-1/0'); 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 '); 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: " 0/12345678" at character 32 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES (' 0/12345678'); 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111'); 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "ABCD/" at character 32 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('ABCD/'); 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38 2024-05-05 02:19:47.573 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111'); 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "/ABCD" at character 32 2024-05-05 02:19:47.573 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('/ABCD'); 2024-05-05 02:19:47.575 UTC client backend[19814] pg_regress/bit ERROR: bit string length 12 does not match type bit(11) 2024-05-05 02:19:47.575 UTC client backend[19814] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'101011111010'); 2024-05-05 02:19:47.577 UTC client backend[19809] pg_regress/int2 ERROR: smallint out of range 2024-05-05 02:19:47.577 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i; 2024-05-05 02:19:47.580 UTC client backend[19809] pg_regress/int2 ERROR: smallint out of range 2024-05-05 02:19:47.580 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i; 2024-05-05 02:19:47.581 UTC client backend[19808] pg_regress/varchar ERROR: value too long for type character varying(1) 2024-05-05 02:19:47.581 UTC client backend[19808] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('cd'); 2024-05-05 02:19:47.583 UTC client backend[19814] pg_regress/bit ERROR: bit string too long for type bit varying(11) 2024-05-05 02:19:47.583 UTC client backend[19814] pg_regress/bit STATEMENT: INSERT INTO VARBIT_TABLE VALUES (B'101011111010'); 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT b' 0'; 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT b'0 '; 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT x' 0'; 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2024-05-05 02:19:47.584 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT x'0 '; 2024-05-05 02:19:47.591 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "34.5" at character 34 2024-05-05 02:19:47.591 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('34.5'); 2024-05-05 02:19:47.591 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: " tru e " 2024-05-05 02:19:47.591 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT ' tru e '::text::boolean AS invalid; 2024-05-05 02:19:47.591 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" 2024-05-05 02:19:47.591 UTC client backend[19810] pg_regress/boolean STATEMENT: SELECT ''::text::boolean AS invalid; 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: value "1000000000000" is out of range for type integer at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('1000000000000'); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "asdf" at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('asdf'); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: " " at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' '); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: " asdf " at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' asdf '); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "- 1234" at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('- 1234'); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "123 5" at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('123 5'); 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "" at character 34 2024-05-05 02:19:47.592 UTC client backend[19819] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (''); 2024-05-05 02:19:47.595 UTC client backend[19809] pg_regress/int2 ERROR: smallint out of range 2024-05-05 02:19:47.595 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i; 2024-05-05 02:19:47.597 UTC client backend[19809] pg_regress/int2 ERROR: smallint out of range 2024-05-05 02:19:47.597 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 * (-1)::int2; 2024-05-05 02:19:47.597 UTC client backend[19809] pg_regress/int2 ERROR: smallint out of range 2024-05-05 02:19:47.597 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 / (-1)::int2; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0b" at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0b'; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0o" at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0o'; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0x" at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0x'; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: value "0b1000000000000000" is out of range for type smallint at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0b1000000000000000'; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: value "0o100000" is out of range for type smallint at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0o100000'; 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: value "0x8000" is out of range for type smallint at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '0x8000'; 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: "" at character 33 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (''); 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: " " at character 33 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' '); 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: value "-0b1000000000000001" is out of range for type smallint at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '-0b1000000000000001'; 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: "asdfasd" at character 33 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('asdfasd'); 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: "99asdfasd" at character 33 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('99asdfasd'); 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 ERROR: value "-0o100001" is out of range for type smallint at character 13 2024-05-05 02:19:47.598 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '-0o100001'; 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: "5 d" at character 33 2024-05-05 02:19:47.598 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 d'); 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: " 5d" at character 33 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' 5d'); 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: "5 5" at character 33 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 5'); 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 ERROR: value "-0x8001" is out of range for type smallint at character 13 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '-0x8001'; 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid ERROR: invalid input syntax for type oid: " - 500" at character 33 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' - 500'); 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid ERROR: value "32958209582039852935" is out of range for type oid at character 33 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935'); 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid ERROR: value "-23582358720398502385" is out of range for type oid at character 33 2024-05-05 02:19:47.599 UTC client backend[19815] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385'); 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "_100" at character 13 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '_100'; 2024-05-05 02:19:47.599 UTC client backend[19818] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 8 2024-05-05 02:19:47.599 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '10e400'::float8; 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "100_" at character 13 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '100_'; 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 ERROR: invalid input syntax for type smallint: "10__000" at character 13 2024-05-05 02:19:47.599 UTC client backend[19809] pg_regress/int2 STATEMENT: SELECT int2 '10__000'; 2024-05-05 02:19:47.599 UTC client backend[19818] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 8 2024-05-05 02:19:47.599 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '-10e400'::float8; 2024-05-05 02:19:47.600 UTC client backend[19818] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 8 2024-05-05 02:19:47.600 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '10e-400'::float8; 2024-05-05 02:19:47.600 UTC client backend[19818] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 8 2024-05-05 02:19:47.600 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '-10e-400'::float8; 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "" at character 36 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (''); 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: " " at character 36 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' '); 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "xyz" at character 36 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz'); 2024-05-05 02:19:47.603 UTC client backend[19808] pg_regress/varchar ERROR: value too long for type character varying(4) 2024-05-05 02:19:47.603 UTC client backend[19808] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde'); 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5.0.0" at character 36 2024-05-05 02:19:47.603 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0'); 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5 . 0" at character 36 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0'); 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5. 0" at character 36 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5. 0'); 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: " - 3" at character 36 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' - 3'); 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "123 5" at character 36 2024-05-05 02:19:47.604 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('123 5'); 2024-05-05 02:19:47.605 UTC client backend[19811] pg_regress/uuid ERROR: duplicate key value violates unique constraint "guid1_unique_btree" 2024-05-05 02:19:47.605 UTC client backend[19811] pg_regress/uuid DETAIL: Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists. 2024-05-05 02:19:47.605 UTC client backend[19811] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111'); 2024-05-05 02:19:47.607 UTC client backend[19812] pg_regress/pg_lsn ERROR: pg_lsn out of range 2024-05-05 02:19:47.607 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric; 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "N A N" at character 8 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT 'N A N'::float8; 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: "NaN x" at character 8 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT 'NaN x'::float8; 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 ERROR: invalid input syntax for type double precision: " INFINITY x" at character 8 2024-05-05 02:19:47.609 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT ' INFINITY x'::float8; 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn ERROR: pg_lsn out of range 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: SELECT '0/1'::pg_lsn - 2::numeric; 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn ERROR: cannot add NaN to pg_lsn 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric; 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn ERROR: cannot subtract NaN from pg_lsn 2024-05-05 02:19:47.611 UTC client backend[19812] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric; 2024-05-05 02:19:47.616 UTC client backend[19810] pg_regress/boolean ERROR: invalid input syntax for type boolean: "XXX" at character 43 2024-05-05 02:19:47.616 UTC client backend[19810] pg_regress/boolean STATEMENT: INSERT INTO BOOLTBL2 (f1) VALUES (bool 'XXX'); 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: " " at character 34 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' '); 2024-05-05 02:19:47.617 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.617 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "xxx" at character 34 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('xxx'); 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 ERROR: value "3908203590239580293850293850329485" is out of range for type bigint at character 34 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485'); 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 ERROR: value "-1204982019841029840928340329840934" is out of range for type bigint at character 34 2024-05-05 02:19:47.617 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934'); 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "- 123" at character 34 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('- 123'); 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: " 345 5" at character 34 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' 345 5'); 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "" at character 34 2024-05-05 02:19:47.618 UTC client backend[19825] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (''); 2024-05-05 02:19:47.618 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.618 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.622 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "" at character 8 2024-05-05 02:19:47.622 UTC client backend[19820] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2024-05-05 02:19:47.622 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select ''::textrange; 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "-[a,z)" at character 8 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '-[a,z)'::textrange; 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "[a,z) - " at character 8 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2024-05-05 02:19:47.623 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '[a,z) - '::textrange; 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(",a)" at character 8 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes DETAIL: Unexpected end of input. 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(",a)'::textrange; 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(,,a)" at character 8 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes DETAIL: Too many commas. 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(,,a)'::textrange; 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(),a)" at character 8 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(),a)'::textrange; 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(a,))" at character 8 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(a,))'::textrange; 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(],a)" at character 8 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2024-05-05 02:19:47.624 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(],a)'::textrange; 2024-05-05 02:19:47.625 UTC client backend[19820] pg_regress/rangetypes ERROR: malformed range literal: "(a,])" at character 8 2024-05-05 02:19:47.625 UTC client backend[19820] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2024-05-05 02:19:47.625 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '(a,])'::textrange; 2024-05-05 02:19:47.625 UTC client backend[19820] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2024-05-05 02:19:47.625 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '[z,a]'::textrange; 2024-05-05 02:19:47.625 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.625 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.626 UTC client backend[19830] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2024-05-05 02:19:47.626 UTC client backend[19830] pg_regress/txid STATEMENT: select '31:12:'::txid_snapshot; 2024-05-05 02:19:47.626 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.626 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.627 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.627 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.627 UTC client backend[19830] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2024-05-05 02:19:47.627 UTC client backend[19830] pg_regress/txid STATEMENT: select '0:1:'::txid_snapshot; 2024-05-05 02:19:47.628 UTC client backend[19830] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2024-05-05 02:19:47.628 UTC client backend[19830] pg_regress/txid STATEMENT: select '12:13:0'::txid_snapshot; 2024-05-05 02:19:47.628 UTC client backend[19830] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2024-05-05 02:19:47.628 UTC client backend[19830] pg_regress/txid STATEMENT: select '12:16:14,13'::txid_snapshot; 2024-05-05 02:19:47.629 UTC client backend[19827] pg_regress/text ERROR: function length(integer) does not exist at character 8 2024-05-05 02:19:47.629 UTC client backend[19827] pg_regress/text HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:47.629 UTC client backend[19827] pg_regress/text STATEMENT: select length(42); 2024-05-05 02:19:47.629 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.629 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i; 2024-05-05 02:19:47.635 UTC client backend[19827] pg_regress/text ERROR: operator does not exist: integer || numeric at character 10 2024-05-05 02:19:47.635 UTC client backend[19827] pg_regress/text HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:47.635 UTC client backend[19827] pg_regress/text STATEMENT: select 3 || 4.0; 2024-05-05 02:19:47.635 UTC client backend[19824] pg_regress/enum ERROR: invalid input value for enum rainbow: "mauve" at character 8 2024-05-05 02:19:47.635 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT 'mauve'::rainbow; 2024-05-05 02:19:47.637 UTC client backend[19829] pg_regress/float4 ERROR: "10e70" is out of range for type real at character 36 2024-05-05 02:19:47.637 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'); 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 ERROR: "-10e70" is out of range for type real at character 36 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'); 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 ERROR: "10e-70" is out of range for type real at character 36 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'); 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 ERROR: "-10e-70" is out of range for type real at character 36 2024-05-05 02:19:47.639 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'); 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 ERROR: value out of range: overflow 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8); 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 ERROR: value out of range: overflow 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8); 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 ERROR: value out of range: underflow 2024-05-05 02:19:47.640 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8); 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 ERROR: value out of range: underflow 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8); 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 ERROR: "10e400" is out of range for type real at character 36 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400'); 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 ERROR: "-10e400" is out of range for type real at character 36 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400'); 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 ERROR: "10e-400" is out of range for type real at character 36 2024-05-05 02:19:47.641 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400'); 2024-05-05 02:19:47.642 UTC client backend[19822] pg_regress/char ERROR: value too long for type character(1) 2024-05-05 02:19:47.642 UTC client backend[19822] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('cd'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: "-10e-400" is out of range for type real at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (''); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: " " at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' '); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "xyz" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "5.0.0" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "5 . 0" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "5. 0" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5. 0'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: " - 3.0" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' - 3.0'); 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "123 5" at character 36 2024-05-05 02:19:47.643 UTC client backend[19829] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('123 5'); 2024-05-05 02:19:47.645 UTC client backend[19813] pg_regress/money ERROR: value "123456789012345678" is out of range for type money at character 8 2024-05-05 02:19:47.645 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '123456789012345678'::money; 2024-05-05 02:19:47.646 UTC client backend[19813] pg_regress/money ERROR: value "9223372036854775807" is out of range for type money at character 8 2024-05-05 02:19:47.646 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '9223372036854775807'::money; 2024-05-05 02:19:47.650 UTC client backend[19813] pg_regress/money ERROR: value "-123456789012345678" is out of range for type money at character 8 2024-05-05 02:19:47.650 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '-123456789012345678'::money; 2024-05-05 02:19:47.650 UTC client backend[19813] pg_regress/money ERROR: value "-9223372036854775808" is out of range for type money at character 8 2024-05-05 02:19:47.650 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '-9223372036854775808'::money; 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int4; 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int4; 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int2; 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.654 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int2; 2024-05-05 02:19:47.657 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.657 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, 0::int4); 2024-05-05 02:19:47.657 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.657 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, (-2147483648)::int4); 2024-05-05 02:19:47.657 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "N A N" at character 8 2024-05-05 02:19:47.657 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT 'N A N'::float4; 2024-05-05 02:19:47.658 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: "NaN x" at character 8 2024-05-05 02:19:47.658 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT 'NaN x'::float4; 2024-05-05 02:19:47.658 UTC client backend[19829] pg_regress/float4 ERROR: invalid input syntax for type real: " INFINITY x" at character 8 2024-05-05 02:19:47.658 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT ' INFINITY x'::float4; 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money ERROR: value "-92233720368547758.09" is out of range for type money at character 8 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '-92233720368547758.09'::money; 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money ERROR: value "92233720368547758.08" is out of range for type money at character 8 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '92233720368547758.08'::money; 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money ERROR: value "-92233720368547758.085" is out of range for type money at character 8 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '-92233720368547758.085'::money; 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money ERROR: value "92233720368547758.075" is out of range for type money at character 8 2024-05-05 02:19:47.659 UTC client backend[19813] pg_regress/money STATEMENT: SELECT '92233720368547758.075'::money; 2024-05-05 02:19:47.659 UTC client backend[19822] pg_regress/char ERROR: value too long for type character(4) 2024-05-05 02:19:47.659 UTC client backend[19822] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('abcde'); 2024-05-05 02:19:47.661 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.661 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT lcm((-2147483648)::int4, 1::int4); 2024-05-05 02:19:47.661 UTC client backend[19819] pg_regress/int4 ERROR: integer out of range 2024-05-05 02:19:47.661 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT lcm(2147483647::int4, 2147483646::int4); 2024-05-05 02:19:47.663 UTC client backend[19818] pg_regress/float8 ERROR: zero raised to a negative power is undefined 2024-05-05 02:19:47.663 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT power(float8 '0', float8 '-inf'); 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "0b" at character 13 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0b'; 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "0o" at character 13 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0o'; 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "0x" at character 13 2024-05-05 02:19:47.663 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0x'; 2024-05-05 02:19:47.664 UTC client backend[19819] pg_regress/int4 ERROR: value "0b10000000000000000000000000000000" is out of range for type integer at character 13 2024-05-05 02:19:47.664 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0b10000000000000000000000000000000'; 2024-05-05 02:19:47.665 UTC client backend[19819] pg_regress/int4 ERROR: value "0o20000000000" is out of range for type integer at character 13 2024-05-05 02:19:47.665 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0o20000000000'; 2024-05-05 02:19:47.665 UTC client backend[19819] pg_regress/int4 ERROR: value "0x80000000" is out of range for type integer at character 13 2024-05-05 02:19:47.665 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '0x80000000'; 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 ERROR: value "-0b10000000000000000000000000000001" is out of range for type integer at character 13 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '-0b10000000000000000000000000000001'; 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 ERROR: value "-0o20000000001" is out of range for type integer at character 13 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '-0o20000000001'; 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 ERROR: value "-0x80000001" is out of range for type integer at character 13 2024-05-05 02:19:47.666 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '-0x80000001'; 2024-05-05 02:19:47.667 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.667 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL; 2024-05-05 02:19:47.667 UTC client backend[19821] pg_regress/regproc ERROR: operator does not exist: ||// at character 16 2024-05-05 02:19:47.667 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regoper('||//'); 2024-05-05 02:19:47.667 UTC client backend[19821] pg_regress/regproc ERROR: operator does not exist: ++(int4,int4) at character 20 2024-05-05 02:19:47.667 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regoperator('++(int4,int4)'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: function "know" does not exist at character 16 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regproc('know'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: function "absinthe(numeric)" does not exist at character 21 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regprocedure('absinthe(numeric)'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: relation "pg_classes" does not exist at character 17 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regclass('pg_classes'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: type "int3" does not exist at character 16 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regtype('int3'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: operator does not exist: ng_catalog.||/ at character 16 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regoper('ng_catalog.||/'); 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc ERROR: operator does not exist: ng_catalog.+(int4,int4) at character 20 2024-05-05 02:19:47.668 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regoperator('ng_catalog.+(int4,int4)'); 2024-05-05 02:19:47.668 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "_100" at character 13 2024-05-05 02:19:47.668 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '_100'; 2024-05-05 02:19:47.668 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "100_" at character 13 2024-05-05 02:19:47.668 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '100_'; 2024-05-05 02:19:47.669 UTC client backend[19819] pg_regress/int4 ERROR: invalid input syntax for type integer: "100__000" at character 13 2024-05-05 02:19:47.669 UTC client backend[19819] pg_regress/int4 STATEMENT: SELECT int4 '100__000'; 2024-05-05 02:19:47.672 UTC client backend[19830] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22 2024-05-05 02:19:47.672 UTC client backend[19830] pg_regress/txid STATEMENT: SELECT txid_snapshot '1:9223372036854775808:3'; 2024-05-05 02:19:47.674 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "foo.boo[]" 2024-05-05 02:19:47.674 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('foo.boo[]'); 2024-05-05 02:19:47.675 UTC client backend[19827] pg_regress/text ERROR: VARIADIC argument must be an array at character 32 2024-05-05 02:19:47.675 UTC client backend[19827] pg_regress/text STATEMENT: select concat_ws(',', variadic 10); 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text ERROR: too few arguments for format() 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text STATEMENT: select format('Hello %s %s', 'World'); 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text ERROR: too few arguments for format() 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text STATEMENT: select format('Hello %s'); 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text ERROR: unrecognized format() type specifier "x" 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text HINT: For a single "%" use "%%". 2024-05-05 02:19:47.676 UTC client backend[19827] pg_regress/text STATEMENT: select format('Hello %x', 20); 2024-05-05 02:19:47.676 UTC client backend[19818] pg_regress/float8 ERROR: a negative number raised to a non-integer power yields a complex result 2024-05-05 02:19:47.676 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT power(float8 '-inf', float8 '3.5'); 2024-05-05 02:19:47.677 UTC client backend[19827] pg_regress/text ERROR: null values cannot be formatted as an SQL identifier 2024-05-05 02:19:47.677 UTC client backend[19827] pg_regress/text STATEMENT: select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello'); 2024-05-05 02:19:47.677 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: " " 2024-05-05 02:19:47.677 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident(' '); 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: " .aaa" 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name DETAIL: No valid identifier before ".". 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident(' .aaa'); 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: " aaa . " 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name DETAIL: No valid identifier after ".". 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident(' aaa . '); 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "aaa.a%b" 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('aaa.a%b'); 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" 2024-05-05 02:19:47.678 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'); 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: ""c".X XXXXXXXXXX" 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident(E'"c".X XXXX\002XXXXXX'); 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "1020" 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('1020'); 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "10.20" 2024-05-05 02:19:47.679 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('10.20'); 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum ERROR: invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto" 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum DETAIL: Labels must be 63 bytes or less. 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto'; 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum ERROR: "zeus" is not an existing enum label 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus'; 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum ERROR: enum label "mercury" already exists 2024-05-05 02:19:47.680 UTC client backend[19824] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'mercury'; 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "." 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name DETAIL: No valid identifier before ".". 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('.'); 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: ".1020" 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name DETAIL: No valid identifier before ".". 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('.1020'); 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name ERROR: string is not a valid identifier: "xxx.1020" 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name DETAIL: No valid identifier after ".". 2024-05-05 02:19:47.680 UTC client backend[19823] pg_regress/name STATEMENT: SELECT parse_ident('xxx.1020'); 2024-05-05 02:19:47.682 UTC client backend[19829] pg_regress/float4 ERROR: division by zero 2024-05-05 02:19:47.682 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT f.f1 / '0.0' from FLOAT4_TBL f; 2024-05-05 02:19:47.686 UTC client backend[19829] pg_regress/float4 ERROR: smallint out of range 2024-05-05 02:19:47.686 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '32767.6'::float4::int2; 2024-05-05 02:19:47.687 UTC client backend[19829] pg_regress/float4 ERROR: smallint out of range 2024-05-05 02:19:47.687 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '-32768.6'::float4::int2; 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: function "ng_catalog.now" does not exist at character 16 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regproc('ng_catalog.now'); 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: function "ng_catalog.abs(numeric)" does not exist at character 21 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regprocedure('ng_catalog.abs(numeric)'); 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: relation "ng_catalog.pg_class" does not exist at character 17 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regclass('ng_catalog.pg_class'); 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: schema "ng_catalog" does not exist at character 16 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regtype('ng_catalog.int4'); 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regcollation('ng_catalog."POSIX"'); 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2024-05-05 02:19:47.688 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regrole('regress_regrole_test'); 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regrole('"regress_regrole_test"'); 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc ERROR: role "nonexistent" does not exist at character 16 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regrole('Nonexistent'); 2024-05-05 02:19:47.689 UTC client backend[19829] pg_regress/float4 ERROR: integer out of range 2024-05-05 02:19:47.689 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '2147483647'::float4::int4; 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc ERROR: role "Nonexistent" does not exist at character 16 2024-05-05 02:19:47.689 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regrole('"Nonexistent"'); 2024-05-05 02:19:47.689 UTC client backend[19829] pg_regress/float4 ERROR: integer out of range 2024-05-05 02:19:47.689 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '-2147483900'::float4::int4; 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc ERROR: invalid name syntax at character 16 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regrole('foo.bar'); 2024-05-05 02:19:47.690 UTC client backend[19829] pg_regress/float4 ERROR: bigint out of range 2024-05-05 02:19:47.690 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '9223372036854775807'::float4::int8; 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc ERROR: schema "nonexistent" does not exist at character 21 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regnamespace('Nonexistent'); 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc ERROR: schema "Nonexistent" does not exist at character 21 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regnamespace('"Nonexistent"'); 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc ERROR: invalid name syntax at character 21 2024-05-05 02:19:47.690 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT regnamespace('foo.bar'); 2024-05-05 02:19:47.690 UTC client backend[19829] pg_regress/float4 ERROR: bigint out of range 2024-05-05 02:19:47.690 UTC client backend[19829] pg_regress/float4 STATEMENT: SELECT '-9223380000000000000'::float4::int8; 2024-05-05 02:19:47.691 UTC client backend[19818] pg_regress/float8 ERROR: value out of range: overflow 2024-05-05 02:19:47.691 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT f.f1 * '1e200' from FLOAT8_TBL f; 2024-05-05 02:19:47.691 UTC client backend[19818] pg_regress/float8 ERROR: value out of range: overflow 2024-05-05 02:19:47.691 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT f.f1 ^ '1e200' from FLOAT8_TBL f; 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 ERROR: cannot take logarithm of zero 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ; 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ; 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 ERROR: value out of range: underflow 2024-05-05 02:19:47.692 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT exp(f.f1) from FLOAT8_TBL f; 2024-05-05 02:19:47.693 UTC client backend[19818] pg_regress/float8 ERROR: division by zero 2024-05-05 02:19:47.693 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT f.f1 / '0.0' from FLOAT8_TBL f; 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text ERROR: too few arguments for format() 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text STATEMENT: select format('%1$s %4$s', 1, 2, 3); 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text ERROR: too few arguments for format() 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text STATEMENT: select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12); 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2024-05-05 02:19:47.694 UTC client backend[19827] pg_regress/text STATEMENT: select format('%0$s', 'Hello'); 2024-05-05 02:19:47.695 UTC client backend[19827] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2024-05-05 02:19:47.695 UTC client backend[19827] pg_regress/text STATEMENT: select format('%*0$s', 'Hello'); 2024-05-05 02:19:47.695 UTC client backend[19827] pg_regress/text ERROR: unterminated format() type specifier 2024-05-05 02:19:47.695 UTC client backend[19827] pg_regress/text HINT: For a single "%" use "%%". 2024-05-05 02:19:47.695 UTC client backend[19827] pg_regress/text STATEMENT: select format('%1$', 1); 2024-05-05 02:19:47.696 UTC client backend[19827] pg_regress/text ERROR: unterminated format() type specifier 2024-05-05 02:19:47.696 UTC client backend[19827] pg_regress/text HINT: For a single "%" use "%%". 2024-05-05 02:19:47.696 UTC client backend[19827] pg_regress/text STATEMENT: select format('%1$1', 1); 2024-05-05 02:19:47.700 UTC client backend[19818] pg_regress/float8 ERROR: input is out of range 2024-05-05 02:19:47.700 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT acosh(float8 '-infinity'); 2024-05-05 02:19:47.700 UTC client backend[19818] pg_regress/float8 ERROR: input is out of range 2024-05-05 02:19:47.700 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT atanh(float8 'infinity'); 2024-05-05 02:19:47.701 UTC client backend[19818] pg_regress/float8 ERROR: input is out of range 2024-05-05 02:19:47.701 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT atanh(float8 '-infinity'); 2024-05-05 02:19:47.703 UTC client backend[19825] pg_regress/int8 ERROR: value "-9223372036854775809" is out of range for type bigint at character 8 2024-05-05 02:19:47.703 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775809'::int8; 2024-05-05 02:19:47.703 UTC client backend[19825] pg_regress/int8 ERROR: value "9223372036854775808" is out of range for type bigint at character 8 2024-05-05 02:19:47.703 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775808'::int8; 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 36 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400'); 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 36 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400'); 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 36 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400'); 2024-05-05 02:19:47.704 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.704 UTC client backend[19825] pg_regress/int8 STATEMENT: select -('-9223372036854775808'::int8); 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 36 2024-05-05 02:19:47.704 UTC client backend[19818] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400'); 2024-05-05 02:19:47.704 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.704 UTC client backend[19825] pg_regress/int8 STATEMENT: select 0::int8 - '-9223372036854775808'::int8; 2024-05-05 02:19:47.709 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.709 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '9223372036854775800'::int8; 2024-05-05 02:19:47.710 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.710 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 - '-9223372036854775800'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '9223372036854775800'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '9223372036854775800'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: division by zero 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 / '0'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: division by zero 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 % '0'::int8; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select abs('-9223372036854775808'::int8); 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int4; 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.711 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int4; 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int4; 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 STATEMENT: select '100'::int4 + '9223372036854775800'::int8; 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-100'::int4 - '9223372036854775800'::int8; 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.714 UTC client backend[19825] pg_regress/int8 STATEMENT: select '100'::int4 * '9223372036854775800'::int8; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int2; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int2; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int2; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: division by zero 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-9223372036854775808'::int8 / '0'::int2; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '100'::int2 + '9223372036854775800'::int8; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '-100'::int2 - '9223372036854775800'::int8; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '100'::int2 * '9223372036854775800'::int8; 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 ERROR: division by zero 2024-05-05 02:19:47.715 UTC client backend[19825] pg_regress/int8 STATEMENT: select '100'::int2 / '0'::int8; 2024-05-05 02:19:47.716 UTC client backend[19825] pg_regress/int8 ERROR: integer out of range 2024-05-05 02:19:47.716 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456; 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 ERROR: smallint out of range 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '32767.6'::float8::int2; 2024-05-05 02:19:47.717 UTC client backend[19825] pg_regress/int8 ERROR: smallint out of range 2024-05-05 02:19:47.717 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456; 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 ERROR: smallint out of range 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '-32768.6'::float8::int2; 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 ERROR: integer out of range 2024-05-05 02:19:47.717 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '2147483647.6'::float8::int4; 2024-05-05 02:19:47.718 UTC client backend[19818] pg_regress/float8 ERROR: integer out of range 2024-05-05 02:19:47.718 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '-2147483648.6'::float8::int4; 2024-05-05 02:19:47.718 UTC client backend[19818] pg_regress/float8 ERROR: bigint out of range 2024-05-05 02:19:47.718 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '9223372036854775807'::float8::int8; 2024-05-05 02:19:47.719 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.719 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT CAST('922337203685477580700.0'::float8 AS int8); 2024-05-05 02:19:47.719 UTC client backend[19825] pg_regress/int8 ERROR: OID out of range 2024-05-05 02:19:47.719 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS oid) FROM INT8_TBL; 2024-05-05 02:19:47.719 UTC client backend[19818] pg_regress/float8 ERROR: bigint out of range 2024-05-05 02:19:47.719 UTC client backend[19818] pg_regress/float8 STATEMENT: SELECT '-9223372036854780000'::float8::int8; 2024-05-05 02:19:47.725 UTC client backend[19825] pg_regress/int8 ERROR: step size cannot equal zero 2024-05-05 02:19:47.725 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0); 2024-05-05 02:19:47.726 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.726 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int8; 2024-05-05 02:19:47.726 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.726 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int8; 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int4; 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int4; 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.727 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int2; 2024-05-05 02:19:47.733 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.733 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int2; 2024-05-05 02:19:47.736 UTC client backend[19821] pg_regress/regproc ERROR: syntax error at or near "type" at character 11 2024-05-05 02:19:47.736 UTC client backend[19821] pg_regress/regproc CONTEXT: invalid type name "incorrect type name syntax" 2024-05-05 02:19:47.736 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype'); 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc ERROR: invalid NUMERIC type modifier 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype'); 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc ERROR: improper qualified name (too many dotted names): way.too.many.names 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype'); 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc ERROR: cross-database references are not implemented: no_such_catalog.schema.name 2024-05-05 02:19:47.737 UTC client backend[19821] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype'); 2024-05-05 02:19:47.741 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.741 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, 0::int8); 2024-05-05 02:19:47.741 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.741 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8); 2024-05-05 02:19:47.742 UTC client backend[19820] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:47.742 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select numrange(2.0, 1.0); 2024-05-05 02:19:47.742 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.742 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT lcm((-9223372036854775808)::int8, 1::int8); 2024-05-05 02:19:47.743 UTC client backend[19825] pg_regress/int8 ERROR: bigint out of range 2024-05-05 02:19:47.743 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8); 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0b" at character 13 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0b'; 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0o" at character 13 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0o'; 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0x" at character 13 2024-05-05 02:19:47.744 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0x'; 2024-05-05 02:19:47.745 UTC client backend[19825] pg_regress/int8 ERROR: value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13 2024-05-05 02:19:47.745 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000'; 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 ERROR: value "0o1000000000000000000000" is out of range for type bigint at character 13 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0o1000000000000000000000'; 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 ERROR: value "0x8000000000000000" is out of range for type bigint at character 13 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '0x8000000000000000'; 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 ERROR: value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001'; 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 ERROR: value "-0o1000000000000000000001" is out of range for type bigint at character 13 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '-0o1000000000000000000001'; 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 ERROR: value "-0x8000000000000001" is out of range for type bigint at character 13 2024-05-05 02:19:47.746 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '-0x8000000000000001'; 2024-05-05 02:19:47.747 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "_100" at character 13 2024-05-05 02:19:47.747 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '_100'; 2024-05-05 02:19:47.747 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100_" at character 13 2024-05-05 02:19:47.747 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '100_'; 2024-05-05 02:19:47.749 UTC client backend[19825] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100__000" at character 13 2024-05-05 02:19:47.749 UTC client backend[19825] pg_regress/int8 STATEMENT: SELECT int8 '100__000'; 2024-05-05 02:19:47.758 UTC client backend[19820] pg_regress/rangetypes ERROR: result of range union would not be contiguous 2024-05-05 02:19:47.758 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select numrange(1.0, 2.0) + numrange(2.5, 3.0); 2024-05-05 02:19:47.779 UTC client backend[19824] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2024-05-05 02:19:47.779 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT 'purple'::rgb; 2024-05-05 02:19:47.779 UTC client backend[19824] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2024-05-05 02:19:47.779 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT 'purple'::rainbow::rgb; 2024-05-05 02:19:47.828 UTC client backend[19824] pg_regress/enum ERROR: insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey" 2024-05-05 02:19:47.828 UTC client backend[19824] pg_regress/enum DETAIL: Key (parent)=(blue) is not present in table "enumtest_parent". 2024-05-05 02:19:47.828 UTC client backend[19824] pg_regress/enum STATEMENT: INSERT INTO enumtest_child VALUES ('blue'); 2024-05-05 02:19:47.829 UTC client backend[19824] pg_regress/enum ERROR: update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child" 2024-05-05 02:19:47.829 UTC client backend[19824] pg_regress/enum DETAIL: Key (id)=(red) is still referenced from table "enumtest_child". 2024-05-05 02:19:47.829 UTC client backend[19824] pg_regress/enum STATEMENT: DELETE FROM enumtest_parent; 2024-05-05 02:19:47.837 UTC client backend[19824] pg_regress/enum ERROR: foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented 2024-05-05 02:19:47.837 UTC client backend[19824] pg_regress/enum DETAIL: Key columns "parent" and "id" are of incompatible types: bogus and rainbow. 2024-05-05 02:19:47.837 UTC client backend[19824] pg_regress/enum STATEMENT: CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent); 2024-05-05 02:19:47.847 UTC client backend[19824] pg_regress/enum ERROR: "red" is not an existing enum label 2024-05-05 02:19:47.847 UTC client backend[19824] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson'; 2024-05-05 02:19:47.848 UTC client backend[19824] pg_regress/enum ERROR: enum label "green" already exists 2024-05-05 02:19:47.848 UTC client backend[19824] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green'; 2024-05-05 02:19:47.854 UTC client backend[19824] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus at character 8 2024-05-05 02:19:47.854 UTC client backend[19824] pg_regress/enum HINT: New enum values must be committed before they can be used. 2024-05-05 02:19:47.854 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT 'new'::bogus; 2024-05-05 02:19:47.855 UTC client backend[19824] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2024-05-05 02:19:47.855 UTC client backend[19824] pg_regress/enum HINT: New enum values must be committed before they can be used. 2024-05-05 02:19:47.855 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT enum_last(null::bogus); 2024-05-05 02:19:47.856 UTC client backend[19824] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2024-05-05 02:19:47.856 UTC client backend[19824] pg_regress/enum HINT: New enum values must be committed before they can be used. 2024-05-05 02:19:47.856 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT enum_range(null::bogus); 2024-05-05 02:19:47.867 UTC client backend[19824] pg_regress/enum ERROR: unsafe use of new value "bad" of enum type bogon at character 8 2024-05-05 02:19:47.867 UTC client backend[19824] pg_regress/enum HINT: New enum values must be committed before they can be used. 2024-05-05 02:19:47.867 UTC client backend[19824] pg_regress/enum STATEMENT: SELECT 'bad'::bogon; 2024-05-05 02:19:47.880 UTC client backend[19814] pg_regress/bit ERROR: negative substring length not allowed 2024-05-05 02:19:47.880 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error"; 2024-05-05 02:19:47.880 UTC client backend[19814] pg_regress/bit ERROR: negative substring length not allowed 2024-05-05 02:19:47.880 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error"; 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit ERROR: cannot AND bit strings of different sizes 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit STATEMENT: select B'001' & B'10'; 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit ERROR: cannot OR bit strings of different sizes 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit STATEMENT: select B'0111' | B'011'; 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit ERROR: cannot XOR bit strings of different sizes 2024-05-05 02:19:47.893 UTC client backend[19814] pg_regress/bit STATEMENT: select B'0010' # B'011101'; 2024-05-05 02:19:47.917 UTC client backend[19814] pg_regress/bit ERROR: bit index 16 out of valid range (0..15) 2024-05-05 02:19:47.917 UTC client backend[19814] pg_regress/bit STATEMENT: SELECT set_bit(B'0101011000100100', 16, 1); 2024-05-05 02:19:47.948 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.948 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric / '0'; 2024-05-05 02:19:47.949 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.949 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric / '0'; 2024-05-05 02:19:47.950 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.950 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '0'::numeric / '0'; 2024-05-05 02:19:47.950 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.950 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric % '0'; 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric % '0'; 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '0'::numeric % '0'; 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.951 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT div('inf'::numeric, '0'); 2024-05-05 02:19:47.952 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.952 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT div('-inf'::numeric, '0'); 2024-05-05 02:19:47.952 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:47.952 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT div('0'::numeric, '0'); 2024-05-05 02:19:47.958 UTC client backend[19826] pg_regress/numeric ERROR: cannot take square root of a negative number 2024-05-05 02:19:47.958 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT sqrt('-1'::numeric); 2024-05-05 02:19:47.958 UTC client backend[19826] pg_regress/numeric ERROR: cannot take square root of a negative number 2024-05-05 02:19:47.958 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT sqrt('-inf'::numeric); 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT ln('0'::numeric); 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT ln('-1'::numeric); 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.960 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT ln('-inf'::numeric); 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('0'::numeric, '10'); 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '0'); 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, '10'); 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.996 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '-inf'); 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '0'); 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '-inf'); 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:47.997 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, 'inf'); 2024-05-05 02:19:47.998 UTC client backend[19826] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2024-05-05 02:19:47.998 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-1'); 2024-05-05 02:19:47.998 UTC client backend[19826] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2024-05-05 02:19:47.998 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-inf'); 2024-05-05 02:19:47.999 UTC client backend[19826] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2024-05-05 02:19:47.999 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '3.3'); 2024-05-05 02:19:47.999 UTC client backend[19826] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2024-05-05 02:19:47.999 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '-1.5'); 2024-05-05 02:19:48.000 UTC client backend[19826] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2024-05-05 02:19:48.000 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT power('-inf'::numeric, '4.5'); 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (3, '1.0'); 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2024-05-05 02:19:48.003 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (6, '0.99995'); 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (10, 'Inf'); 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2024-05-05 02:19:48.004 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (11, '-Inf'); 2024-05-05 02:19:48.005 UTC client backend[19826] pg_regress/numeric ERROR: bigint out of range 2024-05-05 02:19:48.005 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT (-9223372036854775808.5)::int8; 2024-05-05 02:19:48.007 UTC client backend[19826] pg_regress/numeric ERROR: bigint out of range 2024-05-05 02:19:48.007 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 9223372036854775807.5::int8; 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric ERROR: integer out of range 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT (-2147483648.5)::int4; 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric ERROR: integer out of range 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 2147483647.5::int4; 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric ERROR: smallint out of range 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT (-32768.5)::int2; 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric ERROR: smallint out of range 2024-05-05 02:19:48.008 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 32767.5::int2; 2024-05-05 02:19:48.010 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert NaN to smallint 2024-05-05 02:19:48.010 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int2; 2024-05-05 02:19:48.010 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to smallint 2024-05-05 02:19:48.010 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int2; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to smallint 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int2; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert NaN to integer 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int4; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to integer 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int4; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to integer 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int4; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert NaN to bigint 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int8; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to bigint 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int8; 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert infinity to bigint 2024-05-05 02:19:48.011 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int8; 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric ERROR: count must be greater than zero 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, 0); 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric ERROR: count must be greater than zero 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, -5); 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5, 3.0, 3.0, 888); 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric ERROR: count must be greater than zero 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0); 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric ERROR: count must be greater than zero 2024-05-05 02:19:48.015 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5); 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888); 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric ERROR: operand, lower bound, and upper bound cannot be NaN 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket('NaN', 3.0, 4.0, 888); 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric ERROR: operand, lower bound, and upper bound cannot be NaN 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888); 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(2.0, 3.0, '-inf', 888); 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.016 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888); 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10); 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20); 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10); 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric ERROR: lower and upper bounds must be finite 2024-05-05 02:19:48.019 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20); 2024-05-05 02:19:48.022 UTC client backend[19826] pg_regress/numeric ERROR: integer out of range 2024-05-05 02:19:48.022 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(1::float8, 0, 1, 2147483647); 2024-05-05 02:19:48.023 UTC client backend[19826] pg_regress/numeric ERROR: integer out of range 2024-05-05 02:19:48.023 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 1, 0, 2147483647); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' '); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: " 1234 %" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' 1234 %'); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "xyz" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('xyz'); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "- 1234" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('- 1234'); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5 . 0" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5 . 0'); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5. 0 " at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5. 0 '); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (''); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: " N aN " at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' N aN '); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+NaN" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+NaN'); 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "-NaN" at character 40 2024-05-05 02:19:48.043 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('-NaN'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+ infinity" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+ infinity'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "_123" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('_123'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "12__34" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('12__34'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_.456" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_.456'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123._456" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123._456'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e_34" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e_34'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e34_" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e34_'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e3__4" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e3__4'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0b1112" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0b1112'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0c1112" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0c1112'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0o12345678" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0o12345678'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1eg" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1eg'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12.34" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12.34'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x__1234" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x__1234'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1234_" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1234_'); 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12__34" at character 40 2024-05-05 02:19:48.044 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12__34'); 2024-05-05 02:19:48.063 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.063 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale -6 cannot hold an infinite value. 2024-05-05 02:19:48.063 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES ('inf'); 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale -6 must round to an absolute value less than 10^9. 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES (999500000); 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale -3 must round to an absolute value less than 10^6. 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousands) VALUES (999500); 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale 0 must round to an absolute value less than 10^3. 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (units) VALUES (999.5); 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale 3 must round to an absolute value less than 1. 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousandths) VALUES (0.9995); 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric ERROR: numeric field overflow 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric DETAIL: A field with precision 3, scale 6 must round to an absolute value less than 10^-3. 2024-05-05 02:19:48.066 UTC client backend[19826] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millionths) VALUES (0.0009995); 2024-05-05 02:19:48.132 UTC client backend[19826] pg_regress/numeric ERROR: value overflows numeric format 2024-05-05 02:19:48.132 UTC client backend[19826] pg_regress/numeric STATEMENT: select 10.0 ^ 2147483647 as overflows; 2024-05-05 02:19:48.132 UTC client backend[19826] pg_regress/numeric ERROR: value overflows numeric format 2024-05-05 02:19:48.132 UTC client backend[19826] pg_regress/numeric STATEMENT: select 117743296169.0 ^ 1000000000 as overflows; 2024-05-05 02:19:48.142 UTC client backend[19826] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2024-05-05 02:19:48.142 UTC client backend[19826] pg_regress/numeric STATEMENT: select 0.0 ^ (-12.34); 2024-05-05 02:19:48.142 UTC client backend[19826] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2024-05-05 02:19:48.142 UTC client backend[19826] pg_regress/numeric STATEMENT: select (-12.34) ^ 1.2; 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: step size cannot equal zero 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 0::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: step size cannot be NaN 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: start value cannot be NaN 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series('nan'::numeric, 100::numeric, 10::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: stop value cannot be NaN 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: start value cannot be infinity 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: stop value cannot be infinity 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric); 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric ERROR: step size cannot be infinity 2024-05-05 02:19:48.148 UTC client backend[19826] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric); 2024-05-05 02:19:48.150 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:48.150 UTC client backend[19826] pg_regress/numeric STATEMENT: select ln(-12.34); 2024-05-05 02:19:48.150 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:48.150 UTC client backend[19826] pg_regress/numeric STATEMENT: select ln(0.0); 2024-05-05 02:19:48.151 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:48.151 UTC client backend[19826] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2024-05-05 02:19:48.151 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(-12.34); 2024-05-05 02:19:48.152 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:48.152 UTC client backend[19826] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2024-05-05 02:19:48.152 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(0.0); 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(-12.34, 56.78); 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(-12.34, -56.78); 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(12.34, -56.78); 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:48.157 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(0.0, 12.34); 2024-05-05 02:19:48.158 UTC client backend[19826] pg_regress/numeric ERROR: cannot take logarithm of zero 2024-05-05 02:19:48.158 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(12.34, 0.0); 2024-05-05 02:19:48.158 UTC client backend[19826] pg_regress/numeric ERROR: division by zero 2024-05-05 02:19:48.158 UTC client backend[19826] pg_regress/numeric STATEMENT: select log(1.0, 12.34); 2024-05-05 02:19:48.230 UTC client backend[19826] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp19826.0", size 1400000 2024-05-05 02:19:48.230 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT SUM(9999::numeric) FROM generate_series(1, 100000); 2024-05-05 02:19:48.278 UTC client backend[19826] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp19826.1", size 1400000 2024-05-05 02:19:48.278 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT SUM((-9999)::numeric) FROM generate_series(1, 100000); 2024-05-05 02:19:48.459 UTC client backend[19820] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_room_during_excl" 2024-05-05 02:19:48.459 UTC client backend[19820] 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-05-05 02:19:48.459 UTC client backend[19820] 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-05-05 02:19:48.460 UTC client backend[19820] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl" 2024-05-05 02:19:48.460 UTC client backend[19820] 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-05-05 02:19:48.460 UTC client backend[19820] 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-05-05 02:19:48.466 UTC client backend[19820] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2024-05-05 02:19:48.466 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange; 2024-05-05 02:19:48.467 UTC client backend[19820] pg_regress/rangetypes ERROR: function float4mi(double precision, double precision) does not exist 2024-05-05 02:19:48.467 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi); 2024-05-05 02:19:48.475 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot drop type mydomain because other objects depend on it 2024-05-05 02:19:48.475 UTC client backend[19820] pg_regress/rangetypes DETAIL: type mydomainrange depends on type mydomain 2024-05-05 02:19:48.475 UTC client backend[19820] pg_regress/rangetypes HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:48.475 UTC client backend[19820] pg_regress/rangetypes STATEMENT: drop domain mydomain; 2024-05-05 02:19:48.481 UTC client backend[19820] pg_regress/rangetypes ERROR: value for domain restrictedrange violates check constraint "restrictedrange_check" 2024-05-05 02:19:48.481 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select '[4,50)'::restrictedrange @> 7; 2024-05-05 02:19:48.484 UTC client backend[19820] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:48.484 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select textrange1('a','Z') @> 'b'::text; 2024-05-05 02:19:48.493 UTC client backend[19820] pg_regress/rangetypes ERROR: function anyarray_anyrange_func(integer[], numrange) does not exist at character 8 2024-05-05 02:19:48.493 UTC client backend[19820] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:48.493 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20)); 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function bogus_func(anyelement) returns anyrange as 'select int4range(1,10)' language sql; 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:48.494 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function bogus_func(int) returns anyrange as 'select int4range(1,10)' language sql; 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes ERROR: function rangetypes_sql(numrange, integer[]) does not exist at character 8 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select rangetypes_sql(numrange(1,10), ARRAY[2,20]); 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes ERROR: function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:48.498 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20)); 2024-05-05 02:19:48.507 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.507 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2024-05-05 02:19:48.507 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2024-05-05 02:19:48.516 UTC client backend[19820] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:48.516 UTC client backend[19820] pg_regress/rangetypes STATEMENT: select arrayrange(ARRAY[2,1], ARRAY[1,2]); 2024-05-05 02:19:48.520 UTC client backend[19820] pg_regress/rangetypes ERROR: composite type two_ints cannot be made a member of itself 2024-05-05 02:19:48.520 UTC client backend[19820] pg_regress/rangetypes STATEMENT: alter type two_ints add attribute c two_ints_range; 2024-05-05 02:19:48.579 UTC client backend[19826] pg_regress/numeric ERROR: value overflows numeric format 2024-05-05 02:19:48.579 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2); 2024-05-05 02:19:48.580 UTC client backend[19826] pg_regress/numeric ERROR: value overflows numeric format 2024-05-05 02:19:48.580 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT factorial(100000); 2024-05-05 02:19:48.580 UTC client backend[19826] pg_regress/numeric ERROR: factorial of a negative number is undefined 2024-05-05 02:19:48.580 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT factorial(-4); 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric ERROR: pg_lsn out of range 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT pg_lsn(-1::numeric); 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric ERROR: pg_lsn out of range 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT pg_lsn(18446744073709551616::numeric); 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric ERROR: cannot convert NaN to pg_lsn 2024-05-05 02:19:48.581 UTC client backend[19826] pg_regress/numeric STATEMENT: SELECT pg_lsn('NaN'::numeric); 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function outparam_fail(i anyelement, out r anyrange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function inoutparam_fail(inout i anyelement, out r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes ERROR: cannot determine result data type 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:48.589 UTC client backend[19820] pg_regress/rangetypes STATEMENT: create function table_fail(i anyelement) returns table(i anyelement, r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2024-05-05 02:19:48.754 UTC client backend[20217] pg_regress/strings ERROR: syntax error at or near "' - third line'" at character 75 2024-05-05 02:19:48.754 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT 'first line' ' - next line' /* this comment is not allowed here */ ' - third line' AS "Illegal comment within continuation"; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape at character 18 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape at character 18 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: UESCAPE must be followed by a simple string literal at or near "+" at character 33 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE +; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape character at or near "'+'" at character 33 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99xy'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\\'; 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2024-05-05 02:19:48.763 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\0061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 26 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \+00db99\+000061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape value at character 18 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \+2FFFFF'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape at character 17 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \u061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape at character 17 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \U0061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "'" at character 23 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "x" at character 23 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99xy'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\" at character 23 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\\'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\u0061" at character 23 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\u0061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\U00000061" at character 27 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \U0000db99\U00000061'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape value at or near "\U002FFFFF" at character 17 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'wrong: \U002FFFFF'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061"; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*'; 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.764 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&' \' UESCAPE '!' AS "tricky"; 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when standard_conforming_strings is off. 2024-05-05 02:19:48.765 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings ERROR: invalid hexadecimal data: odd number of digits at character 8 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeE'::bytea; 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings ERROR: invalid hexadecimal digit: "x" at character 8 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeEx'::bytea; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03 123" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03 123'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03:04:05" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03:04:05'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05 123" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05 123'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings ERROR: invalid input syntax for type bytea at character 8 2024-05-05 02:19:48.766 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT E'De\\678dBeEf'::bytea; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08002b:01020304050607'::macaddr8; 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b01020304050607" at character 8 2024-05-05 02:19:48.766 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08002b01020304050607'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "0z002b0102030405" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '0z002b0102030405'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b010203xyza" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08002b010203xyza'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2024-05-05 02:19:48.767 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2024-05-05 02:19:48.769 UTC client backend[20219] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "not even close" at character 38 2024-05-05 02:19:48.769 UTC client backend[20219] pg_regress/macaddr8 STATEMENT: INSERT INTO macaddr8_data VALUES (9, 'not even close'); 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "123a" at character 8 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 123abc; 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0o" at character 8 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0x0o; 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.a" at character 8 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0.a; 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0a" at character 8 2024-05-05 02:19:48.772 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0.0a; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near ".0a" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT .0a; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e1a" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0.0e1a; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0.0e; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e+" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0.0e+a; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after parameter at or near "$1a" at character 22 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $1a; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: invalid binary integer at or near "0b" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0b; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1b" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1b; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0b0x" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0b0x; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: invalid octal integer at or near "0o" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0o; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1o" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1o; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0o0x" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0o0x; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: invalid hexadecimal integer at or near "0x" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0x; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1x" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1x; 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0y" at character 8 2024-05-05 02:19:48.773 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 0x0y; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: column "_100" does not exist at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT _100; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100_" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 100_; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100_" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 100__000; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: syntax error at or near ".5" at character 14 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT _1_000.5; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000_" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1_000_.5; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000._" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1_000._5; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5_" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1_000.5_; 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5e" at character 8 2024-05-05 02:19:48.774 UTC client backend[20220] pg_regress/numerology STATEMENT: SELECT 1_000.5e_1; 2024-05-05 02:19:48.781 UTC client backend[20233] pg_regress/inet ERROR: table "inet_tbl" does not exist 2024-05-05 02:19:48.781 UTC client backend[20233] pg_regress/inet STATEMENT: DROP TABLE INET_TBL; 2024-05-05 02:19:48.782 UTC client backend[20231] pg_regress/point ERROR: invalid input syntax for type point: "asdfasdf" at character 35 2024-05-05 02:19:48.782 UTC client backend[20231] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf'); 2024-05-05 02:19:48.782 UTC client backend[20218] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32 2024-05-05 02:19:48.782 UTC client backend[20218] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York'); 2024-05-05 02:19:48.782 UTC client backend[20218] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 m2" at character 32 2024-05-05 02:19:48.782 UTC client backend[20218] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2'); 2024-05-05 02:19:48.783 UTC client backend[20218] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32 2024-05-05 02:19:48.783 UTC client backend[20218] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2'); 2024-05-05 02:19:48.784 UTC client backend[20231] pg_regress/point ERROR: invalid input syntax for type point: "(10.0 10.0)" at character 35 2024-05-05 02:19:48.784 UTC client backend[20231] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)'); 2024-05-05 02:19:48.784 UTC client backend[20231] pg_regress/point ERROR: invalid input syntax for type point: "(10.0, 10.0) x" at character 35 2024-05-05 02:19:48.784 UTC client backend[20231] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x'); 2024-05-05 02:19:48.787 UTC client backend[20231] pg_regress/point ERROR: invalid input syntax for type point: "(10.0,10.0" at character 35 2024-05-05 02:19:48.787 UTC client backend[20231] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0'); 2024-05-05 02:19:48.787 UTC client backend[20231] pg_regress/point ERROR: "1e+500" is out of range for type double precision at character 35 2024-05-05 02:19:48.787 UTC client backend[20231] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)'); 2024-05-05 02:19:48.789 UTC client backend[20230] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "0800:2b01:0203" at character 37 2024-05-05 02:19:48.789 UTC client backend[20230] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203'); 2024-05-05 02:19:48.789 UTC client backend[20230] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "not even close" at character 37 2024-05-05 02:19:48.789 UTC client backend[20230] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (9, 'not even close'); 2024-05-05 02:19:48.795 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "" at character 8 2024-05-05 02:19:48.795 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Missing left brace. 2024-05-05 02:19:48.795 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select ''::textmultirange; 2024-05-05 02:19:48.796 UTC client backend[20224] pg_regress/time ERROR: invalid input syntax for type time: "15:36:39 America/New_York" at character 30 2024-05-05 02:19:48.796 UTC client backend[20224] pg_regress/time STATEMENT: INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York'); 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz ERROR: date/time field value out of range: "24:00:00.01 PDT" at character 8 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT '24:00:00.01 PDT'::timetz; 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz ERROR: date/time field value out of range: "23:59:60.01 PDT" at character 8 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT '23:59:60.01 PDT'::timetz; 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz ERROR: date/time field value out of range: "24:01:00 PDT" at character 8 2024-05-05 02:19:48.798 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT '24:01:00 PDT'::timetz; 2024-05-05 02:19:48.799 UTC client backend[20218] pg_regress/timetz ERROR: date/time field value out of range: "25:00:00 PDT" at character 8 2024-05-05 02:19:48.799 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT '25:00:00 PDT'::timetz; 2024-05-05 02:19:48.799 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "1997-02-29" at character 30 2024-05-05 02:19:48.799 UTC client backend[20228] pg_regress/date STATEMENT: INSERT INTO DATE_TBL VALUES ('1997-02-29'); 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,}" at character 8 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected range start. 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{,}'::textmultirange; 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(,)}." at character 8 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Junk after closing right brace. 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(,)}.'::textmultirange; 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,c),}" at character 8 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected range start. 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{[a,c),}'::textmultirange; 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,[a,c)}" at character 8 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected range start. 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{,[a,c)}'::textmultirange; 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{-[a,z)}" at character 8 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected range start. 2024-05-05 02:19:48.799 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{-[a,z)}'::textmultirange; 2024-05-05 02:19:48.799 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "badly formatted interval" at character 39 2024-05-05 02:19:48.799 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval'); 2024-05-05 02:19:48.800 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "@ 30 eons ago" at character 39 2024-05-05 02:19:48.800 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago'); 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,z) - }" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{[a,z) - }'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(",a)}" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Unexpected end of input. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(",a)}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed range literal: "(,,a)" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Too many commas. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(,,a)}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed range literal: "()" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(),a)}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,))}" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(a,))}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed range literal: "(]" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(],a)}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,])}" at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{(a,])}'::textmultirange; 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2024-05-05 02:19:48.800 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{[z,a]}'::textmultirange; 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path ERROR: invalid input syntax for type path: "[]" at character 30 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[]'); 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path ERROR: invalid input syntax for type path: "[(,2),(3,4)]" at character 30 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]'); 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path ERROR: invalid input syntax for type path: "[(1,2),(3,4)" at character 30 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)'); 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path ERROR: invalid input syntax for type path: "(1,2,3,4" at character 30 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2,3,4'); 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path ERROR: invalid input syntax for type path: "(1,2),(3,4)]" at character 30 2024-05-05 02:19:48.802 UTC client backend[20222] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]'); 2024-05-05 02:19:48.805 UTC client backend[20218] pg_regress/timetz ERROR: operator does not exist: time with time zone + time with time zone at character 11 2024-05-05 02:19:48.805 UTC client backend[20218] pg_regress/timetz HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:48.805 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL; 2024-05-05 02:19:48.806 UTC client backend[20218] pg_regress/timetz ERROR: unit "day" not supported for type time with time zone 2024-05-05 02:19:48.806 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT EXTRACT(DAY FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2024-05-05 02:19:48.806 UTC client backend[20218] pg_regress/timetz ERROR: unit "fortnight" not recognized for type time with time zone 2024-05-05 02:19:48.806 UTC client backend[20218] pg_regress/timetz STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2024-05-05 02:19:48.806 UTC client backend[20227] pg_regress/circle ERROR: invalid input syntax for type circle: "<(-100,0),-100>" at character 32 2024-05-05 02:19:48.806 UTC client backend[20227] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>'); 2024-05-05 02:19:48.806 UTC client backend[20227] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10" at character 32 2024-05-05 02:19:48.806 UTC client backend[20227] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10'); 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10> x" at character 32 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x'); 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle ERROR: invalid input syntax for type circle: "1abc,3,5" at character 32 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5'); 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle ERROR: invalid input syntax for type circle: "(3,(1,2),3)" at character 32 2024-05-05 02:19:48.807 UTC client backend[20227] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)'); 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "1/8/1999" at character 13 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1/8/1999'; 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.810 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time ERROR: date/time field value out of range: "24:00:00.01" at character 8 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time STATEMENT: SELECT '24:00:00.01'::time; 2024-05-05 02:19:48.811 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2024-05-05 02:19:48.811 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.811 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time ERROR: date/time field value out of range: "23:59:60.01" at character 8 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time STATEMENT: SELECT '23:59:60.01'::time; 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time ERROR: date/time field value out of range: "24:01:00" at character 8 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time STATEMENT: SELECT '24:01:00'::time; 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time ERROR: date/time field value out of range: "25:00:00" at character 8 2024-05-05 02:19:48.811 UTC client backend[20224] pg_regress/time STATEMENT: SELECT '25:00:00'::time; 2024-05-05 02:19:48.811 UTC client backend[20235] pg_regress/box ERROR: invalid input syntax for type box: "(2.3, 4.5)" at character 34 2024-05-05 02:19:48.811 UTC client backend[20235] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)'); 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box ERROR: invalid input syntax for type box: "[1, 2, 3, 4)" at character 34 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)'); 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4]" at character 34 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]'); 2024-05-05 02:19:48.812 UTC client backend[20224] pg_regress/time ERROR: operator is not unique: time without time zone + time without time zone at character 11 2024-05-05 02:19:48.812 UTC client backend[20224] pg_regress/time HINT: Could not choose a best candidate operator. You might need to add explicit type casts. 2024-05-05 02:19:48.812 UTC client backend[20224] pg_regress/time STATEMENT: SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL; 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x'); 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box ERROR: invalid input syntax for type box: "asdfasdf(ad" at character 34 2024-05-05 02:19:48.812 UTC client backend[20235] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad'); 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time ERROR: unit "day" not supported for type time without time zone 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time STATEMENT: SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time ERROR: unit "fortnight" not recognized for type time without time zone 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time ERROR: unit "timezone" not supported for type time without time zone 2024-05-05 02:19:48.813 UTC client backend[20224] pg_regress/time STATEMENT: SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); 2024-05-05 02:19:48.813 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "January 8, 99 BC" at character 13 2024-05-05 02:19:48.813 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.813 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date 'January 8, 99 BC'; 2024-05-05 02:19:48.815 UTC client backend[20217] pg_regress/strings ERROR: negative substring length not allowed 2024-05-05 02:19:48.815 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error"; 2024-05-05 02:19:48.816 UTC client backend[20234] pg_regress/polygon ERROR: invalid input syntax for type polygon: "0.0" at character 37 2024-05-05 02:19:48.816 UTC client backend[20234] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('0.0'); 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0.0 0.0" at character 37 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0'); 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2)" at character 37 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)'); 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2,3" at character 37 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3'); 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon ERROR: invalid input syntax for type polygon: "asdf" at character 37 2024-05-05 02:19:48.817 UTC client backend[20234] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('asdf'); 2024-05-05 02:19:48.817 UTC client backend[20217] pg_regress/strings ERROR: SQL regular expression may not contain more than two escape-double-quote separators 2024-05-05 02:19:48.817 UTC client backend[20217] pg_regress/strings CONTEXT: SQL function "substring" statement 1 2024-05-05 02:19:48.817 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error"; 2024-05-05 02:19:48.818 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08-Jan-99" at character 13 2024-05-05 02:19:48.818 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.818 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08-Jan-99'; 2024-05-05 02:19:48.821 UTC client backend[20233] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 37 2024-05-05 02:19:48.821 UTC client backend[20233] pg_regress/inet DETAIL: Value has bits set to right of mask. 2024-05-05 02:19:48.821 UTC client backend[20233] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226'); 2024-05-05 02:19:48.821 UTC client backend[20233] pg_regress/inet ERROR: invalid input syntax for type cidr: "1234::1234::1234" at character 37 2024-05-05 02:19:48.821 UTC client backend[20233] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4'); 2024-05-05 02:19:48.821 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "Jan-08-99" at character 13 2024-05-05 02:19:48.821 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.821 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date 'Jan-08-99'; 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 42 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet DETAIL: Value has bits set to right of mask. 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226'); 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet ERROR: invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet DETAIL: Value has bits set to right of mask. 2024-05-05 02:19:48.822 UTC client backend[20233] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226'); 2024-05-05 02:19:48.823 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2024-05-05 02:19:48.823 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2024-05-05 02:19:48.823 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2024-05-05 02:19:48.823 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2024-05-05 02:19:48.824 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08 Jan 99" at character 13 2024-05-05 02:19:48.824 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.824 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08 Jan 99'; 2024-05-05 02:19:48.825 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "Jan 08 99" at character 13 2024-05-05 02:19:48.825 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.825 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date 'Jan 08 99'; 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08-01-99" at character 13 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08-01-99'; 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08-01-1999" at character 13 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.827 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08-01-1999'; 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "01-08-99" at character 13 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '01-08-99'; 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "01-08-1999" at character 13 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.828 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '01-08-1999'; 2024-05-05 02:19:48.829 UTC client backend[20239] pg_regress/lseg ERROR: invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30 2024-05-05 02:19:48.829 UTC client backend[20239] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[1,2,3, 4" at character 30 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4'); 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]'); 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08 01 99" at character 13 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08 01 99'; 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "08 01 1999" at character 13 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.830 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '08 01 1999'; 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30 2024-05-05 02:19:48.830 UTC client backend[20239] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)'); 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "01 08 99" at character 13 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '01 08 99'; 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "{}" at character 30 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{}'); 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "01 08 1999" at character 13 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.831 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '01 08 1999'; 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "{0" at character 30 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0'); 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "{0,0}" at character 30 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0}'); 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1" at character 30 2024-05-05 02:19:48.831 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1'); 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line ERROR: invalid line specification: A and B cannot both be zero at character 30 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1}'); 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1} x" at character 30 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1} x'); 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "[1,2,3, 4" at character 30 2024-05-05 02:19:48.832 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[1,2,3, 4'); 2024-05-05 02:19:48.833 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "[(,2),(3,4)]" at character 30 2024-05-05 02:19:48.833 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]'); 2024-05-05 02:19:48.834 UTC client backend[20238] pg_regress/line ERROR: invalid input syntax for type line: "[(1,2),(3,4)" at character 30 2024-05-05 02:19:48.834 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)'); 2024-05-05 02:19:48.834 UTC client backend[20238] pg_regress/line ERROR: invalid line specification: must be two distinct points at character 30 2024-05-05 02:19:48.834 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]'); 2024-05-05 02:19:48.835 UTC client backend[20238] pg_regress/line ERROR: invalid line specification: must be two distinct points 2024-05-05 02:19:48.835 UTC client backend[20238] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)')); 2024-05-05 02:19:48.836 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2024-05-05 02:19:48.836 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.836 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2024-05-05 02:19:48.840 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2024-05-05 02:19:48.840 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.840 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2024-05-05 02:19:48.849 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2024-05-05 02:19:48.849 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2024-05-05 02:19:48.850 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2024-05-05 02:19:48.850 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2024-05-05 02:19:48.850 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99 Jan 08" at character 13 2024-05-05 02:19:48.850 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.850 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2024-05-05 02:19:48.851 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2024-05-05 02:19:48.851 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2024-05-05 02:19:48.853 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2024-05-05 02:19:48.853 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.853 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2024-05-05 02:19:48.855 UTC client backend[20217] pg_regress/strings ERROR: invalid escape string 2024-05-05 02:19:48.855 UTC client backend[20217] pg_regress/strings HINT: Escape string must be empty or one character. 2024-05-05 02:19:48.855 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error; 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.857 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2024-05-05 02:19:48.857 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression option: "z" 2024-05-05 02:19:48.857 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z'); 2024-05-05 02:19:48.858 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2024-05-05 02:19:48.858 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.858 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.861 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99 Jan 08" at character 13 2024-05-05 02:19:48.863 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2024-05-05 02:19:48.864 UTC client backend[20228] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2024-05-05 02:19:48.864 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2024-05-05 02:19:48.864 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2024-05-05 02:19:48.864 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.864 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.866 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date ERROR: date out of range: "4714-11-23 BC" at character 13 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '4714-11-23 BC'; 2024-05-05 02:19:48.868 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "start": -1 2024-05-05 02:19:48.868 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i'); 2024-05-05 02:19:48.868 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "n": -1 2024-05-05 02:19:48.868 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i'); 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date ERROR: date out of range: "5874898-01-01" at character 13 2024-05-05 02:19:48.868 UTC client backend[20228] pg_regress/date STATEMENT: SELECT date '5874898-01-01'; 2024-05-05 02:19:48.871 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression option: "1" 2024-05-05 02:19:48.871 UTC client backend[20217] pg_regress/strings HINT: If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly. 2024-05-05 02:19:48.871 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1'); 2024-05-05 02:19:48.882 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "start": 0 2024-05-05 02:19:48.882 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', 0); 2024-05-05 02:19:48.882 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "start": -3 2024-05-05 02:19:48.882 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', -3); 2024-05-05 02:19:48.884 UTC client backend[20217] pg_regress/strings ERROR: regexp_like() does not support the "global" option 2024-05-05 02:19:48.884 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_like('abc', 'a.c', 'g'); 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "start": 0 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 0, 1); 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "n": 0 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 0); 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "endoption": -1 2024-05-05 02:19:48.895 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1); 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "endoption": 2 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2); 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings ERROR: regexp_instr() does not support the "global" option 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g'); 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2024-05-05 02:19:48.896 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1); 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date ERROR: unit "microseconds" not supported for type date 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSECONDS FROM DATE '2020-08-11'); 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date ERROR: unit "milliseconds" not supported for type date 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(MILLISECONDS FROM DATE '2020-08-11'); 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date ERROR: unit "second" not supported for type date 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(SECOND FROM DATE '2020-08-11'); 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date ERROR: unit "minute" not supported for type date 2024-05-05 02:19:48.897 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(MINUTE FROM DATE '2020-08-11'); 2024-05-05 02:19:48.898 UTC client backend[20228] pg_regress/date ERROR: unit "hour" not supported for type date 2024-05-05 02:19:48.898 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(HOUR FROM DATE '2020-08-11'); 2024-05-05 02:19:48.901 UTC client backend[20237] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:48.901 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select nummultirange(numrange(2.0, 1.0)); 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date ERROR: unit "timezone" not supported for type date 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE FROM DATE '2020-08-11'); 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date ERROR: unit "timezone_m" not supported for type date 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_M FROM DATE '2020-08-11'); 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date ERROR: unit "timezone_h" not supported for type date 2024-05-05 02:19:48.903 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_H FROM DATE '2020-08-11'); 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "start": 0 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 0, 1); 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "n": 0 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 0); 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings ERROR: regexp_substr() does not support the "global" option 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g'); 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2024-05-05 02:19:48.905 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1); 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression option: "z" 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz'); 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression: parentheses () not balanced 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$); 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression: invalid repetition count(s) 2024-05-05 02:19:48.911 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$); 2024-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression option: "z" 2024-05-05 02:19:48.921 UTC client backend[20217] 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-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings ERROR: invalid regular expression option: "z" 2024-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz'); 2024-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings ERROR: regexp_split_to_table() does not support the "global" option 2024-05-05 02:19:48.921 UTC client backend[20217] 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-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings ERROR: regexp_split_to_array() does not support the "global" option 2024-05-05 02:19:48.921 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g'); 2024-05-05 02:19:48.927 UTC client backend[20228] pg_regress/date ERROR: unit "microsec" not recognized for type date 2024-05-05 02:19:48.927 UTC client backend[20228] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSEC FROM DATE 'infinity'); 2024-05-05 02:19:48.928 UTC client backend[20228] pg_regress/date ERROR: date field value out of range: 0-07-15 2024-05-05 02:19:48.928 UTC client backend[20228] pg_regress/date STATEMENT: select make_date(0, 7, 15); 2024-05-05 02:19:48.928 UTC client backend[20228] pg_regress/date ERROR: date field value out of range: 2013-02-30 2024-05-05 02:19:48.928 UTC client backend[20228] pg_regress/date STATEMENT: select make_date(2013, 2, 30); 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date ERROR: date field value out of range: 2013-13-01 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date STATEMENT: select make_date(2013, 13, 1); 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date ERROR: date field value out of range: 2013-11--1 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date STATEMENT: select make_date(2013, 11, -1); 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date ERROR: time field value out of range: 10:55:100.1 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date STATEMENT: select make_time(10, 55, 100.1); 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date ERROR: time field value out of range: 24:00:2.1 2024-05-05 02:19:48.929 UTC client backend[20228] pg_regress/date STATEMENT: select make_time(24, 0, 2.1); 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet ERROR: result is out of range 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet + 10000000000; 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet ERROR: result is out of range 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet - 10000000000; 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet ERROR: result is out of range 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet STATEMENT: SELECT '126::1'::inet - '127::2'::inet; 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet ERROR: result is out of range 2024-05-05 02:19:48.933 UTC client backend[20233] pg_regress/inet STATEMENT: SELECT '127::1'::inet - '126::2'::inet; 2024-05-05 02:19:48.935 UTC client backend[20233] pg_regress/inet ERROR: cannot merge addresses from different families 2024-05-05 02:19:48.935 UTC client backend[20233] pg_regress/inet STATEMENT: SELECT inet_merge(c, i) FROM INET_TBL; 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT -('-2147483648 months'::interval); 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT -('-2147483648 days'::interval); 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:48.990 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT -('-9223372036854775808 us'::interval); 2024-05-05 02:19:48.991 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:48.991 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval); 2024-05-05 02:19:48.992 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 42 2024-05-05 02:19:48.992 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days'); 2024-05-05 02:19:48.992 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 42 2024-05-05 02:19:48.992 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days'); 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval ERROR: interval out of range at character 42 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years'); 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval ERROR: interval out of range at character 42 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years'); 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:48.993 UTC client backend[20223] pg_regress/interval STATEMENT: select extract(epoch from '256 microseconds'::interval * (2^55)::float8); 2024-05-05 02:19:48.995 UTC client backend[20217] pg_regress/strings ERROR: negative substring length not allowed 2024-05-05 02:19:48.995 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval * 1000; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval / 0.001; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval * 1000; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval / 0.001; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '1 month 2146410 days'::interval * 1000.5002; 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.025 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '4611686018427387904 usec'::interval / 0.1; 2024-05-05 02:19:49.026 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.026 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_hours(interval '2147483647 days 24 hrs'); 2024-05-05 02:19:49.026 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.026 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_days(interval '2147483647 months 30 days'); 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months 30 days'); 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months -30 days'); 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs'); 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.027 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs'); 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 second 2 seconds" at character 8 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '1 second 2 seconds'::interval; 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '10 milliseconds 20 milliseconds'::interval; 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '5.5 seconds 3 milliseconds'::interval; 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '1:20:05 5 microseconds'::interval; 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 day 1 day" at character 8 2024-05-05 02:19:49.028 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '1 day 1 day'::interval; 2024-05-05 02:19:49.036 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2024-05-05 02:19:49.036 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2' day to minute; 2024-05-05 02:19:49.037 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2024-05-05 02:19:49.037 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2' day to second; 2024-05-05 02:19:49.037 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2024-05-05 02:19:49.037 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to minute; 2024-05-05 02:19:49.044 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2024-05-05 02:19:49.044 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to second; 2024-05-05 02:19:49.045 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2024-05-05 02:19:49.045 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2' minute to second; 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '123 11' day; 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '123 11'; 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "123 2:03 -2:04" at character 17 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '123 2:03 -2:04'; 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2024-05-05 02:19:49.046 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2.345' day to second(2); 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2.345' hour to second(2); 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.3456" at character 17 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '1 2.3456' minute to second(2); 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval ERROR: interval out of range at character 17 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '2562047788:00:54.775807' second(2); 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval ERROR: interval out of range at character 17 2024-05-05 02:19:49.047 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-2562047788:00:54.775807' second(2); 2024-05-05 02:19:49.049 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "" at character 18 2024-05-05 02:19:49.049 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval ''; 2024-05-05 02:19:49.050 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17 2024-05-05 02:19:49.050 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P.Y0M3DT4H5M6S'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483648 years" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483648 years'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483649 years" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483649 years'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483648 months" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483648 months'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483649 months" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483649 months'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483648 days'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483649 days'; 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2562047789 hours" at character 17 2024-05-05 02:19:49.057 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2562047789 hours'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2562047789 hours" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2562047789 hours'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "153722867281 minutes" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '153722867281 minutes'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-153722867281 minutes" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-153722867281 minutes'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036855 seconds" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036855 seconds'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036855 seconds" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036855 seconds'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036854777 millisecond" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036854777 millisecond'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854777 millisecond" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854777 millisecond'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036854775808 microsecond" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036854775808 microsecond'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775809 microsecond" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854775809 microsecond'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P2147483648" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P2147483648'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-2147483649" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-2147483649'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval out of range at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P1-2147483647-2147483647'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT2562047789" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT2562047789'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT-2562047789" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT-2562047789'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 weeks" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 weeks'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 weeks" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 weeks'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 decades" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 decades'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 decades" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 decades'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 centuries" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 centuries'; 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 centuries" at character 17 2024-05-05 02:19:49.058 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 centuries'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 millennium" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 millennium'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 millennium" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 millennium'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "1 week 2147483647 days" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '1 week 2147483647 days'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-1 week -2147483648 days" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-1 week -2147483648 days'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 1 week" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 days 1 week'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -1 week" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 days -1 week'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P1W2147483647D" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P1W2147483647D'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-1W-2147483648D" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-1W-2147483648D'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P2147483647D1W" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P2147483647D1W'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-1W" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-2147483648D-1W'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "1 decade 2147483647 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '1 decade 2147483647 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "1 century 2147483647 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '1 century 2147483647 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "1 millennium 2147483647 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '1 millennium 2147483647 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-1 decade -2147483648 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-1 decade -2147483648 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-1 century -2147483648 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-1 century -2147483648 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-1 millennium -2147483648 years" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-1 millennium -2147483648 years'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 decade" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 years 1 decade'; 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 century" at character 17 2024-05-05 02:19:49.059 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 years 1 century'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 millennium" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 years 1 millennium'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 decade" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 decade'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 century" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 century'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 millennium" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 millennium'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 millennium 2147483647 months" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 millennium 2147483647 months'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 centuries 2147483647 months" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 centuries 2147483647 months'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 decades 2147483647 months" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 decades 2147483647 months'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 yrs 2147483647 months" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 yrs 2147483647 months'; 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 millennium -2147483648 months" at character 17 2024-05-05 02:19:49.060 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 millennium -2147483648 months'; 2024-05-05 02:19:49.064 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 centuries -2147483648 months" at character 17 2024-05-05 02:19:49.064 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 centuries -2147483648 months'; 2024-05-05 02:19:49.064 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 decades -2147483648 months" at character 17 2024-05-05 02:19:49.064 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 decades -2147483648 months'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 yrs -2147483648 months" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 yrs -2147483648 months'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 millennium" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 millennium'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 centuries" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 centuries'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 decades" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 decades'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 yrs" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 yrs'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 millennium" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 millennium'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 centuries" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 centuries'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 decades" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 decades'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 yrs" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 yrs'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 months 2147483647 days" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 months 2147483647 days'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 months -2147483648 days" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 months -2147483648 days'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.1 months" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 days 0.1 months'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.1 months" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.1 months'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.5 weeks 2147483647 days" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.5 weeks 2147483647 days'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.5 weeks -2147483648 days" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.5 weeks -2147483648 days'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.5 weeks" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2147483647 days 0.5 weeks'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.5 weeks" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.5 weeks'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.01 months 9223372036854775807 microseconds'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.01 months -9223372036854775808 microseconds'; 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17 2024-05-05 02:19:49.065 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.01 months'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.01 months'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 weeks 9223372036854775807 microseconds'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 weeks -9223372036854775808 microseconds'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 weeks'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 weeks'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 days 9223372036854775807 microseconds'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-0.1 days -9223372036854775808 microseconds'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 days'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 days'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.1Y2147483647M" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.1Y2147483647M'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-0.1Y-2147483648M" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-0.1Y-2147483648M'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P2147483647M0.1Y" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P2147483647M0.1Y'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-2147483648M-0.1Y" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-2147483648M-0.1Y'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.1M2147483647D" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.1M2147483647D'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-0.1M-2147483648D" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-0.1M-2147483648D'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.1M" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P2147483647D0.1M'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.1M" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.1M'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.5W2147483647D" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.5W2147483647D'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-0.5W-2147483648D" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-0.5W-2147483648D'; 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.5W" at character 17 2024-05-05 02:19:49.066 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P2147483647D0.5W'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.5W" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.5W'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.01MT2562047788H54.775807S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-0.01MT-2562047788H-54.775808S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.1DT2562047788H54.775807S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P-0.1DT-2562047788H-54.775808S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1H54.775807S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT2562047788.1H54.775807S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT-2562047788.1H-54.775808S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT2562047788H0.1M54.775807S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT-2562047788H-0.1M-54.775808S'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P0.1-2147483647-00" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P0.1-2147483647-00'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P00-0.1-2147483647" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P00-0.1-2147483647'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P00-0.01-00T2562047788:00:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'P00-00-0.1T2562047788:00:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1:00:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT2562047788.1:00:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "PT2562047788:01.:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval 'PT2562047788:01.:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775808 ago'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775807" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775807'; 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17 2024-05-05 02:19:49.067 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775808 ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775807'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775808 ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months ago" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days ago" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 days ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds ago" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago'; 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(years := 178956971); 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(years := -178956971); 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(years := 1, months := 2147483647); 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(years := -1, months := -2147483648); 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(weeks := 306783379); 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.068 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(weeks := -306783379); 2024-05-05 02:19:49.069 UTC client backend[20217] pg_regress/strings ERROR: negative substring length not allowed 2024-05-05 02:19:49.069 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2024-05-05 02:19:49.074 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.074 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(weeks := 1, days := 2147483647); 2024-05-05 02:19:49.074 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.074 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(weeks := -1, days := -2147483648); 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval ERROR: value out of range: overflow 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(secs := 1e308); 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(secs := 1e18); 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(secs := -1e18); 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(mins := 1, secs := 9223372036800.0); 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.075 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(mins := -1, secs := -9223372036800.0); 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval ERROR: integer out of range 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(years := 'inf'::float::int); 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval ERROR: integer out of range 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(months := 'NaN'::float::int); 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(secs := 'inf'); 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.078 UTC client backend[20223] pg_regress/interval STATEMENT: select make_interval(secs := 'NaN'); 2024-05-05 02:19:49.079 UTC client backend[20223] pg_regress/interval ERROR: unit "fortnight" not recognized for type interval 2024-05-05 02:19:49.079 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days'); 2024-05-05 02:19:49.079 UTC client backend[20223] pg_regress/interval ERROR: unit "timezone" not supported for type interval 2024-05-05 02:19:49.079 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days'); 2024-05-05 02:19:49.093 UTC client backend[20217] pg_regress/strings ERROR: field position must not be zero 2024-05-05 02:19:49.093 UTC client backend[20217] pg_regress/strings STATEMENT: select split_part('joeuser@mydatabase','@',0) AS "an error"; 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us'; 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us'; 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us'; 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.097 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us'; 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval ERROR: cannot add infinite interval to time 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval 'infinity'; 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval ERROR: cannot add infinite interval to time 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval '-infinity'; 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval ERROR: cannot subtract infinite interval from time 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval 'infinity'; 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval ERROR: cannot subtract infinite interval from time 2024-05-05 02:19:49.101 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval '-infinity'; 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval ERROR: cannot add infinite interval to time 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval 'infinity'; 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval ERROR: cannot add infinite interval to time 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval '-infinity'; 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval ERROR: cannot subtract infinite interval from time 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval 'infinity'; 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval ERROR: cannot subtract infinite interval from time 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval '-infinity'; 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.102 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us'; 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 'nan'; 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 'nan'; 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2; 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 0; 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.103 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 0; 2024-05-05 02:19:49.108 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.108 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '0 days' * 'infinity'::float; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '0 days' * '-infinity'::float; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'infinity'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval 'infinity' / '-infinity'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'nan'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'infinity'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-infinity' / '-infinity'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'nan'; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: interval out of range 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5; 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2024-05-05 02:19:49.109 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::time); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::time); 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2024-05-05 02:19:49.110 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::timetz); 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::timetz); 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: cannot convert infinite interval to time 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT 'infinity'::interval::time; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: cannot convert infinite interval to time 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT '-infinity'::interval::time; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL '42 days 2 seconds ago ago'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "2 minutes ago 5 days" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL '2 minutes ago 5 days'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "hour 5 months" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'hour 5 months'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "1 year months days 5 hours" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL '1 year months days 5 hours'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "now" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'now'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "today" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'today'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "tomorrow" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'tomorrow'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "allballs" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'allballs'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "epoch" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'epoch'; 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "yesterday" at character 17 2024-05-05 02:19:49.111 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'yesterday'; 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity years" at character 17 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity years'; 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity ago" at character 17 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity ago'; 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval ERROR: invalid input syntax for type interval: "+infinity -infinity" at character 17 2024-05-05 02:19:49.112 UTC client backend[20223] pg_regress/interval STATEMENT: SELECT INTERVAL '+infinity -infinity'; 2024-05-05 02:19:49.113 UTC client backend[20217] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2024-05-05 02:19:49.113 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT get_bit('\x1234567890abcdef00'::bytea, 99); 2024-05-05 02:19:49.113 UTC client backend[20217] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2024-05-05 02:19:49.113 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0); 2024-05-05 02:19:49.114 UTC client backend[20217] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2024-05-05 02:19:49.114 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT get_byte('\x1234567890abcdef00'::bytea, 99); 2024-05-05 02:19:49.114 UTC client backend[20217] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2024-05-05 02:19:49.114 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11); 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 8 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 24 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 42 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 62 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 80 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 98 2024-05-05 02:19:49.115 UTC client backend[20217] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2024-05-05 02:19:49.120 UTC client backend[20217] pg_regress/strings ERROR: null character not permitted 2024-05-05 02:19:49.120 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT chr(0); 2024-05-05 02:19:49.121 UTC client backend[20225] pg_regress/timestamptz ERROR: time zone "america/does_not_exist" not recognized at character 37 2024-05-05 02:19:49.121 UTC client backend[20225] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2024-05-05 02:19:49.121 UTC client backend[20217] pg_regress/strings ERROR: negative substring length not allowed 2024-05-05 02:19:49.121 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error"; 2024-05-05 02:19:49.121 UTC client backend[20225] pg_regress/timestamptz ERROR: time zone "America/Does_not_exist" not recognized 2024-05-05 02:19:49.121 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist'; 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99'); 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99\0061'); 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+00db99\+000061'); 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+2FFFFF'); 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \udb99\u0061'); 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode surrogate pair 2024-05-05 02:19:49.123 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U0000db99\U00000061'); 2024-05-05 02:19:49.124 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2024-05-05 02:19:49.124 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U002FFFFF'); 2024-05-05 02:19:49.124 UTC client backend[20217] pg_regress/strings ERROR: invalid Unicode escape 2024-05-05 02:19:49.124 UTC client backend[20217] pg_regress/strings HINT: Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX. 2024-05-05 02:19:49.124 UTC client backend[20217] pg_regress/strings STATEMENT: SELECT unistr('wrong: \xyz'); 2024-05-05 02:19:49.133 UTC client backend[20225] pg_regress/timestamptz ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 37 2024-05-05 02:19:49.133 UTC client backend[20225] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997'); 2024-05-05 02:19:49.133 UTC client backend[20225] pg_regress/timestamptz ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37 2024-05-05 02:19:49.133 UTC client backend[20225] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097'); 2024-05-05 02:19:49.134 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37 2024-05-05 02:19:49.134 UTC client backend[20225] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT '4714-11-23 23:59:59+00 BC'::timestamptz; 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp out of range: "294277-01-01 00:00:00+00" at character 8 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT '294277-01-01 00:00:00+00'::timestamptz; 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp out of range: "294277-12-31 16:00:00-08" at character 8 2024-05-05 02:19:49.135 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT '294277-12-31 16:00:00-08'::timestamptz; 2024-05-05 02:19:49.136 UTC client backend[20236] pg_regress/timestamp ERROR: time zone "america/does_not_exist" not recognized at character 35 2024-05-05 02:19:49.136 UTC client backend[20236] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2024-05-05 02:19:49.139 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2024-05-05 02:19:49.139 UTC client backend[20225] 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-05-05 02:19:49.139 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2024-05-05 02:19:49.139 UTC client backend[20225] 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-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz ERROR: stride must be greater than zero 2024-05-05 02:19:49.140 UTC client backend[20225] 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-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz ERROR: stride must be greater than zero 2024-05-05 02:19:49.140 UTC client backend[20225] 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-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC'); 2024-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz); 2024-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp out of range 2024-05-05 02:19:49.140 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz); 2024-05-05 02:19:49.145 UTC client backend[20236] pg_regress/timestamp ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 35 2024-05-05 02:19:49.145 UTC client backend[20236] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997'); 2024-05-05 02:19:49.146 UTC client backend[20236] pg_regress/timestamp ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35 2024-05-05 02:19:49.146 UTC client backend[20236] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097'); 2024-05-05 02:19:49.146 UTC client backend[20236] pg_regress/timestamp ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35 2024-05-05 02:19:49.146 UTC client backend[20236] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2024-05-05 02:19:49.147 UTC client backend[20236] pg_regress/timestamp ERROR: timestamp out of range: "4714-11-23 23:59:59 BC" at character 8 2024-05-05 02:19:49.147 UTC client backend[20236] pg_regress/timestamp STATEMENT: SELECT '4714-11-23 23:59:59 BC'::timestamp; 2024-05-05 02:19:49.147 UTC client backend[20236] pg_regress/timestamp ERROR: timestamp out of range: "294277-01-01 00:00:00" at character 8 2024-05-05 02:19:49.147 UTC client backend[20236] pg_regress/timestamp STATEMENT: SELECT '294277-01-01 00:00:00'::timestamp; 2024-05-05 02:19:49.153 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.153 UTC client backend[20225] 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-05-05 02:19:49.166 UTC client backend[20236] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2024-05-05 02:19:49.166 UTC client backend[20236] pg_regress/timestamp STATEMENT: SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp STATEMENT: SELECT date_bin('5 years'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp ERROR: stride must be greater than zero 2024-05-05 02:19:49.167 UTC client backend[20236] 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-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp ERROR: stride must be greater than zero 2024-05-05 02:19:49.167 UTC client backend[20236] 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-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp STATEMENT: select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC'); 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.167 UTC client backend[20236] pg_regress/timestamp STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp); 2024-05-05 02:19:49.168 UTC client backend[20236] pg_regress/timestamp ERROR: timestamp out of range 2024-05-05 02:19:49.168 UTC client backend[20236] pg_regress/timestamp STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp); 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz ERROR: invalid input syntax for type numeric time zone: "2" 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz HINT: Numeric time zones must have "-" or "+" as first character. 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2'); 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz ERROR: numeric time zone "+16" out of range 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16'); 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz ERROR: numeric time zone "-16" out of range 2024-05-05 02:19:49.175 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16'); 2024-05-05 02:19:49.176 UTC client backend[20225] pg_regress/timestamptz ERROR: time zone "Nehwon/Lankhmar" not recognized 2024-05-05 02:19:49.176 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar'); 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz ERROR: step size cannot equal zero 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamptz, '2020-01-02 03:00'::timestamptz, '0 hour'::interval); 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz ERROR: step size cannot be infinite 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity'); 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz ERROR: step size cannot be infinite 2024-05-05 02:19:49.177 UTC client backend[20225] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity'); 2024-05-05 02:19:49.178 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.178 UTC client backend[20236] pg_regress/timestamp STATEMENT: SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows; 2024-05-05 02:19:49.194 UTC client backend[20225] pg_regress/timestamptz ERROR: timestamp cannot be NaN 2024-05-05 02:19:49.194 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT to_timestamp('NaN'::float); 2024-05-05 02:19:49.199 UTC client backend[20236] pg_regress/timestamp ERROR: date field value out of range: 0-07-15 2024-05-05 02:19:49.199 UTC client backend[20236] pg_regress/timestamp STATEMENT: select make_timestamp(0, 7, 15, 12, 30, 15); 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp ERROR: step size cannot equal zero 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamp, '2020-01-02 03:00'::timestamp, '0 hour'::interval); 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp ERROR: step size cannot be infinite 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity'); 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp ERROR: step size cannot be infinite 2024-05-05 02:19:49.203 UTC client backend[20236] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity'); 2024-05-05 02:19:49.208 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.208 UTC client backend[20236] pg_regress/timestamp STATEMENT: select timestamp 'infinity' - timestamp 'infinity'; 2024-05-05 02:19:49.209 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.209 UTC client backend[20236] pg_regress/timestamp STATEMENT: select timestamp '-infinity' - timestamp '-infinity'; 2024-05-05 02:19:49.210 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.210 UTC client backend[20236] pg_regress/timestamp STATEMENT: select age(timestamp 'infinity', timestamp 'infinity'); 2024-05-05 02:19:49.210 UTC client backend[20236] pg_regress/timestamp ERROR: interval out of range 2024-05-05 02:19:49.210 UTC client backend[20236] pg_regress/timestamp STATEMENT: select age(timestamp '-infinity', timestamp '-infinity'); 2024-05-05 02:19:49.222 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.222 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT timestamptz 'infinity' - timestamptz 'infinity'; 2024-05-05 02:19:49.222 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.222 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT timestamptz '-infinity' - timestamptz '-infinity'; 2024-05-05 02:19:49.223 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.223 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz 'infinity', timestamptz 'infinity'); 2024-05-05 02:19:49.223 UTC client backend[20225] pg_regress/timestamptz ERROR: interval out of range 2024-05-05 02:19:49.223 UTC client backend[20225] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz '-infinity', timestamptz '-infinity'); 2024-05-05 02:19:49.795 UTC client backend[20237] pg_regress/multirangetypes ERROR: value for domain restrictedmultirange violates check constraint "restrictedmultirange_check" 2024-05-05 02:19:49.795 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select '{[4,50)}'::restrictedmultirange @> 7; 2024-05-05 02:19:49.805 UTC client backend[20237] pg_regress/multirangetypes ERROR: type "intmultirange" already exists 2024-05-05 02:19:49.805 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intrange". 2024-05-05 02:19:49.805 UTC client backend[20237] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2024-05-05 02:19:49.805 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create type intrange as range(subtype=int); 2024-05-05 02:19:49.806 UTC client backend[20237] pg_regress/multirangetypes ERROR: type "intr_multirange" already exists 2024-05-05 02:19:49.806 UTC client backend[20237] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intr". 2024-05-05 02:19:49.806 UTC client backend[20237] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2024-05-05 02:19:49.806 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create type intr as range(subtype=int); 2024-05-05 02:19:49.809 UTC client backend[20237] pg_regress/multirangetypes ERROR: type "int4" already exists 2024-05-05 02:19:49.809 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C"); 2024-05-05 02:19:49.811 UTC client backend[20237] pg_regress/multirangetypes ERROR: function multirange_of_text(textrange2) does not exist at character 8 2024-05-05 02:19:49.811 UTC client backend[20237] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:49.811 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange2('a','Z')); 2024-05-05 02:19:49.811 UTC client backend[20237] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:49.811 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange1('a','Z')) @> 'b'::text; 2024-05-05 02:19:49.823 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot alter multirange type multitextrange1 2024-05-05 02:19:49.823 UTC client backend[20237] pg_regress/multirangetypes HINT: You can alter type textrange1, which will alter the multirange type as well. 2024-05-05 02:19:49.823 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: alter type multitextrange1 owner to regress_multirange_owner; 2024-05-05 02:19:49.824 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot set privileges of multirange types 2024-05-05 02:19:49.824 UTC client backend[20237] pg_regress/multirangetypes HINT: Set the privileges of the range type instead. 2024-05-05 02:19:49.824 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: revoke usage on type multitextrange1 from public; 2024-05-05 02:19:49.838 UTC client backend[20237] pg_regress/multirangetypes ERROR: permission denied for type multitextrange1 2024-05-05 02:19:49.838 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create temp table test2(f1 multitextrange1[]); 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes ERROR: function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20))); 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:49.841 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create function bogus_func(anyelement) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2024-05-05 02:19:49.842 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.842 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:49.842 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create function bogus_func(int) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2024-05-05 02:19:49.843 UTC client backend[20237] pg_regress/multirangetypes ERROR: function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8 2024-05-05 02:19:49.843 UTC client backend[20237] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:49.843 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]); 2024-05-05 02:19:49.844 UTC client backend[20237] pg_regress/multirangetypes ERROR: function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8 2024-05-05 02:19:49.844 UTC client backend[20237] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:49.844 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20))); 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes ERROR: function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20))); 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2024-05-05 02:19:49.845 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2024-05-05 02:19:49.848 UTC client backend[20237] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2024-05-05 02:19:49.848 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2])); 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:49.873 UTC client backend[20237] 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-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes STATEMENT: create function mr_inoutparam_fail(inout i anyelement, out r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes ERROR: cannot determine result data type 2024-05-05 02:19:49.873 UTC client backend[20237] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2024-05-05 02:19:49.873 UTC client backend[20237] 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-05-05 02:19:50.060 UTC client backend[20554] pg_regress/expressions WARNING: TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2024-05-05 02:19:50.060 UTC client backend[20554] pg_regress/expressions WARNING: TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2024-05-05 02:19:50.060 UTC client backend[20554] pg_regress/expressions WARNING: TIME(7) precision reduced to maximum allowed, 6 2024-05-05 02:19:50.060 UTC client backend[20554] pg_regress/expressions WARNING: TIMESTAMP(7) precision reduced to maximum allowed, 6 2024-05-05 02:19:50.069 UTC client backend[20560] pg_regress/tstypes ERROR: syntax error in tsvector: "'' '1' '2'" at character 8 2024-05-05 02:19:50.069 UTC client backend[20560] pg_regress/tstypes STATEMENT: SELECT $$'' '1' '2'$$::tsvector; 2024-05-05 02:19:50.076 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type xid: "" at character 8 2024-05-05 02:19:50.076 UTC client backend[20559] pg_regress/xid STATEMENT: select ''::xid; 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type xid: "asdf" at character 8 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid STATEMENT: select 'asdf'::xid; 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type xid8: "" at character 8 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid STATEMENT: select ''::xid8; 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type xid8: "asdf" at character 8 2024-05-05 02:19:50.077 UTC client backend[20559] pg_regress/xid STATEMENT: select 'asdf'::xid8; 2024-05-05 02:19:50.078 UTC client backend[20557] pg_regress/unicode ERROR: invalid normalization form: def 2024-05-05 02:19:50.078 UTC client backend[20557] pg_regress/unicode STATEMENT: SELECT "normalize"('abc', 'def'); 2024-05-05 02:19:50.081 UTC client backend[20557] pg_regress/unicode ERROR: invalid normalization form: def 2024-05-05 02:19:50.081 UTC client backend[20557] pg_regress/unicode STATEMENT: SELECT is_normalized('abc', 'def'); 2024-05-05 02:19:50.081 UTC client backend[20555] pg_regress/geometry ERROR: value out of range: underflow 2024-05-05 02:19:50.081 UTC client backend[20555] 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-05-05 02:19:50.089 UTC client backend[20559] pg_regress/xid ERROR: operator does not exist: xid < xid at character 17 2024-05-05 02:19:50.089 UTC client backend[20559] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.089 UTC client backend[20559] pg_regress/xid STATEMENT: select '1'::xid < '2'::xid; 2024-05-05 02:19:50.090 UTC client backend[20559] pg_regress/xid ERROR: operator does not exist: xid <= xid at character 17 2024-05-05 02:19:50.090 UTC client backend[20559] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.090 UTC client backend[20559] pg_regress/xid STATEMENT: select '1'::xid <= '2'::xid; 2024-05-05 02:19:50.090 UTC client backend[20555] pg_regress/geometry ERROR: value out of range: overflow 2024-05-05 02:19:50.090 UTC client backend[20555] 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-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid ERROR: operator does not exist: xid > xid at character 17 2024-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid STATEMENT: select '1'::xid > '2'::xid; 2024-05-05 02:19:50.092 UTC client backend[20555] pg_regress/geometry ERROR: division by zero 2024-05-05 02:19:50.092 UTC client backend[20555] 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-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid ERROR: operator does not exist: xid >= xid at character 17 2024-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.092 UTC client backend[20559] pg_regress/xid STATEMENT: select '1'::xid >= '2'::xid; 2024-05-05 02:19:50.094 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33 2024-05-05 02:19:50.094 UTC client backend[20564] pg_regress/horology HINT: Perhaps you need a different "datestyle" setting. 2024-05-05 02:19:50.094 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp with time zone '27/12/2001 04:05:06.789-08'; 2024-05-05 02:19:50.096 UTC client backend[20565] pg_regress/regex ERROR: regexp_match() does not support the "global" option 2024-05-05 02:19:50.096 UTC client backend[20565] pg_regress/regex HINT: Use the regexp_matches function instead. 2024-05-05 02:19:50.096 UTC client backend[20565] pg_regress/regex STATEMENT: select regexp_match('abc', 'Bd', 'ig'); 2024-05-05 02:19:50.102 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28 2024-05-05 02:19:50.102 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT time with time zone 'T040506.789 America/Los_Angeles'; 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 J J J" at character 13 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '1995-08-06 J J J'; 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "J J 1520447" at character 13 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date 'J J 1520447'; 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08'; 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33 2024-05-05 02:19:50.107 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 epoch" at character 13 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '1995-08-06 epoch'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 infinity" at character 13 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '1995-08-06 infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 -infinity" at character 13 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '1995-08-06 -infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "today infinity" at character 13 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date 'today infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type date: "-infinity infinity" at character 13 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '-infinity infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 epoch'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 -infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "epoch 01:01:01" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp 'epoch 01:01:01'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "infinity 01:01:01" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp 'infinity 01:01:01'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp '-infinity 01:01:01'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "now epoch" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp 'now epoch'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity infinity" at character 18 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp '-infinity infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 epoch'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 infinity'; 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20 2024-05-05 02:19:50.109 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 -infinity'; 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz 'epoch 01:01:01'; 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz 'infinity 01:01:01'; 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity 01:01:01'; 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "now epoch" at character 20 2024-05-05 02:19:50.110 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz 'now epoch'; 2024-05-05 02:19:50.111 UTC client backend[20564] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20 2024-05-05 02:19:50.111 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity infinity'; 2024-05-05 02:19:50.115 UTC client backend[20564] pg_regress/horology ERROR: operator does not exist: date - time with time zone at character 26 2024-05-05 02:19:50.115 UTC client backend[20564] pg_regress/horology HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.115 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC"; 2024-05-05 02:19:50.118 UTC client backend[20564] pg_regress/horology ERROR: timestamp out of range 2024-05-05 02:19:50.118 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2024-05-05 02:19:50.118 UTC client backend[20564] pg_regress/horology ERROR: timestamp out of range 2024-05-05 02:19:50.118 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp without time zone '294276-12-31 23:59:59' + interval '9223372036854775807 microseconds' AS "out of range"; 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid STATEMENT: select '31:12:'::pg_snapshot; 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid STATEMENT: select '0:1:'::pg_snapshot; 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid STATEMENT: select '12:13:0'::pg_snapshot; 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2024-05-05 02:19:50.126 UTC client backend[20559] pg_regress/xid STATEMENT: select '12:16:14,13'::pg_snapshot; 2024-05-05 02:19:50.135 UTC client backend[20564] pg_regress/horology ERROR: timestamp out of range 2024-05-05 02:19:50.135 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2024-05-05 02:19:50.135 UTC client backend[20564] pg_regress/horology ERROR: timestamp out of range 2024-05-05 02:19:50.135 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT timestamp with time zone '294276-12-31 23:59:59 UTC' + interval '9223372036854775807 microseconds' AS "out of range"; 2024-05-05 02:19:50.142 UTC client backend[20555] pg_regress/geometry ERROR: operator does not exist: lseg # point at character 23 2024-05-05 02:19:50.142 UTC client backend[20555] pg_regress/geometry HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.142 UTC client backend[20555] pg_regress/geometry STATEMENT: SELECT p.f1, l.s, l.s # p.f1 AS intersection FROM LSEG_TBL l, POINT_TBL p; 2024-05-05 02:19:50.144 UTC client backend[20559] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20 2024-05-05 02:19:50.144 UTC client backend[20559] pg_regress/xid STATEMENT: SELECT pg_snapshot '1:9223372036854775808:3'; 2024-05-05 02:19:50.146 UTC client backend[20554] pg_regress/expressions ERROR: operator does not exist: point = box at character 23 2024-05-05 02:19:50.146 UTC client backend[20554] pg_regress/expressions HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:50.146 UTC client backend[20554] pg_regress/expressions STATEMENT: select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0)); 2024-05-05 02:19:50.150 UTC client backend[20564] pg_regress/horology ERROR: cannot cast type time with time zone to interval at character 8 2024-05-05 02:19:50.150 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01"; 2024-05-05 02:19:50.150 UTC client backend[20564] pg_regress/horology ERROR: cannot cast type interval to time with time zone at character 8 2024-05-05 02:19:50.150 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08"; 2024-05-05 02:19:50.169 UTC client backend[20560] pg_regress/tstypes ERROR: lexeme array may not contain nulls 2024-05-05 02:19:50.169 UTC client backend[20560] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]); 2024-05-05 02:19:50.169 UTC client backend[20560] pg_regress/tstypes ERROR: lexeme array may not contain empty strings 2024-05-05 02:19:50.169 UTC client backend[20560] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']); 2024-05-05 02:19:50.174 UTC client backend[20560] pg_regress/tstypes ERROR: weight array may not contain nulls 2024-05-05 02:19:50.174 UTC client backend[20560] pg_regress/tstypes STATEMENT: SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}'); 2024-05-05 02:19:50.192 UTC client backend[20555] pg_regress/geometry ERROR: open path cannot be converted to polygon 2024-05-05 02:19:50.192 UTC client backend[20555] pg_regress/geometry STATEMENT: SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1); 2024-05-05 02:19:50.220 UTC client backend[20555] pg_regress/geometry ERROR: division by zero 2024-05-05 02:19:50.220 UTC client backend[20555] 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-05-05 02:19:50.402 UTC client backend[20555] pg_regress/geometry ERROR: must request at least 2 points 2024-05-05 02:19:50.402 UTC client backend[20555] pg_regress/geometry STATEMENT: SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>'; 2024-05-05 02:19:50.402 UTC client backend[20555] pg_regress/geometry ERROR: cannot convert circle with radius zero to polygon 2024-05-05 02:19:50.402 UTC client backend[20555] pg_regress/geometry STATEMENT: SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>'; 2024-05-05 02:19:50.431 UTC client backend[20555] pg_regress/geometry ERROR: value out of range: overflow 2024-05-05 02:19:50.431 UTC client backend[20555] 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-05-05 02:19:50.432 UTC client backend[20555] pg_regress/geometry ERROR: division by zero 2024-05-05 02:19:50.432 UTC client backend[20555] 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-05-05 02:19:50.489 UTC client backend[20564] pg_regress/horology ERROR: date out of range for timestamp 2024-05-05 02:19:50.489 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamp; 2024-05-05 02:19:50.490 UTC client backend[20564] pg_regress/horology ERROR: date out of range for timestamp 2024-05-05 02:19:50.490 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamptz; 2024-05-05 02:19:50.493 UTC client backend[20564] pg_regress/horology ERROR: date out of range for timestamp 2024-05-05 02:19:50.493 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT '4714-11-24 BC'::date::timestamptz; 2024-05-05 02:19:50.511 UTC client backend[20564] pg_regress/horology ERROR: invalid value "/Feb/16" for "Mon" 2024-05-05 02:19:50.511 UTC client backend[20564] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2024-05-05 02:19:50.511 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('97/Feb/16', 'YYMonDD'); 2024-05-05 02:19:50.525 UTC client backend[20564] pg_regress/horology ERROR: invalid value "JUNK" for "TZ" 2024-05-05 02:19:50.525 UTC client backend[20564] pg_regress/horology DETAIL: Time zone abbreviation is not recognized. 2024-05-05 02:19:50.525 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ'); 2024-05-05 02:19:50.526 UTC client backend[20564] pg_regress/horology ERROR: invalid value ".." for "TZ" 2024-05-05 02:19:50.526 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.526 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ'); 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology ERROR: invalid value "xy" for "OF" 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF'); 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology ERROR: invalid value "xy" for "OF" 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.528 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF'); 2024-05-05 02:19:50.531 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2018-11-02 12:34:56.123456789" 2024-05-05 02:19:50.531 UTC client backend[20564] 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-05-05 02:19:50.533 UTC client backend[20564] pg_regress/horology ERROR: invalid value "+" for "MON" 2024-05-05 02:19:50.533 UTC client backend[20564] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2024-05-05 02:19:50.533 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2000 + + JUN', 'YYYY MON'); 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology ERROR: invalid value "x1" for "MM" 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2011 x12 x18', 'YYYYxMMxDD'); 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology ERROR: invalid combination of date conventions 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology HINT: Do not mix Gregorian and ISO week date conventions in a formatting template. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2005527', 'YYYYIWID'); 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology ERROR: source string too short for "MM" formatting field 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 remain. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('19971', 'YYYYMMDD'); 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology ERROR: invalid value "1)" for "MM" 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 could be parsed. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2024-05-05 02:19:50.535 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('19971)24', 'YYYYMMDD'); 2024-05-05 02:19:50.538 UTC client backend[20564] pg_regress/horology ERROR: invalid value "da" for "DD" 2024-05-05 02:19:50.538 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.538 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY'); 2024-05-05 02:19:50.545 UTC client backend[20564] pg_regress/horology ERROR: invalid value "uary" for "YYYY" 2024-05-05 02:19:50.545 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.545 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY'); 2024-05-05 02:19:50.547 UTC client backend[20564] pg_regress/horology ERROR: conflicting values for "Mon" field in formatting string 2024-05-05 02:19:50.547 UTC client backend[20564] pg_regress/horology DETAIL: This value contradicts a previous setting for the same field type. 2024-05-05 02:19:50.547 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD'); 2024-05-05 02:19:50.550 UTC client backend[20564] pg_regress/horology ERROR: invalid value "xy" for "DD" 2024-05-05 02:19:50.550 UTC client backend[20564] pg_regress/horology DETAIL: Value must be an integer. 2024-05-05 02:19:50.550 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('199711xy', 'YYYYMMDD'); 2024-05-05 02:19:50.551 UTC client backend[20564] pg_regress/horology ERROR: value for "YYYY" in source string is out of range 2024-05-05 02:19:50.551 UTC client backend[20564] pg_regress/horology DETAIL: Value must be in the range -2147483648 to 2147483647. 2024-05-05 02:19:50.551 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('10000000000', 'FMYYYY'); 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 25:00:00" 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:60:00" 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:50:60" 2024-05-05 02:19:50.559 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology ERROR: hour "15" is invalid for the 12-hour clock 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology HINT: Use the 24-hour clock, or give an hour between 1 and 12. 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS'); 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-13-01 15:50:55" 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30 15:50:55" 2024-05-05 02:19:50.560 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.561 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29 15:50:55" 2024-05-05 02:19:50.561 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2024-05-05 02:19:50.562 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2024-05-05 02:19:50.562 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS'); 2024-05-05 02:19:50.563 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2024-05-05 02:19:50.563 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS'); 2024-05-05 02:19:50.564 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-13-10" 2024-05-05 02:19:50.564 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2016-13-10', 'YYYY-MM-DD'); 2024-05-05 02:19:50.567 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30" 2024-05-05 02:19:50.567 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2016-02-30', 'YYYY-MM-DD'); 2024-05-05 02:19:50.567 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29" 2024-05-05 02:19:50.567 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2015-02-29', 'YYYY-MM-DD'); 2024-05-05 02:19:50.569 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2015 366" 2024-05-05 02:19:50.569 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2015 366', 'YYYY DDD'); 2024-05-05 02:19:50.572 UTC client backend[20564] pg_regress/horology ERROR: date/time field value out of range: "2016 367" 2024-05-05 02:19:50.572 UTC client backend[20564] pg_regress/horology STATEMENT: SELECT to_date('2016 367', 'YYYY DDD'); 2024-05-05 02:19:50.856 UTC client backend[20565] pg_regress/regex ERROR: invalid regular expression: regular expression is too complex 2024-05-05 02:19:50.856 UTC client backend[20565] pg_regress/regex STATEMENT: select 'x' ~ repeat('x*y*z*', 1000); 2024-05-05 02:19:50.925 UTC client backend[20565] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2024-05-05 02:19:50.925 UTC client backend[20565] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=\1)'; 2024-05-05 02:19:50.925 UTC client backend[20565] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2024-05-05 02:19:50.925 UTC client backend[20565] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=(\1))'; 2024-05-05 02:19:50.926 UTC client backend[20565] pg_regress/regex ERROR: invalid regular expression: invalid escape \ sequence 2024-05-05 02:19:50.926 UTC client backend[20565] pg_regress/regex STATEMENT: select 'a' ~ '\x7fffffff'; 2024-05-05 02:19:51.306 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.306 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing; 2024-05-05 02:19:51.306 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.306 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing; 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'g') to stdout; 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2024-05-05 02:19:51.311 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2024-05-05 02:19:51.313 UTC client backend[20882] pg_regress/copydml ERROR: DO ALSO rules are not supported for the COPY 2024-05-05 02:19:51.313 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2024-05-05 02:19:51.313 UTC client backend[20882] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.313 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2024-05-05 02:19:51.314 UTC client backend[20882] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.314 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2024-05-05 02:19:51.315 UTC client backend[20882] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2024-05-05 02:19:51.315 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2024-05-05 02:19:51.315 UTC client backend[20884] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2024-05-05 02:19:51.315 UTC client backend[20884] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2024-05-05 02:19:51.315 UTC client backend[20884] pg_regress/copyselect STATEMENT: copy v_test1 to stdout; 2024-05-05 02:19:51.317 UTC client backend[20882] pg_regress/copydml ERROR: DO ALSO rules are not supported for the COPY 2024-05-05 02:19:51.317 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect ERROR: COPY (SELECT INTO) is not supported 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect STATEMENT: copy (select t into temp test3 from test1 where id=3) to stdout; 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect ERROR: syntax error at or near "from" at character 28 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect STATEMENT: copy (select * from test1) from stdin; 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect ERROR: syntax error at or near "(" at character 28 2024-05-05 02:19:51.317 UTC client backend[20884] pg_regress/copyselect STATEMENT: copy (select * from test1) (t,id) to stdout; 2024-05-05 02:19:51.318 UTC client backend[20882] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.318 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2024-05-05 02:19:51.318 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.318 UTC client backend[20886] 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-05-05 02:19:51.319 UTC client backend[20882] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.319 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2024-05-05 02:19:51.319 UTC client backend[20882] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2024-05-05 02:19:51.319 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2024-05-05 02:19:51.320 UTC client backend[20882] pg_regress/copydml ERROR: DO ALSO rules are not supported for the COPY 2024-05-05 02:19:51.320 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2024-05-05 02:19:51.322 UTC client backend[20884] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2024-05-05 02:19:51.322 UTC client backend[20884] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2024-05-05 02:19:51.322 UTC client backend[20884] pg_regress/copyselect STATEMENT: COPY v_test1 TO STDOUT 2024-05-05 02:19:51.327 UTC client backend[20882] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.327 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2024-05-05 02:19:51.328 UTC client backend[20882] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2024-05-05 02:19:51.328 UTC client backend[20882] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2024-05-05 02:19:51.328 UTC client backend[20886] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52 2024-05-05 02:19:51.328 UTC client backend[20886] pg_regress/insert_conflict HINT: For example, ON CONFLICT (column_name). 2024-05-05 02:19:51.328 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit; 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "excluded" at character 117 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict DETAIL: There is an entry for table "excluded", but it cannot be referenced from this part of the query. 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit; 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict ERROR: column "keyy" does not exist at character 64 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key". 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict ERROR: column excluded.fruitt does not exist at character 92 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "excluded.fruit". 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt; 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.329 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.330 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.330 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.330 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.330 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.333 UTC client backend[20889] pg_regress/insert ERROR: null value in column "col2" of relation "inserttest" violates not-null constraint 2024-05-05 02:19:51.333 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (null, null, testing). 2024-05-05 02:19:51.333 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT); 2024-05-05 02:19:51.333 UTC client backend[20884] pg_regress/copyselect ERROR: division by zero 2024-05-05 02:19:51.333 UTC client backend[20884] pg_regress/copyselect STATEMENT: copy (select 1) to stdout; select 1/0; 2024-05-05 02:19:51.333 UTC client backend[20884] pg_regress/copyselect ERROR: division by zero 2024-05-05 02:19:51.333 UTC client backend[20884] pg_regress/copyselect STATEMENT: select 1/0; copy (select 1) to stdout; 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "insertconflicttest" at character 106 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict HINT: Perhaps you meant to reference the table alias "ict". 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit; 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict ERROR: column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict HINT: SET target columns cannot be qualified with the relation name. 2024-05-05 02:19:51.334 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango'; 2024-05-05 02:19:51.336 UTC client backend[20889] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2024-05-05 02:19:51.336 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT); 2024-05-05 02:19:51.336 UTC client backend[20889] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2024-05-05 02:19:51.336 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (1, 2); 2024-05-05 02:19:51.337 UTC client backend[20889] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 42 2024-05-05 02:19:51.337 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (col1) values (1, 2); 2024-05-05 02:19:51.337 UTC client backend[20889] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 48 2024-05-05 02:19:51.337 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (col1) values (DEFAULT, DEFAULT); 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.339 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.343 UTC client backend[20880] pg_regress/copy ERROR: cannot perform COPY FREEZE on a partitioned table 2024-05-05 02:19:51.343 UTC client backend[20880] pg_regress/copy STATEMENT: copy parted_copytest from '/tmp/cirrus-ci-build/build/testrun/regress/regress/results/parted_copytest.csv' (freeze); 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.348 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.351 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.351 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.351 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.351 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.357 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.357 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.359 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.359 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.359 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.359 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.363 UTC client backend[20886] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "fruit_index" 2024-05-05 02:19:51.363 UTC client backend[20886] pg_regress/insert_conflict DETAIL: Key (fruit)=(Peach) already exists. 2024-05-05 02:19:51.363 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.368 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.368 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit; 2024-05-05 02:19:51.369 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.369 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing; 2024-05-05 02:19:51.369 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.369 UTC client backend[20886] 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-05-05 02:19:51.375 UTC client backend[20889] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 32 2024-05-05 02:19:51.375 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (f2[1], f2[2]) values (1,default); 2024-05-05 02:19:51.378 UTC client backend[20889] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 33 2024-05-05 02:19:51.378 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttest (f3.if1, f3.if2) values (1,default); 2024-05-05 02:19:51.398 UTC client backend[20886] pg_regress/insert_conflict ERROR: column excluded.ctid does not exist at character 82 2024-05-05 02:19:51.398 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text; 2024-05-05 02:19:51.406 UTC client backend[20880] pg_regress/copy ERROR: cannot use "match" with HEADER in COPY TO 2024-05-05 02:19:51.406 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest to stdout with (header match); 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy ERROR: header requires a Boolean value or "match" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header wrong_choice); 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy ERROR: column name mismatch in header line field 1: got "a", expected "c" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest (c, b, a) from stdin with (header match); 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy ERROR: column name mismatch in header line field 3: got null value ("\N"), expected "c" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b \N" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy ERROR: wrong number of fields in header line: got 2, expected 3 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy ERROR: wrong number of fields in header line: got 4, expected 3 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c d" 2024-05-05 02:19:51.407 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy ERROR: column name mismatch in header line field 3: got "d", expected "c" 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b d" 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a ........pg.dropped.2........ c" 2024-05-05 02:19:51.408 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2024-05-05 02:19:51.409 UTC client backend[20880] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2024-05-05 02:19:51.409 UTC client backend[20880] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a c b" 2024-05-05 02:19:51.409 UTC client backend[20880] pg_regress/copy STATEMENT: copy header_copytest (a, c) from stdin with (header match); 2024-05-05 02:19:51.415 UTC client backend[20880] pg_regress/copy ERROR: value too long for type character varying(5) 2024-05-05 02:19:51.415 UTC client backend[20880] pg_regress/copy STATEMENT: copy oversized_column_default (col2) from stdin; 2024-05-05 02:19:51.415 UTC client backend[20880] pg_regress/copy ERROR: value too long for type character varying(5) 2024-05-05 02:19:51.415 UTC client backend[20880] pg_regress/copy STATEMENT: copy oversized_column_default from stdin (default ''); 2024-05-05 02:19:51.456 UTC client backend[20889] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 33 2024-05-05 02:19:51.456 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (1,default); 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (0,2); 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6); 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2024-05-05 02:19:51.457 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) select 0,8; 2024-05-05 02:19:51.464 UTC client backend[20886] pg_regress/insert_conflict ERROR: table reference "excluded" is ambiguous at character 76 2024-05-05 02:19:51.464 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *; 2024-05-05 02:19:51.465 UTC client backend[20889] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 34 2024-05-05 02:19:51.465 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,default); 2024-05-05 02:19:51.473 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2024-05-05 02:19:51.473 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,array[null]); 2024-05-05 02:19:51.473 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2024-05-05 02:19:51.473 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}'); 2024-05-05 02:19:51.474 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2024-05-05 02:19:51.474 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}'; 2024-05-05 02:19:51.491 UTC client backend[20886] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "twoconstraints_f1_key" 2024-05-05 02:19:51.491 UTC client backend[20886] pg_regress/insert_conflict DETAIL: Key (f1)=(1) already exists. 2024-05-05 02:19:51.491 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(1, '((2,2),(3,3))'); 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))'); 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2024-05-05 02:19:51.492 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))') on conflict on constraint twoconstraints_f1_key do nothing; 2024-05-05 02:19:51.498 UTC client backend[20886] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2024-05-05 02:19:51.498 UTC client backend[20886] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2024-05-05 02:19:51.498 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0; 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0; 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2024-05-05 02:19:51.499 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0; 2024-05-05 02:19:51.509 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.509 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a; 2024-05-05 02:19:51.533 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_nnarray violates check constraint "insert_nnarray_check" 2024-05-05 02:19:51.533 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttesta (f1[1]) values (1); 2024-05-05 02:19:51.535 UTC client backend[20889] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2024-05-05 02:19:51.535 UTC client backend[20889] pg_regress/insert STATEMENT: insert into inserttestb (f1.if1) values (1); 2024-05-05 02:19:51.544 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2024-05-05 02:19:51.544 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 11). 2024-05-05 02:19:51.544 UTC client backend[20889] pg_regress/insert STATEMENT: insert into range_parted values ('a', 11); 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (a, 11). 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part1 values ('a', 11); 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (b, 1). 2024-05-05 02:19:51.560 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part1 values ('b', 1); 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (b, 21). 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part4 values ('b', 21); 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (a, 10). 2024-05-05 02:19:51.563 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part4 values ('a', 10); 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (null, null). 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part1 values (null); 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (1, null). 2024-05-05 02:19:51.564 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part1 values (1); 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_aa_bb values ('cc', 1); 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (AAa, 1). 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_aa_bb values ('AAa', 1); 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (null, null). 2024-05-05 02:19:51.575 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_aa_bb values (null); 2024-05-05 02:19:51.582 UTC client backend[20886] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2024-05-05 02:19:51.582 UTC client backend[20886] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_1 values (40, 'cuarenta') on conflict (a) do update set b = excluded.b; 2024-05-05 02:19:51.588 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2024-05-05 02:19:51.588 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (aa, 2). 2024-05-05 02:19:51.588 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_default values ('aa', 2); 2024-05-05 02:19:51.589 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2024-05-05 02:19:51.589 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (null, 2). 2024-05-05 02:19:51.589 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_default values (null, 2); 2024-05-05 02:19:51.608 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2024-05-05 02:19:51.608 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (EE, 11). 2024-05-05 02:19:51.608 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('EE', 11); 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_default_p2" violates partition constraint 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (gg, 43). 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_default_p2 values ('gg', 43); 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('cc', 1); 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "part_default" found for row 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (43). 2024-05-05 02:19:51.609 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_default values ('gg', 43); 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 0). 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert STATEMENT: insert into range_parted values ('a', 0); 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 20). 2024-05-05 02:19:51.616 UTC client backend[20889] pg_regress/insert STATEMENT: insert into range_parted values ('a', 20); 2024-05-05 02:19:51.617 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2024-05-05 02:19:51.617 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, null). 2024-05-05 02:19:51.617 UTC client backend[20889] pg_regress/insert STATEMENT: insert into range_parted values ('a'); 2024-05-05 02:19:51.620 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "part_def" violates partition constraint 2024-05-05 02:19:51.620 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (b, 10). 2024-05-05 02:19:51.620 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_def values ('b', 10); 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert STATEMENT: insert into list_parted values ('EE', 0); 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2024-05-05 02:19:51.626 UTC client backend[20889] pg_regress/insert STATEMENT: insert into part_ee_ff values ('EE', 0); 2024-05-05 02:19:51.688 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "hpart0" violates partition constraint 2024-05-05 02:19:51.688 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (11). 2024-05-05 02:19:51.688 UTC client backend[20889] pg_regress/insert STATEMENT: insert into hpart0 values(11); 2024-05-05 02:19:51.753 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted1" found for row 2024-05-05 02:19:51.753 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains ((b + 0)) = (5). 2024-05-05 02:19:51.753 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted (a, b) values (1, 5); 2024-05-05 02:19:51.756 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted11" violates check constraint "check_b" 2024-05-05 02:19:51.756 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (1, 4). 2024-05-05 02:19:51.756 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 2); 2024-05-05 02:19:51.757 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted1" violates partition constraint 2024-05-05 02:19:51.757 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (3, 2). 2024-05-05 02:19:51.757 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted1 (a, b) values (2, 3); 2024-05-05 02:19:51.758 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "lparted_nonullpart" found for row 2024-05-05 02:19:51.758 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (null). 2024-05-05 02:19:51.758 UTC client backend[20889] pg_regress/insert STATEMENT: insert into lparted_nonullpart values (1); 2024-05-05 02:19:51.779 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted5a" violates check constraint "check_b" 2024-05-05 02:19:51.779 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (1, 45, a). 2024-05-05 02:19:51.779 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'a'); 2024-05-05 02:19:51.780 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted5a" violates partition constraint 2024-05-05 02:19:51.780 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (b, 1, 40). 2024-05-05 02:19:51.780 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted5 (a, b, c) values (1, 40, 'a'); 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted_def" found for row 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a) = (70). 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (70, 100); 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted_def1" violates partition constraint 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (52, 50, null). 2024-05-05 02:19:51.787 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted_def1 values (52, 50); 2024-05-05 02:19:51.788 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mlparted_def2" violates partition constraint 2024-05-05 02:19:51.788 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (34, 50, null). 2024-05-05 02:19:51.788 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted_def2 values (34, 50); 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2024-05-05 02:19:51.816 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2024-05-05 02:19:51.834 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2024-05-05 02:19:51.841 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2024-05-05 02:19:51.841 UTC client backend[20889] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2024-05-05 02:19:51.842 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2024-05-05 02:19:51.842 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (1). 2024-05-05 02:19:51.842 UTC client backend[20889] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2024-05-05 02:19:51.842 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "key_desc" found for row 2024-05-05 02:19:51.842 UTC client backend[20889] pg_regress/insert STATEMENT: insert into key_desc values (2, 1); 2024-05-05 02:19:51.853 UTC client backend[20889] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 75 2024-05-05 02:19:51.853 UTC client backend[20889] pg_regress/insert STATEMENT: create table mcrparted0 partition of mcrparted for values from (minvalue, 0, 0) to (1, maxvalue, maxvalue); 2024-05-05 02:19:51.854 UTC client backend[20889] pg_regress/insert ERROR: every bound following MAXVALUE must also be MAXVALUE at character 100 2024-05-05 02:19:51.854 UTC client backend[20889] pg_regress/insert STATEMENT: create table mcrparted2 partition of mcrparted for values from (10, 6, minvalue) to (10, maxvalue, minvalue); 2024-05-05 02:19:51.854 UTC client backend[20889] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 79 2024-05-05 02:19:51.854 UTC client backend[20889] pg_regress/insert STATEMENT: create table mcrparted4 partition of mcrparted for values from (21, minvalue, 0) to (30, 20, minvalue); 2024-05-05 02:19:51.873 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2024-05-05 02:19:51.873 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (null, null, null). 2024-05-05 02:19:51.873 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mcrparted values (null, null, null); 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (11, 1, -1). 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mcrparted values (11, 1, -1); 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mcrparted3" violates partition constraint 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (11, 1, -1). 2024-05-05 02:19:51.890 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mcrparted3 values (11, 1, -1); 2024-05-05 02:19:51.891 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "mcrparted4" violates partition constraint 2024-05-05 02:19:51.891 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (30, 21, 20). 2024-05-05 02:19:51.891 UTC client backend[20889] pg_regress/insert STATEMENT: insert into mcrparted4 values (30, 21, 20); 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert STATEMENT: insert into brtrigpartcon values (1, 'hi there'); 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2024-05-05 02:19:51.925 UTC client backend[20889] pg_regress/insert STATEMENT: insert into brtrigpartcon1 values (1, 'hi there'); 2024-05-05 02:19:51.959 UTC client backend[20889] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2024-05-05 02:19:51.959 UTC client backend[20889] pg_regress/insert DETAIL: Failing row contains (a, b) = (2, hi there). 2024-05-05 02:19:51.959 UTC client backend[20889] pg_regress/insert STATEMENT: with result as (insert into brtrigpartcon values (1, 'hi there') returning 1) insert into inserttest3 (f3) select * from result; 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE unknowntab ( u unknown -- fail ); 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TYPE unknown_comptype AS ( u unknown -- fail ); 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table ERROR: unrecognized parameter "Fillfactor" 2024-05-05 02:19:52.534 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE tas_case WITH ("Fillfactor" = 10) AS SELECT 1 a; 2024-05-05 02:19:52.540 UTC client backend[21226] pg_regress/create_operator ERROR: operator right argument type must be specified 2024-05-05 02:19:52.540 UTC client backend[21226] pg_regress/create_operator DETAIL: Postfix operators are not supported. 2024-05-05 02:19:52.540 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #%# ( leftarg = int8, -- fail, postfix is no longer supported procedure = factorial ); 2024-05-05 02:19:52.540 UTC client backend[21226] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2024-05-05 02:19:52.540 UTC client backend[21226] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (NONE, int4) IS 'bad prefix'; 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: postfix operators are not supported 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, NONE) IS 'bad postfix'; 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, int8) IS 'bad infix'; 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (NONE, int4); 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: postfix operators are not supported 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, NONE); 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, int8); 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: syntax error at or near "=>" at character 17 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR => ( rightarg = int8, procedure = factorial ); 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator ERROR: syntax error at or near ";" at character 14 2024-05-05 02:19:52.541 UTC client backend[21226] pg_regress/create_operator STATEMENT: SELECT 10 !=-; 2024-05-05 02:19:52.543 UTC client backend[21223] pg_regress/create_table ERROR: only temporary relations may be created in temporary schemas at character 23 2024-05-05 02:19:52.543 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE UNLOGGED TABLE pg_temp.unlogged3 (a int primary key); 2024-05-05 02:19:52.544 UTC client backend[21226] pg_regress/create_operator ERROR: permission denied for schema schema_op1 2024-05-05 02:19:52.544 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR schema_op1.#*# ( rightarg = int8, procedure = factorial ); 2024-05-05 02:19:52.544 UTC client backend[21226] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2024-05-05 02:19:52.544 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = SETOF int8, procedure = factorial ); 2024-05-05 02:19:52.545 UTC client backend[21226] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2024-05-05 02:19:52.545 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( rightarg = SETOF int8, procedure = factorial ); 2024-05-05 02:19:52.548 UTC client backend[21223] pg_regress/create_table ERROR: cannot create temporary relation in non-temporary schema at character 19 2024-05-05 02:19:52.548 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TEMP TABLE public.temp_to_perm (a int primary key); 2024-05-05 02:19:52.548 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "invalid_att" not recognized 2024-05-05 02:19:52.548 UTC client backend[21226] pg_regress/create_operator ERROR: operator argument types must be specified 2024-05-05 02:19:52.548 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( procedure = factorial ); 2024-05-05 02:19:52.548 UTC client backend[21226] pg_regress/create_operator ERROR: operator function must be specified 2024-05-05 02:19:52.548 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( rightarg = int8 ); 2024-05-05 02:19:52.550 UTC client backend[21226] pg_regress/create_operator ERROR: permission denied for type type_op3 2024-05-05 02:19:52.550 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = type_op3, rightarg = int8, procedure = fn_op3 ); 2024-05-05 02:19:52.550 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist at character 6 2024-05-05 02:19:52.550 UTC client backend[21227] pg_regress/create_procedure HINT: No procedure matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:52.550 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL nonexistent(); 2024-05-05 02:19:52.551 UTC client backend[21227] pg_regress/create_procedure ERROR: random() is not a procedure at character 6 2024-05-05 02:19:52.551 UTC client backend[21227] pg_regress/create_procedure HINT: To call a function, use SELECT. 2024-05-05 02:19:52.551 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL random(); 2024-05-05 02:19:52.552 UTC client backend[21226] pg_regress/create_operator ERROR: permission denied for type type_op4 2024-05-05 02:19:52.552 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = type_op4, procedure = fn_op4 ); 2024-05-05 02:19:52.554 UTC client backend[21226] pg_regress/create_operator ERROR: permission denied for function fn_op5 2024-05-05 02:19:52.554 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op5 ); 2024-05-05 02:19:52.555 UTC client backend[21226] pg_regress/create_operator ERROR: permission denied for type type_op6 2024-05-05 02:19:52.555 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op6 ); 2024-05-05 02:19:52.556 UTC client backend[21226] pg_regress/create_operator ERROR: operator cannot be its own negator 2024-05-05 02:19:52.556 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = === ); 2024-05-05 02:19:52.557 UTC client backend[21226] pg_regress/create_operator ERROR: operator cannot be its own negator 2024-05-05 02:19:52.557 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR ===!!! ( leftarg = integer, rightarg = integer, procedure = int4ne, negator = ===!!! ); 2024-05-05 02:19:52.557 UTC client backend[21226] pg_regress/create_operator ERROR: commutator operator = is already the commutator of operator = 2024-05-05 02:19:52.557 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, commutator = = ); 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator ERROR: negator operator <> is already the negator of operator = 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = <> ); 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Leftarg" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Rightarg" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Procedure" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Commutator" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Negator" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Restrict" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Join" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Hashes" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator WARNING: operator attribute "Merges" not recognized 2024-05-05 02:19:52.558 UTC client backend[21226] pg_regress/create_operator ERROR: operator function must be specified 2024-05-05 02:19:52.558 UTC client backend[21226] 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-05-05 02:19:52.561 UTC client backend[21223] pg_regress/create_table ERROR: relation "as_select1" already exists 2024-05-05 02:19:52.561 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relkind = 'r'; 2024-05-05 02:19:52.565 UTC client backend[21223] pg_regress/create_table ERROR: relation "as_select1" already exists 2024-05-05 02:19:52.565 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS EXECUTE select1; 2024-05-05 02:19:52.580 UTC client backend[21227] pg_regress/create_procedure ERROR: ptest1(unknown) is a procedure at character 8 2024-05-05 02:19:52.580 UTC client backend[21227] pg_regress/create_procedure HINT: To call a procedure, use CALL. 2024-05-05 02:19:52.580 UTC client backend[21227] pg_regress/create_procedure STATEMENT: SELECT ptest1('x'); 2024-05-05 02:19:52.583 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.583 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE SEQUENCE schema_not_existing.seq; 2024-05-05 02:19:52.584 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.584 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE TABLE schema_not_existing.tab (id int); 2024-05-05 02:19:52.584 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.584 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE VIEW schema_not_existing.view AS SELECT 1; 2024-05-05 02:19:52.585 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.585 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE INDEX ON schema_not_existing.tab (id); 2024-05-05 02:19:52.585 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.585 UTC client backend[21229] 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-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2024-05-05 02:19:52.587 UTC client backend[21229] 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-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2024-05-05 02:19:52.587 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2024-05-05 02:19:52.588 UTC client backend[21229] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2024-05-05 02:19:52.588 UTC client backend[21229] 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-05-05 02:19:52.590 UTC client backend[21235] pg_regress/create_function_c ERROR: could not access file "nosuchfile": No such file or directory 2024-05-05 02:19:52.590 UTC client backend[21235] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C AS 'nosuchfile'; 2024-05-05 02:19:52.592 UTC client backend[21235] pg_regress/create_function_c ERROR: could not find function "nosuchsymbol" in file "/tmp/cirrus-ci-build/build/src/test/regress/regress.so" 2024-05-05 02:19:52.592 UTC client backend[21235] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C AS '/tmp/cirrus-ci-build/build/src/test/regress/regress.so', 'nosuchsymbol'; 2024-05-05 02:19:52.593 UTC client backend[21227] pg_regress/create_procedure ERROR: CREATE TABLE is not yet supported in unquoted SQL function body 2024-05-05 02:19:52.593 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL BEGIN ATOMIC CREATE TABLE x (a int); END; 2024-05-05 02:19:52.593 UTC client backend[21235] pg_regress/create_function_c ERROR: there is no built-in function named "nosuch" 2024-05-05 02:19:52.593 UTC client backend[21235] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE internal AS 'nosuch'; 2024-05-05 02:19:52.598 UTC client backend[21227] pg_regress/create_procedure ERROR: calling procedures with output arguments is not supported in SQL functions 2024-05-05 02:19:52.598 UTC client backend[21227] pg_regress/create_procedure CONTEXT: SQL function "ptest4b" 2024-05-05 02:19:52.598 UTC client backend[21227] 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-05-05 02:19:52.605 UTC client backend[21234] pg_regress/create_type ERROR: type "shell" already exists 2024-05-05 02:19:52.605 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TYPE shell; 2024-05-05 02:19:52.607 UTC client backend[21234] pg_regress/create_type ERROR: type "shell" does not exist 2024-05-05 02:19:52.607 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP TYPE shell; 2024-05-05 02:19:52.611 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure ptest9(numeric) does not exist at character 6 2024-05-05 02:19:52.611 UTC client backend[21227] pg_regress/create_procedure HINT: No procedure matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:52.611 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL ptest9(1./0.); 2024-05-05 02:19:52.614 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2024-05-05 02:19:52.614 UTC client backend[21227] pg_regress/create_procedure HINT: Specify the argument list to select the procedure unambiguously. 2024-05-05 02:19:52.614 UTC client backend[21227] pg_regress/create_procedure STATEMENT: drop procedure ptest10; 2024-05-05 02:19:52.614 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2024-05-05 02:19:52.614 UTC client backend[21227] pg_regress/create_procedure STATEMENT: drop procedure ptest10(int, int, int); 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: version() is not a procedure at character 6 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure HINT: To call a function, use SELECT. 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL version(); 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: sum(integer) is not a procedure at character 6 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure HINT: To call a function, use SELECT. 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL sum(1); 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL WINDOW AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL STRICT AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: VARIADIC parameter must be the last parameter 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a VARIADIC int[], b OUT int) LANGUAGE SQL AS $$ SELECT a[1] $$; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure OUT parameters cannot appear after one with a default value 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a int DEFAULT 42, b OUT int) LANGUAGE SQL AS $$ SELECT a $$; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 30 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE ptest1(text) STRICT; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: ALTER FUNCTION ptest1(text) VOLATILE; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE cp_testfunc1(int) VOLATILE; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE nonexistent() VOLATILE; 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: DROP FUNCTION ptest1(text); 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2024-05-05 02:19:52.616 UTC client backend[21227] pg_regress/create_procedure STATEMENT: DROP PROCEDURE cp_testfunc1(int); 2024-05-05 02:19:52.617 UTC client backend[21227] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2024-05-05 02:19:52.617 UTC client backend[21227] pg_regress/create_procedure STATEMENT: DROP PROCEDURE nonexistent(); 2024-05-05 02:19:52.617 UTC client backend[21227] pg_regress/create_procedure ERROR: permission denied for procedure ptest1 2024-05-05 02:19:52.617 UTC client backend[21227] pg_regress/create_procedure STATEMENT: CALL ptest1('a'); 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Internallength" not recognized at character 27 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Input" not recognized at character 50 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Output" not recognized at character 71 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Alignment" not recognized at character 94 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Default" not recognized at character 115 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type WARNING: type attribute "Passedbyvalue" not recognized at character 132 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type ERROR: type input function must be specified 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type ( "Internallength" = 4, "Input" = int42_in, "Output" = int42_out, "Alignment" = int4, "Default" = 42, "Passedbyvalue" ); 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type ERROR: type input function array_in must return type bogus_type 2024-05-05 02:19:52.632 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2024-05-05 02:19:52.637 UTC client backend[21234] pg_regress/create_type ERROR: type "bogus_type" does not exist 2024-05-05 02:19:52.637 UTC client backend[21234] 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-05-05 02:19:52.637 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2024-05-05 02:19:52.639 UTC client backend[21234] pg_regress/create_type ERROR: type "bad" does not exist 2024-05-05 02:19:52.639 UTC client backend[21234] pg_regress/create_type STATEMENT: COMMENT ON TYPE bad IS 'bad comment'; 2024-05-05 02:19:52.640 UTC client backend[21234] pg_regress/create_type ERROR: column "nope" of relation "default_test_row" does not exist 2024-05-05 02:19:52.640 UTC client backend[21234] pg_regress/create_type STATEMENT: COMMENT ON COLUMN default_test_row.nope IS 'bad comment'; 2024-05-05 02:19:52.640 UTC client backend[21234] pg_regress/create_type ERROR: type "text_w_default" already exists 2024-05-05 02:19:52.640 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TYPE text_w_default; 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type ERROR: cannot drop function base_fn_in(cstring) because other objects depend on it 2024-05-05 02:19:52.642 UTC client backend[21234] 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-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_in(cstring); 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type ERROR: cannot drop function base_fn_out(base_type) because other objects depend on it 2024-05-05 02:19:52.642 UTC client backend[21234] 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-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_out(base_type); 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type ERROR: cannot drop type base_type because other objects depend on it 2024-05-05 02:19:52.642 UTC client backend[21234] 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-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.642 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP TYPE base_type; 2024-05-05 02:19:52.644 UTC client backend[21234] pg_regress/create_type ERROR: invalid NUMERIC type modifier at character 30 2024-05-05 02:19:52.644 UTC client backend[21234] pg_regress/create_type STATEMENT: CREATE TEMP TABLE mytab (foo widget(42,13,7)); 2024-05-05 02:19:52.657 UTC client backend[21234] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2024-05-05 02:19:52.657 UTC client backend[21234] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('(1,2)', 'widget'); 2024-05-05 02:19:52.657 UTC client backend[21234] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2024-05-05 02:19:52.657 UTC client backend[21234] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('{"(1,2)"}', 'widget[]'); 2024-05-05 02:19:52.658 UTC client backend[21234] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2024-05-05 02:19:52.658 UTC client backend[21234] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('("(1,2)")', 'mytab'); 2024-05-05 02:19:52.661 UTC client backend[21234] pg_regress/create_type ERROR: type "myvarchar" is only a shell 2024-05-05 02:19:52.661 UTC client backend[21234] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = extended); 2024-05-05 02:19:52.661 UTC client backend[21234] pg_regress/create_type ERROR: cannot change type's storage to PLAIN 2024-05-05 02:19:52.661 UTC client backend[21234] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = plain); 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table ERROR: syntax error at or near "OIDS" at character 29 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH OIDS; 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids); 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2024-05-05 02:19:52.669 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids = true); 2024-05-05 02:19:52.671 UTC client backend[21234] pg_regress/create_type ERROR: cannot drop function myvarcharsend(myvarchar) because other objects depend on it 2024-05-05 02:19:52.671 UTC client backend[21234] 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-05-05 02:19:52.671 UTC client backend[21234] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.671 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP FUNCTION myvarcharsend(myvarchar); 2024-05-05 02:19:52.672 UTC client backend[21234] pg_regress/create_type ERROR: cannot drop type myvarchar because other objects depend on it 2024-05-05 02:19:52.672 UTC client backend[21234] 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-05-05 02:19:52.672 UTC client backend[21234] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.672 UTC client backend[21234] pg_regress/create_type STATEMENT: DROP TYPE myvarchar; 2024-05-05 02:19:52.678 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2024-05-05 02:19:52.678 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (id)); 2024-05-05 02:19:52.679 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2024-05-05 02:19:52.679 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (bar.id)); 2024-05-05 02:19:52.679 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 59 2024-05-05 02:19:52.679 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg_column (id int DEFAULT (avg(id))); 2024-05-05 02:19:52.680 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 58 2024-05-05 02:19:52.680 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_non_column (a int DEFAULT (avg(non_existent))); 2024-05-05 02:19:52.680 UTC client backend[21223] pg_regress/create_table ERROR: aggregate functions are not allowed in DEFAULT expressions at character 47 2024-05-05 02:19:52.680 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (avg(1))); 2024-05-05 02:19:52.681 UTC client backend[21223] pg_regress/create_table ERROR: cannot use subquery in DEFAULT expression at character 46 2024-05-05 02:19:52.681 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (select 1)); 2024-05-05 02:19:52.682 UTC client backend[21223] pg_regress/create_table ERROR: set-returning functions are not allowed in DEFAULT expressions at character 47 2024-05-05 02:19:52.682 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (generate_series(1,3))); 2024-05-05 02:19:52.688 UTC client backend[21223] pg_regress/create_table ERROR: cannot create partitioned table as inheritance child 2024-05-05 02:19:52.688 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) INHERITS (some_table) PARTITION BY LIST (a); 2024-05-05 02:19:52.688 UTC client backend[21223] pg_regress/create_table ERROR: cannot use "list" partition strategy with more than one column 2024-05-05 02:19:52.688 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a1 int, a2 int ) PARTITION BY LIST (a1, a2); 2024-05-05 02:19:52.689 UTC client backend[21223] pg_regress/create_table ERROR: set-returning functions are not allowed in partition key expressions 2024-05-05 02:19:52.689 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (retset(a)); 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table ERROR: aggregate functions are not allowed in partition key expressions 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((avg(a))); 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table ERROR: window functions are not allowed in partition key expressions 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE ((avg(a) OVER (PARTITION BY b))); 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table ERROR: cannot use subquery in partition key expression 2024-05-05 02:19:52.690 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY LIST ((a LIKE (SELECT 1))); 2024-05-05 02:19:52.691 UTC client backend[21223] pg_regress/create_table ERROR: cannot use constant expression as partition key 2024-05-05 02:19:52.691 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((42)); 2024-05-05 02:19:52.691 UTC client backend[21223] pg_regress/create_table ERROR: cannot use constant expression as partition key 2024-05-05 02:19:52.691 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (const_func()); 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table ERROR: unrecognized partitioning strategy "magic" 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY MAGIC (a); 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table ERROR: column "b" named in partition key does not exist at character 57 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (b); 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table ERROR: cannot use system column "xmin" in partition key at character 57 2024-05-05 02:19:52.692 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (xmin); 2024-05-05 02:19:52.693 UTC client backend[21223] pg_regress/create_table ERROR: partition key column 1 has pseudo-type record 2024-05-05 02:19:52.693 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (((a, b))); 2024-05-05 02:19:52.693 UTC client backend[21223] pg_regress/create_table ERROR: partition key column 2 has pseudo-type unknown 2024-05-05 02:19:52.693 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (a, ('unknown')); 2024-05-05 02:19:52.694 UTC client backend[21223] pg_regress/create_table ERROR: functions in partition key expression must be marked IMMUTABLE 2024-05-05 02:19:52.694 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (immut_func(a)); 2024-05-05 02:19:52.695 UTC client backend[21223] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2024-05-05 02:19:52.695 UTC client backend[21223] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2024-05-05 02:19:52.695 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a); 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a point_ops); 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a); 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2024-05-05 02:19:52.696 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a point_ops); 2024-05-05 02:19:52.697 UTC client backend[21223] pg_regress/create_table ERROR: cannot add NO INHERIT constraint to partitioned table "partitioned" 2024-05-05 02:19:52.697 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, CONSTRAINT check_a CHECK (a > 0) NO INHERIT ) PARTITION BY RANGE (a); 2024-05-05 02:19:52.699 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop function plusone(integer) because other objects depend on it 2024-05-05 02:19:52.699 UTC client backend[21223] pg_regress/create_table DETAIL: table partitioned depends on function plusone(integer) 2024-05-05 02:19:52.699 UTC client backend[21223] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.699 UTC client backend[21223] pg_regress/create_table STATEMENT: DROP FUNCTION plusone(int); 2024-05-05 02:19:52.700 UTC client backend[21223] pg_regress/create_table ERROR: cannot inherit from partitioned table "partitioned2" 2024-05-05 02:19:52.700 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail () INHERITS (partitioned2); 2024-05-05 02:19:52.727 UTC client backend[21223] pg_regress/create_table ERROR: no partition of relation "partitioned2" found for row 2024-05-05 02:19:52.727 UTC client backend[21223] pg_regress/create_table DETAIL: Partition key of the failing row contains ((a + 1), substr(b, 1, 5)) = (2, hello). 2024-05-05 02:19:52.727 UTC client backend[21223] pg_regress/create_table STATEMENT: INSERT INTO partitioned2 VALUES (1, 'hello'); 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table STATEMENT: drop domain intdom1; 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2024-05-05 02:19:52.769 UTC client backend[21223] pg_regress/create_table STATEMENT: table partitioned; 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:52.770 UTC client backend[21223] pg_regress/create_table STATEMENT: drop domain intdom1; 2024-05-05 02:19:52.771 UTC client backend[21223] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2024-05-05 02:19:52.771 UTC client backend[21223] pg_regress/create_table STATEMENT: table partitioned; 2024-05-05 02:19:52.781 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2024-05-05 02:19:52.781 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename); 2024-05-05 02:19:52.784 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2024-05-05 02:19:52.784 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename.somename); 2024-05-05 02:19:52.785 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2024-05-05 02:19:52.785 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (a); 2024-05-05 02:19:52.785 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2024-05-05 02:19:52.785 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(a)); 2024-05-05 02:19:52.786 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2024-05-05 02:19:52.786 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(somename)); 2024-05-05 02:19:52.786 UTC client backend[21223] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 75 2024-05-05 02:19:52.786 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(1)); 2024-05-05 02:19:52.787 UTC client backend[21223] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 75 2024-05-05 02:19:52.787 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((select 1)); 2024-05-05 02:19:52.787 UTC client backend[21223] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 75 2024-05-05 02:19:52.787 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (generate_series(4, 6)); 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table ERROR: collations are not supported by type integer at character 81 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((1+1) collate "POSIX"); 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table ERROR: syntax error at or near ")" at character 64 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES IN (); 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2024-05-05 02:19:52.788 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES FROM (1) TO (2); 2024-05-05 02:19:52.789 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2024-05-05 02:19:52.789 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2024-05-05 02:19:52.791 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "part_default" at character 57 2024-05-05 02:19:52.791 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF list_parted DEFAULT; 2024-05-05 02:19:52.792 UTC client backend[21223] pg_regress/create_table ERROR: specified value cannot be cast to type boolean for column "a" at character 59 2024-05-05 02:19:52.792 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE bools_true PARTITION OF bools FOR VALUES IN (1); 2024-05-05 02:19:52.799 UTC client backend[21223] pg_regress/create_table ERROR: partition "bigintp_10_2" would overlap partition "bigintp_10" at character 63 2024-05-05 02:19:52.799 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE bigintp_10_2 PARTITION OF bigintp FOR VALUES IN ('10'); 2024-05-05 02:19:52.801 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2024-05-05 02:19:52.801 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (somename) TO ('2019-01-01'); 2024-05-05 02:19:52.801 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2024-05-05 02:19:52.801 UTC client backend[21223] 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-05-05 02:19:52.802 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2024-05-05 02:19:52.802 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (a) TO ('2019-01-01'); 2024-05-05 02:19:52.802 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2024-05-05 02:19:52.802 UTC client backend[21223] 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-05-05 02:19:52.803 UTC client backend[21223] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2024-05-05 02:19:52.803 UTC client backend[21223] 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-05-05 02:19:52.803 UTC client backend[21223] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 80 2024-05-05 02:19:52.803 UTC client backend[21223] 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-05-05 02:19:52.804 UTC client backend[21223] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 80 2024-05-05 02:19:52.804 UTC client backend[21223] 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-05-05 02:19:52.804 UTC client backend[21223] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 80 2024-05-05 02:19:52.804 UTC client backend[21223] 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-05-05 02:19:52.805 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2024-05-05 02:19:52.805 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES IN ('a'); 2024-05-05 02:19:52.805 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2024-05-05 02:19:52.805 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2024-05-05 02:19:52.806 UTC client backend[21223] pg_regress/create_table ERROR: FROM must specify exactly one value per partitioning column 2024-05-05 02:19:52.806 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a', 1) TO ('z'); 2024-05-05 02:19:52.807 UTC client backend[21223] pg_regress/create_table ERROR: TO must specify exactly one value per partitioning column 2024-05-05 02:19:52.807 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a') TO ('z', 1); 2024-05-05 02:19:52.807 UTC client backend[21223] pg_regress/create_table ERROR: cannot specify NULL in range bound 2024-05-05 02:19:52.807 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM (null) TO (maxvalue); 2024-05-05 02:19:52.808 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2024-05-05 02:19:52.808 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2024-05-05 02:19:52.811 UTC client backend[21223] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2024-05-05 02:19:52.811 UTC client backend[21223] pg_regress/create_table DETAIL: The new modulus 25 is not divisible by 10, the modulus of existing partition "hpart_4". 2024-05-05 02:19:52.811 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 25, REMAINDER 3); 2024-05-05 02:19:52.812 UTC client backend[21223] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2024-05-05 02:19:52.812 UTC client backend[21223] pg_regress/create_table DETAIL: The new modulus 150 is not a factor of 200, the modulus of existing partition "hpart_3". 2024-05-05 02:19:52.812 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 150, REMAINDER 3); 2024-05-05 02:19:52.812 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "hpart_4" at character 60 2024-05-05 02:19:52.812 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 100, REMAINDER 3); 2024-05-05 02:19:52.813 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2024-05-05 02:19:52.813 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES FROM ('a', 1) TO ('z'); 2024-05-05 02:19:52.813 UTC client backend[21223] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2024-05-05 02:19:52.813 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES IN (1000); 2024-05-05 02:19:52.814 UTC client backend[21223] pg_regress/create_table ERROR: a hash-partitioned table may not have a default partition 2024-05-05 02:19:52.814 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF hash_parted DEFAULT; 2024-05-05 02:19:52.815 UTC client backend[21223] pg_regress/create_table ERROR: "unparted" is not partitioned 2024-05-05 02:19:52.815 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES IN ('a'); 2024-05-05 02:19:52.815 UTC client backend[21223] pg_regress/create_table ERROR: "unparted" is not partitioned 2024-05-05 02:19:52.815 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2024-05-05 02:19:52.816 UTC client backend[21223] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2024-05-05 02:19:52.816 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF temp_parted FOR VALUES IN ('a'); 2024-05-05 02:19:52.826 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_null_z" at character 65 2024-05-05 02:19:52.826 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN (null); 2024-05-05 02:19:52.827 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_ab" at character 65 2024-05-05 02:19:52.827 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('b', 'c'); 2024-05-05 02:19:52.828 UTC client backend[21223] pg_regress/create_table ERROR: updated partition constraint for default partition "list_parted2_def" would be violated by some row 2024-05-05 02:19:52.828 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('W', 'X', 'Y'); 2024-05-05 02:19:52.829 UTC client backend[21223] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2024-05-05 02:19:52.829 UTC client backend[21223] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (0). 2024-05-05 02:19:52.829 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (0); 2024-05-05 02:19:52.831 UTC client backend[21223] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2024-05-05 02:19:52.831 UTC client backend[21223] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (1). 2024-05-05 02:19:52.831 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (1); 2024-05-05 02:19:52.832 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2024-05-05 02:19:52.832 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (minvalue) TO (2); 2024-05-05 02:19:52.834 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2024-05-05 02:19:52.834 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (-1) TO (1); 2024-05-05 02:19:52.834 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part1" at character 68 2024-05-05 02:19:52.834 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (9) TO (maxvalue); 2024-05-05 02:19:52.836 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2024-05-05 02:19:52.836 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (30); 2024-05-05 02:19:52.842 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2024-05-05 02:19:52.842 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (50); 2024-05-05 02:19:52.844 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "range2_default" at character 59 2024-05-05 02:19:52.844 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF range_parted2 DEFAULT; 2024-05-05 02:19:52.845 UTC client backend[21223] pg_regress/create_table ERROR: updated partition constraint for default partition "range2_default" would be violated by some row 2024-05-05 02:19:52.845 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (80) TO (90); 2024-05-05 02:19:52.848 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part00" at character 68 2024-05-05 02:19:52.848 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (0, minvalue) TO (0, 1); 2024-05-05 02:19:52.851 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part12" at character 71 2024-05-05 02:19:52.851 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, 10) TO (1, 20); 2024-05-05 02:19:52.852 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part10" at character 68 2024-05-05 02:19:52.852 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, minvalue) TO (1, maxvalue); 2024-05-05 02:19:52.882 UTC client backend[21223] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "h2part_4" at character 61 2024-05-05 02:19:52.882 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2024-05-05 02:19:52.883 UTC client backend[21223] pg_regress/create_table ERROR: modulus for hash partition must be an integer value greater than zero 2024-05-05 02:19:52.883 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 0, REMAINDER 1); 2024-05-05 02:19:52.883 UTC client backend[21223] pg_regress/create_table ERROR: remainder for hash partition must be less than modulus 2024-05-05 02:19:52.883 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 8, REMAINDER 8); 2024-05-05 02:19:52.887 UTC client backend[21223] pg_regress/create_table ERROR: column "b" specified more than once 2024-05-05 02:19:52.887 UTC client backend[21223] 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-05-05 02:19:52.931 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop inherited constraint "check_a" of relation "part_b" 2024-05-05 02:19:52.931 UTC client backend[21223] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_a; 2024-05-05 02:19:52.932 UTC client backend[21223] pg_regress/create_table ERROR: cannot drop inherited constraint "check_b" of relation "part_b" 2024-05-05 02:19:52.932 UTC client backend[21223] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_b; 2024-05-05 02:19:52.937 UTC client backend[21223] pg_regress/create_table ERROR: column "c" named in partition key does not exist at character 98 2024-05-05 02:19:52.937 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE fail_part_col_not_found PARTITION OF parted FOR VALUES IN ('c') PARTITION BY RANGE (c); 2024-05-05 02:19:52.950 UTC client backend[21223] pg_regress/create_table ERROR: null value in column "b" of relation "parted_notnull_inh_test1" violates not-null constraint 2024-05-05 02:19:52.950 UTC client backend[21223] pg_regress/create_table DETAIL: Failing row contains (1, null). 2024-05-05 02:19:52.950 UTC client backend[21223] pg_regress/create_table STATEMENT: insert into parted_notnull_inh_test (b) values (null); 2024-05-05 02:19:53.208 UTC client backend[21223] pg_regress/create_table ERROR: cannot specify storage parameters for a partitioned table 2024-05-05 02:19:53.208 UTC client backend[21223] pg_regress/create_table HINT: Specify storage parameters for its leaf partitions instead. 2024-05-05 02:19:53.208 UTC client backend[21223] pg_regress/create_table STATEMENT: CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a) WITH (fillfactor=100); 2024-05-05 02:19:53.242 UTC client backend[21223] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2024-05-05 02:19:53.242 UTC client backend[21223] pg_regress/create_table STATEMENT: create table perm_part partition of temp_parted default; 2024-05-05 02:19:53.242 UTC client backend[21223] pg_regress/create_table ERROR: cannot create a temporary relation as partition of permanent relation "perm_parted" 2024-05-05 02:19:53.242 UTC client backend[21223] pg_regress/create_table STATEMENT: create temp table temp_part partition of perm_parted default; 2024-05-05 02:19:53.246 UTC client backend[21223] 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-05-05 02:19:53.246 UTC client backend[21223] 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-05-05 02:19:53.246 UTC client backend[21223] pg_regress/create_table STATEMENT: insert into tab_part_create values (1); 2024-05-05 02:19:53.255 UTC client backend[21223] pg_regress/create_table ERROR: updated partition constraint for default partition "defcheck_def" would be violated by some row 2024-05-05 02:19:53.255 UTC client backend[21223] pg_regress/create_table STATEMENT: create table defcheck_0 partition of defcheck for values in (0); 2024-05-05 02:19:53.575 UTC client backend[21501] pg_regress/create_index ERROR: syntax error at or near "ON" at character 28 2024-05-05 02:19:53.575 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops); 2024-05-05 02:19:53.603 UTC client backend[21498] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_idx_unique" 2024-05-05 02:19:53.603 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2024-05-05 02:19:53.603 UTC client backend[21498] 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-05-05 02:19:53.603 UTC client backend[21498] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_c1_c2_c3_c4_key" 2024-05-05 02:19:53.603 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2024-05-05 02:19:53.603 UTC client backend[21498] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_unique2 add UNIQUE (c1, c2) INCLUDE (c3, c4); 2024-05-05 02:19:53.624 UTC client backend[21498] pg_regress/index_including ERROR: could not create unique index "tbl_include_box_pk_pkey" 2024-05-05 02:19:53.624 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2024-05-05 02:19:53.624 UTC client backend[21498] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_box_pk add PRIMARY KEY (c1, c2) INCLUDE (c3, c4); 2024-05-05 02:19:53.631 UTC client backend[21498] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2024-05-05 02:19:53.631 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2024-05-05 02:19:53.631 UTC client backend[21498] 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-05-05 02:19:53.637 UTC client backend[21499] pg_regress/create_view ERROR: relation "noview" does not exist 2024-05-05 02:19:53.637 UTC client backend[21499] pg_regress/create_view STATEMENT: COMMENT ON VIEW noview IS 'no view'; 2024-05-05 02:19:53.645 UTC client backend[21499] pg_regress/create_view ERROR: cannot drop constraint view_base_table_pkey on table view_base_table because other objects depend on it 2024-05-05 02:19:53.645 UTC client backend[21499] pg_regress/create_view DETAIL: view key_dependent_view depends on constraint view_base_table_pkey on table view_base_table 2024-05-05 02:19:53.645 UTC client backend[21499] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:53.645 UTC client backend[21499] pg_regress/create_view STATEMENT: ALTER TABLE view_base_table DROP CONSTRAINT view_base_table_pkey; 2024-05-05 02:19:53.646 UTC client backend[21498] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2024-05-05 02:19:53.646 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2024-05-05 02:19:53.646 UTC client backend[21498] 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-05-05 02:19:53.646 UTC client backend[21498] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2024-05-05 02:19:53.646 UTC client backend[21498] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2024-05-05 02:19:53.646 UTC client backend[21498] 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-05-05 02:19:53.657 UTC client backend[21499] pg_regress/create_view ERROR: cannot drop columns from view 2024-05-05 02:19:53.657 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a FROM viewtest_tbl WHERE a <> 20; 2024-05-05 02:19:53.657 UTC client backend[21499] pg_regress/create_view ERROR: cannot change name of view column "a" to "?column?" 2024-05-05 02:19:53.657 UTC client backend[21499] pg_regress/create_view HINT: Use ALTER VIEW ... RENAME COLUMN ... to change name of view column instead. 2024-05-05 02:19:53.657 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT 1, * FROM viewtest_tbl; 2024-05-05 02:19:53.658 UTC client backend[21499] pg_regress/create_view ERROR: cannot change data type of view column "b" from integer to numeric 2024-05-05 02:19:53.658 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b::numeric, c, d FROM viewtest_tbl; 2024-05-05 02:19:53.658 UTC client backend[21499] pg_regress/create_view ERROR: cannot change data type of view column "c" from numeric(10,1) to numeric(10,2) 2024-05-05 02:19:53.658 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c::numeric(10,2), d FROM viewtest_tbl; 2024-05-05 02:19:53.659 UTC client backend[21498] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_c1_c2_c3_c4_key" 2024-05-05 02:19:53.659 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2024-05-05 02:19:53.659 UTC client backend[21498] 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-05-05 02:19:53.660 UTC client backend[21499] pg_regress/create_view ERROR: cannot change collation of view column "d" from "C" to "POSIX" 2024-05-05 02:19:53.660 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c, d COLLATE "POSIX" FROM viewtest_tbl; 2024-05-05 02:19:53.665 UTC client backend[21498] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_pkey" 2024-05-05 02:19:53.665 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2024-05-05 02:19:53.665 UTC client backend[21498] 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-05-05 02:19:53.677 UTC client backend[21498] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2024-05-05 02:19:53.677 UTC client backend[21498] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2024-05-05 02:19:53.677 UTC client backend[21498] 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-05-05 02:19:53.679 UTC client backend[21499] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2024-05-05 02:19:53.679 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE VIEW temp_view_test.v3_temp AS SELECT * FROM temp_table; 2024-05-05 02:19:53.679 UTC client backend[21499] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2024-05-05 02:19:53.679 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE SCHEMA test_view_schema CREATE TEMP VIEW testview AS SELECT 1; 2024-05-05 02:19:53.701 UTC client backend[21498] pg_regress/index_including ERROR: conflicting key value violates exclusion constraint "tbl_c1_c3_c4_excl" 2024-05-05 02:19:53.701 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1)=(1) conflicts with existing key (c1)=(1). 2024-05-05 02:19:53.701 UTC client backend[21498] 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-05-05 02:19:53.789 UTC client backend[21498] pg_regress/index_including ERROR: cannot alter statistics on non-expression column "c1" of index "tbl_idx" 2024-05-05 02:19:53.789 UTC client backend[21498] pg_regress/index_including HINT: Alter statistics on table column instead. 2024-05-05 02:19:53.789 UTC client backend[21498] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 1 SET STATISTICS 1000; 2024-05-05 02:19:53.790 UTC client backend[21498] pg_regress/index_including ERROR: cannot alter statistics on included column "c2" of index "tbl_idx" 2024-05-05 02:19:53.790 UTC client backend[21498] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 3 SET STATISTICS 1000; 2024-05-05 02:19:53.790 UTC client backend[21498] pg_regress/index_including ERROR: column number 4 of relation "tbl_idx" does not exist 2024-05-05 02:19:53.790 UTC client backend[21498] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 4 SET STATISTICS 1000; 2024-05-05 02:19:53.834 UTC client backend[21501] pg_regress/create_index ERROR: relation "six_wrong" does not exist 2024-05-05 02:19:53.834 UTC client backend[21501] pg_regress/create_index STATEMENT: COMMENT ON INDEX six_wrong IS 'bad index'; 2024-05-05 02:19:53.837 UTC client backend[21499] pg_regress/create_view ERROR: invalid value for boolean option "security_barrier": 100 2024-05-05 02:19:53.837 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE VIEW mysecview5 WITH (security_barrier=100) -- Error AS SELECT * FROM tbl1 WHERE a > 100; 2024-05-05 02:19:53.837 UTC client backend[21499] pg_regress/create_view ERROR: unrecognized parameter "invalid_option" 2024-05-05 02:19:53.837 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE VIEW mysecview6 WITH (invalid_option) -- Error AS SELECT * FROM tbl1 WHERE a < 100; 2024-05-05 02:19:53.841 UTC client backend[21499] pg_regress/create_view ERROR: invalid value for boolean option "security_invoker": 100 2024-05-05 02:19:53.841 UTC client backend[21499] pg_regress/create_view STATEMENT: CREATE VIEW mysecview10 WITH (security_invoker=100) -- Error AS SELECT * FROM tbl1 WHERE a <> 100; 2024-05-05 02:19:53.857 UTC client backend[21498] pg_regress/index_including ERROR: relation "tbl_c1_c2_c3_c4_key" does not exist 2024-05-05 02:19:53.857 UTC client backend[21498] pg_regress/index_including STATEMENT: REINDEX INDEX tbl_c1_c2_c3_c4_key; 2024-05-05 02:19:53.879 UTC client backend[21498] pg_regress/index_including ERROR: access method "brin" does not support included columns 2024-05-05 02:19:53.879 UTC client backend[21498] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING brin(c1, c2) INCLUDE (c3, c4); 2024-05-05 02:19:53.898 UTC client backend[21498] pg_regress/index_including ERROR: access method "gin" does not support included columns 2024-05-05 02:19:53.898 UTC client backend[21498] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING gin(c1, c2) INCLUDE (c3, c4); 2024-05-05 02:19:53.898 UTC client backend[21498] pg_regress/index_including ERROR: access method "hash" does not support included columns 2024-05-05 02:19:53.898 UTC client backend[21498] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING hash(c1, c2) INCLUDE (c3, c4); 2024-05-05 02:19:53.919 UTC client backend[21498] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_idx_unique" 2024-05-05 02:19:53.919 UTC client backend[21498] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2024-05-05 02:19:53.919 UTC client backend[21498] pg_regress/index_including STATEMENT: UPDATE tbl SET c2 = 2 WHERE c1 = 1; 2024-05-05 02:19:54.218 UTC client backend[21497] pg_regress/index_including_gist ERROR: conflicting key value violates exclusion constraint "tbl_gist_c4_c1_c2_c3_excl" 2024-05-05 02:19:54.218 UTC client backend[21497] pg_regress/index_including_gist DETAIL: Key (c4)=((4,5),(2,3)) conflicts with existing key (c4)=((2,3),(1,2)). 2024-05-05 02:19:54.218 UTC client backend[21497] 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-05-05 02:19:54.281 UTC client backend[21499] pg_regress/create_view ERROR: cannot drop column f3 of table tt14t because other objects depend on it 2024-05-05 02:19:54.281 UTC client backend[21499] pg_regress/create_view DETAIL: view tt14v depends on column f3 of table tt14t 2024-05-05 02:19:54.281 UTC client backend[21499] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:54.281 UTC client backend[21499] pg_regress/create_view STATEMENT: alter table tt14t drop column f3; 2024-05-05 02:19:54.289 UTC client backend[21499] pg_regress/create_view ERROR: attribute 3 of type record has been dropped 2024-05-05 02:19:54.289 UTC client backend[21499] pg_regress/create_view STATEMENT: select * from tt14v; 2024-05-05 02:19:54.290 UTC client backend[21499] pg_regress/create_view ERROR: cannot alter type of a column used by a view or rule 2024-05-05 02:19:54.290 UTC client backend[21499] pg_regress/create_view DETAIL: rule _RETURN on view tt14v depends on column "f4" 2024-05-05 02:19:54.290 UTC client backend[21499] pg_regress/create_view STATEMENT: alter table tt14t alter column f4 type integer using f4::integer; 2024-05-05 02:19:54.298 UTC client backend[21499] pg_regress/create_view ERROR: attribute 4 of type record has wrong type 2024-05-05 02:19:54.298 UTC client backend[21499] pg_regress/create_view DETAIL: Table has type integer, but query expects text. 2024-05-05 02:19:54.298 UTC client backend[21499] pg_regress/create_view STATEMENT: select * from tt14v; 2024-05-05 02:19:54.321 UTC client backend[21501] pg_regress/create_index ERROR: duplicate key value violates unique constraint "unique_idx2" 2024-05-05 02:19:54.321 UTC client backend[21501] pg_regress/create_index DETAIL: Key (i)=(null) already exists. 2024-05-05 02:19:54.321 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO unique_tbl (t) VALUES ('seven'); 2024-05-05 02:19:54.323 UTC client backend[21501] pg_regress/create_index ERROR: could not create unique index "unique_idx4" 2024-05-05 02:19:54.323 UTC client backend[21501] pg_regress/create_index DETAIL: Key (i)=(null) is duplicated. 2024-05-05 02:19:54.323 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX unique_idx4 ON unique_tbl (i) NULLS NOT DISTINCT; 2024-05-05 02:19:54.340 UTC client backend[21501] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2024-05-05 02:19:54.340 UTC client backend[21501] pg_regress/create_index DETAIL: Key (textcat(f1, f2))=(ABCDEF) already exists. 2024-05-05 02:19:54.340 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2024-05-05 02:19:54.341 UTC client backend[21499] pg_regress/create_view ERROR: operator does not exist: text = text[] at character 20 2024-05-05 02:19:54.341 UTC client backend[21499] pg_regress/create_view HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:54.341 UTC client backend[21499] pg_regress/create_view STATEMENT: select 'foo'::text = any((select array['abc','def','foo']::text[])); 2024-05-05 02:19:54.351 UTC client backend[21501] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2024-05-05 02:19:54.351 UTC client backend[21501] pg_regress/create_index DETAIL: Key ((f1 || f2))=(ABCDEF) already exists. 2024-05-05 02:19:54.351 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2024-05-05 02:19:54.359 UTC client backend[21501] pg_regress/create_index ERROR: column "row" has pseudo-type record 2024-05-05 02:19:54.359 UTC client backend[21501] pg_regress/create_index STATEMENT: create index on func_index_heap ((f1 || f2), (row(f1, f2))); 2024-05-05 02:19:54.361 UTC client backend[21501] pg_regress/create_index ERROR: duplicate key value violates unique constraint "covering_index_index" 2024-05-05 02:19:54.361 UTC client backend[21501] pg_regress/create_index DETAIL: Key (f1, f2)=(1, 2) already exists. 2024-05-05 02:19:54.361 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO covering_index_heap VALUES(1,2,'BBB'); 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index ERROR: duplicate key value violates unique constraint "concur_index2" 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index DETAIL: Key (f1)=(b) already exists. 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO concur_heap VALUES ('b','x'); 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2024-05-05 02:19:54.443 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2); 2024-05-05 02:19:54.673 UTC client backend[21501] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:54.673 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_index7 ON concur_heap(f1); 2024-05-05 02:19:54.685 UTC client backend[21501] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2024-05-05 02:19:54.685 UTC client backend[21501] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2024-05-05 02:19:54.685 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE concur_heap; 2024-05-05 02:19:54.792 UTC client backend[21501] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:54.792 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_temp_ind ON concur_temp(f1); 2024-05-05 02:19:54.816 UTC client backend[21501] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY does not support dropping multiple objects 2024-05-05 02:19:54.816 UTC client backend[21501] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index2", "concur_index3"; 2024-05-05 02:19:54.817 UTC client backend[21501] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:54.817 UTC client backend[21501] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index5"; 2024-05-05 02:19:54.907 UTC client backend[21501] pg_regress/create_index ERROR: cannot drop index cwi_replaced_pkey because constraint cwi_replaced_pkey on table cwi_test requires it 2024-05-05 02:19:54.907 UTC client backend[21501] pg_regress/create_index HINT: You can drop constraint cwi_replaced_pkey on table cwi_test instead. 2024-05-05 02:19:54.907 UTC client backend[21501] pg_regress/create_index STATEMENT: DROP INDEX cwi_replaced_pkey; 2024-05-05 02:19:54.909 UTC client backend[21501] pg_regress/create_index ERROR: index "cwi_uniq3_idx" column number 1 does not have default sorting behavior at character 26 2024-05-05 02:19:54.909 UTC client backend[21501] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2024-05-05 02:19:54.909 UTC client backend[21501] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq3_idx; 2024-05-05 02:19:54.910 UTC client backend[21501] pg_regress/create_index ERROR: index "cwi_uniq4_idx" column number 1 does not have default sorting behavior at character 26 2024-05-05 02:19:54.910 UTC client backend[21501] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2024-05-05 02:19:54.910 UTC client backend[21501] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq4_idx; 2024-05-05 02:19:54.917 UTC client backend[21501] pg_regress/create_index ERROR: ALTER TABLE / ADD CONSTRAINT USING INDEX is not supported on partitioned tables 2024-05-05 02:19:54.917 UTC client backend[21501] pg_regress/create_index STATEMENT: alter table cwi_test add primary key using index cwi_test_a_idx ; 2024-05-05 02:19:54.921 UTC client backend[21501] pg_regress/create_index ERROR: primary keys cannot use NULLS NOT DISTINCT indexes 2024-05-05 02:19:54.921 UTC client backend[21501] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD PRIMARY KEY USING INDEX cwi_a_nnd; 2024-05-05 02:19:54.924 UTC client backend[21501] pg_regress/create_index ERROR: relation "syscolcol_table" does not exist 2024-05-05 02:19:54.924 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX ON syscolcol_table (ctid); 2024-05-05 02:19:54.925 UTC client backend[21501] pg_regress/create_index ERROR: index creation on system columns is not supported 2024-05-05 02:19:54.925 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table ((ctid >= '(1000,0)')); 2024-05-05 02:19:54.925 UTC client backend[21501] pg_regress/create_index ERROR: index creation on system columns is not supported 2024-05-05 02:19:54.925 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table (a) WHERE ctid >= '(1000,0)'; 2024-05-05 02:19:55.160 UTC client backend[21501] pg_regress/create_index ERROR: concurrent index creation for exclusion constraints is not supported 2024-05-05 02:19:55.160 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_tab3_c2_excl; 2024-05-05 02:19:55.160 UTC client backend[21501] pg_regress/create_index WARNING: cannot reindex exclusion constraint index "public.concur_reindex_tab3_c2_excl" concurrently, skipping 2024-05-05 02:19:55.188 UTC client backend[21501] pg_regress/create_index ERROR: conflicting key value violates exclusion constraint "concur_reindex_tab3_c2_excl" 2024-05-05 02:19:55.188 UTC client backend[21501] pg_regress/create_index DETAIL: Key (c2)=([2,5)) conflicts with existing key (c2)=([1,3)). 2024-05-05 02:19:55.188 UTC client backend[21501] pg_regress/create_index STATEMENT: INSERT INTO concur_reindex_tab3 VALUES (4, '[2,4]'); 2024-05-05 02:19:55.299 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2024-05-05 02:19:55.299 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index; 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index; 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index_10; 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2024-05-05 02:19:55.300 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index_10; 2024-05-05 02:19:55.301 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX INDEX cannot run inside a transaction block 2024-05-05 02:19:55.301 UTC client backend[21501] pg_regress/create_index CONTEXT: while reindexing partitioned index "public.concur_reindex_part_index" 2024-05-05 02:19:55.301 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_index; 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part; 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part; 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_10; 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2024-05-05 02:19:55.345 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part_10; 2024-05-05 02:19:55.346 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX TABLE cannot run inside a transaction block 2024-05-05 02:19:55.346 UTC client backend[21501] pg_regress/create_index CONTEXT: while reindexing partitioned table "public.concur_reindex_part" 2024-05-05 02:19:55.346 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part; 2024-05-05 02:19:55.380 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:55.380 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_tab; 2024-05-05 02:19:55.380 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.380 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_class; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_class_oid_index; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_toast.pg_toast_1260; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_toast.pg_toast_1260_index; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX SYSTEM CONCURRENTLY postgres; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM postgres; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM; 2024-05-05 02:19:55.381 UTC client backend[21501] pg_regress/create_index WARNING: cannot reindex system catalogs concurrently, skipping all 2024-05-05 02:19:55.382 UTC client backend[21501] pg_regress/create_index ERROR: can only reindex the currently open database 2024-05-05 02:19:55.382 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX DATABASE not_current_database; 2024-05-05 02:19:55.412 UTC client backend[21501] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5" 2024-05-05 02:19:55.412 UTC client backend[21501] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2024-05-05 02:19:55.412 UTC client backend[21501] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_reindex_ind5 ON concur_reindex_tab4 (c1); 2024-05-05 02:19:55.413 UTC client backend[21501] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5_ccnew" 2024-05-05 02:19:55.413 UTC client backend[21501] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2024-05-05 02:19:55.413 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_ind5; 2024-05-05 02:19:55.432 UTC client backend[21501] pg_regress/create_index WARNING: skipping reindex of invalid index "public.concur_reindex_ind5" 2024-05-05 02:19:55.432 UTC client backend[21501] pg_regress/create_index HINT: Use DROP INDEX or REINDEX INDEX. 2024-05-05 02:19:55.536 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:55.536 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_1; 2024-05-05 02:19:55.543 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2024-05-05 02:19:55.543 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_3; 2024-05-05 02:19:55.574 UTC client backend[21501] pg_regress/create_index ERROR: schema "schema_to_reindex" does not exist 2024-05-05 02:19:55.574 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2024-05-05 02:19:55.651 UTC client backend[21501] pg_regress/create_index ERROR: REINDEX SCHEMA cannot run inside a transaction block 2024-05-05 02:19:55.651 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2024-05-05 02:19:55.673 UTC client backend[21501] pg_regress/create_index ERROR: must be owner of schema schema_to_reindex 2024-05-05 02:19:55.673 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2024-05-05 02:19:55.675 UTC client backend[21501] pg_regress/create_index ERROR: permission denied for table pg_toast_1260 2024-05-05 02:19:55.675 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX TABLE pg_toast.pg_toast_1260; 2024-05-05 02:19:55.675 UTC client backend[21501] pg_regress/create_index ERROR: permission denied for index pg_toast_1260_index 2024-05-05 02:19:55.675 UTC client backend[21501] pg_regress/create_index STATEMENT: REINDEX INDEX pg_toast.pg_toast_1260_index; 2024-05-05 02:19:55.800 UTC client backend[21993] pg_regress/create_am ERROR: function int4in(internal) does not exist 2024-05-05 02:19:55.800 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER int4in; 2024-05-05 02:19:55.800 UTC client backend[21993] pg_regress/create_am ERROR: function heap_tableam_handler must return type index_am_handler 2024-05-05 02:19:55.800 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER heap_tableam_handler; 2024-05-05 02:19:55.800 UTC client backend[21996] pg_regress/create_aggregate ERROR: aggregate newavg_wrong(integer) does not exist 2024-05-05 02:19:55.800 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE newavg_wrong (int4) IS 'an agg comment'; 2024-05-05 02:19:55.803 UTC client backend[21993] pg_regress/create_am ERROR: data type box has no default operator class for access method "gist2" 2024-05-05 02:19:55.803 UTC client backend[21993] 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-05-05 02:19:55.803 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE INDEX grect2ind2 ON fast_emp4000 USING gist2 (home_base); 2024-05-05 02:19:55.809 UTC client backend[21996] pg_regress/create_aggregate ERROR: aggregate nosuchagg(*) does not exist 2024-05-05 02:19:55.809 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE nosuchagg (*) IS 'should fail'; 2024-05-05 02:19:55.817 UTC client backend[21996] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2024-05-05 02:19:55.817 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2024-05-05 02:19:55.818 UTC client backend[21995] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2024-05-05 02:19:55.818 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2024-05-05 02:19:55.818 UTC client backend[21990] pg_regress/typed_table ERROR: type "nothing" does not exist 2024-05-05 02:19:55.818 UTC client backend[21990] pg_regress/typed_table STATEMENT: CREATE TABLE ttable1 OF nothing; 2024-05-05 02:19:55.820 UTC client backend[21992] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 15 2024-05-05 02:19:55.820 UTC client backend[21992] pg_regress/errors STATEMENT: select * from nonesuch; 2024-05-05 02:19:55.822 UTC client backend[21992] pg_regress/errors ERROR: column "nonesuch" does not exist at character 8 2024-05-05 02:19:55.822 UTC client backend[21992] pg_regress/errors STATEMENT: select nonesuch from pg_database; 2024-05-05 02:19:55.823 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "from" at character 17 2024-05-05 02:19:55.823 UTC client backend[21992] pg_regress/errors STATEMENT: select distinct from pg_database; 2024-05-05 02:19:55.823 UTC client backend[21992] pg_regress/errors ERROR: column "nonesuch" does not exist at character 33 2024-05-05 02:19:55.823 UTC client backend[21992] pg_regress/errors STATEMENT: select * from pg_database where nonesuch = pg_database.datname; 2024-05-05 02:19:55.824 UTC client backend[21999] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2024-05-05 02:19:55.824 UTC client backend[21999] pg_regress/create_cast HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:55.824 UTC client backend[21999] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2024-05-05 02:19:55.825 UTC client backend[21999] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2024-05-05 02:19:55.825 UTC client backend[21999] pg_regress/create_cast HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:55.825 UTC client backend[21999] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2024-05-05 02:19:55.825 UTC client backend[21992] pg_regress/errors ERROR: column "nonesuch" does not exist at character 55 2024-05-05 02:19:55.825 UTC client backend[21992] pg_regress/errors STATEMENT: select * from pg_database where pg_database.datname = nonesuch; 2024-05-05 02:19:55.826 UTC client backend[21992] pg_regress/errors ERROR: column "foobar" does not exist at character 21 2024-05-05 02:19:55.826 UTC client backend[21992] pg_regress/errors STATEMENT: select distinct on (foobar) * from pg_database; 2024-05-05 02:19:55.827 UTC client backend[21992] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2024-05-05 02:19:55.827 UTC client backend[21992] pg_regress/errors STATEMENT: select null from pg_database group by datname for update; 2024-05-05 02:19:55.827 UTC client backend[21992] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2024-05-05 02:19:55.827 UTC client backend[21992] pg_regress/errors STATEMENT: select null from pg_database group by grouping sets (()) for update; 2024-05-05 02:19:55.828 UTC client backend[21985] pg_regress/triggers ERROR: trigger "check_fkeys2_pkey_bad" for table "fkeys2" does not exist 2024-05-05 02:19:55.828 UTC client backend[21985] pg_regress/triggers STATEMENT: COMMENT ON TRIGGER check_fkeys2_pkey_bad ON fkeys2 IS 'wrong'; 2024-05-05 02:19:55.828 UTC client backend[21999] pg_regress/create_cast ERROR: cannot cast type integer to casttesttype at character 18 2024-05-05 02:19:55.828 UTC client backend[21999] pg_regress/create_cast STATEMENT: SELECT 1234::int4::casttesttype; 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 12 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors STATEMENT: delete from; 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 13 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors STATEMENT: delete from nonesuch; 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2024-05-05 02:19:55.828 UTC client backend[21992] pg_regress/errors STATEMENT: drop table; 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors ERROR: table "nonesuch" does not exist 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors STATEMENT: drop table nonesuch; 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 19 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors STATEMENT: alter table rename; 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors ERROR: relation "nonesuch" does not exist 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors STATEMENT: alter table nonesuch rename to newnonesuch; 2024-05-05 02:19:55.829 UTC client backend[21995] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2024-05-05 02:19:55.829 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors ERROR: relation "nonesuch" does not exist 2024-05-05 02:19:55.829 UTC client backend[21992] pg_regress/errors STATEMENT: alter table nonesuch rename to stud_emp; 2024-05-05 02:19:55.830 UTC client backend[21992] pg_regress/errors ERROR: relation "student" already exists 2024-05-05 02:19:55.830 UTC client backend[21992] pg_regress/errors STATEMENT: alter table stud_emp rename to student; 2024-05-05 02:19:55.830 UTC client backend[21992] pg_regress/errors ERROR: relation "stud_emp" already exists 2024-05-05 02:19:55.830 UTC client backend[21992] pg_regress/errors STATEMENT: alter table stud_emp rename to stud_emp; 2024-05-05 02:19:55.831 UTC client backend[21992] pg_regress/errors ERROR: relation "nonesuchrel" does not exist 2024-05-05 02:19:55.831 UTC client backend[21992] pg_regress/errors STATEMENT: alter table nonesuchrel rename column nonesuchatt to newnonesuchatt; 2024-05-05 02:19:55.831 UTC client backend[21992] pg_regress/errors ERROR: column "nonesuchatt" does not exist 2024-05-05 02:19:55.831 UTC client backend[21992] pg_regress/errors STATEMENT: alter table emp rename column nonesuchatt to newnonesuchatt; 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors ERROR: column "manager" of relation "stud_emp" already exists 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors STATEMENT: alter table emp rename column salary to manager; 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors ERROR: column name "ctid" conflicts with a system column name 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors STATEMENT: alter table emp rename column salary to ctid; 2024-05-05 02:19:55.833 UTC client backend[21997] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2024-05-05 02:19:55.833 UTC client backend[21997] pg_regress/hash_func STATEMENT: SELECT v as value, hash_array(v)::bit(32) as standard FROM (VALUES ('{101}'::varbit[])) x(v); 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors WARNING: there is no transaction in progress 2024-05-05 02:19:55.833 UTC client backend[21996] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2024-05-05 02:19:55.833 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2024-05-05 02:19:55.833 UTC client backend[21992] pg_regress/errors WARNING: there is no transaction in progress 2024-05-05 02:19:55.834 UTC client backend[21997] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2024-05-05 02:19:55.834 UTC client backend[21997] 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-05-05 02:19:55.834 UTC client backend[21992] pg_regress/errors ERROR: function int2um(integer) does not exist 2024-05-05 02:19:55.834 UTC client backend[21992] pg_regress/errors STATEMENT: create aggregate newavg2 (sfunc = int4pl, basetype = int4, stype = int4, finalfunc = int2um, initcond = '0'); 2024-05-05 02:19:55.835 UTC client backend[21992] pg_regress/errors ERROR: aggregate input type must be specified 2024-05-05 02:19:55.835 UTC client backend[21992] pg_regress/errors STATEMENT: create aggregate newcnt1 (sfunc = int4inc, stype = int4, initcond = '0'); 2024-05-05 02:19:55.836 UTC client backend[21985] pg_regress/triggers ERROR: tuple references non-existent key 2024-05-05 02:19:55.836 UTC client backend[21985] pg_regress/triggers DETAIL: Trigger "check_fkeys2_pkey_exist" found tuple referencing non-existent key in "pkeys". 2024-05-05 02:19:55.836 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into fkeys2 values (70, '5', 3); 2024-05-05 02:19:55.836 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2024-05-05 02:19:55.836 UTC client backend[21992] pg_regress/errors STATEMENT: drop index; 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "314159" at character 12 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors STATEMENT: drop index 314159; 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors ERROR: index "nonesuch" does not exist 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors STATEMENT: drop index nonesuch; 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 15 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate; 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 23 2024-05-05 02:19:55.837 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate newcnt1; 2024-05-05 02:19:55.838 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "314159" at character 16 2024-05-05 02:19:55.838 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate 314159 (int); 2024-05-05 02:19:55.838 UTC client backend[21992] pg_regress/errors ERROR: type "nonesuch" does not exist 2024-05-05 02:19:55.838 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate newcnt (nonesuch); 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors ERROR: aggregate nonesuch(integer) does not exist 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate nonesuch (int4); 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors ERROR: aggregate newcnt(real) does not exist 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors STATEMENT: drop aggregate newcnt (float4); 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors STATEMENT: drop function (); 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "314159" at character 15 2024-05-05 02:19:55.839 UTC client backend[21992] pg_regress/errors STATEMENT: drop function 314159(); 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors ERROR: function nonesuch() does not exist 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors STATEMENT: drop function nonesuch(); 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors STATEMENT: drop type; 2024-05-05 02:19:55.840 UTC client backend[21995] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2024-05-05 02:19:55.840 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2024-05-05 02:19:55.840 UTC client backend[21992] pg_regress/errors STATEMENT: drop type 314159; 2024-05-05 02:19:55.841 UTC client backend[21992] pg_regress/errors ERROR: type "nonesuch" does not exist 2024-05-05 02:19:55.841 UTC client backend[21992] pg_regress/errors STATEMENT: drop type nonesuch; 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator; 2024-05-05 02:19:55.842 UTC client backend[21995] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2024-05-05 02:19:55.842 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 21 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator equals; 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 18 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator ===; 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "," at character 19 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator int4, int4; 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator (int4, int4); 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ")" at character 20 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator === (); 2024-05-05 02:19:55.842 UTC client backend[21985] pg_regress/triggers ERROR: tuple references non-existent key 2024-05-05 02:19:55.842 UTC client backend[21985] pg_regress/triggers DETAIL: Trigger "check_fkeys_pkey_exist" found tuple referencing non-existent key in "pkeys". 2024-05-05 02:19:55.842 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into fkeys values (70, '5', 1); 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors ERROR: missing argument at character 24 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2024-05-05 02:19:55.842 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator === (int4); 2024-05-05 02:19:55.843 UTC client backend[21992] pg_regress/errors ERROR: operator does not exist: integer === integer 2024-05-05 02:19:55.843 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator === (int4, int4); 2024-05-05 02:19:55.843 UTC client backend[21992] pg_regress/errors ERROR: missing argument at character 26 2024-05-05 02:19:55.843 UTC client backend[21992] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2024-05-05 02:19:55.843 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator = (nonesuch); 2024-05-05 02:19:55.844 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "," at character 19 2024-05-05 02:19:55.844 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator = ( , int4); 2024-05-05 02:19:55.845 UTC client backend[21992] pg_regress/errors ERROR: type "nonesuch" does not exist 2024-05-05 02:19:55.845 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator = (nonesuch, int4); 2024-05-05 02:19:55.845 UTC client backend[21992] pg_regress/errors ERROR: type "nonesuch" does not exist 2024-05-05 02:19:55.845 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator = (int4, nonesuch); 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ")" at character 24 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors STATEMENT: drop operator = (int4, ); 2024-05-05 02:19:55.846 UTC client backend[21985] pg_regress/triggers ERROR: tuple references non-existent key 2024-05-05 02:19:55.846 UTC client backend[21985] pg_regress/triggers DETAIL: Trigger "check_fkeys_pkey2_exist" found tuple referencing non-existent key in "fkeys2". 2024-05-05 02:19:55.846 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into fkeys values (60, '6', 4); 2024-05-05 02:19:55.846 UTC client backend[21994] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2024-05-05 02:19:55.846 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: ALTER FUNCTION functest_E_2(int) LEAKPROOF; 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors STATEMENT: drop rule; 2024-05-05 02:19:55.846 UTC client backend[21994] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2024-05-05 02:19:55.846 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_E_3(int) RETURNS bool LANGUAGE 'sql' LEAKPROOF AS 'SELECT $1 < 200'; 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors STATEMENT: drop rule 314159; 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors ERROR: relation "noplace" does not exist 2024-05-05 02:19:55.846 UTC client backend[21992] pg_regress/errors STATEMENT: drop rule nonesuch on noplace; 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "tuple" at character 6 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors STATEMENT: drop tuple rule nonesuch; 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "instance" at character 6 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors STATEMENT: drop instance rule nonesuch on noplace; 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "rewrite" at character 6 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors STATEMENT: drop rewrite rule nonesuch; 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.847 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0; 2024-05-05 02:19:55.848 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.848 UTC client backend[21992] pg_regress/errors STATEMENT: select 1::int8/0; 2024-05-05 02:19:55.848 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.848 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0::int8; 2024-05-05 02:19:55.849 UTC client backend[21985] pg_regress/triggers ERROR: "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys" 2024-05-05 02:19:55.849 UTC client backend[21985] pg_regress/triggers CONTEXT: SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 " 2024-05-05 02:19:55.849 UTC client backend[21985] pg_regress/triggers STATEMENT: delete from pkeys where pkey1 = 30 and pkey2 = '3'; 2024-05-05 02:19:55.849 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.849 UTC client backend[21992] pg_regress/errors STATEMENT: select 1::int2/0; 2024-05-05 02:19:55.849 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.849 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0::int2; 2024-05-05 02:19:55.851 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.851 UTC client backend[21992] pg_regress/errors STATEMENT: select 1::numeric/0; 2024-05-05 02:19:55.851 UTC client backend[21985] pg_regress/triggers ERROR: "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys" 2024-05-05 02:19:55.851 UTC client backend[21985] pg_regress/triggers CONTEXT: SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 " 2024-05-05 02:19:55.851 UTC client backend[21985] pg_regress/triggers STATEMENT: update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 50 and pkey2 = '5'; 2024-05-05 02:19:55.852 UTC client backend[21995] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2024-05-05 02:19:55.852 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2024-05-05 02:19:55.852 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.852 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0::numeric; 2024-05-05 02:19:55.853 UTC client backend[21995] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2024-05-05 02:19:55.853 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2024-05-05 02:19:55.853 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.853 UTC client backend[21992] pg_regress/errors STATEMENT: select 1::float8/0; 2024-05-05 02:19:55.854 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.854 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0::float8; 2024-05-05 02:19:55.855 UTC client backend[21987] pg_regress/constraints ERROR: syntax error at or near ")" at character 45 2024-05-05 02:19:55.855 UTC client backend[21987] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (i int DEFAULT (100, )); 2024-05-05 02:19:55.855 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.855 UTC client backend[21992] pg_regress/errors STATEMENT: select 1::float4/0; 2024-05-05 02:19:55.855 UTC client backend[21987] pg_regress/constraints ERROR: syntax error at or near "IN" at character 43 2024-05-05 02:19:55.855 UTC client backend[21987] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (b1 bool DEFAULT 1 IN (1, 2)); 2024-05-05 02:19:55.857 UTC client backend[21992] pg_regress/errors ERROR: division by zero 2024-05-05 02:19:55.857 UTC client backend[21992] pg_regress/errors STATEMENT: select 1/0::float4; 2024-05-05 02:19:55.857 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "xxx" at character 1 2024-05-05 02:19:55.857 UTC client backend[21992] pg_regress/errors STATEMENT: xxx; 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "foo" at character 8 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors STATEMENT: CREATE foo; 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors STATEMENT: CREATE TABLE ; 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors ERROR: syntax error at end of input at character 13 2024-05-05 02:19:55.858 UTC client backend[21992] pg_regress/errors STATEMENT: CREATE TABLE 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "foo" at character 29 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) foo; 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "123" at character 13 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors STATEMENT: INSERT INTO 123 VALUES(123); 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "123" at character 29 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) 123 ; 2024-05-05 02:19:55.860 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 94 2024-05-05 02:19:55.860 UTC client backend[21992] 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-05-05 02:19:55.861 UTC client backend[21995] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2024-05-05 02:19:55.861 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2024-05-05 02:19:55.861 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2024-05-05 02:19:55.861 UTC client backend[21992] 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-05-05 02:19:55.861 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 35 2024-05-05 02:19:55.861 UTC client backend[21992] 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-05-05 02:19:55.861 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2024-05-05 02:19:55.861 UTC client backend[21992] 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-05-05 02:19:55.861 UTC client backend[21995] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2024-05-05 02:19:55.861 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2024-05-05 02:19:55.861 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 100 2024-05-05 02:19:55.861 UTC client backend[21992] 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-05-05 02:19:55.862 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 45 2024-05-05 02:19:55.862 UTC client backend[21992] 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-05-05 02:19:55.863 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 153 2024-05-05 02:19:55.863 UTC client backend[21992] 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-05-05 02:19:55.863 UTC client backend[21992] pg_regress/errors ERROR: syntax error at or near "NUL" at character 180 2024-05-05 02:19:55.863 UTC client backend[21992] 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-05-05 02:19:55.865 UTC client backend[21995] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2024-05-05 02:19:55.865 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2024-05-05 02:19:55.865 UTC client backend[21995] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2024-05-05 02:19:55.865 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2024-05-05 02:19:55.871 UTC client backend[21995] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2024-05-05 02:19:55.871 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2024-05-05 02:19:55.872 UTC client backend[21995] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2024-05-05 02:19:55.872 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2024-05-05 02:19:55.878 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2024-05-05 02:19:55.878 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (3). 2024-05-05 02:19:55.878 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (3); 2024-05-05 02:19:55.879 UTC client backend[21995] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2024-05-05 02:19:55.879 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate ERROR: must specify both or neither of serialization and deserialization functions 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize ); 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate ERROR: function numeric_avg_deserialize(internal) does not exist 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_deserialize, deserialfunc = numeric_avg_deserialize ); 2024-05-05 02:19:55.879 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2024-05-05 02:19:55.879 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (2). 2024-05-05 02:19:55.879 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (2); 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate ERROR: function numeric_avg_serialize(bytea, internal) does not exist 2024-05-05 02:19:55.879 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize, deserialfunc = numeric_avg_serialize ); 2024-05-05 02:19:55.880 UTC client backend[21996] pg_regress/create_aggregate ERROR: function int4larger(internal, internal) does not exist 2024-05-05 02:19:55.880 UTC client backend[21996] 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-05-05 02:19:55.881 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2024-05-05 02:19:55.881 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (1). 2024-05-05 02:19:55.881 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (1); 2024-05-05 02:19:55.882 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_u2" does not exist 2024-05-05 02:19:55.882 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u2; 2024-05-05 02:19:55.884 UTC client backend[21994] pg_regress/create_function_sql ERROR: duplicate function body specified 2024-05-05 02:19:55.884 UTC client backend[21994] 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-05-05 02:19:55.885 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_u1" does not exist 2024-05-05 02:19:55.885 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u1; 2024-05-05 02:19:55.885 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_r2" does not exist 2024-05-05 02:19:55.885 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r2; 2024-05-05 02:19:55.886 UTC client backend[21997] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2024-05-05 02:19:55.886 UTC client backend[21997] 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-05-05 02:19:55.886 UTC client backend[21994] pg_regress/create_function_sql ERROR: SQL function with unquoted function body cannot have polymorphic arguments 2024-05-05 02:19:55.886 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x anyarray) RETURNS anyelement LANGUAGE SQL RETURN x[1]; 2024-05-05 02:19:55.886 UTC client backend[21997] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2024-05-05 02:19:55.886 UTC client backend[21997] 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-05-05 02:19:55.888 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_r1" does not exist 2024-05-05 02:19:55.888 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r1; 2024-05-05 02:19:55.888 UTC client backend[21994] pg_regress/create_function_sql ERROR: operator does not exist: date > integer at character 85 2024-05-05 02:19:55.888 UTC client backend[21994] pg_regress/create_function_sql HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2024-05-05 02:19:55.888 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x date) RETURNS boolean LANGUAGE SQL RETURN x > 1; 2024-05-05 02:19:55.888 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_g2" does not exist 2024-05-05 02:19:55.888 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g2; 2024-05-05 02:19:55.889 UTC client backend[21995] pg_regress/drop_if_exists ERROR: role "regress_test_g1" does not exist 2024-05-05 02:19:55.889 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g1; 2024-05-05 02:19:55.890 UTC client backend[21995] pg_regress/drop_if_exists ERROR: conversion "test_conversion_exists" does not exist 2024-05-05 02:19:55.890 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP CONVERSION test_conversion_exists; 2024-05-05 02:19:55.895 UTC client backend[21995] pg_regress/drop_if_exists ERROR: text search parser "test_tsparser_exists" does not exist 2024-05-05 02:19:55.895 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH PARSER test_tsparser_exists; 2024-05-05 02:19:55.896 UTC client backend[21995] pg_regress/drop_if_exists ERROR: text search dictionary "test_tsdict_exists" does not exist 2024-05-05 02:19:55.896 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH DICTIONARY test_tsdict_exists; 2024-05-05 02:19:55.898 UTC client backend[21996] pg_regress/create_aggregate ERROR: cannot change return type of existing function 2024-05-05 02:19:55.898 UTC client backend[21996] pg_regress/create_aggregate HINT: Use DROP AGGREGATE myavg(numeric) first. 2024-05-05 02:19:55.898 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (numeric) ( stype = numeric, sfunc = numeric_add, finalfunc = numeric_out ); 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (1, x check failed, -2). 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (1, 'x check failed', -2); 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (5, z check failed, 10). 2024-05-05 02:19:55.898 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (5, 'z check failed', 10); 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (0, check failed, -2). 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (0, 'check failed', -2); 2024-05-05 02:19:55.899 UTC client backend[21996] pg_regress/create_aggregate ERROR: cannot change routine kind 2024-05-05 02:19:55.899 UTC client backend[21996] pg_regress/create_aggregate DETAIL: "myavg" is an ordinary aggregate function. 2024-05-05 02:19:55.899 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (order by numeric) ( stype = numeric, sfunc = numeric_add ); 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (6, check failed, 11). 2024-05-05 02:19:55.899 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (6, 'check failed', 11); 2024-05-05 02:19:55.902 UTC client backend[21996] pg_regress/create_aggregate ERROR: cannot change routine kind 2024-05-05 02:19:55.902 UTC client backend[21996] pg_regress/create_aggregate DETAIL: "sum3" is a function. 2024-05-05 02:19:55.902 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE sum3 (int8,int8,int8) ( stype = int8, sfunc = sum4 ); 2024-05-05 02:19:55.903 UTC client backend[21995] pg_regress/drop_if_exists ERROR: text search template "test_tstemplate_exists" does not exist 2024-05-05 02:19:55.903 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH TEMPLATE test_tstemplate_exists; 2024-05-05 02:19:55.904 UTC client backend[21995] pg_regress/drop_if_exists ERROR: text search configuration "test_tsconfig_exists" does not exist 2024-05-05 02:19:55.904 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH CONFIGURATION test_tsconfig_exists; 2024-05-05 02:19:55.909 UTC client backend[21996] pg_regress/create_aggregate ERROR: parameter "parallel" must be SAFE, RESTRICTED, or UNSAFE 2024-05-05 02:19:55.909 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE mysum (int) ( stype = int, sfunc = int4pl, parallel = pear ); 2024-05-05 02:19:55.909 UTC client backend[21990] pg_regress/typed_table ERROR: cannot add column to typed table 2024-05-05 02:19:55.909 UTC client backend[21990] pg_regress/typed_table STATEMENT: ALTER TABLE persons ADD COLUMN comment text; 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table ERROR: cannot drop column from typed table 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table STATEMENT: ALTER TABLE persons DROP COLUMN name; 2024-05-05 02:19:55.910 UTC client backend[21996] pg_regress/create_aggregate ERROR: strictness of aggregate's forward and inverse transition functions must match 2024-05-05 02:19:55.910 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE invalidsumdouble (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_n ); 2024-05-05 02:19:55.910 UTC client backend[21995] pg_regress/drop_if_exists ERROR: extension "test_extension_exists" does not exist 2024-05-05 02:19:55.910 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP EXTENSION test_extension_exists; 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table ERROR: cannot rename column of typed table 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table STATEMENT: ALTER TABLE persons RENAME COLUMN id TO num; 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table ERROR: cannot alter column type of typed table 2024-05-05 02:19:55.910 UTC client backend[21990] pg_regress/typed_table STATEMENT: ALTER TABLE persons ALTER COLUMN name TYPE varchar; 2024-05-05 02:19:55.911 UTC client backend[21995] pg_regress/drop_if_exists ERROR: function test_function_exists() does not exist 2024-05-05 02:19:55.911 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(); 2024-05-05 02:19:55.913 UTC client backend[21995] pg_regress/drop_if_exists ERROR: function test_function_exists(integer, text, integer[]) does not exist 2024-05-05 02:19:55.913 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(int, text, int[]); 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate ERROR: return type of inverse transition function float8mi_int is not double precision 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE wrongreturntype (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_int ); 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc1" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Basetype" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Stype1" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Initcond1" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE case_agg ( -- old syntax "Sfunc1" = int4pl, "Basetype" = int4, "Stype1" = int4, "Initcond1" = '0', "Parallel" = safe ); 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Stype" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_extra" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_modify" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2024-05-05 02:19:55.913 UTC client backend[21996] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2024-05-05 02:19:55.913 UTC client backend[21996] 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-05-05 02:19:55.914 UTC client backend[21995] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(*) does not exist 2024-05-05 02:19:55.914 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(*); 2024-05-05 02:19:55.914 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.914 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (2, -NULL-, -2). 2024-05-05 02:19:55.914 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (2, -2); 2024-05-05 02:19:55.915 UTC client backend[21995] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(integer) does not exist 2024-05-05 02:19:55.915 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(int); 2024-05-05 02:19:55.915 UTC client backend[21990] pg_regress/typed_table ERROR: cannot change inheritance of typed table 2024-05-05 02:19:55.915 UTC client backend[21990] pg_regress/typed_table STATEMENT: ALTER TABLE persons INHERIT stuff; 2024-05-05 02:19:55.915 UTC client backend[21990] pg_regress/typed_table ERROR: column "myname" does not exist 2024-05-05 02:19:55.915 UTC client backend[21990] pg_regress/typed_table STATEMENT: CREATE TABLE personsx OF person_type (myname WITH OPTIONS NOT NULL); 2024-05-05 02:19:55.915 UTC client backend[21995] pg_regress/drop_if_exists ERROR: operator does not exist: integer @#@ integer 2024-05-05 02:19:55.915 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR @#@ (int, int); 2024-05-05 02:19:55.919 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.919 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (2, Y, -2). 2024-05-05 02:19:55.919 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2024-05-05 02:19:55.925 UTC client backend[21995] pg_regress/drop_if_exists ERROR: language "test_language_exists" does not exist 2024-05-05 02:19:55.925 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP LANGUAGE test_language_exists; 2024-05-05 02:19:55.925 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2024-05-05 02:19:55.925 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (1, -NULL-, -2). 2024-05-05 02:19:55.925 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (1, -2); 2024-05-05 02:19:55.925 UTC client backend[21995] pg_regress/drop_if_exists ERROR: cast from type text to type text does not exist 2024-05-05 02:19:55.925 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP CAST (text AS text); 2024-05-05 02:19:55.926 UTC client backend[21993] pg_regress/create_am ERROR: cannot drop access method gist2 because other objects depend on it 2024-05-05 02:19:55.926 UTC client backend[21993] pg_regress/create_am DETAIL: index grect2ind2 depends on operator class box_ops for access method gist2 2024-05-05 02:19:55.926 UTC client backend[21993] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:55.926 UTC client backend[21993] pg_regress/create_am STATEMENT: DROP ACCESS METHOD gist2; 2024-05-05 02:19:55.926 UTC client backend[21995] pg_regress/drop_if_exists ERROR: trigger "test_trigger_exists" for table "test_exists" does not exist 2024-05-05 02:19:55.926 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON test_exists; 2024-05-05 02:19:55.927 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.927 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2024-05-05 02:19:55.927 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL VALUES (5, 'check failed', -5); 2024-05-05 02:19:55.927 UTC client backend[21995] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2024-05-05 02:19:55.927 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_table; 2024-05-05 02:19:55.928 UTC client backend[21995] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2024-05-05 02:19:55.928 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_schema.no_such_table; 2024-05-05 02:19:55.929 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2024-05-05 02:19:55.929 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (5, check failed, 4). 2024-05-05 02:19:55.929 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) VALUES ('check failed', 4); 2024-05-05 02:19:55.930 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.930 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2024-05-05 02:19:55.930 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,y) VALUES (5, 'check failed'); 2024-05-05 02:19:55.932 UTC client backend[21995] pg_regress/drop_if_exists ERROR: rule "test_rule_exists" for relation "test_exists" does not exist 2024-05-05 02:19:55.932 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON test_exists; 2024-05-05 02:19:55.932 UTC client backend[21995] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2024-05-05 02:19:55.932 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_table; 2024-05-05 02:19:55.934 UTC client backend[21995] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2024-05-05 02:19:55.934 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_schema.no_such_table; 2024-05-05 02:19:55.934 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.934 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (8, Y, -8). 2024-05-05 02:19:55.934 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2024-05-05 02:19:55.938 UTC client backend[21993] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "" 2024-05-05 02:19:55.938 UTC client backend[21993] pg_regress/create_am DETAIL: default_table_access_method cannot be empty. 2024-05-05 02:19:55.938 UTC client backend[21993] pg_regress/create_am STATEMENT: SET default_table_access_method = ''; 2024-05-05 02:19:55.939 UTC client backend[21993] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "I do not exist AM" 2024-05-05 02:19:55.939 UTC client backend[21993] pg_regress/create_am DETAIL: Table access method "I do not exist AM" does not exist. 2024-05-05 02:19:55.939 UTC client backend[21993] pg_regress/create_am STATEMENT: SET default_table_access_method = 'I do not exist AM'; 2024-05-05 02:19:55.940 UTC client backend[21995] pg_regress/drop_if_exists ERROR: foreign-data wrapper "test_fdw_exists" does not exist 2024-05-05 02:19:55.940 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP FOREIGN DATA WRAPPER test_fdw_exists; 2024-05-05 02:19:55.940 UTC client backend[21993] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2024-05-05 02:19:55.940 UTC client backend[21993] pg_regress/create_am STATEMENT: SET default_table_access_method = 'btree'; 2024-05-05 02:19:55.942 UTC client backend[21995] pg_regress/drop_if_exists ERROR: server "test_server_exists" does not exist 2024-05-05 02:19:55.942 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP SERVER test_server_exists; 2024-05-05 02:19:55.942 UTC client backend[21993] pg_regress/create_am ERROR: function int4in(internal) does not exist 2024-05-05 02:19:55.942 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER int4in; 2024-05-05 02:19:55.944 UTC client backend[21995] pg_regress/drop_if_exists ERROR: operator class "test_operator_class" does not exist for access method "btree" 2024-05-05 02:19:55.944 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING btree; 2024-05-05 02:19:55.944 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "sys_col_check_tbl" violates check constraint "sys_col_check_tbl_check" 2024-05-05 02:19:55.944 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (Olympia, Washington, t, 100). 2024-05-05 02:19:55.944 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO SYS_COL_CHECK_TBL VALUES ('Olympia', 'Washington', true, 100); 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING no_such_am; 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS IF EXISTS test_operator_class USING no_such_am; 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists ERROR: operator family "test_operator_family" does not exist for access method "btree" 2024-05-05 02:19:55.945 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING btree; 2024-05-05 02:19:55.945 UTC client backend[21993] pg_regress/create_am ERROR: function bthandler must return type table_am_handler 2024-05-05 02:19:55.945 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER bthandler; 2024-05-05 02:19:55.946 UTC client backend[21995] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2024-05-05 02:19:55.946 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING no_such_am; 2024-05-05 02:19:55.946 UTC client backend[21995] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2024-05-05 02:19:55.946 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY IF EXISTS test_operator_family USING no_such_am; 2024-05-05 02:19:55.947 UTC client backend[21995] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2024-05-05 02:19:55.947 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP ACCESS METHOD no_such_am; 2024-05-05 02:19:55.950 UTC client backend[21995] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2024-05-05 02:19:55.950 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2024-05-05 02:19:55.958 UTC client backend[21987] pg_regress/constraints ERROR: system column "ctid" reference in check constraint is invalid at character 138 2024-05-05 02:19:55.958 UTC client backend[21987] 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-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am ERROR: syntax error at or near "USING" at character 41 2024-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am STATEMENT: SELECT INTO tableam_tblselectinto_heap2 USING heap2 FROM tableam_tbl_heap2; 2024-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am ERROR: syntax error at or near "USING" at character 32 2024-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE VIEW tableam_view_heap2 USING heap2 AS SELECT * FROM tableam_tbl_heap2; 2024-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am ERROR: syntax error at or near "USING" at character 35 2024-05-05 02:19:55.959 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE SEQUENCE tableam_seq_heap2 USING heap2; 2024-05-05 02:19:55.967 UTC client backend[22002] pg_regress/inherit ERROR: null value in column "aa" of relation "z" violates not-null constraint 2024-05-05 02:19:55.967 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (null, text). 2024-05-05 02:19:55.967 UTC client backend[22002] pg_regress/inherit STATEMENT: INSERT INTO z VALUES (NULL, 'text'); 2024-05-05 02:19:55.969 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_child_check" 2024-05-05 02:19:55.969 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (7, -NULL-, -7, 42, 6). 2024-05-05 02:19:55.969 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6); 2024-05-05 02:19:55.970 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_check" 2024-05-05 02:19:55.970 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (6, -NULL-, -7, 42, 7). 2024-05-05 02:19:55.970 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7); 2024-05-05 02:19:55.972 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_con" 2024-05-05 02:19:55.972 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (6, check failed, -6, 42, 7). 2024-05-05 02:19:55.972 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7); 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_ambiguous_funcname; 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2024-05-05 02:19:55.982 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION IF EXISTS test_ambiguous_funcname; 2024-05-05 02:19:55.984 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view1" 2024-05-05 02:19:55.984 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2024-05-05 02:19:55.984 UTC client backend[21984] 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-05-05 02:19:55.984 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view1; 2024-05-05 02:19:55.985 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2024-05-05 02:19:55.985 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (-3). 2024-05-05 02:19:55.985 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE test_ambiguous_procname; 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2024-05-05 02:19:55.985 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE IF EXISTS test_ambiguous_procname; 2024-05-05 02:19:55.985 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view2" 2024-05-05 02:19:55.985 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing GROUP BY are not automatically updatable. 2024-05-05 02:19:55.985 UTC client backend[21984] 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-05-05 02:19:55.985 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view2; 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists ERROR: routine name "test_ambiguous_procname" is not unique 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists HINT: Specify the argument list to select the routine unambiguously. 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: DROP ROUTINE IF EXISTS test_ambiguous_procname; 2024-05-05 02:19:55.986 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view3" 2024-05-05 02:19:55.986 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing HAVING are not automatically updatable. 2024-05-05 02:19:55.986 UTC client backend[21984] 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-05-05 02:19:55.986 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view3; 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists (force); 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2024-05-05 02:19:55.986 UTC client backend[21995] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists with (force); 2024-05-05 02:19:55.988 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view4" 2024-05-05 02:19:55.988 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that return aggregate functions are not automatically updatable. 2024-05-05 02:19:55.988 UTC client backend[21984] 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-05-05 02:19:55.988 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view4; 2024-05-05 02:19:55.989 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view5" 2024-05-05 02:19:55.989 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that return window functions are not automatically updatable. 2024-05-05 02:19:55.989 UTC client backend[21984] 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-05-05 02:19:55.989 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view5; 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view6" 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable. 2024-05-05 02:19:55.991 UTC client backend[21984] 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-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view6; 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view7" 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing WITH are not automatically updatable. 2024-05-05 02:19:55.991 UTC client backend[21984] 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-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view7 SET a=a+1; 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view8" 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2024-05-05 02:19:55.991 UTC client backend[21984] 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-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view8 SET a=a+1; 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view9" 2024-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2024-05-05 02:19:55.991 UTC client backend[21984] 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-05-05 02:19:55.991 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view9 SET a=a+1; 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view10" 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.992 UTC client backend[21984] 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-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view10 SET a=a+1; 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view11" 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.992 UTC client backend[21984] 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-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view11 SET a=a+1; 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view12" 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.992 UTC client backend[21984] 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-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view12 SET a=a+1; 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.992 UTC client backend[21984] 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-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view13 VALUES (3, 'Row 3'); 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view13" 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.992 UTC client backend[21984] pg_regress/updatable_views HINT: To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger. 2024-05-05 02:19:55.992 UTC client backend[21984] 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-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view13" 2024-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views HINT: To enable updating the view using MERGE, provide an INSTEAD OF UPDATE trigger. 2024-05-05 02:19:55.993 UTC client backend[21984] 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-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2024-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:55.993 UTC client backend[21984] pg_regress/updatable_views HINT: To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger. 2024-05-05 02:19:55.993 UTC client backend[21984] 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-05-05 02:19:55.995 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into column "ctid" of view "rw_view14" 2024-05-05 02:19:55.995 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2024-05-05 02:19:55.995 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view14 VALUES (null, 3, 'Row 3'); 2024-05-05 02:19:55.997 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update column "ctid" of view "rw_view14" 2024-05-05 02:19:55.997 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2024-05-05 02:19:55.997 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE rw_view14 SET ctid=null WHERE a=3; 2024-05-05 02:19:56.002 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot merge into column "ctid" of view "rw_view14" 2024-05-05 02:19:56.002 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2024-05-05 02:19:56.002 UTC client backend[21984] 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-05-05 02:19:56.005 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "atacc2" violates check constraint "atacc1_test_check" 2024-05-05 02:19:56.005 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2024-05-05 02:19:56.005 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO ATACC2 (TEST) VALUES (-3); 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test2_check" 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (null, 3). 2024-05-05 02:19:56.006 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST2) VALUES (3); 2024-05-05 02:19:56.007 UTC client backend[21998] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2024-05-05 02:19:56.007 UTC client backend[21998] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2024-05-05 02:19:56.007 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE vaccluster; 2024-05-05 02:19:56.009 UTC client backend[21990] pg_regress/typed_table ERROR: column "name" specified more than once 2024-05-05 02:19:56.009 UTC client backend[21990] 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-05-05 02:19:56.010 UTC client backend[21990] pg_regress/typed_table ERROR: cannot drop type person_type because other objects depend on it 2024-05-05 02:19:56.010 UTC client backend[21990] 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-05-05 02:19:56.010 UTC client backend[21990] pg_regress/typed_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:56.010 UTC client backend[21990] pg_regress/typed_table STATEMENT: DROP TYPE person_type RESTRICT; 2024-05-05 02:19:56.010 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2024-05-05 02:19:56.010 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2024-05-05 02:19:56.010 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 VALUES (3, 'ROW 3'); 2024-05-05 02:19:56.015 UTC client backend[21985] pg_regress/triggers ERROR: ttdummy (tttest): you cannot change price_on and/or price_off columns (use set_ttdummy) 2024-05-05 02:19:56.015 UTC client backend[21985] pg_regress/triggers STATEMENT: update tttest set price_on = -1 where price_id = 1; 2024-05-05 02:19:56.019 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2024-05-05 02:19:56.019 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2024-05-05 02:19:56.019 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (3) ON CONFLICT (a) DO UPDATE set upper = 'blarg'; 2024-05-05 02:19:56.046 UTC client backend[21990] pg_regress/typed_table ERROR: type stuff is not a composite type 2024-05-05 02:19:56.046 UTC client backend[21990] pg_regress/typed_table STATEMENT: CREATE TABLE persons5 OF stuff; 2024-05-05 02:19:56.046 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2024-05-05 02:19:56.046 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2024-05-05 02:19:56.046 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (4); 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper='ROW 3' WHERE a=3; 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2024-05-05 02:19:56.047 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper=DEFAULT WHERE a=3; 2024-05-05 02:19:56.048 UTC client backend[21984] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2024-05-05 02:19:56.048 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 VALUES (3, 'Row 3', 3); 2024-05-05 02:19:56.048 UTC client backend[21984] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2024-05-05 02:19:56.048 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET a=3, aa=-3 WHERE a=3; 2024-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into view "ro_view1" 2024-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2024-05-05 02:19:56.052 UTC client backend[21984] 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-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view17 VALUES (3, 'ROW 3'); 2024-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "ro_view18" 2024-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:56.052 UTC client backend[21984] 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-05-05 02:19:56.052 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view18; 2024-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view19" 2024-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2024-05-05 02:19:56.053 UTC client backend[21984] 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-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view19 SET last_value=1000; 2024-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "ro_view20" 2024-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views that return set-returning functions are not automatically updatable. 2024-05-05 02:19:56.053 UTC client backend[21984] 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-05-05 02:19:56.053 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE ro_view20 SET b=upper(b); 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot insert into view "rw_view16" 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2024-05-05 02:19:56.057 UTC client backend[21984] 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-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 (a, b) VALUES (3, 'Row 3'); 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot update view "rw_view16" 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2024-05-05 02:19:56.057 UTC client backend[21984] 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-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET b='ROW 2' WHERE a=2; 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot delete from view "rw_view16" 2024-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2024-05-05 02:19:56.057 UTC client backend[21984] 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-05-05 02:19:56.057 UTC client backend[21984] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view16 WHERE a=2; 2024-05-05 02:19:56.058 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view16" 2024-05-05 02:19:56.058 UTC client backend[21984] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2024-05-05 02:19:56.058 UTC client backend[21984] 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-05-05 02:19:56.075 UTC client backend[21998] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2024-05-05 02:19:56.075 UTC client backend[21998] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2024-05-05 02:19:56.075 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM FULL vaccluster; 2024-05-05 02:19:56.083 UTC client backend[21994] pg_regress/create_function_sql ERROR: could not find a function named "functest_b_1" 2024-05-05 02:19:56.083 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_1; 2024-05-05 02:19:56.083 UTC client backend[21994] pg_regress/create_function_sql ERROR: function name "functest_b_2" is not unique 2024-05-05 02:19:56.083 UTC client backend[21994] pg_regress/create_function_sql HINT: Specify the argument list to select the function unambiguously. 2024-05-05 02:19:56.083 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_2; 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql ERROR: cannot change routine kind 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE FUNCTION functest1(a int) RETURNS int LANGUAGE SQL WINDOW AS 'SELECT $1'; 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql ERROR: cannot change routine kind 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2024-05-05 02:19:56.084 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE PROCEDURE functest1(a int) LANGUAGE SQL AS 'SELECT $1'; 2024-05-05 02:19:56.091 UTC client backend[21993] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2024-05-05 02:19:56.091 UTC client backend[21993] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2024-05-05 02:19:56.092 UTC client backend[21993] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2024-05-05 02:19:56.092 UTC client backend[21993] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD DEFAULT, SET ACCESS METHOD heap2; 2024-05-05 02:19:56.092 UTC client backend[21993] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2024-05-05 02:19:56.092 UTC client backend[21993] pg_regress/create_am STATEMENT: ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2024-05-05 02:19:56.123 UTC client backend[21994] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2024-05-05 02:19:56.123 UTC client backend[21994] pg_regress/create_function_sql DETAIL: Actual return type is text. 2024-05-05 02:19:56.123 UTC client backend[21994] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2024-05-05 02:19:56.123 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT ''not an integer'';'; 2024-05-05 02:19:56.124 UTC client backend[21994] pg_regress/create_function_sql ERROR: syntax error at or near "not" at character 62 2024-05-05 02:19:56.124 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'not even SQL'; 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql DETAIL: Final statement must return exactly one column. 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT 1, 2, 3;'; 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql ERROR: there is no parameter $2 at character 69 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT $2;'; 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql ERROR: only one AS item needed for language "sql" 2024-05-05 02:19:56.125 UTC client backend[21994] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'a', 'b'; 2024-05-05 02:19:56.143 UTC client backend[21987] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2024-05-05 02:19:56.143 UTC client backend[21987] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int NOT NULL NO INHERIT) PARTITION BY LIST (a); 2024-05-05 02:19:56.144 UTC client backend[21987] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2024-05-05 02:19:56.144 UTC client backend[21987] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int, NOT NULL a NO INHERIT) PARTITION BY LIST (a); 2024-05-05 02:19:56.151 UTC client backend[21987] pg_regress/constraints ERROR: column "a" of relation "atacc3" contains null values 2024-05-05 02:19:56.151 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE ATACC1 ADD CONSTRAINT ditto NOT NULL a; 2024-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: duplicate trigger events specified at or near "ON" at character 63 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: column "a" specified more than once 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: syntax error at or near "OF" at character 42 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: INSERT trigger's WHEN condition cannot reference OLD values at character 88 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: DELETE trigger's WHEN condition cannot reference NEW values at character 97 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: BEFORE trigger's WHEN condition cannot reference NEW system columns at character 88 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.160 UTC client backend[21985] pg_regress/triggers ERROR: statement trigger's WHEN condition cannot reference column values at character 90 2024-05-05 02:19:56.160 UTC client backend[21985] 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-05-05 02:19:56.161 UTC client backend[21985] pg_regress/triggers ERROR: cannot drop column b of table main_table because other objects depend on it 2024-05-05 02:19:56.161 UTC client backend[21985] 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-05-05 02:19:56.161 UTC client backend[21985] pg_regress/triggers HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:56.161 UTC client backend[21985] pg_regress/triggers STATEMENT: ALTER TABLE main_table DROP COLUMN b; 2024-05-05 02:19:56.163 UTC client backend[22002] pg_regress/inherit ERROR: column "tomorrow" inherits conflicting default values 2024-05-05 02:19:56.163 UTC client backend[22002] pg_regress/inherit HINT: To resolve the conflict, specify a default explicitly. 2024-05-05 02:19:56.163 UTC client backend[22002] pg_regress/inherit STATEMENT: CREATE TABLE otherchild () INHERITS (firstparent, thirdparent); 2024-05-05 02:19:56.208 UTC client backend[21993] pg_regress/create_am ERROR: zero-length delimited identifier at or near """" at character 37 2024-05-05 02:19:56.208 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING ""; 2024-05-05 02:19:56.208 UTC client backend[21993] pg_regress/create_am ERROR: access method "i_do_not_exist_am" does not exist 2024-05-05 02:19:56.208 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING i_do_not_exist_am; 2024-05-05 02:19:56.209 UTC client backend[21993] pg_regress/create_am ERROR: access method "I do not exist AM" does not exist 2024-05-05 02:19:56.209 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "I do not exist AM"; 2024-05-05 02:19:56.209 UTC client backend[21993] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2024-05-05 02:19:56.209 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "btree"; 2024-05-05 02:19:56.210 UTC client backend[21993] pg_regress/create_am ERROR: "tableam_parted_a_heap2" is not partitioned 2024-05-05 02:19:56.210 UTC client backend[21993] pg_regress/create_am STATEMENT: CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x; 2024-05-05 02:19:56.212 UTC client backend[21993] pg_regress/create_am ERROR: cannot drop access method heap2 because other objects depend on it 2024-05-05 02:19:56.212 UTC client backend[21993] 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-05-05 02:19:56.212 UTC client backend[21993] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2024-05-05 02:19:56.212 UTC client backend[21993] pg_regress/create_am STATEMENT: DROP ACCESS METHOD heap2; 2024-05-05 02:19:56.224 UTC client backend[22002] pg_regress/inherit ERROR: cannot alter inherited column "f1" of relation "childtab" 2024-05-05 02:19:56.224 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table parent1 alter column f1 type bigint; 2024-05-05 02:19:56.275 UTC client backend[21987] pg_regress/constraints ERROR: cannot add NOT NULL constraint to column "a" of relation "atacc2" with inheritance children 2024-05-05 02:19:56.275 UTC client backend[21987] pg_regress/constraints DETAIL: Existing constraint "a_is_not_null" is marked NO INHERIT. 2024-05-05 02:19:56.275 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE ATACC2 INHERIT ATACC1; 2024-05-05 02:19:56.280 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:56.280 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (8, try again, -8). 2024-05-05 02:19:56.280 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) SELECT yd, -8 FROM tmp WHERE yd = 'try again'; 2024-05-05 02:19:56.284 UTC client backend[22002] pg_regress/inherit ERROR: constraint "p2chk" conflicts with inherited constraint on relation "c2" 2024-05-05 02:19:56.284 UTC client backend[22002] pg_regress/inherit STATEMENT: create table c2 (constraint p2chk check (ff1 > 10) no inherit) inherits (p1); 2024-05-05 02:19:56.286 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2024-05-05 02:19:56.286 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (-4, Y, 4). 2024-05-05 02:19:56.286 UTC client backend[21987] pg_regress/constraints STATEMENT: UPDATE INSERT_TBL SET x = z, z = x; 2024-05-05 02:19:56.293 UTC client backend[21987] pg_regress/constraints ERROR: new row for relation "copy_tbl" violates check constraint "copy_con" 2024-05-05 02:19:56.293 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (7, check failed, 6). 2024-05-05 02:19:56.293 UTC client backend[21987] pg_regress/constraints CONTEXT: COPY copy_tbl, line 2: "7 check failed 6" 2024-05-05 02:19:56.293 UTC client backend[21987] pg_regress/constraints STATEMENT: COPY COPY_TBL FROM '/tmp/cirrus-ci-build/src/test/regress/data/constrf.data'; 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "primary_tbl_pkey" 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL VALUES (1, 'three'); 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (null, six). 2024-05-05 02:19:56.302 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2024-05-05 02:19:56.312 UTC client backend[21987] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2024-05-05 02:19:56.312 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (null, six). 2024-05-05 02:19:56.312 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2024-05-05 02:19:56.323 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.323 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.323 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2024-05-05 02:19:56.325 UTC client backend[21987] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2024-05-05 02:19:56.325 UTC client backend[21987] pg_regress/constraints HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2024-05-05 02:19:56.325 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'a'), (2, 'b'), (2, 'b') ON CONFLICT (i) DO UPDATE SET t = 'fails'; 2024-05-05 02:19:56.328 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.328 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.328 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2024-05-05 02:19:56.328 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_check" 2024-05-05 02:19:56.328 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (null). 2024-05-05 02:19:56.328 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2024-05-05 02:19:56.329 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_check" 2024-05-05 02:19:56.329 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (null, null). 2024-05-05 02:19:56.329 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2024-05-05 02:19:56.329 UTC client backend[22002] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_check" of relation "bc" 2024-05-05 02:19:56.329 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_check; 2024-05-05 02:19:56.333 UTC client backend[21984] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view1" 2024-05-05 02:19:56.333 UTC client backend[21984] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2024-05-05 02:19:56.333 UTC client backend[21984] 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-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_aa_check" 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (null). 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_aa_check" 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (null, null). 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_aa_check" of relation "bc" 2024-05-05 02:19:56.335 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_aa_check; 2024-05-05 02:19:56.336 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.336 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(null) already exists. 2024-05-05 02:19:56.336 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL (t) VALUES ('seven'); 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.343 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers ERROR: "main_view" is a view 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2024-05-05 02:19:56.344 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2024-05-05 02:19:56.345 UTC client backend[21985] pg_regress/triggers ERROR: "main_table" is a table 2024-05-05 02:19:56.345 UTC client backend[21985] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2024-05-05 02:19:56.345 UTC client backend[21985] 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-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers ERROR: "main_table" is a table 2024-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2024-05-05 02:19:56.346 UTC client backend[21985] 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-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers ERROR: "main_table" is a table 2024-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2024-05-05 02:19:56.346 UTC client backend[21985] 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-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have WHEN conditions 2024-05-05 02:19:56.346 UTC client backend[21985] 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-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have column lists 2024-05-05 02:19:56.346 UTC client backend[21985] 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-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers ERROR: INSTEAD OF triggers must be FOR EACH ROW 2024-05-05 02:19:56.346 UTC client backend[21985] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2024-05-05 02:19:56.346 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_t_key" 2024-05-05 02:19:56.346 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i, t)=(1, one) already exists. 2024-05-05 02:19:56.346 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'one'); 2024-05-05 02:19:56.355 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.355 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.355 UTC client backend[21987] pg_regress/constraints STATEMENT: UPDATE unique_tbl SET i = 1 WHERE i = 0; 2024-05-05 02:19:56.368 UTC client backend[21998] pg_regress/vacuum ERROR: parallel workers for vacuum must be between 0 and 1024 at character 9 2024-05-05 02:19:56.368 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL -1) pvactst; 2024-05-05 02:19:56.370 UTC client backend[21998] pg_regress/vacuum ERROR: VACUUM FULL cannot be performed in parallel 2024-05-05 02:19:56.370 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL 2, FULL TRUE) pvactst; 2024-05-05 02:19:56.370 UTC client backend[21998] pg_regress/vacuum ERROR: parallel option requires a value between 0 and 1024 at character 9 2024-05-05 02:19:56.370 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL) pvactst; 2024-05-05 02:19:56.376 UTC client backend[21998] pg_regress/vacuum WARNING: disabling parallel option of vacuum on "tmp" --- cannot vacuum temporary tables in parallel 2024-05-05 02:19:56.376 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.376 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2024-05-05 02:19:56.376 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMIT; 2024-05-05 02:19:56.377 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.377 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2024-05-05 02:19:56.377 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO unique_tbl VALUES (3, 'Three'); 2024-05-05 02:19:56.377 UTC client backend[22002] pg_regress/inherit ERROR: check constraint "cc" of relation "c1" is violated by some row 2024-05-05 02:19:56.377 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table p2 add constraint cc check (f2>0); 2024-05-05 02:19:56.377 UTC client backend[22002] pg_regress/inherit ERROR: check constraint "p2_f2_check" of relation "c1" is violated by some row 2024-05-05 02:19:56.377 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table p2 add check (f2>0); 2024-05-05 02:19:56.378 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "c1" violates check constraint "p2_f2_check" 2024-05-05 02:19:56.378 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (1, -1, 2). 2024-05-05 02:19:56.378 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into c1 values(1,-1,2); 2024-05-05 02:19:56.379 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.379 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2024-05-05 02:19:56.379 UTC client backend[21987] pg_regress/constraints STATEMENT: SET CONSTRAINTS ALL IMMEDIATE; 2024-05-05 02:19:56.397 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2024-05-05 02:19:56.397 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.397 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO parted_uniq_tbl VALUES (1); 2024-05-05 02:19:56.398 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2024-05-05 02:19:56.398 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2024-05-05 02:19:56.398 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMIT; TRAP: failed Assert("!TTS_EMPTY(slot)"), File: "../src/backend/executor/execTuples.c", Line: 1737, PID: 21984 postgres: postgres regression [local] MERGE(ExceptionalCondition+0x56)[0x55835cf335f3] postgres: postgres regression [local] MERGE(ExecFetchSlotHeapTuple+0x145)[0x55835c8844d9] postgres: postgres regression [local] MERGE(ExecIRDeleteTriggers+0x2a9)[0x55835c807fe3] postgres: postgres regression [local] MERGE(+0xd3795a)[0x55835c8e795a] postgres: postgres regression [local] MERGE(+0xd38a42)[0x55835c8e8a42] postgres: postgres regression [local] MERGE(+0xd3a799)[0x55835c8ea799] postgres: postgres regression [local] MERGE(+0xcc66a4)[0x55835c8766a4] postgres: postgres regression [local] MERGE(+0xcb2d9f)[0x55835c862d9f] postgres: postgres regression [local] MERGE(standard_ExecutorRun+0x298)[0x55835c8630e9] postgres: postgres regression [local] MERGE(ExecutorRun+0x25)[0x55835c863254] postgres: postgres regression [local] MERGE(+0x10d90ef)[0x55835cc890ef] postgres: postgres regression [local] MERGE(+0x10dae3e)[0x55835cc8ae3e] postgres: postgres regression [local] MERGE(+0x10db4e4)[0x55835cc8b4e4] postgres: postgres regression [local] MERGE(PortalRun+0x537)[0x55835cc8bb43] postgres: postgres regression [local] MERGE(+0x10d4ac7)[0x55835cc84ac7] postgres: postgres regression [local] MERGE(PostgresMain+0x8f3)[0x55835cc8788a] postgres: postgres regression [local] MERGE(BackendMain+0x92)[0x55835cc7e027] postgres: postgres regression [local] MERGE(postmaster_child_launch+0x188)[0x55835cb2234c] postgres: postgres regression [local] MERGE(+0xf7867a)[0x55835cb2867a] postgres: postgres regression [local] MERGE(+0xf78c28)[0x55835cb28c28] postgres: postgres regression [local] MERGE(BackgroundWorkerInitializeConnection+0x0)[0x55835cb2a64a] postgres: postgres regression [local] MERGE(main+0x393)[0x55835c94a8c2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f1ab66fdd0a] postgres: postgres regression [local] MERGE(_start+0x2a)[0x55835c49924a] 2024-05-05 02:19:56.429 UTC client backend[21987] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2024-05-05 02:19:56.429 UTC client backend[21987] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2024-05-05 02:19:56.429 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMIT; 2024-05-05 02:19:56.443 UTC client backend[21987] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "circles_c1_c2_excl" 2024-05-05 02:19:56.443 UTC client backend[21987] 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-05-05 02:19:56.443 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>'); 2024-05-05 02:19:56.444 UTC client backend[21987] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2024-05-05 02:19:56.444 UTC client backend[21987] 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-05-05 02:19:56.445 UTC client backend[21987] pg_regress/constraints ERROR: could not create exclusion constraint "circles_c1_c2_excl1" 2024-05-05 02:19:56.445 UTC client backend[21987] 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-05-05 02:19:56.445 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE circles ADD EXCLUDE USING gist (c1 WITH &&, (c2::circle) WITH &&); 2024-05-05 02:19:56.448 UTC client backend[22003] pg_regress/infinite_recurse ERROR: stack depth limit exceeded 2024-05-05 02:19:56.448 UTC client backend[22003] 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-05-05 02:19:56.448 UTC client backend[22003] 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 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 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-05-05 02:19:56.448 UTC client backend[22003] pg_regress/infinite_recurse STATEMENT: select infinite_recurse(); 2024-05-05 02:19:56.452 UTC client backend[21987] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2024-05-05 02:19:56.452 UTC client backend[21987] pg_regress/constraints DETAIL: Key (f1)=(1) conflicts with existing key (f1)=(1). 2024-05-05 02:19:56.452 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1); 2024-05-05 02:19:56.452 UTC client backend[21987] pg_regress/constraints ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters 2024-05-05 02:19:56.452 UTC client backend[21987] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1) ON CONFLICT ON CONSTRAINT deferred_excl_con DO NOTHING; 2024-05-05 02:19:56.453 UTC client backend[21987] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2024-05-05 02:19:56.453 UTC client backend[21987] pg_regress/constraints DETAIL: Key (f1)=(2) conflicts with existing key (f1)=(2). 2024-05-05 02:19:56.453 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMIT; 2024-05-05 02:19:56.454 UTC client backend[21987] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2024-05-05 02:19:56.454 UTC client backend[21987] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with existing key (f1)=(3). 2024-05-05 02:19:56.454 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMIT; 2024-05-05 02:19:56.458 UTC client backend[21987] pg_regress/constraints ERROR: could not create exclusion constraint "deferred_excl_f1_excl" 2024-05-05 02:19:56.458 UTC client backend[21987] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with key (f1)=(3). 2024-05-05 02:19:56.458 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE deferred_excl ADD EXCLUDE (f1 WITH =); 2024-05-05 02:19:56.473 UTC client backend[21998] pg_regress/vacuum ERROR: null value in column "i" of relation "vac_truncate_test" violates not-null constraint 2024-05-05 02:19:56.473 UTC client backend[21998] pg_regress/vacuum DETAIL: Failing row contains (null, null). 2024-05-05 02:19:56.473 UTC client backend[21998] pg_regress/vacuum STATEMENT: INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL); 2024-05-05 02:19:56.493 UTC client backend[21987] pg_regress/constraints ERROR: constraint "notnull_tbl1_a_not_null" for relation "notnull_tbl1" already exists 2024-05-05 02:19:56.493 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD COLUMN b INT CONSTRAINT notnull_tbl1_a_not_null NOT NULL; 2024-05-05 02:19:56.504 UTC client backend[21998] pg_regress/vacuum ERROR: column "a" of relation "vacparted" appears more than once 2024-05-05 02:19:56.504 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vacparted(a,b,a); 2024-05-05 02:19:56.504 UTC client backend[21998] pg_regress/vacuum ERROR: column "b" of relation "vacparted" appears more than once 2024-05-05 02:19:56.504 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE vacparted(a,b,b); 2024-05-05 02:19:56.508 UTC client backend[22002] pg_regress/inherit ERROR: cannot rename inherited column "b" 2024-05-05 02:19:56.508 UTC client backend[22002] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; 2024-05-05 02:19:56.508 UTC client backend[22002] pg_regress/inherit ERROR: cannot rename inherited column "aa" 2024-05-05 02:19:56.508 UTC client backend[22002] pg_regress/inherit STATEMENT: ALTER TABLE inhts RENAME aa TO aaa; 2024-05-05 02:19:56.538 UTC client backend[21987] pg_regress/constraints ERROR: constraint "blah" for relation "notnull_tbl2" already exists 2024-05-05 02:19:56.538 UTC client backend[21987] pg_regress/constraints STATEMENT: CREATE TABLE notnull_tbl2 (a INTEGER CONSTRAINT blah NOT NULL, b INTEGER CONSTRAINT blah NOT NULL); 2024-05-05 02:19:56.539 UTC client backend[21987] pg_regress/constraints ERROR: column "a" is in a primary key 2024-05-05 02:19:56.539 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl2 ALTER a DROP NOT NULL; 2024-05-05 02:19:56.541 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.541 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM vacparted, does_not_exist; 2024-05-05 02:19:56.545 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.545 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (FREEZE) does_not_exist, vaccluster; 2024-05-05 02:19:56.547 UTC client backend[21998] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vactst" does not exist 2024-05-05 02:19:56.547 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vactst (does_not_exist), vacparted (b); 2024-05-05 02:19:56.550 UTC client backend[21985] pg_regress/triggers ERROR: No such country: "Japon" 2024-05-05 02:19:56.550 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function city_update() line 9 at RAISE 2024-05-05 02:19:56.550 UTC client backend[21985] pg_regress/triggers STATEMENT: UPDATE city_view SET country_name = 'Japon' WHERE city_name = 'Tokyo'; 2024-05-05 02:19:56.554 UTC client backend[21998] pg_regress/vacuum ERROR: ANALYZE option must be specified when a column list is provided 2024-05-05 02:19:56.554 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM FULL vactst, vacparted (a, b), vaccluster (i); 2024-05-05 02:19:56.558 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.558 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE vactst, does_not_exist, vacparted; 2024-05-05 02:19:56.558 UTC client backend[21998] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vacparted" does not exist 2024-05-05 02:19:56.558 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE vactst (i), vacparted (does_not_exist); 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE) does_not_exist; 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum ERROR: syntax error at or near "arg" at character 22 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE (nonexistent-arg) does_not_exist; 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum ERROR: unrecognized ANALYZE option "nonexistentarg" at character 10 2024-05-05 02:19:56.560 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE (nonexistentarg) does_not_exit; 2024-05-05 02:19:56.561 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.561 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE (SKIP_LOCKED, VERBOSE) does_not_exist; 2024-05-05 02:19:56.562 UTC client backend[21998] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2024-05-05 02:19:56.562 UTC client backend[21998] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE, SKIP_LOCKED) does_not_exist; 2024-05-05 02:19:56.595 UTC client backend[21987] pg_regress/constraints ERROR: column "c1" is in index used as replica identity 2024-05-05 02:19:56.595 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER c1 DROP NOT NULL; 2024-05-05 02:19:56.618 UTC client backend[21998] pg_regress/vacuum ERROR: PROCESS_TOAST required with VACUUM FULL 2024-05-05 02:19:56.618 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (PROCESS_TOAST FALSE, FULL) vac_option_tab; 2024-05-05 02:19:56.618 UTC client backend[22002] pg_regress/inherit ERROR: cannot rename inherited column "b" 2024-05-05 02:19:56.618 UTC client backend[22002] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; 2024-05-05 02:19:56.650 UTC client backend[21998] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2024-05-05 02:19:56.650 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 16777220) vac_option_tab; 2024-05-05 02:19:56.650 UTC client backend[21998] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2024-05-05 02:19:56.650 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 120) vac_option_tab; 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum HINT: Value exceeds integer range. 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 10000000000) vac_option_tab; 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT cannot be specified for VACUUM FULL 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT '512 kB', FULL) vac_option_tab; 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum ERROR: ONLY_DATABASE_STATS cannot be specified with a list of tables 2024-05-05 02:19:56.651 UTC client backend[21998] pg_regress/vacuum STATEMENT: VACUUM (ONLY_DATABASE_STATS) vactst; 2024-05-05 02:19:56.680 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2024-05-05 02:19:56.680 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned", skipping it 2024-05-05 02:19:56.681 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2024-05-05 02:19:56.681 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2024-05-05 02:19:56.682 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "pg_class", skipping it 2024-05-05 02:19:56.682 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2024-05-05 02:19:56.682 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2024-05-05 02:19:56.683 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "pg_authid", skipping it 2024-05-05 02:19:56.683 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2024-05-05 02:19:56.683 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2024-05-05 02:19:56.683 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.684 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.684 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.684 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.684 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2024-05-05 02:19:56.685 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2024-05-05 02:19:56.688 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.688 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2024-05-05 02:19:56.688 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.688 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2024-05-05 02:19:56.689 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.689 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.689 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.689 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.690 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.692 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.692 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.693 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.693 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.696 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.697 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2024-05-05 02:19:56.697 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2024-05-05 02:19:56.698 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.699 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.701 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.701 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.702 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.702 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.702 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2024-05-05 02:19:56.703 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.703 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2024-05-05 02:19:56.703 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2024-05-05 02:19:56.704 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.704 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.704 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2024-05-05 02:19:56.704 UTC client backend[21998] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2024-05-05 02:19:56.755 UTC client backend[21985] pg_regress/triggers ERROR: U9999 2024-05-05 02:19:56.755 UTC client backend[21985] 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-05-05 02:19:56.755 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into depth_a values (1); 2024-05-05 02:19:56.775 UTC client backend[21985] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2024-05-05 02:19:56.775 UTC client backend[21985] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2024-05-05 02:19:56.775 UTC client backend[21985] pg_regress/triggers STATEMENT: update parent set val1 = 'b' where aid = 1; 2024-05-05 02:19:56.775 UTC client backend[21985] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2024-05-05 02:19:56.775 UTC client backend[21985] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2024-05-05 02:19:56.775 UTC client backend[21985] 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-05-05 02:19:56.776 UTC client backend[21985] pg_regress/triggers ERROR: tuple to be deleted was already modified by an operation triggered by the current command 2024-05-05 02:19:56.776 UTC client backend[21985] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2024-05-05 02:19:56.776 UTC client backend[21985] pg_regress/triggers STATEMENT: delete from parent where aid = 1; 2024-05-05 02:19:56.777 UTC client backend[21985] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2024-05-05 02:19:56.777 UTC client backend[21985] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2024-05-05 02:19:56.777 UTC client backend[21985] pg_regress/triggers STATEMENT: merge into parent p using (values (1)) as v(id) on p.aid = v.id when matched then delete; 2024-05-05 02:19:56.781 UTC client backend[21987] pg_regress/constraints ERROR: multiple primary keys for table "cnn_parent" are not allowed 2024-05-05 02:19:56.781 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE cnn_parent ADD PRIMARY KEY (b); 2024-05-05 02:19:56.795 UTC client backend[21985] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2024-05-05 02:19:56.795 UTC client backend[21985] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2024-05-05 02:19:56.795 UTC client backend[21985] pg_regress/triggers STATEMENT: delete from self_ref_trigger; 2024-05-05 02:19:56.809 UTC client backend[21985] pg_regress/triggers ERROR: cannot ALTER TABLE "trigger_ddl_table" because it is being used by active queries in this session 2024-05-05 02:19:56.809 UTC client backend[21985] 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-05-05 02:19:56.809 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2024-05-05 02:19:56.810 UTC client backend[21985] pg_regress/triggers ERROR: cannot CREATE INDEX "trigger_ddl_table" because it is being used by active queries in this session 2024-05-05 02:19:56.810 UTC client backend[21985] 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-05-05 02:19:56.810 UTC client backend[21985] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2024-05-05 02:19:56.817 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (1,black) 2024-05-05 02:19:56.817 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.817 UTC client backend[21985] pg_regress/triggers WARNING: after insert (new): (1,black) 2024-05-05 02:19:56.817 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (2,red) 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new, modified): (3,"red trig modified") 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers WARNING: after insert (new): (3,"red trig modified") 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (3,orange) 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers WARNING: before update (old): (3,"red trig modified") 2024-05-05 02:19:56.818 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: before update (new): (3,"updated red trig modified") 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: after update (old): (3,"red trig modified") 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: after update (new): (3,"updated red trig modified") 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (4,green) 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new, modified): (5,"green trig modified") 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers WARNING: after insert (new): (5,"green trig modified") 2024-05-05 02:19:56.819 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (5,purple) 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers WARNING: before update (old): (5,"green trig modified") 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers WARNING: before update (new): (5,"updated green trig modified") 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers WARNING: after update (old): (5,"green trig modified") 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers WARNING: after update (new): (5,"updated green trig modified") 2024-05-05 02:19:56.820 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (6,white) 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new, modified): (7,"white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: after insert (new): (7,"white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (7,pink) 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: before update (old): (7,"white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: before update (new): (7,"updated white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: after update (old): (7,"white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers WARNING: after update (new): (7,"updated white trig modified") 2024-05-05 02:19:56.821 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new): (8,yellow) 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers WARNING: before insert (new, modified): (9,"yellow trig modified") 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers WARNING: after insert (new): (9,"yellow trig modified") 2024-05-05 02:19:56.822 UTC client backend[21985] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2024-05-05 02:19:56.838 UTC client backend[21985] pg_regress/triggers ERROR: "my_view" is a view 2024-05-05 02:19:56.838 UTC client backend[21985] pg_regress/triggers DETAIL: Triggers on views cannot have transition tables. 2024-05-05 02:19:56.838 UTC client backend[21985] 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-05-05 02:19:56.849 UTC client backend[21985] pg_regress/triggers ERROR: "parted_trig" is a table 2024-05-05 02:19:56.849 UTC client backend[21985] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2024-05-05 02:19:56.849 UTC client backend[21985] pg_regress/triggers STATEMENT: create trigger failed instead of update on parted_trig for each row execute procedure trigger_nothing(); 2024-05-05 02:19:56.849 UTC client backend[21985] pg_regress/triggers ERROR: "parted_trig" is a partitioned table 2024-05-05 02:19:56.849 UTC client backend[21985] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported on partitioned tables. 2024-05-05 02:19:56.849 UTC client backend[21985] 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-05-05 02:19:56.857 UTC client backend[21987] pg_regress/constraints ERROR: constraint "cnn_parent_pkey" of relation "cnn_parent" does not exist 2024-05-05 02:19:56.857 UTC client backend[21987] pg_regress/constraints STATEMENT: ALTER TABLE cnn_parent DROP CONSTRAINT cnn_parent_pkey; 2024-05-05 02:19:56.868 UTC client backend[21985] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart1 because trigger trg1 on table trigpart requires it 2024-05-05 02:19:56.868 UTC client backend[21985] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2024-05-05 02:19:56.868 UTC client backend[21985] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart1; 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart2 because trigger trg1 on table trigpart requires it 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart2; 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart3 because trigger trg1 on table trigpart requires it 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2024-05-05 02:19:56.869 UTC client backend[21985] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2024-05-05 02:19:56.896 UTC client backend[21987] pg_regress/constraints ERROR: null value in column "a" of relation "cnn2_part1" violates not-null constraint 2024-05-05 02:19:56.896 UTC client backend[21987] pg_regress/constraints DETAIL: Failing row contains (null). 2024-05-05 02:19:56.896 UTC client backend[21987] pg_regress/constraints STATEMENT: insert into cnn2_part1 values (null); 2024-05-05 02:19:56.903 UTC client backend[21985] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart3" does not exist 2024-05-05 02:19:56.903 UTC client backend[21985] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2024-05-05 02:19:56.905 UTC client backend[21985] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart41" does not exist 2024-05-05 02:19:56.905 UTC client backend[21985] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart41; 2024-05-05 02:19:56.968 UTC client backend[21987] pg_regress/constraints ERROR: column "a" in child table must be marked NOT NULL 2024-05-05 02:19:56.968 UTC client backend[21987] pg_regress/constraints STATEMENT: alter table cnn2_parted attach partition cnn2_part1 for values in (1); 2024-05-05 02:19:56.972 UTC client backend[21987] pg_regress/constraints ERROR: column "a" of relation "cnn_part1" contains null values 2024-05-05 02:19:56.972 UTC client backend[21987] pg_regress/constraints STATEMENT: alter table cnn2_parted add primary key (a); 2024-05-05 02:19:57.009 UTC client backend[21985] pg_regress/triggers ERROR: trigger "trg1" for relation "trigpart3" already exists 2024-05-05 02:19:57.009 UTC client backend[21985] pg_regress/triggers STATEMENT: alter table trigpart attach partition trigpart3 FOR VALUES FROM (2000) to (3000); 2024-05-05 02:19:57.017 UTC client backend[22002] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1" 2024-05-05 02:19:57.017 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table p1_c1 drop constraint f1_pos; 2024-05-05 02:19:57.099 UTC client backend[22002] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c2" 2024-05-05 02:19:57.099 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table p1_c2 drop constraint f1_pos; 2024-05-05 02:19:57.100 UTC client backend[22002] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1c2" 2024-05-05 02:19:57.100 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table p1_c1c2 drop constraint f1_pos; 2024-05-05 02:19:57.113 UTC client backend[22002] pg_regress/inherit ERROR: constraint "inh_check_constraint" conflicts with NOT VALID constraint on relation "invalid_check_con_child" 2024-05-05 02:19:57.113 UTC client backend[22002] pg_regress/inherit STATEMENT: alter table invalid_check_con add constraint inh_check_constraint check(f1 > 0); 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "invalid_check_con" violates check constraint "inh_check_constraint" 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (0). 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into invalid_check_con values(0); 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit ERROR: new row for relation "invalid_check_con_child" violates check constraint "inh_check_constraint" 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit DETAIL: Failing row contains (0). 2024-05-05 02:19:57.114 UTC client backend[22002] pg_regress/inherit STATEMENT: insert into invalid_check_con_child values(0); 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints ERROR: constraint "no_constraint" for table "constraint_comments_tbl" does not exist 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON constraint_comments_tbl IS 'yes, the comment'; 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints ERROR: constraint "no_constraint" for domain constraint_comments_dom does not exist 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON DOMAIN constraint_comments_dom IS 'yes, another comment'; 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints ERROR: relation "no_comments_tbl" does not exist 2024-05-05 02:19:57.154 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON no_comments_tbl IS 'bad comment'; 2024-05-05 02:19:57.155 UTC client backend[21987] pg_regress/constraints ERROR: type "no_comments_dom" does not exist 2024-05-05 02:19:57.155 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN no_comments_dom IS 'another bad comment'; 2024-05-05 02:19:57.156 UTC client backend[21987] pg_regress/constraints ERROR: must be owner of relation constraint_comments_tbl 2024-05-05 02:19:57.156 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON constraint_comments_tbl IS 'no, the comment'; 2024-05-05 02:19:57.156 UTC client backend[21987] pg_regress/constraints ERROR: must be owner of type constraint_comments_dom 2024-05-05 02:19:57.156 UTC client backend[21987] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN constraint_comments_dom IS 'no, another comment'; 2024-05-05 02:19:57.385 UTC postmaster[19619] LOG: server process (PID 21984) was terminated by signal 6: Aborted 2024-05-05 02:19:57.385 UTC postmaster[19619] 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-05-05 02:19:57.385 UTC postmaster[19619] LOG: terminating any other active server processes 2024-05-05 02:19:57.392 UTC postmaster[19619] LOG: all server processes terminated; reinitializing 2024-05-05 02:19:57.411 UTC startup[22183] LOG: database system was interrupted; last known up at 2024-05-05 02:19:46 UTC 2024-05-05 02:19:57.411 UTC startup[22183] LOG: database system was not properly shut down; automatic recovery in progress 2024-05-05 02:19:57.412 UTC startup[22183] LOG: redo starts at 0/151E778 2024-05-05 02:19:57.436 UTC client backend[22216] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.436 UTC client backend[22216] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.459 UTC client backend[22245] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.459 UTC client backend[22245] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.470 UTC client backend[22247] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.470 UTC client backend[22247] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.477 UTC client backend[22249] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.477 UTC client backend[22249] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.478 UTC client backend[22250] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.478 UTC client backend[22250] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.480 UTC client backend[22251] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.480 UTC client backend[22251] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.485 UTC client backend[22256] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.485 UTC client backend[22256] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.493 UTC client backend[22258] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.493 UTC client backend[22258] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.494 UTC client backend[22255] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.494 UTC client backend[22255] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.495 UTC client backend[22257] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.495 UTC client backend[22257] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.495 UTC client backend[22252] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.495 UTC client backend[22252] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.506 UTC client backend[22253] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.506 UTC client backend[22253] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.513 UTC client backend[22259] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.513 UTC client backend[22259] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.514 UTC client backend[22261] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.514 UTC client backend[22261] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.516 UTC client backend[22260] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.516 UTC client backend[22260] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.524 UTC client backend[22266] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.524 UTC client backend[22266] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.524 UTC client backend[22248] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.524 UTC client backend[22248] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.525 UTC client backend[22262] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.525 UTC client backend[22262] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.527 UTC client backend[22267] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.527 UTC client backend[22267] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.540 UTC client backend[22254] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.540 UTC client backend[22254] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:57.566 UTC client backend[22272] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:57.566 UTC client backend[22272] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.049 UTC client backend[22444] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.049 UTC client backend[22444] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.050 UTC client backend[22442] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.050 UTC client backend[22442] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.053 UTC client backend[22443] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.053 UTC client backend[22443] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.054 UTC client backend[22449] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.054 UTC client backend[22449] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.056 UTC client backend[22447] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.056 UTC client backend[22447] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.057 UTC client backend[22446] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.057 UTC client backend[22446] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.061 UTC client backend[22445] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.061 UTC client backend[22445] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.062 UTC client backend[22451] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.062 UTC client backend[22451] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.062 UTC client backend[22452] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.062 UTC client backend[22452] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.064 UTC client backend[22453] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.064 UTC client backend[22453] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.064 UTC client backend[22454] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.064 UTC client backend[22454] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.066 UTC client backend[22456] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.066 UTC client backend[22456] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.067 UTC client backend[22459] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.067 UTC client backend[22459] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.079 UTC client backend[22450] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.079 UTC client backend[22450] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.081 UTC client backend[22462] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.081 UTC client backend[22462] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.081 UTC client backend[22457] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.081 UTC client backend[22457] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.086 UTC client backend[22465] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.086 UTC client backend[22465] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.090 UTC client backend[22461] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.090 UTC client backend[22461] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.100 UTC client backend[22468] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.100 UTC client backend[22468] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.102 UTC client backend[22466] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.102 UTC client backend[22466] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.373 UTC client backend[22576] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.373 UTC client backend[22576] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.376 UTC client backend[22577] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.376 UTC client backend[22577] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.500 UTC client backend[22623] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.500 UTC client backend[22623] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.501 UTC client backend[22624] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.501 UTC client backend[22624] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.502 UTC client backend[22626] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.502 UTC client backend[22626] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.514 UTC client backend[22627] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.514 UTC client backend[22627] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.516 UTC client backend[22628] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.516 UTC client backend[22628] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.517 UTC client backend[22634] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.517 UTC client backend[22634] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.518 UTC client backend[22631] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.518 UTC client backend[22631] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.520 UTC client backend[22632] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.520 UTC client backend[22632] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.520 UTC client backend[22636] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.520 UTC client backend[22636] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.521 UTC client backend[22625] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.521 UTC client backend[22625] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.523 UTC client backend[22635] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.523 UTC client backend[22635] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.523 UTC client backend[22638] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.523 UTC client backend[22638] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.524 UTC client backend[22637] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.524 UTC client backend[22637] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.525 UTC client backend[22645] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.525 UTC client backend[22645] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.526 UTC client backend[22642] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.526 UTC client backend[22642] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.532 UTC client backend[22639] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.532 UTC client backend[22639] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.534 UTC client backend[22640] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.534 UTC client backend[22640] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.536 UTC client backend[22643] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.536 UTC client backend[22643] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.826 UTC client backend[22763] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.826 UTC client backend[22763] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.831 UTC client backend[22764] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.831 UTC client backend[22764] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.835 UTC client backend[22768] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.835 UTC client backend[22768] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.839 UTC client backend[22767] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.839 UTC client backend[22767] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.839 UTC client backend[22766] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.839 UTC client backend[22766] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.839 UTC client backend[22770] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.839 UTC client backend[22770] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:58.848 UTC client backend[22772] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:58.848 UTC client backend[22772] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.026 UTC client backend[22858] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.026 UTC client backend[22858] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.101 UTC client backend[22874] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.101 UTC client backend[22874] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.141 UTC client backend[22882] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.141 UTC client backend[22882] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.175 UTC client backend[22899] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.175 UTC client backend[22899] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.195 UTC client backend[22903] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.195 UTC client backend[22903] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.301 UTC client backend[22938] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.301 UTC client backend[22938] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.301 UTC client backend[22936] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.301 UTC client backend[22936] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.302 UTC client backend[22937] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.302 UTC client backend[22937] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.304 UTC client backend[22942] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.304 UTC client backend[22942] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.305 UTC client backend[22940] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.305 UTC client backend[22940] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.306 UTC client backend[22939] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.306 UTC client backend[22939] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.307 UTC client backend[22943] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.307 UTC client backend[22943] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.308 UTC client backend[22941] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.308 UTC client backend[22941] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.309 UTC client backend[22944] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.309 UTC client backend[22944] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.309 UTC client backend[22947] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.309 UTC client backend[22947] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.310 UTC client backend[22946] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.310 UTC client backend[22946] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.310 UTC client backend[22945] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.310 UTC client backend[22945] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.312 UTC client backend[22952] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.312 UTC client backend[22952] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.313 UTC client backend[22950] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.313 UTC client backend[22950] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.314 UTC client backend[22951] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.314 UTC client backend[22951] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.315 UTC client backend[22949] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.315 UTC client backend[22949] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.324 UTC client backend[22948] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.324 UTC client backend[22948] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.491 UTC client backend[23058] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.491 UTC client backend[23058] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.492 UTC client backend[23060] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.492 UTC client backend[23060] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.494 UTC client backend[23061] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.494 UTC client backend[23061] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.494 UTC client backend[23063] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.494 UTC client backend[23063] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.495 UTC client backend[23062] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.495 UTC client backend[23062] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.501 UTC client backend[23057] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.501 UTC client backend[23057] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.502 UTC client backend[23066] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.502 UTC client backend[23066] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.504 UTC client backend[23064] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.504 UTC client backend[23064] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.505 UTC client backend[23067] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.505 UTC client backend[23067] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.865 UTC client backend[23172] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.865 UTC client backend[23172] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.868 UTC client backend[23174] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.868 UTC client backend[23174] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.872 UTC client backend[23168] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.872 UTC client backend[23168] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.873 UTC client backend[23170] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.873 UTC client backend[23170] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.875 UTC client backend[23173] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.875 UTC client backend[23173] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.878 UTC client backend[23177] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.878 UTC client backend[23177] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.879 UTC client backend[23175] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.879 UTC client backend[23175] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.881 UTC client backend[23181] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.881 UTC client backend[23181] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.883 UTC client backend[23182] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.883 UTC client backend[23182] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.883 UTC client backend[23179] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.883 UTC client backend[23179] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.884 UTC client backend[23184] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.884 UTC client backend[23184] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.884 UTC client backend[23178] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.884 UTC client backend[23178] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.885 UTC client backend[23183] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.885 UTC client backend[23183] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.886 UTC client backend[23188] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.886 UTC client backend[23188] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.887 UTC client backend[23186] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.887 UTC client backend[23186] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.888 UTC client backend[23187] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.888 UTC client backend[23187] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.888 UTC client backend[23180] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.888 UTC client backend[23180] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:19:59.889 UTC client backend[23185] [unknown] FATAL: the database system is not yet accepting connections 2024-05-05 02:19:59.889 UTC client backend[23185] [unknown] DETAIL: Consistent recovery state has not been yet reached. 2024-05-05 02:20:00.171 UTC startup[22183] LOG: invalid record length at 0/4C42DD8: expected at least 24, got 0 2024-05-05 02:20:00.171 UTC startup[22183] LOG: redo done at 0/4C42B70 system usage: CPU: user: 0.39 s, system: 0.13 s, elapsed: 2.75 s 2024-05-05 02:20:00.209 UTC checkpointer[22184] LOG: checkpoint starting: end-of-recovery immediate wait 2024-05-05 02:20:00.250 UTC checkpointer[22184] LOG: checkpoint complete: wrote 4496 buffers (27.4%); 0 WAL file(s) added, 0 removed, 3 recycled; write=0.040 s, sync=0.001 s, total=0.041 s; sync files=0, longest=0.000 s, average=0.000 s; distance=56465 kB, estimate=56465 kB; lsn=0/4C42DD8, redo lsn=0/4C42DD8 2024-05-05 02:20:00.255 UTC postmaster[19619] LOG: database system is ready to accept connections 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions ERROR: value 2 out of bounds for option "fillfactor" 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=2); 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions ERROR: value 110 out of bounds for option "fillfactor" 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=110); 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions ERROR: value -10.0 out of bounds for option "autovacuum_analyze_scale_factor" 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "0.000000" and "100.000000". 2024-05-05 02:20:00.580 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = -10.0); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: value 110.0 out of bounds for option "autovacuum_analyze_scale_factor" 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "0.000000" and "100.000000". 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = 110.0); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (not_existing_option=2); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: unrecognized parameter namespace "not_existing_namespace" 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (not_existing_namespace.fillfactor=2); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: value -30.1 out of bounds for option "fillfactor" 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=-30.1); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": string 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor='string'); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": true 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=true); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": 12 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=12); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": 30.5 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=30.5); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for boolean option "autovacuum_enabled": string 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled='string'); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for floating point option "autovacuum_analyze_scale_factor": string 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor='string'); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for floating point option "autovacuum_analyze_scale_factor": true 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor=true); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: parameter "fillfactor" specified more than once 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=30, fillfactor=40); 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions ERROR: invalid value for integer option "fillfactor": true 2024-05-05 02:20:00.581 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2(i INT) WITH (fillfactor); 2024-05-05 02:20:00.609 UTC client backend[23433] pg_regress/reloptions ERROR: RESET must not include values for parameters 2024-05-05 02:20:00.609 UTC client backend[23433] pg_regress/reloptions STATEMENT: ALTER TABLE reloptions_test RESET (fillfactor=12); 2024-05-05 02:20:00.619 UTC client backend[23439] pg_regress/partition_split ERROR: relation "sales_xxx" does not exist 2024-05-05 02:20:00.619 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: relation "sales_jan2022" already exists 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: invalid bound specification for a range partition at character 106 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: empty range bound specified for partition "sales_mar2022" at character 189 2024-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split DETAIL: Specified lower bound ('03-01-2022') is greater than or equal to upper bound ('02-01-2022'). 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: list of new partitions should contain at least two items 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_feb2022" is less than lower bound of split partition at character 112 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.620 UTC client backend[23439] pg_regress/partition_split ERROR: name "sales_feb_mar_apr2022" is already used at character 166 2024-05-05 02:20:00.620 UTC client backend[23439] 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-05-05 02:20:00.630 UTC client backend[23439] pg_regress/partition_split ERROR: name "sales_feb2022" is already used at character 158 2024-05-05 02:20:00.630 UTC client backend[23439] 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-05-05 02:20:00.630 UTC client backend[23439] pg_regress/partition_split ERROR: "sales_feb_mar_apr2022" is not a partitioned table 2024-05-05 02:20:00.630 UTC client backend[23439] 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-05-05 02:20:00.631 UTC client backend[23439] pg_regress/partition_split ERROR: upper bound of partition "sales_apr2022" is greater than upper bound of split partition at character 284 2024-05-05 02:20:00.631 UTC client backend[23439] 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-05-05 02:20:00.631 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_mar2022" conflicts with upper bound of previous partition "sales_feb2022" at character 189 2024-05-05 02:20:00.631 UTC client backend[23439] 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-05-05 02:20:00.637 UTC client backend[23440] pg_regress/hash_part ERROR: could not open relation with OID 0 2024-05-05 02:20:00.637 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition(0, 4, 0, NULL); 2024-05-05 02:20:00.637 UTC client backend[23433] pg_regress/reloptions ERROR: null value in column "i" of relation "reloptions_test" violates not-null constraint 2024-05-05 02:20:00.637 UTC client backend[23433] pg_regress/reloptions DETAIL: Failing row contains (null, null). 2024-05-05 02:20:00.637 UTC client backend[23433] pg_regress/reloptions STATEMENT: INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL); 2024-05-05 02:20:00.639 UTC client backend[23440] pg_regress/hash_part ERROR: "tenk1" is not a hash partitioned table 2024-05-05 02:20:00.639 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('tenk1'::regclass, 4, 0, NULL); 2024-05-05 02:20:00.640 UTC client backend[23433] pg_regress/reloptions ERROR: null value in column "i" of relation "reloptions_test" violates not-null constraint 2024-05-05 02:20:00.640 UTC client backend[23433] pg_regress/reloptions DETAIL: Failing row contains (null, null). 2024-05-05 02:20:00.640 UTC client backend[23433] pg_regress/reloptions STATEMENT: INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL); 2024-05-05 02:20:00.641 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_feb2022" is not equal to lower bound of split partition at character 112 2024-05-05 02:20:00.641 UTC client backend[23439] 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-05-05 02:20:00.645 UTC client backend[23440] pg_regress/hash_part ERROR: "mchash1" is not a hash partitioned table 2024-05-05 02:20:00.645 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash1'::regclass, 4, 0, NULL); 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part ERROR: modulus for hash partition must be an integer value greater than zero 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 0, 0, NULL); 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part ERROR: remainder for hash partition must be an integer value greater than or equal to zero 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 1, -1, NULL); 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part ERROR: remainder for hash partition must be less than modulus 2024-05-05 02:20:00.652 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 1, 1, NULL); 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (3) 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, NULL::int, NULL::text, NULL::json); 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (1) 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int); 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part ERROR: column 2 of the partition key has type text, but supplied value is of type integer 2024-05-05 02:20:00.653 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int); 2024-05-05 02:20:00.654 UTC client backend[23440] pg_regress/hash_part ERROR: column 2 of the partition key has type "text", but supplied value is of type "integer" 2024-05-05 02:20:00.654 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, variadic array[1,2]::int[]); 2024-05-05 02:20:00.657 UTC client backend[23437] pg_regress/explain ERROR: EXPLAIN options ANALYZE and GENERIC_PLAN cannot be used together 2024-05-05 02:20:00.657 UTC client backend[23437] pg_regress/explain CONTEXT: PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement 2024-05-05 02:20:00.657 UTC client backend[23437] pg_regress/explain STATEMENT: select explain_filter('explain (analyze, generic_plan) select unique1 from tenk1 where thousand = $1'); 2024-05-05 02:20:00.664 UTC client backend[23440] pg_regress/hash_part ERROR: number of partitioning columns (2) does not match number of partition keys provided (0) 2024-05-05 02:20:00.664 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0, variadic array[]::int[]); 2024-05-05 02:20:00.664 UTC client backend[23440] 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-05-05 02:20:00.664 UTC client backend[23440] pg_regress/hash_part STATEMENT: SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0, variadic array[now(), now()]); 2024-05-05 02:20:00.674 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.foo2" 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge ERROR: partition with name "sales_feb2022" is already used at character 73 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_range MERGE PARTITIONS (sales_feb2022, sales_mar2022, sales_feb2022) INTO sales_feb_mar_apr2022; 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge ERROR: "sales_apr2022" is not a table 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_range MERGE PARTITIONS (sales_feb2022, sales_mar2022, sales_apr2022) INTO sales_feb_mar_apr2022; 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge ERROR: lower bound of partition "sales_mar2022" conflicts with upper bound of previous partition "sales_jan2022" 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_range MERGE PARTITIONS (sales_jan2022, sales_mar2022) INTO sales_jan_mar2022; 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge ERROR: lower bound of partition "sales_jan2022" conflicts with upper bound of previous partition "sales_dec2021" 2024-05-05 02:20:00.686 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_range MERGE PARTITIONS (sales_dec2021, sales_jan2022, sales_feb2022) INTO sales_dec_jan_feb2022; 2024-05-05 02:20:00.690 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.foo" 2024-05-05 02:20:00.691 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.bar2" 2024-05-05 02:20:00.691 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.bar" 2024-05-05 02:20:00.691 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.z" 2024-05-05 02:20:00.692 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.parent2" 2024-05-05 02:20:00.693 UTC autovacuum worker[23454] LOG: autovacuum: dropping orphan temp table "regression.pg_temp_80.parent1" 2024-05-05 02:20:00.694 UTC client backend[23433] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2024-05-05 02:20:00.694 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE TABLE reloptions_test2 (i int) WITH (toast.not_existing_option = 42); 2024-05-05 02:20:00.709 UTC client backend[23431] pg_regress/indexing ERROR: cannot create index on partitioned table "idxpart" concurrently 2024-05-05 02:20:00.709 UTC client backend[23431] pg_regress/indexing STATEMENT: create index concurrently on idxpart (a); 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions ERROR: unrecognized parameter "not_existing_option" 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx ON reloptions_test (s) WITH (not_existing_option=2); 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions ERROR: unrecognized parameter namespace "not_existing_ns" 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx ON reloptions_test (s) WITH (not_existing_ns.fillfactor=2); 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions ERROR: value 1 out of bounds for option "fillfactor" 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=1); 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions ERROR: value 130 out of bounds for option "fillfactor" 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions DETAIL: Valid values are between "10" and "100". 2024-05-05 02:20:00.717 UTC client backend[23433] pg_regress/reloptions STATEMENT: CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=130); 2024-05-05 02:20:00.913 UTC client backend[23444] pg_regress/compression ERROR: column data type integer does not support compression 2024-05-05 02:20:00.913 UTC client backend[23444] pg_regress/compression STATEMENT: CREATE TABLE cmdata2 (f1 int COMPRESSION pglz); 2024-05-05 02:20:01.018 UTC client backend[23431] pg_regress/indexing ERROR: "idxpart_c" is not a partitioned table 2024-05-05 02:20:01.018 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart_c attach partition idxpart1_c for values from (10) to (20); 2024-05-05 02:20:01.023 UTC client backend[23431] pg_regress/indexing ERROR: ALTER action DETACH PARTITION cannot be performed on relation "idxpart_c" 2024-05-05 02:20:01.023 UTC client backend[23431] pg_regress/indexing DETAIL: This operation is not supported for partitioned indexes. 2024-05-05 02:20:01.023 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart_c detach partition idxpart1_c; 2024-05-05 02:20:01.036 UTC client backend[23439] pg_regress/partition_split ERROR: relation "sales_jan_feb2022" does not exist at character 15 2024-05-05 02:20:01.036 UTC client backend[23439] pg_regress/partition_split STATEMENT: SELECT * FROM sales_jan_feb2022; 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression ERROR: column "f1" has a compression method conflict 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression DETAIL: pglz versus lz4 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression STATEMENT: CREATE TABLE cminh() INHERITS(cmdata, cmdata1); 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression ERROR: column "f1" has a compression method conflict 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression DETAIL: pglz versus lz4 2024-05-05 02:20:01.144 UTC client backend[23444] pg_regress/compression STATEMENT: CREATE TABLE cminh(f1 TEXT COMPRESSION lz4) INHERITS(cmdata); 2024-05-05 02:20:01.145 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop index idxpart1_a_idx because index idxpart_a_idx requires it 2024-05-05 02:20:01.145 UTC client backend[23431] pg_regress/indexing HINT: You can drop index idxpart_a_idx instead. 2024-05-05 02:20:01.145 UTC client backend[23431] pg_regress/indexing STATEMENT: drop index idxpart1_a_idx; 2024-05-05 02:20:01.148 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop partitioned index "idxpart_a_idx" concurrently 2024-05-05 02:20:01.148 UTC client backend[23431] pg_regress/indexing STATEMENT: drop index concurrently idxpart_a_idx; 2024-05-05 02:20:01.155 UTC client backend[23444] pg_regress/compression ERROR: invalid value for parameter "default_toast_compression": "" 2024-05-05 02:20:01.155 UTC client backend[23444] pg_regress/compression HINT: Available values: pglz, lz4. 2024-05-05 02:20:01.155 UTC client backend[23444] pg_regress/compression STATEMENT: SET default_toast_compression = ''; 2024-05-05 02:20:01.156 UTC client backend[23444] pg_regress/compression ERROR: invalid value for parameter "default_toast_compression": "I do not exist compression" 2024-05-05 02:20:01.156 UTC client backend[23444] pg_regress/compression HINT: Available values: pglz, lz4. 2024-05-05 02:20:01.156 UTC client backend[23444] pg_regress/compression STATEMENT: SET default_toast_compression = 'I do not exist compression'; 2024-05-05 02:20:01.191 UTC client backend[23443] pg_regress/partition_prune ERROR: table "part_rev" contains column "c" not found in parent "part" 2024-05-05 02:20:01.191 UTC client backend[23443] pg_regress/partition_prune DETAIL: The new partition may contain only the columns present in parent. 2024-05-05 02:20:01.191 UTC client backend[23443] pg_regress/partition_prune STATEMENT: ALTER TABLE part ATTACH PARTITION part_rev FOR VALUES IN (3); 2024-05-05 02:20:01.191 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop index idxpart1_temp_a_idx because index idxpart_temp_a_idx requires it 2024-05-05 02:20:01.191 UTC client backend[23431] pg_regress/indexing HINT: You can drop index idxpart_temp_a_idx instead. 2024-05-05 02:20:01.191 UTC client backend[23431] pg_regress/indexing STATEMENT: drop index idxpart1_temp_a_idx; 2024-05-05 02:20:01.246 UTC client backend[23431] pg_regress/indexing ERROR: "idxpart" is not an index 2024-05-05 02:20:01.246 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart attach partition idxpart1; 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing ERROR: "idxpart1" is not an index 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1; 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart_a_b_idx" as a partition of index "idxpart_a_b_idx" 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing DETAIL: Index "idxpart_a_b_idx" is not an index on any partition of table "idxpart". 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart_a_b_idx; 2024-05-05 02:20:01.247 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170 2024-05-05 02:20:01.247 UTC client backend[23439] 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-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing ERROR: relation "idxpart1_b_idx" does not exist 2024-05-05 02:20:01.247 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_b_idx; 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst1" as a partition of index "idxpart_a_b_idx" 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst1; 2024-05-05 02:20:01.248 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_feb2022" conflicts with upper bound of previous partition "sales_error" at character 239 2024-05-05 02:20:01.248 UTC client backend[23439] 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-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst2" as a partition of index "idxpart_a_b_idx" 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst2; 2024-05-05 02:20:01.248 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170 2024-05-05 02:20:01.248 UTC client backend[23439] 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-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_tst3" as a partition of index "idxpart_a_b_idx" 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.248 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_tst3; 2024-05-05 02:20:01.248 UTC client backend[23439] pg_regress/partition_split ERROR: lower bound of partition "sales_error" conflicts with upper bound of previous partition "sales_dec2022" at character 170 2024-05-05 02:20:01.248 UTC client backend[23439] 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-05-05 02:20:01.249 UTC client backend[23439] pg_regress/partition_split ERROR: one partition in the list should be DEFAULT because split partition is DEFAULT at character 72 2024-05-05 02:20:01.249 UTC client backend[23439] 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-05-05 02:20:01.264 UTC client backend[23444] pg_regress/compression ERROR: invalid compression method "i_do_not_exist_compression" 2024-05-05 02:20:01.264 UTC client backend[23444] pg_regress/compression STATEMENT: CREATE TABLE badcompresstbl (a text COMPRESSION I_Do_Not_Exist_Compression); 2024-05-05 02:20:01.265 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_2_a_b" as a partition of index "idxpart_a_b_idx" 2024-05-05 02:20:01.265 UTC client backend[23431] pg_regress/indexing DETAIL: Another index is already attached for partition "idxpart1". 2024-05-05 02:20:01.265 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_b_idx attach partition idxpart1_2_a_b; 2024-05-05 02:20:01.267 UTC client backend[23444] pg_regress/compression ERROR: invalid compression method "i_do_not_exist_compression" 2024-05-05 02:20:01.267 UTC client backend[23444] pg_regress/compression STATEMENT: ALTER TABLE badcompresstbl ALTER a SET COMPRESSION I_Do_Not_Exist_Compression; 2024-05-05 02:20:01.363 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:01.387 UTC checkpointer[22184] LOG: checkpoint complete: wrote 1080 buffers (6.6%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.010 s, sync=0.001 s, total=0.026 s; sync files=0, longest=0.000 s, average=0.000 s; distance=6938 kB, estimate=51512 kB; lsn=0/53C7000, redo lsn=0/5309798 2024-05-05 02:20:01.395 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:01.406 UTC client backend[23439] pg_regress/partition_split ERROR: new row for relation "sales_mar2022" violates check constraint "sales_range_sales_amount_check" 2024-05-05 02:20:01.406 UTC client backend[23439] pg_regress/partition_split DETAIL: Failing row contains (1, 0, 03-11-2022). 2024-05-05 02:20:01.406 UTC client backend[23439] pg_regress/partition_split STATEMENT: INSERT INTO sales_range VALUES (1, 0, '2022-03-11'); 2024-05-05 02:20:01.407 UTC client backend[23439] pg_regress/partition_split ERROR: insert or update on table "sales_mar2022" violates foreign key constraint "sales_range_salesperson_id_fkey" 2024-05-05 02:20:01.407 UTC client backend[23439] pg_regress/partition_split DETAIL: Key (salesperson_id)=(-1) is not present in table "salespeople". 2024-05-05 02:20:01.407 UTC client backend[23439] pg_regress/partition_split STATEMENT: INSERT INTO sales_range VALUES (-1, 10, '2022-03-11'); 2024-05-05 02:20:01.409 UTC checkpointer[22184] LOG: checkpoint complete: wrote 508 buffers (3.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.015 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1244 kB, estimate=46486 kB; lsn=0/54BDC48, redo lsn=0/5440970 2024-05-05 02:20:01.419 UTC client backend[23514] pg_regress/stats ERROR: unrecognized reset target: "unknown" 2024-05-05 02:20:01.419 UTC client backend[23514] pg_regress/stats HINT: Target must be "archiver", "bgwriter", "checkpointer", "io", "recovery_prefetch", "slru", or "wal". 2024-05-05 02:20:01.419 UTC client backend[23514] pg_regress/stats STATEMENT: SELECT pg_stat_reset_shared('unknown'); 2024-05-05 02:20:01.442 UTC client backend[23514] pg_regress/stats ERROR: invalid statistics kind: "zaphod" 2024-05-05 02:20:01.442 UTC client backend[23514] pg_regress/stats STATEMENT: SELECT pg_stat_have_stats('zaphod', 0, 0); 2024-05-05 02:20:01.479 UTC client backend[23439] pg_regress/partition_split ERROR: insert or update on table "sales" violates foreign key constraint "sales_salesperson_id_fkey" 2024-05-05 02:20:01.479 UTC client backend[23439] pg_regress/partition_split DETAIL: Key (salesperson_id)=(40) is not present in table "salespeople". 2024-05-05 02:20:01.479 UTC client backend[23439] pg_regress/partition_split STATEMENT: INSERT INTO sales VALUES (40, 50, '2022-03-04'); 2024-05-05 02:20:01.618 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:01.622 UTC checkpointer[22184] LOG: checkpoint complete: wrote 412 buffers (2.5%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.004 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1945 kB, estimate=42032 kB; lsn=0/5634AB0, redo lsn=0/5626F20 2024-05-05 02:20:01.622 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:01.623 UTC checkpointer[22184] LOG: checkpoint complete: wrote 15 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=55 kB, estimate=37834 kB; lsn=0/5644B10, redo lsn=0/5634B28 2024-05-05 02:20:01.640 UTC client backend[23445] pg_regress/partition_merge ERROR: "sales_external" is not a partition 2024-05-05 02:20:01.640 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_east, sales_external) INTO sales_all; 2024-05-05 02:20:01.641 UTC client backend[23445] pg_regress/partition_merge ERROR: "sales_external2" is not a partition 2024-05-05 02:20:01.641 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_east, sales_external2) INTO sales_all; 2024-05-05 02:20:01.641 UTC client backend[23445] pg_regress/partition_merge ERROR: relation "sales_nord2" is not a partition of relation "sales_list" 2024-05-05 02:20:01.641 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE sales_list MERGE PARTITIONS (sales_west, sales_nord2, sales_east) INTO sales_all; 2024-05-05 02:20:01.780 UTC client backend[23445] pg_regress/partition_merge ERROR: relation "t1p1" is not a partition of relation "t2" 2024-05-05 02:20:01.780 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE t2 MERGE PARTITIONS (t1p1, t2pa) INTO t2p; 2024-05-05 02:20:01.780 UTC client backend[23445] pg_regress/partition_merge ERROR: "t3" is not a partition 2024-05-05 02:20:01.780 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE t2 MERGE PARTITIONS (t2pa, t3) INTO t2p; 2024-05-05 02:20:01.881 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart2_a_idx" as a partition of index "idxpart_a_idx" 2024-05-05 02:20:01.881 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.881 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_a_idx attach partition idxpart2_a_idx; 2024-05-05 02:20:01.899 UTC client backend[23439] pg_regress/partition_split ERROR: new partition "sales_east" would overlap with another (not split) partition "sales_nord" at character 200 2024-05-05 02:20:01.899 UTC client backend[23439] 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-05-05 02:20:01.904 UTC client backend[23439] pg_regress/partition_split ERROR: new partition "sales_west" would overlap with another new partition "sales_central" at character 94 2024-05-05 02:20:01.904 UTC client backend[23439] 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-05-05 02:20:01.904 UTC client backend[23439] pg_regress/partition_split ERROR: new partition "sales_west" cannot have NULL value because split partition does not have at character 126 2024-05-05 02:20:01.904 UTC client backend[23439] 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-05-05 02:20:01.909 UTC client backend[23439] pg_regress/partition_split ERROR: new partitions do not have value NULL but split partition does 2024-05-05 02:20:01.909 UTC client backend[23439] 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-05-05 02:20:01.909 UTC client backend[23439] pg_regress/partition_split ERROR: new partitions do not have value 'Kyiv' but split partition does 2024-05-05 02:20:01.909 UTC client backend[23439] 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-05-05 02:20:01.967 UTC client backend[23445] pg_regress/partition_merge ERROR: cannot create a temporary relation as partition of permanent relation "t" 2024-05-05 02:20:01.967 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE t MERGE PARTITIONS (tp_0_1, tp_1_2) INTO tp_0_2; 2024-05-05 02:20:01.968 UTC client backend[23445] pg_regress/partition_merge ERROR: cannot create a temporary relation as partition of permanent relation "t" 2024-05-05 02:20:01.968 UTC client backend[23445] pg_regress/partition_merge STATEMENT: ALTER TABLE t MERGE PARTITIONS (tp_0_1, tp_1_2) INTO pg_temp.tp_0_2; 2024-05-05 02:20:01.979 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_1b_idx" as a partition of index "idxpart_1_idx" 2024-05-05 02:20:01.979 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.979 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_1_idx attach partition idxpart1_1b_idx; 2024-05-05 02:20:01.983 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_2b_idx" as a partition of index "idxpart_2_idx" 2024-05-05 02:20:01.983 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.983 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_2_idx attach partition idxpart1_2b_idx; 2024-05-05 02:20:01.984 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_2c_idx" as a partition of index "idxpart_2_idx" 2024-05-05 02:20:01.984 UTC client backend[23431] pg_regress/indexing DETAIL: The index definitions do not match. 2024-05-05 02:20:01.984 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_2_idx attach partition idxpart1_2c_idx; 2024-05-05 02:20:02.035 UTC client backend[23701] pg_regress/stats LOG: wait_for_hot_stats delayed 0.000525 seconds 2024-05-05 02:20:02.035 UTC client backend[23701] pg_regress/stats CONTEXT: PL/pgSQL function wait_for_hot_stats() line 17 at RAISE 2024-05-05 02:20:02.035 UTC client backend[23701] pg_regress/stats STATEMENT: SELECT wait_for_hot_stats(); 2024-05-05 02:20:02.226 UTC client backend[23439] pg_regress/partition_split ERROR: relation "t1pa" is not a partition of relation "t2" 2024-05-05 02:20:02.226 UTC client backend[23439] 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-05-05 02:20:02.379 UTC client backend[23431] pg_regress/indexing ERROR: multiple primary keys for table "failpart" are not allowed 2024-05-05 02:20:02.379 UTC client backend[23431] pg_regress/indexing STATEMENT: create table failpart partition of idxpart (b primary key) for values from (0) to (100); 2024-05-05 02:20:02.416 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.416 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.416 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int unique, b int) partition by range (a, b); 2024-05-05 02:20:02.421 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.421 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2024-05-05 02:20:02.421 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int, b int unique) partition by range (a, b); 2024-05-05 02:20:02.422 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.422 UTC client backend[23431] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.422 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int primary key, b int) partition by range (b, a); 2024-05-05 02:20:02.425 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.425 UTC client backend[23431] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "a" which is part of the partition key. 2024-05-05 02:20:02.425 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int, b int primary key) partition by range (b, a); 2024-05-05 02:20:02.455 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.455 UTC client backend[23431] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.455 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int4range, b int4range, exclude USING GIST (a with = )) partition by range (a, b); 2024-05-05 02:20:02.461 UTC client backend[23431] pg_regress/indexing ERROR: cannot match partition key to index on column "a" using non-equal operator "-|-" 2024-05-05 02:20:02.461 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int4range, exclude USING GIST (a with -|- )) partition by range (a); 2024-05-05 02:20:02.469 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.469 UTC client backend[23431] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2024-05-05 02:20:02.469 UTC client backend[23431] 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-05-05 02:20:02.475 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.0", size 499712 2024-05-05 02:20:02.475 UTC client backend[23426] pg_regress/tuplesort STATEMENT: COMMIT; 2024-05-05 02:20:02.481 UTC client backend[23431] pg_regress/indexing ERROR: unsupported PRIMARY KEY constraint with partition key definition 2024-05-05 02:20:02.481 UTC client backend[23431] pg_regress/indexing DETAIL: PRIMARY KEY constraints cannot be used when partition keys include expressions. 2024-05-05 02:20:02.481 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int primary key, b int) partition by range ((b + a)); 2024-05-05 02:20:02.482 UTC client backend[23431] pg_regress/indexing ERROR: unsupported UNIQUE constraint with partition key definition 2024-05-05 02:20:02.482 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraints cannot be used when partition keys include expressions. 2024-05-05 02:20:02.482 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart (a int unique, b int) partition by range ((b + a)); 2024-05-05 02:20:02.483 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.483 UTC client backend[23431] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.483 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart add primary key (a); 2024-05-05 02:20:02.534 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.534 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.534 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart add unique (a); 2024-05-05 02:20:02.559 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.559 UTC client backend[23431] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.559 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (a with =); 2024-05-05 02:20:02.560 UTC client backend[23431] pg_regress/indexing ERROR: cannot match partition key to index on column "a" using non-equal operator "-|-" 2024-05-05 02:20:02.560 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (a with -|-); 2024-05-05 02:20:02.568 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.568 UTC client backend[23431] pg_regress/indexing DETAIL: EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key. 2024-05-05 02:20:02.568 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart add exclude USING GIST (b with =, c with &&); 2024-05-05 02:20:02.609 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.609 UTC client backend[23431] pg_regress/indexing DETAIL: PRIMARY KEY constraint on table "idxpart2" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.609 UTC client backend[23431] pg_regress/indexing STATEMENT: create table idxpart2 partition of idxpart for values from (0) to (1000) partition by range (b); 2024-05-05 02:20:02.616 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.616 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraint on table "idxpart1" lacks column "b" which is part of the partition key. 2024-05-05 02:20:02.616 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart attach partition idxpart1 for values from (1) to (1000); 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop index idxpart0_pkey because index idxpart_pkey requires it 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing HINT: You can drop index idxpart_pkey instead. 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing STATEMENT: drop index idxpart0_pkey; 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop index idxpart1_pkey because index idxpart_pkey requires it 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing HINT: You can drop index idxpart_pkey instead. 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing STATEMENT: drop index idxpart1_pkey; 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop inherited constraint "idxpart0_pkey" of relation "idxpart0" 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart0 drop constraint idxpart0_pkey; 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop inherited constraint "idxpart1_pkey" of relation "idxpart1" 2024-05-05 02:20:02.667 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart1 drop constraint idxpart1_pkey; 2024-05-05 02:20:02.685 UTC client backend[23431] pg_regress/indexing ERROR: multiple primary keys for table "idxpart1" are not allowed 2024-05-05 02:20:02.685 UTC client backend[23431] pg_regress/indexing STATEMENT: ALTER TABLE idxpart ATTACH PARTITION idxpart1 FOR VALUES FROM (100) TO (200); 2024-05-05 02:20:02.700 UTC client backend[23431] pg_regress/indexing ERROR: multiple primary keys for table "idxpart11" are not allowed 2024-05-05 02:20:02.700 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart attach partition idxpart1 for values from (0) to (10000); 2024-05-05 02:20:02.821 UTC client backend[23431] pg_regress/indexing ERROR: invalid primary key definition 2024-05-05 02:20:02.821 UTC client backend[23431] pg_regress/indexing DETAIL: Column "a" of relation "idxpart0" is not marked NOT NULL. 2024-05-05 02:20:02.821 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_pkey attach partition idxpart0_a_key; 2024-05-05 02:20:02.826 UTC client backend[23431] pg_regress/indexing ERROR: column "a" is marked NOT NULL in parent table 2024-05-05 02:20:02.826 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table idxpart0 alter column a drop not null; 2024-05-05 02:20:02.849 UTC client backend[23431] pg_regress/indexing ERROR: cannot attach index "idxpart1_a_idx" as a partition of index "idxpart_pkey" 2024-05-05 02:20:02.849 UTC client backend[23431] 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-05-05 02:20:02.849 UTC client backend[23431] pg_regress/indexing STATEMENT: alter index idxpart_pkey attach partition idxpart1_a_idx; 2024-05-05 02:20:02.865 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart1_a_idx" 2024-05-05 02:20:02.865 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(65536) already exists. 2024-05-05 02:20:02.865 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into idxpart select 2^g, format('two to power of %s', g) from generate_series(15, 17) g; 2024-05-05 02:20:02.873 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart2_a_idx" 2024-05-05 02:20:02.873 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(285714) already exists. 2024-05-05 02:20:02.873 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into idxpart select a * 2, b || b from idxpart where a between 2^16 and 2^19; 2024-05-05 02:20:02.874 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "idxpart2_a_idx" 2024-05-05 02:20:02.874 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(572814) already exists. 2024-05-05 02:20:02.874 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into idxpart values (572814, 'five'); 2024-05-05 02:20:02.883 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.3", size 425984 2024-05-05 02:20:02.883 UTC client backend[23426] 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-05-05 02:20:02.894 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.4", size 270336 2024-05-05 02:20:02.894 UTC client backend[23426] 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-05-05 02:20:02.907 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.2", size 876544 2024-05-05 02:20:02.907 UTC client backend[23426] 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-05-05 02:20:02.907 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.6", size 270336 2024-05-05 02:20:02.907 UTC client backend[23426] 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-05-05 02:20:02.907 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.7", size 425984 2024-05-05 02:20:02.907 UTC client backend[23426] 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-05-05 02:20:02.907 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.5", size 344064 2024-05-05 02:20:02.907 UTC client backend[23426] 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-05-05 02:20:02.908 UTC client backend[23426] pg_regress/tuplesort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp23426.1", size 974848 2024-05-05 02:20:02.908 UTC client backend[23426] 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-05-05 02:20:02.934 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart1_a_b_idx" 2024-05-05 02:20:02.934 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(1) already exists. 2024-05-05 02:20:02.934 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into covidxpart values (1, 1); 2024-05-05 02:20:02.937 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart3_a_b_idx" 2024-05-05 02:20:02.937 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(3) already exists. 2024-05-05 02:20:02.937 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into covidxpart values (3, 1); 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing ERROR: duplicate key value violates unique constraint "covidxpart4_a_b_idx" 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing DETAIL: Key (a)=(4) already exists. 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing STATEMENT: insert into covidxpart values (4, 1); 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing ERROR: unique constraint on partitioned table must include all partitioning columns 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing DETAIL: UNIQUE constraint on table "covidxpart" lacks column "a" which is part of the partition key. 2024-05-05 02:20:02.940 UTC client backend[23431] pg_regress/indexing STATEMENT: create unique index on covidxpart (b) include (a); 2024-05-05 02:20:02.947 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop inherited constraint "parted_pk_detach_test1_pkey" of relation "parted_pk_detach_test1" 2024-05-05 02:20:02.947 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table parted_pk_detach_test1 drop constraint parted_pk_detach_test1_pkey; 2024-05-05 02:20:02.954 UTC client backend[23431] pg_regress/indexing ERROR: cannot drop inherited constraint "parted_uniq_detach_test1_a_key" of relation "parted_uniq_detach_test1" 2024-05-05 02:20:02.954 UTC client backend[23431] pg_regress/indexing STATEMENT: alter table parted_uniq_detach_test1 drop constraint parted_uniq_detach_test1_a_key; 2024-05-05 02:20:03.047 UTC client backend[23431] pg_regress/indexing ERROR: division by zero 2024-05-05 02:20:03.047 UTC client backend[23431] pg_regress/indexing STATEMENT: create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b)); 2024-05-05 02:20:03.469 UTC client backend[24274] pg_regress/event_trigger ERROR: function pg_backend_pid must return type event_trigger 2024-05-05 02:20:03.469 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger on ddl_command_start execute procedure pg_backend_pid(); 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger ERROR: trigger functions can only be called as triggers 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger CONTEXT: compilation of PL/pgSQL function "test_event_trigger" near line 1 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger STATEMENT: SELECT test_event_trigger(); 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger ERROR: event trigger functions cannot have declared arguments 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger CONTEXT: compilation of PL/pgSQL function "test_event_trigger_arg" near line 1 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create function test_event_trigger_arg(name text) returns event_trigger as $$ BEGIN RETURN 1; END $$ language plpgsql; 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger ERROR: SQL functions cannot return type event_trigger 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create function test_event_trigger_sql() returns event_trigger as $$ SELECT 1 $$ language sql; 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger ERROR: unrecognized event name "elephant_bootstrap" 2024-05-05 02:20:03.471 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger on elephant_bootstrap execute procedure test_event_trigger(); 2024-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: unrecognized filter variable "food" 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: filter value "sandwich" not recognized for filter variable "tag" 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: filter value "create skunkcabbage" not recognized for filter variable "tag" 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: event triggers are not supported for DROP EVENT TRIGGER 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE ROLE 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE DATABASE 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: event triggers are not supported for CREATE TABLESPACE 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: filter variable "tag" specified more than once 2024-05-05 02:20:03.472 UTC client backend[24274] 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-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger ERROR: syntax error at or near "'argument not allowed'" at character 106 2024-05-05 02:20:03.472 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger2 on ddl_command_start execute procedure test_event_trigger('argument not allowed'); 2024-05-05 02:20:03.473 UTC client backend[24274] pg_regress/event_trigger ERROR: permission denied to create event trigger "regress_event_trigger_noperms" 2024-05-05 02:20:03.473 UTC client backend[24274] pg_regress/event_trigger HINT: Must be superuser to create an event trigger. 2024-05-05 02:20:03.473 UTC client backend[24274] pg_regress/event_trigger STATEMENT: create event trigger regress_event_trigger_noperms on ddl_command_start execute procedure test_event_trigger(); 2024-05-05 02:20:03.492 UTC client backend[24274] pg_regress/event_trigger ERROR: permission denied to change owner of event trigger "regress_event_trigger" 2024-05-05 02:20:03.492 UTC client backend[24274] pg_regress/event_trigger HINT: The owner of an event trigger must be a superuser. 2024-05-05 02:20:03.492 UTC client backend[24274] pg_regress/event_trigger STATEMENT: alter event trigger regress_event_trigger owner to regress_evt_user; 2024-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger ERROR: event trigger "regress_event_trigger2" already exists 2024-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger STATEMENT: alter event trigger regress_event_trigger rename to regress_event_trigger2; 2024-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger ERROR: event trigger "regress_event_trigger" does not exist 2024-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger STATEMENT: drop event trigger regress_event_trigger; 2024-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger ERROR: role "regress_evt_user" cannot be dropped because some objects depend on it 2024-05-05 02:20:03.493 UTC client backend[24274] 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-05-05 02:20:03.493 UTC client backend[24274] pg_regress/event_trigger STATEMENT: drop role regress_evt_user; 2024-05-05 02:20:03.511 UTC client backend[24274] pg_regress/event_trigger ERROR: object audit_tbls.schema_two_table_three of type table cannot be dropped 2024-05-05 02:20:03.511 UTC client backend[24274] 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-05-05 02:20:03.511 UTC client backend[24274] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2024-05-05 02:20:03.514 UTC client backend[24274] pg_regress/event_trigger ERROR: object schema_one.table_three of type table cannot be dropped 2024-05-05 02:20:03.514 UTC client backend[24274] pg_regress/event_trigger CONTEXT: PL/pgSQL function undroppable() line 14 at RAISE 2024-05-05 02:20:03.514 UTC client backend[24274] pg_regress/event_trigger STATEMENT: DROP SCHEMA schema_one, schema_two CASCADE; 2024-05-05 02:20:03.567 UTC client backend[24274] pg_regress/event_trigger ERROR: pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function 2024-05-05 02:20:03.567 UTC client backend[24274] pg_regress/event_trigger STATEMENT: select pg_event_trigger_table_rewrite_oid(); 2024-05-05 02:20:03.573 UTC client backend[24274] pg_regress/event_trigger ERROR: rewrites not allowed 2024-05-05 02:20:03.573 UTC client backend[24274] pg_regress/event_trigger CONTEXT: PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE 2024-05-05 02:20:03.573 UTC client backend[24274] pg_regress/event_trigger STATEMENT: alter table rewriteme alter column foo type numeric; 2024-05-05 02:20:03.595 UTC client backend[24274] pg_regress/event_trigger ERROR: cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it 2024-05-05 02:20:03.595 UTC client backend[24274] pg_regress/event_trigger STATEMENT: alter type rewritetype alter attribute a type varchar cascade; 2024-05-05 02:20:04.156 UTC client backend[24848] pg_regress/tablespace ERROR: tablespace location must be an absolute path 2024-05-05 02:20:04.156 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLESPACE regress_tblspace LOCATION 'relative'; 2024-05-05 02:20:04.156 UTC client backend[24848] pg_regress/tablespace ERROR: tablespace location must be an absolute path 2024-05-05 02:20:04.156 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLESPACE regress_tblspace LOCATION ''; 2024-05-05 02:20:04.157 UTC client backend[24848] pg_regress/tablespace ERROR: unrecognized parameter "some_nonexistent_parameter" 2024-05-05 02:20:04.157 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLESPACE regress_tblspacewith LOCATION '' WITH (some_nonexistent_parameter = true); 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace ERROR: unrecognized parameter "some_nonexistent_parameter" 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace STATEMENT: ALTER TABLESPACE regress_tblspace SET (some_nonexistent_parameter = true); 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace ERROR: RESET must not include values for parameters 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace STATEMENT: ALTER TABLESPACE regress_tblspace RESET (random_page_cost = 2.0); 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move system relation "pg_am_name_index" 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE pg_am; 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:20:04.159 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_am; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move system relation "pg_authid_rolname_index" 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE pg_authid; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_authid; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move system relation "pg_toast_1260_index" 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) INDEX pg_toast.pg_toast_1260_index; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) INDEX CONCURRENTLY pg_toast.pg_toast_1260_index; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move system relation "pg_toast_1260_index" 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE pg_toast.pg_toast_1260; 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:20:04.160 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_toast.pg_toast_1260; 2024-05-05 02:20:04.161 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move system relation "pg_authid_rolname_index" 2024-05-05 02:20:04.161 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE pg_global) TABLE pg_authid; 2024-05-05 02:20:04.161 UTC client backend[24848] pg_regress/tablespace ERROR: cannot reindex system catalogs concurrently 2024-05-05 02:20:04.161 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE pg_global) TABLE CONCURRENTLY pg_authid; 2024-05-05 02:20:04.166 UTC client backend[24848] pg_regress/tablespace ERROR: only shared relations can be placed in pg_global tablespace 2024-05-05 02:20:04.166 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE pg_global) INDEX regress_tblspace_test_tbl_idx; 2024-05-05 02:20:04.166 UTC client backend[24848] pg_regress/tablespace ERROR: cannot move non-shared relation to tablespace "pg_global" 2024-05-05 02:20:04.166 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE pg_global) INDEX CONCURRENTLY regress_tblspace_test_tbl_idx; 2024-05-05 02:20:04.225 UTC client backend[24848] pg_regress/tablespace ERROR: only shared relations can be placed in pg_global tablespace 2024-05-05 02:20:04.225 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.part_1 PARTITION OF testschema.part FOR VALUES IN (1); 2024-05-05 02:20:04.227 UTC client backend[24848] pg_regress/tablespace ERROR: only shared relations can be placed in pg_global tablespace 2024-05-05 02:20:04.227 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.part_3 PARTITION OF testschema.part FOR VALUES IN (3); 2024-05-05 02:20:04.229 UTC client backend[24848] pg_regress/tablespace ERROR: only shared relations can be placed in pg_global tablespace 2024-05-05 02:20:04.229 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.part_78 PARTITION OF testschema.part FOR VALUES IN (7, 8) PARTITION BY LIST (a); 2024-05-05 02:20:04.274 UTC client backend[24848] pg_regress/tablespace ERROR: cannot specify default tablespace for partitioned relations 2024-05-05 02:20:04.274 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE pg_default; 2024-05-05 02:20:04.274 UTC client backend[24848] pg_regress/tablespace ERROR: cannot specify default tablespace for partitioned relations 2024-05-05 02:20:04.274 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE pg_default) PARTITION BY LIST (a); 2024-05-05 02:20:04.275 UTC client backend[24848] pg_regress/tablespace ERROR: cannot specify default tablespace for partitioned relations 2024-05-05 02:20:04.275 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE regress_tblspace; 2024-05-05 02:20:04.275 UTC client backend[24848] pg_regress/tablespace ERROR: cannot specify default tablespace for partitioned relations 2024-05-05 02:20:04.275 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE regress_tblspace) PARTITION BY LIST (a); 2024-05-05 02:20:04.494 UTC client backend[24848] pg_regress/tablespace ERROR: only shared relations can be placed in pg_global tablespace 2024-05-05 02:20:04.494 UTC client backend[24848] pg_regress/tablespace STATEMENT: ALTER INDEX testschema.part_a_idx SET TABLESPACE pg_global; 2024-05-05 02:20:04.495 UTC client backend[24848] pg_regress/tablespace ERROR: duplicate key value violates unique constraint "anindex" 2024-05-05 02:20:04.495 UTC client backend[24848] pg_regress/tablespace DETAIL: Key (column1)=(1) already exists. 2024-05-05 02:20:04.495 UTC client backend[24848] pg_regress/tablespace STATEMENT: INSERT INTO testschema.atable VALUES(1); 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace ERROR: directory "/no/such/location" does not exist 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLESPACE regress_badspace LOCATION '/no/such/location'; 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace ERROR: tablespace "regress_nosuchspace" does not exist 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE bar (i int) TABLESPACE regress_nosuchspace; 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace ERROR: tablespace "regress_tblspace" cannot be dropped because some objects depend on it 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace DETAIL: tablespace for index testschema.part_a_idx 2024-05-05 02:20:04.498 UTC client backend[24848] pg_regress/tablespace STATEMENT: DROP TABLESPACE regress_tblspace; 2024-05-05 02:20:04.499 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:04.515 UTC checkpointer[22184] LOG: checkpoint complete: wrote 1340 buffers (8.2%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.007 s, sync=0.001 s, total=0.017 s; sync files=0, longest=0.000 s, average=0.000 s; distance=13150 kB, estimate=35365 kB; lsn=0/630C3C8, redo lsn=0/630C370 2024-05-05 02:20:04.516 UTC client backend[24848] pg_regress/tablespace ERROR: tablespace "regress_tblspace" is not empty 2024-05-05 02:20:04.516 UTC client backend[24848] pg_regress/tablespace STATEMENT: DROP TABLESPACE regress_tblspace; 2024-05-05 02:20:04.520 UTC client backend[24848] pg_regress/tablespace ERROR: permission denied for tablespace regress_tblspace 2024-05-05 02:20:04.520 UTC client backend[24848] pg_regress/tablespace STATEMENT: CREATE TABLE tablespace_table (i int) TABLESPACE regress_tblspace; 2024-05-05 02:20:04.523 UTC client backend[24848] pg_regress/tablespace ERROR: permission denied for tablespace regress_tblspace 2024-05-05 02:20:04.523 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace) TABLE tablespace_table; 2024-05-05 02:20:04.523 UTC client backend[24848] pg_regress/tablespace ERROR: permission denied for tablespace regress_tblspace 2024-05-05 02:20:04.523 UTC client backend[24848] pg_regress/tablespace STATEMENT: REINDEX (TABLESPACE regress_tblspace, CONCURRENTLY) TABLE tablespace_table; 2024-05-05 02:20:04.528 UTC checkpointer[22184] LOG: checkpoint starting: immediate force wait 2024-05-05 02:20:04.529 UTC checkpointer[22184] LOG: checkpoint complete: wrote 41 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=318 kB, estimate=31861 kB; lsn=0/635BBD8, redo lsn=0/635BB80 2024-05-05 02:20:04.554 UTC postmaster[19619] LOG: received fast shutdown request 2024-05-05 02:20:04.554 UTC postmaster[19619] LOG: aborting any active transactions 2024-05-05 02:20:04.558 UTC postmaster[19619] LOG: background worker "logical replication launcher" (PID 23342) exited with exit code 1 2024-05-05 02:20:04.559 UTC checkpointer[22184] LOG: shutting down 2024-05-05 02:20:04.559 UTC checkpointer[22184] LOG: checkpoint starting: shutdown immediate 2024-05-05 02:20:04.559 UTC checkpointer[22184] LOG: checkpoint complete: wrote 23 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.001 s; sync files=0, longest=0.000 s, average=0.000 s; distance=94 kB, estimate=28684 kB; lsn=0/6373408, redo lsn=0/6373408 2024-05-05 02:20:04.569 UTC postmaster[19619] LOG: database system is shut down