2025-11-17 08:40:43.315 UTC postmaster[21503] LOG: starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit 2025-11-17 08:40:43.315 UTC postmaster[21503] LOG: listening on Unix socket "/tmp/pg_regress-EAgJGZ/.s.PGSQL.58928" 2025-11-17 08:40:43.345 UTC startup[21528] LOG: database system was shut down at 2025-11-17 08:40:43 UTC 2025-11-17 08:40:43.348 UTC unrecognized[21529] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:43.348 UTC client backend[21529] [unknown] FATAL: the database system is starting up 2025-11-17 08:40:43.371 UTC postmaster[21503] LOG: database system is ready to accept connections 2025-11-17 08:40:43.409 UTC unrecognized[21550] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:43.416 UTC client backend[21550] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:43.416 UTC client backend[21550] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-17 08:40:43.460 UTC client backend[21550] pg_regress LOG: connection ready: setup total=54.180 ms, fork=2.981 ms, authentication=5.389 ms 2025-11-17 08:40:43.461 UTC client backend[21550] pg_regress LOG: disconnection: session time: 0:00:00.051 user=postgres database=postgres host=[local] 2025-11-17 08:40:43.492 UTC unrecognized[21577] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:43.494 UTC client backend[21577] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:43.494 UTC client backend[21577] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-11-17 08:40:43.496 UTC client backend[21577] pg_regress LOG: connection ready: setup total=9.480 ms, fork=4.959 ms, authentication=0.446 ms 2025-11-17 08:40:43.648 UTC client backend[21577] pg_regress LOG: disconnection: session time: 0:00:00.155 user=postgres database=postgres host=[local] 2025-11-17 08:40:43.692 UTC unrecognized[21602] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:43.693 UTC client backend[21602] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:43.693 UTC client backend[21602] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/test_setup 2025-11-17 08:40:43.740 UTC client backend[21602] pg_regress/test_setup LOG: connection ready: setup total=52.576 ms, fork=1.539 ms, authentication=0.358 ms 2025-11-17 08:40:44.749 UTC client backend[21602] pg_regress/test_setup LOG: disconnection: session time: 0:00:01.060 user=postgres database=regression host=[local] 2025-11-17 08:40:44.819 UTC unrecognized[21814] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.821 UTC client backend[21814] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.821 UTC client backend[21814] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/name 2025-11-17 08:40:44.823 UTC client backend[21814] pg_regress/name LOG: connection ready: setup total=7.539 ms, fork=3.004 ms, authentication=0.340 ms 2025-11-17 08:40:44.824 UTC unrecognized[21815] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.825 UTC client backend[21815] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.825 UTC client backend[21815] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/char 2025-11-17 08:40:44.840 UTC unrecognized[21820] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.842 UTC client backend[21820] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.842 UTC client backend[21820] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/varchar 2025-11-17 08:40:44.844 UTC unrecognized[21824] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.845 UTC client backend[21824] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.845 UTC client backend[21824] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/boolean 2025-11-17 08:40:44.853 UTC client backend[21815] pg_regress/char LOG: connection ready: setup total=35.571 ms, fork=1.333 ms, authentication=0.375 ms 2025-11-17 08:40:44.853 UTC unrecognized[21829] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.854 UTC client backend[21829] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.854 UTC client backend[21829] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int4 2025-11-17 08:40:44.860 UTC unrecognized[21828] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.861 UTC client backend[21828] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.861 UTC client backend[21828] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/text 2025-11-17 08:40:44.864 UTC unrecognized[21830] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.865 UTC client backend[21830] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.865 UTC client backend[21830] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int2 2025-11-17 08:40:44.877 UTC client backend[21829] pg_regress/int4 LOG: connection ready: setup total=27.844 ms, fork=2.504 ms, authentication=0.359 ms 2025-11-17 08:40:44.879 UTC client backend[21820] pg_regress/varchar LOG: connection ready: setup total=60.186 ms, fork=21.574 ms, authentication=0.351 ms 2025-11-17 08:40:44.884 UTC client backend[21824] pg_regress/boolean LOG: connection ready: setup total=51.348 ms, fork=10.894 ms, authentication=0.316 ms 2025-11-17 08:40:44.885 UTC unrecognized[21833] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.886 UTC client backend[21833] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.886 UTC client backend[21833] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float8 2025-11-17 08:40:44.888 UTC unrecognized[21834] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.888 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "34.5" at character 34 2025-11-17 08:40:44.888 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('34.5'); 2025-11-17 08:40:44.889 UTC client backend[21834] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.889 UTC client backend[21834] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float4 2025-11-17 08:40:44.892 UTC client backend[21815] pg_regress/char ERROR: value too long for type character(1) 2025-11-17 08:40:44.892 UTC client backend[21815] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('cd'); 2025-11-17 08:40:44.892 UTC unrecognized[21835] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.893 UTC client backend[21828] pg_regress/text LOG: connection ready: setup total=44.762 ms, fork=11.806 ms, authentication=0.357 ms 2025-11-17 08:40:44.893 UTC client backend[21830] pg_regress/int2 LOG: connection ready: setup total=43.138 ms, fork=13.379 ms, authentication=0.319 ms 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 ERROR: value "1000000000000" is out of range for type integer at character 34 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('1000000000000'); 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "asdf" at character 34 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('asdf'); 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: " " at character 34 2025-11-17 08:40:44.894 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' '); 2025-11-17 08:40:44.895 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: " asdf " at character 34 2025-11-17 08:40:44.895 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' asdf '); 2025-11-17 08:40:44.895 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "- 1234" at character 34 2025-11-17 08:40:44.895 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('- 1234'); 2025-11-17 08:40:44.895 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "34.5" at character 34 2025-11-17 08:40:44.895 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('34.5'); 2025-11-17 08:40:44.896 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "123 5" at character 34 2025-11-17 08:40:44.896 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('123 5'); 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: value "100000" is out of range for type smallint at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('100000'); 2025-11-17 08:40:44.896 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "" at character 34 2025-11-17 08:40:44.896 UTC client backend[21829] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (''); 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "asdf" at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('asdf'); 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: " " at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (' '); 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "- 1234" at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('- 1234'); 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "4 444" at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('4 444'); 2025-11-17 08:40:44.896 UTC client backend[21835] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.896 UTC client backend[21835] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/oid 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "123 dt" at character 34 2025-11-17 08:40:44.896 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('123 dt'); 2025-11-17 08:40:44.897 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "" at character 34 2025-11-17 08:40:44.897 UTC client backend[21830] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (''); 2025-11-17 08:40:44.899 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "test" at character 13 2025-11-17 08:40:44.899 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'test' AS error; 2025-11-17 08:40:44.900 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "foo" at character 13 2025-11-17 08:40:44.900 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'foo' AS error; 2025-11-17 08:40:44.903 UTC unrecognized[21837] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.903 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "yeah" at character 13 2025-11-17 08:40:44.903 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'yeah' AS error; 2025-11-17 08:40:44.904 UTC unrecognized[21836] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.905 UTC client backend[21837] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.905 UTC client backend[21837] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/txid 2025-11-17 08:40:44.905 UTC client backend[21836] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.905 UTC client backend[21836] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numeric 2025-11-17 08:40:44.907 UTC client backend[21837] pg_regress/txid LOG: connection ready: setup total=8.625 ms, fork=3.511 ms, authentication=0.605 ms 2025-11-17 08:40:44.907 UTC client backend[21836] pg_regress/numeric LOG: connection ready: setup total=24.611 ms, fork=16.257 ms, authentication=0.325 ms 2025-11-17 08:40:44.908 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "nay" at character 13 2025-11-17 08:40:44.908 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'nay' AS error; 2025-11-17 08:40:44.908 UTC unrecognized[21838] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.910 UTC client backend[21838] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.910 UTC client backend[21838] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int8 2025-11-17 08:40:44.917 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "o" at character 13 2025-11-17 08:40:44.917 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'o' AS error; 2025-11-17 08:40:44.917 UTC client backend[21835] pg_regress/oid LOG: connection ready: setup total=35.697 ms, fork=10.175 ms, authentication=0.334 ms 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "on_" at character 13 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'on_' AS error; 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "off_" at character 13 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool 'off_' AS error; 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "11" at character 13 2025-11-17 08:40:44.918 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool '11' AS error; 2025-11-17 08:40:44.919 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "000" at character 13 2025-11-17 08:40:44.919 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool '000' AS error; 2025-11-17 08:40:44.919 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" at character 13 2025-11-17 08:40:44.919 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT bool '' AS error; 2025-11-17 08:40:44.919 UTC unrecognized[21840] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.920 UTC client backend[21828] pg_regress/text ERROR: function length(integer) does not exist at character 8 2025-11-17 08:40:44.920 UTC client backend[21828] pg_regress/text DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:44.920 UTC client backend[21828] pg_regress/text HINT: You might need to add explicit type casts. 2025-11-17 08:40:44.920 UTC client backend[21828] pg_regress/text STATEMENT: select length(42); 2025-11-17 08:40:44.920 UTC unrecognized[21841] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.921 UTC client backend[21841] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.921 UTC client backend[21841] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rangetypes 2025-11-17 08:40:44.921 UTC client backend[21833] pg_regress/float8 LOG: connection ready: setup total=42.471 ms, fork=5.110 ms, authentication=0.343 ms 2025-11-17 08:40:44.925 UTC client backend[21838] pg_regress/int8 LOG: connection ready: setup total=25.134 ms, fork=7.723 ms, authentication=0.301 ms 2025-11-17 08:40:44.926 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: " " at character 34 2025-11-17 08:40:44.926 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' '); 2025-11-17 08:40:44.926 UTC client backend[21830] pg_regress/int2 ERROR: table "f" has 1 columns available but 2 columns specified 2025-11-17 08:40:44.926 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT * FROM INT2_TBL AS f(a, b); 2025-11-17 08:40:44.927 UTC client backend[21830] pg_regress/int2 ERROR: table "s" has 1 columns available but 2 columns specified 2025-11-17 08:40:44.927 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT * FROM (TABLE int2_tbl) AS s (a, b); 2025-11-17 08:40:44.928 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "xxx" at character 34 2025-11-17 08:40:44.928 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('xxx'); 2025-11-17 08:40:44.930 UTC client backend[21838] pg_regress/int8 ERROR: value "3908203590239580293850293850329485" is out of range for type bigint at character 34 2025-11-17 08:40:44.930 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485'); 2025-11-17 08:40:44.930 UTC client backend[21838] pg_regress/int8 ERROR: value "-1204982019841029840928340329840934" is out of range for type bigint at character 34 2025-11-17 08:40:44.930 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934'); 2025-11-17 08:40:44.930 UTC client backend[21828] pg_regress/text ERROR: operator does not exist: integer || numeric at character 10 2025-11-17 08:40:44.930 UTC client backend[21828] pg_regress/text DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:44.930 UTC client backend[21828] pg_regress/text HINT: You might need to add explicit type casts. 2025-11-17 08:40:44.930 UTC client backend[21828] pg_regress/text STATEMENT: select 3 || 4.0; 2025-11-17 08:40:44.930 UTC client backend[21840] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.930 UTC client backend[21840] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/bit 2025-11-17 08:40:44.933 UTC client backend[21840] pg_regress/bit LOG: connection ready: setup total=18.901 ms, fork=3.133 ms, authentication=9.939 ms 2025-11-17 08:40:44.936 UTC client backend[21837] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-11-17 08:40:44.936 UTC client backend[21837] pg_regress/txid STATEMENT: select '31:12:'::txid_snapshot; 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid STATEMENT: select '0:1:'::txid_snapshot; 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid STATEMENT: select '12:13:0'::txid_snapshot; 2025-11-17 08:40:44.937 UTC client backend[21815] pg_regress/char ERROR: value too long for type character(4) 2025-11-17 08:40:44.937 UTC client backend[21815] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('abcde'); 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-11-17 08:40:44.937 UTC client backend[21837] pg_regress/txid STATEMENT: select '12:16:14,13'::txid_snapshot; 2025-11-17 08:40:44.938 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "- 123" at character 34 2025-11-17 08:40:44.938 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('- 123'); 2025-11-17 08:40:44.940 UTC unrecognized[21843] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.941 UTC client backend[21834] pg_regress/float4 LOG: connection ready: setup total=60.391 ms, fork=4.018 ms, authentication=0.326 ms 2025-11-17 08:40:44.941 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: " 345 5" at character 34 2025-11-17 08:40:44.941 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' 345 5'); 2025-11-17 08:40:44.943 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "" at character 34 2025-11-17 08:40:44.943 UTC client backend[21838] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (''); 2025-11-17 08:40:44.944 UTC client backend[21820] pg_regress/varchar ERROR: value too long for type character varying(1) 2025-11-17 08:40:44.944 UTC client backend[21820] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('cd'); 2025-11-17 08:40:44.944 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.944 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.947 UTC client backend[21828] pg_regress/text ERROR: VARIADIC argument must be an array at character 32 2025-11-17 08:40:44.947 UTC client backend[21828] pg_regress/text STATEMENT: select concat_ws(',', variadic 10); 2025-11-17 08:40:44.947 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: "" at character 33 2025-11-17 08:40:44.947 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (''); 2025-11-17 08:40:44.947 UTC client backend[21841] pg_regress/rangetypes LOG: connection ready: setup total=31.167 ms, fork=1.505 ms, authentication=0.374 ms 2025-11-17 08:40:44.948 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: " tru e " 2025-11-17 08:40:44.948 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT ' tru e '::text::boolean AS invalid; 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: " " at character 33 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' '); 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: "asdfasd" at character 33 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('asdfasd'); 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: "99asdfasd" at character 33 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('99asdfasd'); 2025-11-17 08:40:44.949 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" 2025-11-17 08:40:44.949 UTC client backend[21824] pg_regress/boolean STATEMENT: SELECT ''::text::boolean AS invalid; 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: "5 d" at character 33 2025-11-17 08:40:44.949 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 d'); 2025-11-17 08:40:44.952 UTC unrecognized[21845] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: " 5d" at character 33 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' 5d'); 2025-11-17 08:40:44.952 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.952 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: "5 5" at character 33 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 5'); 2025-11-17 08:40:44.952 UTC unrecognized[21844] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid ERROR: invalid input syntax for type oid: " - 500" at character 33 2025-11-17 08:40:44.952 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' - 500'); 2025-11-17 08:40:44.953 UTC client backend[21835] pg_regress/oid ERROR: value "32958209582039852935" is out of range for type oid at character 33 2025-11-17 08:40:44.953 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935'); 2025-11-17 08:40:44.953 UTC client backend[21835] pg_regress/oid ERROR: value "-23582358720398502385" is out of range for type oid at character 33 2025-11-17 08:40:44.953 UTC client backend[21835] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385'); 2025-11-17 08:40:44.953 UTC client backend[21828] pg_regress/text ERROR: too few arguments for format() 2025-11-17 08:40:44.953 UTC client backend[21828] pg_regress/text STATEMENT: select format('Hello %s %s', 'World'); 2025-11-17 08:40:44.953 UTC client backend[21845] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.953 UTC client backend[21845] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/money 2025-11-17 08:40:44.953 UTC client backend[21844] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.954 UTC client backend[21844] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regproc 2025-11-17 08:40:44.954 UTC client backend[21828] pg_regress/text ERROR: too few arguments for format() 2025-11-17 08:40:44.954 UTC client backend[21828] pg_regress/text STATEMENT: select format('Hello %s'); 2025-11-17 08:40:44.954 UTC client backend[21828] pg_regress/text ERROR: unrecognized format() type specifier "x" 2025-11-17 08:40:44.954 UTC client backend[21828] pg_regress/text HINT: For a single "%" use "%%". 2025-11-17 08:40:44.954 UTC client backend[21828] pg_regress/text STATEMENT: select format('Hello %x', 20); 2025-11-17 08:40:44.955 UTC client backend[21843] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.955 UTC client backend[21843] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/uuid 2025-11-17 08:40:44.958 UTC client backend[21843] pg_regress/uuid LOG: connection ready: setup total=40.633 ms, fork=19.103 ms, authentication=0.446 ms 2025-11-17 08:40:44.958 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.958 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.958 UTC client backend[21828] pg_regress/text ERROR: null values cannot be formatted as an SQL identifier 2025-11-17 08:40:44.958 UTC client backend[21828] pg_regress/text STATEMENT: select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello'); 2025-11-17 08:40:44.959 UTC unrecognized[21846] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.960 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.960 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.961 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "" at character 8 2025-11-17 08:40:44.961 UTC client backend[21841] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-11-17 08:40:44.961 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select ''::textrange; 2025-11-17 08:40:44.961 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "foo.boo[]" 2025-11-17 08:40:44.961 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('foo.boo[]'); 2025-11-17 08:40:44.963 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: " " 2025-11-17 08:40:44.963 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident(' '); 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: " .aaa" 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident(' .aaa'); 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: " aaa . " 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name DETAIL: No valid identifier after ".". 2025-11-17 08:40:44.964 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident(' aaa . '); 2025-11-17 08:40:44.964 UTC client backend[21815] pg_regress/char LOG: disconnection: session time: 0:00:00.145 user=postgres database=regression host=[local] 2025-11-17 08:40:44.965 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "aaa.a%b" 2025-11-17 08:40:44.965 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('aaa.a%b'); 2025-11-17 08:40:44.965 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" 2025-11-17 08:40:44.965 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'); 2025-11-17 08:40:44.966 UTC client backend[21828] pg_regress/text ERROR: too few arguments for format() 2025-11-17 08:40:44.966 UTC client backend[21828] pg_regress/text STATEMENT: select format('%1$s %4$s', 1, 2, 3); 2025-11-17 08:40:44.966 UTC client backend[21830] pg_regress/int2 ERROR: smallint out of range 2025-11-17 08:40:44.966 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i; 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text ERROR: too few arguments for format() 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text STATEMENT: select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12); 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text STATEMENT: select format('%0$s', 'Hello'); 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-11-17 08:40:44.967 UTC client backend[21828] pg_regress/text STATEMENT: select format('%*0$s', 'Hello'); 2025-11-17 08:40:44.969 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.969 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "-[a,z)" at character 8 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '-[a,z)'::textrange; 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "[a,z) - " at character 8 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '[a,z) - '::textrange; 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(",a)" at character 8 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes DETAIL: Unexpected end of input. 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(",a)'::textrange; 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes DETAIL: Too many commas. 2025-11-17 08:40:44.969 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(,,a)'::textrange; 2025-11-17 08:40:44.970 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: ""c".X XXXXXXXXXX" 2025-11-17 08:40:44.970 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident(E'"c".X XXXX\002XXXXXX'); 2025-11-17 08:40:44.970 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(),a)" at character 8 2025-11-17 08:40:44.970 UTC client backend[21841] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-11-17 08:40:44.970 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(),a)'::textrange; 2025-11-17 08:40:44.971 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(a,))" at character 8 2025-11-17 08:40:44.971 UTC client backend[21841] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-17 08:40:44.971 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(a,))'::textrange; 2025-11-17 08:40:44.971 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:44.971 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i; 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(],a)" at character 8 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(],a)'::textrange; 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text ERROR: unterminated format() type specifier 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text HINT: For a single "%" use "%%". 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text STATEMENT: select format('%1$', 1); 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text ERROR: unterminated format() type specifier 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text HINT: For a single "%" use "%%". 2025-11-17 08:40:44.972 UTC client backend[21828] pg_regress/text STATEMENT: select format('%1$1', 1); 2025-11-17 08:40:44.972 UTC client backend[21846] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.972 UTC client backend[21846] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/enum 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes ERROR: malformed range literal: "(a,])" at character 8 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '(a,])'::textrange; 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-17 08:40:44.972 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '[z,a]'::textrange; 2025-11-17 08:40:44.974 UTC client backend[21830] pg_regress/int2 ERROR: smallint out of range 2025-11-17 08:40:44.974 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i; 2025-11-17 08:40:44.974 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "1020" 2025-11-17 08:40:44.974 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('1020'); 2025-11-17 08:40:44.975 UTC client backend[21846] pg_regress/enum LOG: connection ready: setup total=25.547 ms, fork=8.837 ms, authentication=0.347 ms 2025-11-17 08:40:44.978 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "10.20" 2025-11-17 08:40:44.978 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('10.20'); 2025-11-17 08:40:44.978 UTC client backend[21833] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 8 2025-11-17 08:40:44.978 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '10e400'::float8; 2025-11-17 08:40:44.978 UTC client backend[21833] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 8 2025-11-17 08:40:44.978 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '-10e400'::float8; 2025-11-17 08:40:44.980 UTC client backend[21833] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 8 2025-11-17 08:40:44.980 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '10e-400'::float8; 2025-11-17 08:40:44.980 UTC client backend[21833] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 8 2025-11-17 08:40:44.980 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '-10e-400'::float8; 2025-11-17 08:40:44.980 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "." 2025-11-17 08:40:44.980 UTC client backend[21814] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-17 08:40:44.980 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('.'); 2025-11-17 08:40:44.981 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: ".1020" 2025-11-17 08:40:44.981 UTC client backend[21814] pg_regress/name DETAIL: No valid identifier before ".". 2025-11-17 08:40:44.981 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('.1020'); 2025-11-17 08:40:44.982 UTC client backend[21814] pg_regress/name ERROR: string is not a valid identifier: "xxx.1020" 2025-11-17 08:40:44.982 UTC client backend[21814] pg_regress/name DETAIL: No valid identifier after ".". 2025-11-17 08:40:44.982 UTC client backend[21814] pg_regress/name STATEMENT: SELECT parse_ident('xxx.1020'); 2025-11-17 08:40:44.983 UTC client backend[21844] pg_regress/regproc LOG: connection ready: setup total=48.227 ms, fork=13.892 ms, authentication=0.347 ms 2025-11-17 08:40:44.983 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "" at character 36 2025-11-17 08:40:44.983 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (''); 2025-11-17 08:40:44.985 UTC client backend[21814] pg_regress/name LOG: disconnection: session time: 0:00:00.166 user=postgres database=regression host=[local] 2025-11-17 08:40:44.988 UTC unrecognized[21848] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:44.988 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: " " at character 36 2025-11-17 08:40:44.988 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' '); 2025-11-17 08:40:44.989 UTC client backend[21845] pg_regress/money LOG: connection ready: setup total=40.416 ms, fork=2.320 ms, authentication=0.349 ms 2025-11-17 08:40:44.989 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "xyz" at character 36 2025-11-17 08:40:44.989 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz'); 2025-11-17 08:40:44.989 UTC client backend[21848] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:44.989 UTC client backend[21848] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/pg_lsn 2025-11-17 08:40:44.989 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5.0.0" at character 36 2025-11-17 08:40:44.989 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0'); 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5 . 0" at character 36 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0'); 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5. 0" at character 36 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5. 0'); 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: " - 3" at character 36 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' - 3'); 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "123 5" at character 36 2025-11-17 08:40:44.990 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('123 5'); 2025-11-17 08:40:44.993 UTC client backend[21830] pg_regress/int2 ERROR: smallint out of range 2025-11-17 08:40:44.993 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i; 2025-11-17 08:40:44.995 UTC client backend[21834] pg_regress/float4 ERROR: "10e70" is out of range for type real at character 36 2025-11-17 08:40:44.995 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'); 2025-11-17 08:40:44.996 UTC client backend[21834] pg_regress/float4 ERROR: "-10e70" is out of range for type real at character 36 2025-11-17 08:40:44.996 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'); 2025-11-17 08:40:44.997 UTC client backend[21840] pg_regress/bit ERROR: bit string length 2 does not match type bit(11) 2025-11-17 08:40:44.997 UTC client backend[21840] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'10'); 2025-11-17 08:40:44.997 UTC client backend[21834] pg_regress/float4 ERROR: "10e-70" is out of range for type real at character 36 2025-11-17 08:40:44.997 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'); 2025-11-17 08:40:44.998 UTC client backend[21834] pg_regress/float4 ERROR: "-10e-70" is out of range for type real at character 36 2025-11-17 08:40:44.998 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'); 2025-11-17 08:40:44.999 UTC client backend[21834] pg_regress/float4 ERROR: value out of range: overflow 2025-11-17 08:40:44.999 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8); 2025-11-17 08:40:45.001 UTC client backend[21834] pg_regress/float4 ERROR: value out of range: overflow 2025-11-17 08:40:45.001 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8); 2025-11-17 08:40:45.002 UTC client backend[21834] pg_regress/float4 ERROR: value out of range: underflow 2025-11-17 08:40:45.002 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8); 2025-11-17 08:40:45.004 UTC client backend[21824] pg_regress/boolean ERROR: invalid input syntax for type boolean: "XXX" at character 43 2025-11-17 08:40:45.004 UTC client backend[21824] pg_regress/boolean STATEMENT: INSERT INTO BOOLTBL2 (f1) VALUES (bool 'XXX'); 2025-11-17 08:40:45.005 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.005 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int4; 2025-11-17 08:40:45.006 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.006 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int4; 2025-11-17 08:40:45.008 UTC client backend[21830] pg_regress/int2 ERROR: smallint out of range 2025-11-17 08:40:45.008 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 * (-1)::int2; 2025-11-17 08:40:45.008 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "N A N" at character 8 2025-11-17 08:40:45.008 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT 'N A N'::float8; 2025-11-17 08:40:45.008 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: "NaN x" at character 8 2025-11-17 08:40:45.008 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT 'NaN x'::float8; 2025-11-17 08:40:45.008 UTC client backend[21834] pg_regress/float4 ERROR: value out of range: underflow 2025-11-17 08:40:45.008 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8); 2025-11-17 08:40:45.009 UTC client backend[21834] pg_regress/float4 ERROR: "10e400" is out of range for type real at character 36 2025-11-17 08:40:45.009 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400'); 2025-11-17 08:40:45.011 UTC client backend[21834] pg_regress/float4 ERROR: "-10e400" is out of range for type real at character 36 2025-11-17 08:40:45.011 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400'); 2025-11-17 08:40:45.011 UTC client backend[21840] pg_regress/bit ERROR: bit string length 12 does not match type bit(11) 2025-11-17 08:40:45.011 UTC client backend[21840] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'101011111010'); 2025-11-17 08:40:45.011 UTC client backend[21834] pg_regress/float4 ERROR: "10e-400" is out of range for type real at character 36 2025-11-17 08:40:45.011 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400'); 2025-11-17 08:40:45.012 UTC client backend[21833] pg_regress/float8 ERROR: invalid input syntax for type double precision: " INFINITY x" at character 8 2025-11-17 08:40:45.012 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT ' INFINITY x'::float8; 2025-11-17 08:40:45.012 UTC client backend[21834] pg_regress/float4 ERROR: "-10e-400" is out of range for type real at character 36 2025-11-17 08:40:45.012 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400'); 2025-11-17 08:40:45.012 UTC client backend[21820] pg_regress/varchar ERROR: value too long for type character varying(4) 2025-11-17 08:40:45.012 UTC client backend[21820] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde'); 2025-11-17 08:40:45.012 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "" at character 36 2025-11-17 08:40:45.012 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (''); 2025-11-17 08:40:45.012 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.012 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int2; 2025-11-17 08:40:45.013 UTC client backend[21830] pg_regress/int2 ERROR: smallint out of range 2025-11-17 08:40:45.013 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 / (-1)::int2; 2025-11-17 08:40:45.013 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: " " at character 36 2025-11-17 08:40:45.013 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' '); 2025-11-17 08:40:45.013 UTC client backend[21848] pg_regress/pg_lsn LOG: connection ready: setup total=62.563 ms, fork=29.834 ms, authentication=0.343 ms 2025-11-17 08:40:45.014 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "xyz" at character 36 2025-11-17 08:40:45.014 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz'); 2025-11-17 08:40:45.015 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "5.0.0" at character 36 2025-11-17 08:40:45.015 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0'); 2025-11-17 08:40:45.015 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "5 . 0" at character 36 2025-11-17 08:40:45.015 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0'); 2025-11-17 08:40:45.016 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.016 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int2; 2025-11-17 08:40:45.017 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "5. 0" at character 36 2025-11-17 08:40:45.017 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5. 0'); 2025-11-17 08:40:45.019 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: " - 3.0" at character 36 2025-11-17 08:40:45.019 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' - 3.0'); 2025-11-17 08:40:45.019 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "123 5" at character 36 2025-11-17 08:40:45.019 UTC client backend[21834] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('123 5'); 2025-11-17 08:40:45.021 UTC client backend[21820] pg_regress/varchar LOG: disconnection: session time: 0:00:00.180 user=postgres database=regression host=[local] 2025-11-17 08:40:45.021 UTC client backend[21828] pg_regress/text LOG: disconnection: session time: 0:00:00.161 user=postgres database=regression host=[local] 2025-11-17 08:40:45.028 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.028 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, 0::int4); 2025-11-17 08:40:45.028 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.028 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, (-2147483648)::int4); 2025-11-17 08:40:45.029 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0b" at character 13 2025-11-17 08:40:45.029 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0b'; 2025-11-17 08:40:45.029 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0o" at character 13 2025-11-17 08:40:45.029 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0o'; 2025-11-17 08:40:45.030 UTC client backend[21840] pg_regress/bit ERROR: bit string too long for type bit varying(11) 2025-11-17 08:40:45.030 UTC client backend[21840] pg_regress/bit STATEMENT: INSERT INTO VARBIT_TABLE VALUES (B'101011111010'); 2025-11-17 08:40:45.030 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0x" at character 13 2025-11-17 08:40:45.030 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0x'; 2025-11-17 08:40:45.032 UTC client backend[21830] pg_regress/int2 ERROR: value "0b1000000000000000" is out of range for type smallint at character 13 2025-11-17 08:40:45.032 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0b1000000000000000'; 2025-11-17 08:40:45.032 UTC client backend[21840] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-11-17 08:40:45.032 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT b' 0'; 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT b'0 '; 2025-11-17 08:40:45.033 UTC client backend[21830] pg_regress/int2 ERROR: value "0o100000" is out of range for type smallint at character 13 2025-11-17 08:40:45.033 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0o100000'; 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT x' 0'; 2025-11-17 08:40:45.033 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "N A N" at character 8 2025-11-17 08:40:45.033 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT 'N A N'::float4; 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-11-17 08:40:45.033 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT x'0 '; 2025-11-17 08:40:45.034 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: "NaN x" at character 8 2025-11-17 08:40:45.034 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT 'NaN x'::float4; 2025-11-17 08:40:45.036 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.036 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT lcm((-2147483648)::int4, 1::int4); 2025-11-17 08:40:45.036 UTC client backend[21829] pg_regress/int4 ERROR: integer out of range 2025-11-17 08:40:45.036 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT lcm(2147483647::int4, 2147483646::int4); 2025-11-17 08:40:45.037 UTC client backend[21846] pg_regress/enum ERROR: invalid input value for enum rainbow: "mauve" at character 8 2025-11-17 08:40:45.037 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT 'mauve'::rainbow; 2025-11-17 08:40:45.038 UTC client backend[21835] pg_regress/oid LOG: disconnection: session time: 0:00:00.146 user=postgres database=regression host=[local] 2025-11-17 08:40:45.041 UTC client backend[21834] pg_regress/float4 ERROR: invalid input syntax for type real: " INFINITY x" at character 8 2025-11-17 08:40:45.041 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT ' INFINITY x'::float4; 2025-11-17 08:40:45.041 UTC client backend[21830] pg_regress/int2 ERROR: value "0x8000" is out of range for type smallint at character 13 2025-11-17 08:40:45.041 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '0x8000'; 2025-11-17 08:40:45.042 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "0b" at character 13 2025-11-17 08:40:45.042 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0b'; 2025-11-17 08:40:45.042 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "0o" at character 13 2025-11-17 08:40:45.042 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0o'; 2025-11-17 08:40:45.044 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "0x" at character 13 2025-11-17 08:40:45.044 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0x'; 2025-11-17 08:40:45.044 UTC client backend[21829] pg_regress/int4 ERROR: value "0b10000000000000000000000000000000" is out of range for type integer at character 13 2025-11-17 08:40:45.044 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0b10000000000000000000000000000000'; 2025-11-17 08:40:45.045 UTC client backend[21829] pg_regress/int4 ERROR: value "0o20000000000" is out of range for type integer at character 13 2025-11-17 08:40:45.045 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0o20000000000'; 2025-11-17 08:40:45.046 UTC client backend[21830] pg_regress/int2 ERROR: value "-0b1000000000000001" is out of range for type smallint at character 13 2025-11-17 08:40:45.046 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '-0b1000000000000001'; 2025-11-17 08:40:45.047 UTC client backend[21830] pg_regress/int2 ERROR: value "-0o100001" is out of range for type smallint at character 13 2025-11-17 08:40:45.047 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '-0o100001'; 2025-11-17 08:40:45.048 UTC client backend[21830] pg_regress/int2 ERROR: value "-0x8001" is out of range for type smallint at character 13 2025-11-17 08:40:45.048 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '-0x8001'; 2025-11-17 08:40:45.050 UTC client backend[21837] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22 2025-11-17 08:40:45.050 UTC client backend[21837] pg_regress/txid STATEMENT: SELECT txid_snapshot '1:9223372036854775808:3'; 2025-11-17 08:40:45.052 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "_100" at character 13 2025-11-17 08:40:45.052 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '_100'; 2025-11-17 08:40:45.052 UTC client backend[21829] pg_regress/int4 ERROR: value "0x80000000" is out of range for type integer at character 13 2025-11-17 08:40:45.052 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '0x80000000'; 2025-11-17 08:40:45.052 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "100_" at character 13 2025-11-17 08:40:45.052 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '100_'; 2025-11-17 08:40:45.053 UTC client backend[21830] pg_regress/int2 ERROR: invalid input syntax for type smallint: "10__000" at character 13 2025-11-17 08:40:45.053 UTC client backend[21830] pg_regress/int2 STATEMENT: SELECT int2 '10__000'; 2025-11-17 08:40:45.053 UTC client backend[21829] pg_regress/int4 ERROR: value "-0b10000000000000000000000000000001" is out of range for type integer at character 13 2025-11-17 08:40:45.053 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '-0b10000000000000000000000000000001'; 2025-11-17 08:40:45.054 UTC client backend[21829] pg_regress/int4 ERROR: value "-0o20000000001" is out of range for type integer at character 13 2025-11-17 08:40:45.054 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '-0o20000000001'; 2025-11-17 08:40:45.059 UTC client backend[21830] pg_regress/int2 LOG: disconnection: session time: 0:00:00.195 user=postgres database=regression host=[local] 2025-11-17 08:40:45.061 UTC client backend[21829] pg_regress/int4 ERROR: value "-0x80000001" is out of range for type integer at character 13 2025-11-17 08:40:45.061 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '-0x80000001'; 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "_100" at character 13 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '_100'; 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "100_" at character 13 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '100_'; 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 ERROR: invalid input syntax for type integer: "100__000" at character 13 2025-11-17 08:40:45.063 UTC client backend[21829] pg_regress/int4 STATEMENT: SELECT int4 '100__000'; 2025-11-17 08:40:45.064 UTC client backend[21848] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "G/0" at character 32 2025-11-17 08:40:45.064 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('G/0'); 2025-11-17 08:40:45.064 UTC client backend[21848] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "-1/0" at character 32 2025-11-17 08:40:45.064 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('-1/0'); 2025-11-17 08:40:45.065 UTC client backend[21848] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: " 0/12345678" at character 32 2025-11-17 08:40:45.065 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES (' 0/12345678'); 2025-11-17 08:40:45.065 UTC client backend[21848] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "ABCD/" at character 32 2025-11-17 08:40:45.065 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('ABCD/'); 2025-11-17 08:40:45.066 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.066 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL; 2025-11-17 08:40:45.067 UTC client backend[21846] pg_regress/enum ERROR: enum label "foo" used more than once 2025-11-17 08:40:45.067 UTC client backend[21846] pg_regress/enum STATEMENT: CREATE TYPE dup_enum AS ENUM ('foo','bar','foo'); 2025-11-17 08:40:45.067 UTC client backend[21829] pg_regress/int4 LOG: disconnection: session time: 0:00:00.214 user=postgres database=regression host=[local] 2025-11-17 08:40:45.068 UTC client backend[21848] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "/ABCD" at character 32 2025-11-17 08:40:45.068 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('/ABCD'); 2025-11-17 08:40:45.082 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38 2025-11-17 08:40:45.082 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F'); 2025-11-17 08:40:45.088 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38 2025-11-17 08:40:45.088 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}'); 2025-11-17 08:40:45.089 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38 2025-11-17 08:40:45.089 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111'); 2025-11-17 08:40:45.089 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38 2025-11-17 08:40:45.089 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 '); 2025-11-17 08:40:45.090 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38 2025-11-17 08:40:45.090 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111'); 2025-11-17 08:40:45.090 UTC client backend[21843] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38 2025-11-17 08:40:45.090 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111'); 2025-11-17 08:40:45.108 UTC client backend[21834] pg_regress/float4 ERROR: division by zero 2025-11-17 08:40:45.108 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT f.f1 / '0.0' from FLOAT4_TBL f; 2025-11-17 08:40:45.111 UTC client backend[21833] pg_regress/float8 ERROR: zero raised to a negative power is undefined 2025-11-17 08:40:45.111 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT power(float8 '0', float8 '-inf'); 2025-11-17 08:40:45.114 UTC client backend[21837] pg_regress/txid LOG: disconnection: session time: 0:00:00.212 user=postgres database=regression host=[local] 2025-11-17 08:40:45.119 UTC client backend[21834] pg_regress/float4 ERROR: smallint out of range 2025-11-17 08:40:45.119 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '32767.6'::float4::int2; 2025-11-17 08:40:45.120 UTC client backend[21846] pg_regress/enum ERROR: invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto" 2025-11-17 08:40:45.120 UTC client backend[21846] pg_regress/enum DETAIL: Labels must be 63 bytes or less. 2025-11-17 08:40:45.120 UTC client backend[21846] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto'; 2025-11-17 08:40:45.120 UTC client backend[21846] pg_regress/enum ERROR: "zeus" is not an existing enum label 2025-11-17 08:40:45.120 UTC client backend[21846] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus'; 2025-11-17 08:40:45.121 UTC client backend[21846] pg_regress/enum ERROR: enum label "mercury" already exists 2025-11-17 08:40:45.121 UTC client backend[21846] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'mercury'; 2025-11-17 08:40:45.121 UTC client backend[21848] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-11-17 08:40:45.121 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric; 2025-11-17 08:40:45.122 UTC client backend[21848] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-11-17 08:40:45.122 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: SELECT '0/1'::pg_lsn - 2::numeric; 2025-11-17 08:40:45.124 UTC client backend[21834] pg_regress/float4 ERROR: smallint out of range 2025-11-17 08:40:45.124 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '-32768.6'::float4::int2; 2025-11-17 08:40:45.125 UTC client backend[21844] pg_regress/regproc ERROR: constant of the type regrole cannot be used here 2025-11-17 08:40:45.125 UTC client backend[21844] pg_regress/regproc STATEMENT: CREATE TABLE regrole_test (rolid OID DEFAULT 'regress_regrole_test'::regrole); 2025-11-17 08:40:45.128 UTC client backend[21848] pg_regress/pg_lsn ERROR: cannot add NaN to pg_lsn 2025-11-17 08:40:45.128 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric; 2025-11-17 08:40:45.128 UTC client backend[21848] pg_regress/pg_lsn ERROR: cannot subtract NaN from pg_lsn 2025-11-17 08:40:45.128 UTC client backend[21848] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric; 2025-11-17 08:40:45.130 UTC client backend[21833] pg_regress/float8 ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-17 08:40:45.130 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT power(float8 '-inf', float8 '3.5'); 2025-11-17 08:40:45.132 UTC client backend[21834] pg_regress/float4 ERROR: integer out of range 2025-11-17 08:40:45.132 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '2147483647'::float4::int4; 2025-11-17 08:40:45.133 UTC client backend[21834] pg_regress/float4 ERROR: integer out of range 2025-11-17 08:40:45.133 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '-2147483900'::float4::int4; 2025-11-17 08:40:45.133 UTC client backend[21845] pg_regress/money ERROR: value "123456789012345678" is out of range for type money at character 8 2025-11-17 08:40:45.133 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '123456789012345678'::money; 2025-11-17 08:40:45.134 UTC client backend[21834] pg_regress/float4 ERROR: bigint out of range 2025-11-17 08:40:45.134 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '9223372036854775807'::float4::int8; 2025-11-17 08:40:45.134 UTC client backend[21845] pg_regress/money ERROR: value "9223372036854775807" is out of range for type money at character 8 2025-11-17 08:40:45.134 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '9223372036854775807'::money; 2025-11-17 08:40:45.135 UTC client backend[21834] pg_regress/float4 ERROR: bigint out of range 2025-11-17 08:40:45.135 UTC client backend[21834] pg_regress/float4 STATEMENT: SELECT '-9223380000000000000'::float4::int8; 2025-11-17 08:40:45.135 UTC client backend[21845] pg_regress/money ERROR: value "-123456789012345678" is out of range for type money at character 8 2025-11-17 08:40:45.135 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-123456789012345678'::money; 2025-11-17 08:40:45.136 UTC client backend[21845] pg_regress/money ERROR: value "-9223372036854775808" is out of range for type money at character 8 2025-11-17 08:40:45.136 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-9223372036854775808'::money; 2025-11-17 08:40:45.142 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.142 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT f.f1 * '1e200' from FLOAT8_TBL f; 2025-11-17 08:40:45.143 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.143 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT f.f1 ^ '1e200' from FLOAT8_TBL f; 2025-11-17 08:40:45.145 UTC client backend[21833] pg_regress/float8 ERROR: cannot take logarithm of zero 2025-11-17 08:40:45.145 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ; 2025-11-17 08:40:45.146 UTC client backend[21833] pg_regress/float8 ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.146 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ; 2025-11-17 08:40:45.146 UTC client backend[21844] pg_regress/regproc ERROR: constant of the type regdatabase cannot be used here 2025-11-17 08:40:45.146 UTC client backend[21844] pg_regress/regproc STATEMENT: CREATE TABLE regdatabase_test (datid OID DEFAULT 'template1'::regdatabase); 2025-11-17 08:40:45.147 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: underflow 2025-11-17 08:40:45.147 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT exp(f.f1) from FLOAT8_TBL f; 2025-11-17 08:40:45.147 UTC client backend[21845] pg_regress/money ERROR: value "-92233720368547758.09" is out of range for type money at character 8 2025-11-17 08:40:45.147 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-92233720368547758.09'::money; 2025-11-17 08:40:45.147 UTC client backend[21845] pg_regress/money ERROR: value "92233720368547758.08" is out of range for type money at character 8 2025-11-17 08:40:45.147 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '92233720368547758.08'::money; 2025-11-17 08:40:45.148 UTC client backend[21833] pg_regress/float8 ERROR: division by zero 2025-11-17 08:40:45.148 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT f.f1 / '0.0' from FLOAT8_TBL f; 2025-11-17 08:40:45.148 UTC client backend[21845] pg_regress/money ERROR: value "-92233720368547758.085" is out of range for type money at character 8 2025-11-17 08:40:45.148 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-92233720368547758.085'::money; 2025-11-17 08:40:45.148 UTC client backend[21845] pg_regress/money ERROR: value "92233720368547758.075" is out of range for type money at character 8 2025-11-17 08:40:45.148 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '92233720368547758.075'::money; 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc ERROR: operator does not exist: ||// at character 16 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regoper('||//'); 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc ERROR: operator does not exist: ++(int4,int4) at character 20 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regoperator('++(int4,int4)'); 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc ERROR: function "know" does not exist at character 16 2025-11-17 08:40:45.153 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regproc('know'); 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc ERROR: function "absinthe(numeric)" does not exist at character 21 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regprocedure('absinthe(numeric)'); 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc ERROR: relation "pg_classes" does not exist at character 17 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regclass('pg_classes'); 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc ERROR: type "int3" does not exist at character 16 2025-11-17 08:40:45.154 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regtype('int3'); 2025-11-17 08:40:45.155 UTC client backend[21844] pg_regress/regproc ERROR: operator does not exist: ng_catalog.||/ at character 16 2025-11-17 08:40:45.155 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regoper('ng_catalog.||/'); 2025-11-17 08:40:45.155 UTC client backend[21844] pg_regress/regproc ERROR: operator does not exist: ng_catalog.+(int4,int4) at character 20 2025-11-17 08:40:45.155 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regoperator('ng_catalog.+(int4,int4)'); 2025-11-17 08:40:45.156 UTC client backend[21844] pg_regress/regproc ERROR: function "ng_catalog.now" does not exist at character 16 2025-11-17 08:40:45.156 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regproc('ng_catalog.now'); 2025-11-17 08:40:45.157 UTC client backend[21848] pg_regress/pg_lsn LOG: disconnection: session time: 0:00:00.175 user=postgres database=regression host=[local] 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc ERROR: function "ng_catalog.abs(numeric)" does not exist at character 21 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regprocedure('ng_catalog.abs(numeric)'); 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc ERROR: relation "ng_catalog.pg_class" does not exist at character 17 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regclass('ng_catalog.pg_class'); 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc ERROR: schema "ng_catalog" does not exist at character 16 2025-11-17 08:40:45.157 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regtype('ng_catalog.int4'); 2025-11-17 08:40:45.158 UTC client backend[21844] pg_regress/regproc ERROR: collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21 2025-11-17 08:40:45.158 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regcollation('ng_catalog."POSIX"'); 2025-11-17 08:40:45.168 UTC client backend[21838] pg_regress/int8 ERROR: value "-9223372036854775809" is out of range for type bigint at character 8 2025-11-17 08:40:45.168 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775809'::int8; 2025-11-17 08:40:45.168 UTC client backend[21838] pg_regress/int8 ERROR: value "9223372036854775808" is out of range for type bigint at character 8 2025-11-17 08:40:45.168 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775808'::int8; 2025-11-17 08:40:45.169 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.169 UTC client backend[21838] pg_regress/int8 STATEMENT: select -('-9223372036854775808'::int8); 2025-11-17 08:40:45.169 UTC client backend[21844] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-11-17 08:40:45.169 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regrole('regress_regrole_test'); 2025-11-17 08:40:45.170 UTC client backend[21844] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-11-17 08:40:45.170 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regrole('"regress_regrole_test"'); 2025-11-17 08:40:45.170 UTC client backend[21844] pg_regress/regproc ERROR: role "nonexistent" does not exist at character 16 2025-11-17 08:40:45.170 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regrole('Nonexistent'); 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc ERROR: role "Nonexistent" does not exist at character 16 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regrole('"Nonexistent"'); 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc ERROR: invalid name syntax at character 16 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regrole('foo.bar'); 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc ERROR: schema "nonexistent" does not exist at character 21 2025-11-17 08:40:45.171 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regnamespace('Nonexistent'); 2025-11-17 08:40:45.172 UTC client backend[21844] pg_regress/regproc ERROR: schema "Nonexistent" does not exist at character 21 2025-11-17 08:40:45.172 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regnamespace('"Nonexistent"'); 2025-11-17 08:40:45.172 UTC client backend[21841] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:45.172 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select numrange(2.0, 1.0); 2025-11-17 08:40:45.174 UTC client backend[21844] pg_regress/regproc ERROR: invalid name syntax at character 21 2025-11-17 08:40:45.174 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regnamespace('foo.bar'); 2025-11-17 08:40:45.174 UTC client backend[21844] pg_regress/regproc ERROR: database "nonexistent" does not exist at character 20 2025-11-17 08:40:45.174 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regdatabase('Nonexistent'); 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select 0::int8 - '-9223372036854775808'::int8; 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '9223372036854775800'::int8; 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 - '-9223372036854775800'::int8; 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '9223372036854775800'::int8; 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.177 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '9223372036854775800'::int8; 2025-11-17 08:40:45.177 UTC client backend[21844] pg_regress/regproc ERROR: database "Nonexistent" does not exist at character 20 2025-11-17 08:40:45.177 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regdatabase('"Nonexistent"'); 2025-11-17 08:40:45.178 UTC client backend[21844] pg_regress/regproc ERROR: invalid name syntax at character 20 2025-11-17 08:40:45.178 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT regdatabase('foo.bar'); 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 ERROR: division by zero 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 / '0'::int8; 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 ERROR: division by zero 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 % '0'::int8; 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.179 UTC client backend[21838] pg_regress/int8 STATEMENT: select abs('-9223372036854775808'::int8); 2025-11-17 08:40:45.180 UTC client backend[21843] pg_regress/uuid ERROR: duplicate key value violates unique constraint "guid1_unique_btree" 2025-11-17 08:40:45.180 UTC client backend[21843] pg_regress/uuid DETAIL: Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists. 2025-11-17 08:40:45.180 UTC client backend[21843] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111'); 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int4; 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int4; 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.182 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int4; 2025-11-17 08:40:45.185 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.185 UTC client backend[21838] pg_regress/int8 STATEMENT: select '100'::int4 + '9223372036854775800'::int8; 2025-11-17 08:40:45.185 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.185 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-100'::int4 - '9223372036854775800'::int8; 2025-11-17 08:40:45.186 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.186 UTC client backend[21838] pg_regress/int8 STATEMENT: select '100'::int4 * '9223372036854775800'::int8; 2025-11-17 08:40:45.186 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.186 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int2; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int2; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int2; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: division by zero 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-9223372036854775808'::int8 / '0'::int2; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '100'::int2 + '9223372036854775800'::int8; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '-100'::int2 - '9223372036854775800'::int8; 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.187 UTC client backend[21838] pg_regress/int8 STATEMENT: select '100'::int2 * '9223372036854775800'::int8; 2025-11-17 08:40:45.187 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.187 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money + '0.01'::money; 2025-11-17 08:40:45.188 UTC client backend[21833] pg_regress/float8 ERROR: input is out of range 2025-11-17 08:40:45.188 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT acosh(float8 '-infinity'); 2025-11-17 08:40:45.188 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.188 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-92233720368547758.08'::money - '0.01'::money; 2025-11-17 08:40:45.188 UTC client backend[21838] pg_regress/int8 ERROR: division by zero 2025-11-17 08:40:45.188 UTC client backend[21838] pg_regress/int8 STATEMENT: select '100'::int2 / '0'::int8; 2025-11-17 08:40:45.188 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.188 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::float8; 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '-1'::money / 1.175494e-38::float4; 2025-11-17 08:40:45.189 UTC client backend[21833] pg_regress/float8 ERROR: input is out of range 2025-11-17 08:40:45.189 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT atanh(float8 'infinity'); 2025-11-17 08:40:45.189 UTC client backend[21833] pg_regress/float8 ERROR: input is out of range 2025-11-17 08:40:45.189 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT atanh(float8 '-infinity'); 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::int4; 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money ERROR: division by zero 2025-11-17 08:40:45.189 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '1'::money / 0::int2; 2025-11-17 08:40:45.190 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.190 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '42'::money * 'inf'::float8; 2025-11-17 08:40:45.190 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.190 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '42'::money * '-inf'::float8; 2025-11-17 08:40:45.191 UTC client backend[21845] pg_regress/money ERROR: money out of range 2025-11-17 08:40:45.191 UTC client backend[21845] pg_regress/money STATEMENT: SELECT '42'::money * 'nan'::float4; 2025-11-17 08:40:45.196 UTC client backend[21845] pg_regress/money LOG: disconnection: session time: 0:00:00.245 user=postgres database=regression host=[local] 2025-11-17 08:40:45.198 UTC client backend[21838] pg_regress/int8 ERROR: integer out of range 2025-11-17 08:40:45.198 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456; 2025-11-17 08:40:45.200 UTC client backend[21838] pg_regress/int8 ERROR: smallint out of range 2025-11-17 08:40:45.200 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456; 2025-11-17 08:40:45.206 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.206 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT CAST('922337203685477580700.0'::float8 AS int8); 2025-11-17 08:40:45.206 UTC client backend[21838] pg_regress/int8 ERROR: OID out of range 2025-11-17 08:40:45.206 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS oid) FROM INT8_TBL; 2025-11-17 08:40:45.212 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.212 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-infinity'); 2025-11-17 08:40:45.212 UTC client backend[21841] pg_regress/rangetypes ERROR: result of range union would not be contiguous 2025-11-17 08:40:45.212 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select numrange(1.0, 2.0) + numrange(2.5, 3.0); 2025-11-17 08:40:45.212 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: underflow 2025-11-17 08:40:45.212 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1000.5'); 2025-11-17 08:40:45.220 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.220 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1'); 2025-11-17 08:40:45.220 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.220 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '-1'); 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT gamma(float8 '0'); 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '0'); 2025-11-17 08:40:45.221 UTC client backend[21838] pg_regress/int8 ERROR: step size cannot equal zero 2025-11-17 08:40:45.221 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0); 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT gamma(float8 '1000'); 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 ERROR: value out of range: overflow 2025-11-17 08:40:45.221 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '1e308'); 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 36 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400'); 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 36 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400'); 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 36 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400'); 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 36 2025-11-17 08:40:45.222 UTC client backend[21833] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400'); 2025-11-17 08:40:45.225 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.225 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int8; 2025-11-17 08:40:45.229 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.229 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int8; 2025-11-17 08:40:45.229 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.229 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int4; 2025-11-17 08:40:45.230 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.230 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int4; 2025-11-17 08:40:45.231 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.231 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int2; 2025-11-17 08:40:45.231 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.231 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int2; 2025-11-17 08:40:45.235 UTC client backend[21834] pg_regress/float4 LOG: disconnection: session time: 0:00:00.350 user=postgres database=regression host=[local] 2025-11-17 08:40:45.239 UTC client backend[21833] pg_regress/float8 ERROR: smallint out of range 2025-11-17 08:40:45.239 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '32767.6'::float8::int2; 2025-11-17 08:40:45.243 UTC client backend[21833] pg_regress/float8 ERROR: smallint out of range 2025-11-17 08:40:45.243 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '-32768.6'::float8::int2; 2025-11-17 08:40:45.247 UTC client backend[21833] pg_regress/float8 ERROR: integer out of range 2025-11-17 08:40:45.247 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '2147483647.6'::float8::int4; 2025-11-17 08:40:45.247 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.247 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, 0::int8); 2025-11-17 08:40:45.248 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.248 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8); 2025-11-17 08:40:45.248 UTC client backend[21833] pg_regress/float8 ERROR: integer out of range 2025-11-17 08:40:45.248 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '-2147483648.6'::float8::int4; 2025-11-17 08:40:45.248 UTC client backend[21833] pg_regress/float8 ERROR: bigint out of range 2025-11-17 08:40:45.248 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '9223372036854775807'::float8::int8; 2025-11-17 08:40:45.249 UTC client backend[21833] pg_regress/float8 ERROR: bigint out of range 2025-11-17 08:40:45.249 UTC client backend[21833] pg_regress/float8 STATEMENT: SELECT '-9223372036854780000'::float8::int8; 2025-11-17 08:40:45.250 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.250 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT lcm((-9223372036854775808)::int8, 1::int8); 2025-11-17 08:40:45.250 UTC client backend[21838] pg_regress/int8 ERROR: bigint out of range 2025-11-17 08:40:45.250 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8); 2025-11-17 08:40:45.251 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0b" at character 13 2025-11-17 08:40:45.251 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0b'; 2025-11-17 08:40:45.251 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0o" at character 13 2025-11-17 08:40:45.251 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0o'; 2025-11-17 08:40:45.252 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0x" at character 13 2025-11-17 08:40:45.252 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0x'; 2025-11-17 08:40:45.252 UTC client backend[21838] pg_regress/int8 ERROR: value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13 2025-11-17 08:40:45.252 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000'; 2025-11-17 08:40:45.252 UTC client backend[21844] pg_regress/regproc ERROR: syntax error at or near "type" at character 11 2025-11-17 08:40:45.252 UTC client backend[21844] pg_regress/regproc CONTEXT: invalid type name "incorrect type name syntax" 2025-11-17 08:40:45.252 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype'); 2025-11-17 08:40:45.252 UTC client backend[21844] pg_regress/regproc ERROR: invalid NUMERIC type modifier 2025-11-17 08:40:45.252 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype'); 2025-11-17 08:40:45.253 UTC client backend[21844] pg_regress/regproc ERROR: improper qualified name (too many dotted names): way.too.many.names 2025-11-17 08:40:45.253 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype'); 2025-11-17 08:40:45.253 UTC client backend[21844] pg_regress/regproc ERROR: cross-database references are not implemented: no_such_catalog.schema.name 2025-11-17 08:40:45.253 UTC client backend[21844] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype'); 2025-11-17 08:40:45.256 UTC client backend[21844] pg_regress/regproc LOG: disconnection: session time: 0:00:00.306 user=postgres database=regression host=[local] 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 ERROR: value "0o1000000000000000000000" is out of range for type bigint at character 13 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0o1000000000000000000000'; 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 ERROR: value "0x8000000000000000" is out of range for type bigint at character 13 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '0x8000000000000000'; 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 ERROR: value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13 2025-11-17 08:40:45.256 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001'; 2025-11-17 08:40:45.257 UTC client backend[21838] pg_regress/int8 ERROR: value "-0o1000000000000000000001" is out of range for type bigint at character 13 2025-11-17 08:40:45.257 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '-0o1000000000000000000001'; 2025-11-17 08:40:45.257 UTC client backend[21838] pg_regress/int8 ERROR: value "-0x8000000000000001" is out of range for type bigint at character 13 2025-11-17 08:40:45.257 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '-0x8000000000000001'; 2025-11-17 08:40:45.266 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "_100" at character 13 2025-11-17 08:40:45.266 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '_100'; 2025-11-17 08:40:45.267 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100_" at character 13 2025-11-17 08:40:45.267 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '100_'; 2025-11-17 08:40:45.267 UTC client backend[21838] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100__000" at character 13 2025-11-17 08:40:45.267 UTC client backend[21838] pg_regress/int8 STATEMENT: SELECT int8 '100__000'; 2025-11-17 08:40:45.268 UTC client backend[21838] pg_regress/int8 LOG: disconnection: session time: 0:00:00.359 user=postgres database=regression host=[local] 2025-11-17 08:40:45.277 UTC client backend[21833] pg_regress/float8 ERROR: type "no_such_type" does not exist at character 69 2025-11-17 08:40:45.277 UTC client backend[21833] pg_regress/float8 STATEMENT: create type xfloat8 (input = xfloat8in, output = xfloat8out, like = no_such_type); 2025-11-17 08:40:45.316 UTC client backend[21846] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-11-17 08:40:45.316 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT 'purple'::rgb; 2025-11-17 08:40:45.316 UTC client backend[21846] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-11-17 08:40:45.316 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT 'purple'::rainbow::rgb; 2025-11-17 08:40:45.321 UTC client backend[21833] pg_regress/float8 LOG: disconnection: session time: 0:00:00.437 user=postgres database=regression host=[local] 2025-11-17 08:40:45.452 UTC client backend[21846] pg_regress/enum ERROR: insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey" 2025-11-17 08:40:45.452 UTC client backend[21846] pg_regress/enum DETAIL: Key (parent)=(blue) is not present in table "enumtest_parent". 2025-11-17 08:40:45.452 UTC client backend[21846] pg_regress/enum STATEMENT: INSERT INTO enumtest_child VALUES ('blue'); 2025-11-17 08:40:45.458 UTC client backend[21846] pg_regress/enum ERROR: update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child" 2025-11-17 08:40:45.458 UTC client backend[21846] pg_regress/enum DETAIL: Key (id)=(red) is still referenced from table "enumtest_child". 2025-11-17 08:40:45.458 UTC client backend[21846] pg_regress/enum STATEMENT: DELETE FROM enumtest_parent; 2025-11-17 08:40:45.463 UTC client backend[21846] pg_regress/enum ERROR: foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented 2025-11-17 08:40:45.463 UTC client backend[21846] pg_regress/enum DETAIL: Key columns "parent" of the referencing table and "id" of the referenced table are of incompatible types: bogus and rainbow. 2025-11-17 08:40:45.463 UTC client backend[21846] pg_regress/enum STATEMENT: CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent); 2025-11-17 08:40:45.469 UTC client backend[21846] pg_regress/enum ERROR: "red" is not an existing enum label 2025-11-17 08:40:45.469 UTC client backend[21846] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson'; 2025-11-17 08:40:45.469 UTC client backend[21846] pg_regress/enum ERROR: enum label "green" already exists 2025-11-17 08:40:45.469 UTC client backend[21846] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green'; 2025-11-17 08:40:45.476 UTC client backend[21846] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus at character 8 2025-11-17 08:40:45.476 UTC client backend[21846] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-17 08:40:45.476 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT 'new'::bogus; 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT enum_last(null::bogus); 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-17 08:40:45.477 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT enum_range(null::bogus); 2025-11-17 08:40:45.479 UTC client backend[21846] pg_regress/enum ERROR: unsafe use of new value "bad" of enum type bogon at character 8 2025-11-17 08:40:45.479 UTC client backend[21846] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-11-17 08:40:45.479 UTC client backend[21846] pg_regress/enum STATEMENT: SELECT 'bad'::bogon; 2025-11-17 08:40:45.536 UTC client backend[21846] pg_regress/enum LOG: disconnection: session time: 0:00:00.577 user=postgres database=regression host=[local] 2025-11-17 08:40:45.585 UTC client backend[21843] pg_regress/uuid LOG: disconnection: session time: 0:00:00.648 user=postgres database=regression host=[local] 2025-11-17 08:40:45.716 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.716 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric / '0'; 2025-11-17 08:40:45.716 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.716 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric / '0'; 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '0'::numeric / '0'; 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric % '0'; 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric % '0'; 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '0'::numeric % '0'; 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT div('inf'::numeric, '0'); 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.717 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT div('-inf'::numeric, '0'); 2025-11-17 08:40:45.718 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:45.718 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT div('0'::numeric, '0'); 2025-11-17 08:40:45.725 UTC client backend[21836] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-11-17 08:40:45.725 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT sqrt('-1'::numeric); 2025-11-17 08:40:45.726 UTC client backend[21836] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-11-17 08:40:45.726 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT sqrt('-inf'::numeric); 2025-11-17 08:40:45.726 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:45.726 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT ln('0'::numeric); 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT ln('-1'::numeric); 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT ln('-inf'::numeric); 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:45.727 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('0'::numeric, '10'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '0'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, '10'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '-inf'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '0'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '-inf'); 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:45.728 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, 'inf'); 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-1'); 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-inf'); 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-17 08:40:45.732 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '3.3'); 2025-11-17 08:40:45.733 UTC client backend[21836] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-17 08:40:45.733 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '-1.5'); 2025-11-17 08:40:45.736 UTC client backend[21836] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-17 08:40:45.736 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT power('-inf'::numeric, '4.5'); 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (3, '1.0'); 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-11-17 08:40:45.746 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (6, '0.99995'); 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (10, 'Inf'); 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-11-17 08:40:45.752 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (11, '-Inf'); 2025-11-17 08:40:45.755 UTC client backend[21836] pg_regress/numeric ERROR: bigint out of range 2025-11-17 08:40:45.755 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT (-9223372036854775808.5)::int8; 2025-11-17 08:40:45.760 UTC client backend[21836] pg_regress/numeric ERROR: bigint out of range 2025-11-17 08:40:45.760 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 9223372036854775807.5::int8; 2025-11-17 08:40:45.760 UTC client backend[21836] pg_regress/numeric ERROR: integer out of range 2025-11-17 08:40:45.760 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT (-2147483648.5)::int4; 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric ERROR: integer out of range 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 2147483647.5::int4; 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric ERROR: smallint out of range 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT (-32768.5)::int2; 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric ERROR: smallint out of range 2025-11-17 08:40:45.761 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 32767.5::int2; 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert NaN to smallint 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int2; 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int2; 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int2; 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert NaN to integer 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int4; 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-11-17 08:40:45.768 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int4; 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int4; 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert NaN to bigint 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int8; 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int8; 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-11-17 08:40:45.769 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int8; 2025-11-17 08:40:45.793 UTC client backend[21836] pg_regress/numeric ERROR: value overflows numeric format 2025-11-17 08:40:45.793 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT round(5.5e131071, -131072); 2025-11-17 08:40:45.797 UTC client backend[21836] pg_regress/numeric ERROR: count must be greater than zero 2025-11-17 08:40:45.797 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, 0); 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric ERROR: count must be greater than zero 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, -5); 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5, 3.0, 3.0, 888); 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric ERROR: count must be greater than zero 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0); 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric ERROR: count must be greater than zero 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5); 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-11-17 08:40:45.800 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888); 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0, 'NaN', 4.0, 888); 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888); 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(2.0, 3.0, '-inf', 888); 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.801 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888); 2025-11-17 08:40:45.810 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.810 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10); 2025-11-17 08:40:45.810 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.810 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20); 2025-11-17 08:40:45.811 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.811 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10); 2025-11-17 08:40:45.812 UTC client backend[21836] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-11-17 08:40:45.812 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20); 2025-11-17 08:40:45.823 UTC client backend[21836] pg_regress/numeric ERROR: integer out of range 2025-11-17 08:40:45.823 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(1::float8, 0, 1, 2147483647); 2025-11-17 08:40:45.823 UTC client backend[21836] pg_regress/numeric ERROR: integer out of range 2025-11-17 08:40:45.823 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 1, 0, 2147483647); 2025-11-17 08:40:45.859 UTC client backend[21840] pg_regress/bit ERROR: negative substring length not allowed 2025-11-17 08:40:45.859 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error"; 2025-11-17 08:40:45.860 UTC client backend[21840] pg_regress/bit ERROR: negative substring length not allowed 2025-11-17 08:40:45.860 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error"; 2025-11-17 08:40:45.905 UTC client backend[21840] pg_regress/bit ERROR: cannot AND bit strings of different sizes 2025-11-17 08:40:45.905 UTC client backend[21840] pg_regress/bit STATEMENT: select B'001' & B'10'; 2025-11-17 08:40:45.905 UTC client backend[21840] pg_regress/bit ERROR: cannot OR bit strings of different sizes 2025-11-17 08:40:45.905 UTC client backend[21840] pg_regress/bit STATEMENT: select B'0111' | B'011'; 2025-11-17 08:40:45.906 UTC client backend[21840] pg_regress/bit ERROR: cannot XOR bit strings of different sizes 2025-11-17 08:40:45.906 UTC client backend[21840] pg_regress/bit STATEMENT: select B'0010' # B'011101'; 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('viv', 'RN'); 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('DCCCD', 'RN'); 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('XIXL', 'RN'); 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.909 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('MCCM', 'RN'); 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('MMMM', 'RN'); 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('VV', 'RN'); 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.910 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('IL', 'RN'); 2025-11-17 08:40:45.919 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.919 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('VIX', 'RN'); 2025-11-17 08:40:45.919 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.919 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('LXC', 'RN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('DCM', 'RN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('MMMDCM', 'RN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('CLXC', 'RN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: "RN" is incompatible with other formats 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric DETAIL: "RN" may only be used together with "FM". 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'MIRN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: cannot use "RN" twice 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'RNRN'); 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.920 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('qiv', 'RN'); 2025-11-17 08:40:45.921 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " 2025-11-17 08:40:45.921 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number('', 'RN'); 2025-11-17 08:40:45.921 UTC client backend[21836] pg_regress/numeric ERROR: invalid Roman numeral 2025-11-17 08:40:45.921 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT to_number(' ', 'RN'); 2025-11-17 08:40:45.940 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " at character 40 2025-11-17 08:40:45.940 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' '); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: " 1234 %" at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' 1234 %'); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "xyz" at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('xyz'); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "- 1234" at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('- 1234'); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5 . 0" at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5 . 0'); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5. 0 " at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5. 0 '); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "" at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (''); 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: " N aN " at character 40 2025-11-17 08:40:45.941 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' N aN '); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+NaN" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+NaN'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "-NaN" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('-NaN'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+ infinity" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+ infinity'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "_123" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('_123'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "12__34" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('12__34'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_.456" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_.456'); 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123._456" at character 40 2025-11-17 08:40:45.942 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123._456'); 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e_34" at character 40 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e_34'); 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e34_" at character 40 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e34_'); 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e3__4" at character 40 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e3__4'); 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0b1112" at character 40 2025-11-17 08:40:45.943 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0b1112'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0c1112" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0c1112'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0o12345678" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0o12345678'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1eg" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1eg'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12.34" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12.34'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x__1234" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x__1234'); 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1234_" at character 40 2025-11-17 08:40:45.944 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1234_'); 2025-11-17 08:40:45.947 UTC client backend[21836] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12__34" at character 40 2025-11-17 08:40:45.947 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12__34'); 2025-11-17 08:40:45.964 UTC client backend[21840] pg_regress/bit ERROR: bit index 16 out of valid range (0..15) 2025-11-17 08:40:45.964 UTC client backend[21840] pg_regress/bit STATEMENT: SELECT set_bit(B'0101011000100100', 16, 1); 2025-11-17 08:40:45.965 UTC client backend[21824] pg_regress/boolean LOG: disconnection: session time: 0:00:01.121 user=postgres database=regression host=[local] 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale -6 cannot hold an infinite value. 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES ('inf'); 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale -6 must round to an absolute value less than 10^9. 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES (999500000); 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale -3 must round to an absolute value less than 10^6. 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousands) VALUES (999500); 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale 0 must round to an absolute value less than 10^3. 2025-11-17 08:40:46.064 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (units) VALUES (999.5); 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale 3 must round to an absolute value less than 1. 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousandths) VALUES (0.9995); 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric ERROR: numeric field overflow 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric DETAIL: A field with precision 3, scale 6 must round to an absolute value less than 10^-3. 2025-11-17 08:40:46.065 UTC client backend[21836] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millionths) VALUES (0.0009995); 2025-11-17 08:40:46.077 UTC client backend[21840] pg_regress/bit LOG: disconnection: session time: 0:00:01.159 user=postgres database=regression host=[local] 2025-11-17 08:40:46.099 UTC client backend[21836] pg_regress/numeric ERROR: value overflows numeric format 2025-11-17 08:40:46.099 UTC client backend[21836] pg_regress/numeric STATEMENT: select 10.0 ^ 2147483647 as overflows; 2025-11-17 08:40:46.100 UTC client backend[21836] pg_regress/numeric ERROR: value overflows numeric format 2025-11-17 08:40:46.100 UTC client backend[21836] pg_regress/numeric STATEMENT: select 117743296169.0 ^ 1000000000 as overflows; 2025-11-17 08:40:46.114 UTC client backend[21836] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-11-17 08:40:46.114 UTC client backend[21836] pg_regress/numeric STATEMENT: select 0.0 ^ (-12.34); 2025-11-17 08:40:46.116 UTC client backend[21836] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-11-17 08:40:46.116 UTC client backend[21836] pg_regress/numeric STATEMENT: select (-12.34) ^ 1.2; 2025-11-17 08:40:46.127 UTC client backend[21836] pg_regress/numeric ERROR: step size cannot equal zero 2025-11-17 08:40:46.127 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 0::numeric); 2025-11-17 08:40:46.127 UTC client backend[21836] pg_regress/numeric ERROR: step size cannot be NaN 2025-11-17 08:40:46.127 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric); 2025-11-17 08:40:46.128 UTC client backend[21836] pg_regress/numeric ERROR: start value cannot be NaN 2025-11-17 08:40:46.128 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series('nan'::numeric, 100::numeric, 10::numeric); 2025-11-17 08:40:46.128 UTC client backend[21836] pg_regress/numeric ERROR: stop value cannot be NaN 2025-11-17 08:40:46.128 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric); 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric ERROR: start value cannot be infinity 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric); 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric ERROR: stop value cannot be infinity 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric); 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric ERROR: step size cannot be infinity 2025-11-17 08:40:46.132 UTC client backend[21836] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric); 2025-11-17 08:40:46.134 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:46.134 UTC client backend[21836] pg_regress/numeric STATEMENT: select ln(-12.34); 2025-11-17 08:40:46.135 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:46.135 UTC client backend[21836] pg_regress/numeric STATEMENT: select ln(0.0); 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(-12.34); 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-11-17 08:40:46.141 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(0.0); 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(-12.34, 56.78); 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(-12.34, -56.78); 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(12.34, -56.78); 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(0.0, 12.34); 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-11-17 08:40:46.148 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(12.34, 0.0); 2025-11-17 08:40:46.149 UTC client backend[21836] pg_regress/numeric ERROR: division by zero 2025-11-17 08:40:46.149 UTC client backend[21836] pg_regress/numeric STATEMENT: select log(1.0, 12.34); 2025-11-17 08:40:46.273 UTC client backend[21836] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp21836.0", size 1400000 2025-11-17 08:40:46.273 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT SUM(9999::numeric) FROM generate_series(1, 100000); 2025-11-17 08:40:46.397 UTC client backend[21836] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp21836.1", size 1400000 2025-11-17 08:40:46.397 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT SUM((-9999)::numeric) FROM generate_series(1, 100000); 2025-11-17 08:40:46.646 UTC client backend[21836] pg_regress/numeric ERROR: value overflows numeric format 2025-11-17 08:40:46.646 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2); 2025-11-17 08:40:46.656 UTC client backend[21836] pg_regress/numeric ERROR: value overflows numeric format 2025-11-17 08:40:46.656 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT factorial(100000); 2025-11-17 08:40:46.657 UTC client backend[21836] pg_regress/numeric ERROR: factorial of a negative number is undefined 2025-11-17 08:40:46.657 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT factorial(-4); 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric ERROR: pg_lsn out of range 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT pg_lsn(-1::numeric); 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric ERROR: pg_lsn out of range 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT pg_lsn(18446744073709551616::numeric); 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric ERROR: cannot convert NaN to pg_lsn 2025-11-17 08:40:46.658 UTC client backend[21836] pg_regress/numeric STATEMENT: SELECT pg_lsn('NaN'::numeric); 2025-11-17 08:40:46.661 UTC client backend[21836] pg_regress/numeric LOG: disconnection: session time: 0:00:01.761 user=postgres database=regression host=[local] 2025-11-17 08:40:46.829 UTC client backend[21841] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_room_during_excl" 2025-11-17 08:40:46.829 UTC client backend[21841] 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")). 2025-11-17 08:40:46.829 UTC client backend[21841] 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)'); 2025-11-17 08:40:46.833 UTC client backend[21841] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl" 2025-11-17 08:40:46.833 UTC client backend[21841] 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")). 2025-11-17 08:40:46.833 UTC client backend[21841] 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)'); 2025-11-17 08:40:46.834 UTC client backend[21841] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-17 08:40:46.834 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange; 2025-11-17 08:40:46.835 UTC client backend[21841] pg_regress/rangetypes ERROR: function float4mi(double precision, double precision) does not exist 2025-11-17 08:40:46.835 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi); 2025-11-17 08:40:46.862 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot drop type mydomain because other objects depend on it 2025-11-17 08:40:46.862 UTC client backend[21841] pg_regress/rangetypes DETAIL: type mydomainrange depends on type mydomain 2025-11-17 08:40:46.862 UTC client backend[21841] pg_regress/rangetypes HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-11-17 08:40:46.862 UTC client backend[21841] pg_regress/rangetypes STATEMENT: drop domain mydomain; 2025-11-17 08:40:46.871 UTC client backend[21841] pg_regress/rangetypes ERROR: value for domain restrictedrange violates check constraint "restrictedrange_check" 2025-11-17 08:40:46.871 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select '[4,50)'::restrictedrange @> 7; 2025-11-17 08:40:46.892 UTC client backend[21841] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:46.892 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select textrange1('a','Z') @> 'b'::text; 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes ERROR: function anyarray_anyrange_func(integer[], numrange) does not exist at character 8 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20)); 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function bogus_func(anyelement) returns anyrange as 'select int4range(1,10)' language sql; 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:46.910 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function bogus_func(int) returns anyrange as 'select int4range(1,10)' language sql; 2025-11-17 08:40:46.918 UTC client backend[21841] pg_regress/rangetypes ERROR: function rangetypes_sql(numrange, integer[]) does not exist at character 8 2025-11-17 08:40:46.918 UTC client backend[21841] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:46.918 UTC client backend[21841] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:46.918 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select rangetypes_sql(numrange(1,10), ARRAY[2,20]); 2025-11-17 08:40:46.919 UTC client backend[21841] pg_regress/rangetypes ERROR: function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8 2025-11-17 08:40:46.919 UTC client backend[21841] pg_regress/rangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:46.919 UTC client backend[21841] pg_regress/rangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:46.919 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20)); 2025-11-17 08:40:46.920 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.920 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-17 08:40:46.920 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-11-17 08:40:46.944 UTC client backend[21841] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:46.944 UTC client backend[21841] pg_regress/rangetypes STATEMENT: select arrayrange(ARRAY[2,1], ARRAY[1,2]); 2025-11-17 08:40:46.960 UTC client backend[21841] pg_regress/rangetypes ERROR: composite type two_ints cannot be made a member of itself 2025-11-17 08:40:46.960 UTC client backend[21841] pg_regress/rangetypes STATEMENT: alter type two_ints add attribute c two_ints_range; 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function outparam_fail(i anyelement, out r anyrange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function inoutparam_fail(inout i anyelement, out r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes ERROR: cannot determine result data type 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:46.991 UTC client backend[21841] pg_regress/rangetypes STATEMENT: create function table_fail(i anyelement) returns table(i anyelement, r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-17 08:40:47.027 UTC client backend[21841] pg_regress/rangetypes LOG: disconnection: session time: 0:00:02.109 user=postgres database=regression host=[local] 2025-11-17 08:40:47.196 UTC unrecognized[22161] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.198 UTC client backend[22161] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.198 UTC client backend[22161] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/strings 2025-11-17 08:40:47.204 UTC unrecognized[22163] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.205 UTC client backend[22163] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.205 UTC client backend[22163] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/point 2025-11-17 08:40:47.224 UTC unrecognized[22164] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.226 UTC unrecognized[22165] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.227 UTC client backend[22165] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.227 UTC client backend[22165] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/lseg 2025-11-17 08:40:47.228 UTC unrecognized[22166] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.229 UTC client backend[22166] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.229 UTC client backend[22166] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numerology 2025-11-17 08:40:47.237 UTC client backend[22161] pg_regress/strings LOG: connection ready: setup total=68.086 ms, fork=27.118 ms, authentication=0.383 ms 2025-11-17 08:40:47.243 UTC unrecognized[22168] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.244 UTC client backend[22163] pg_regress/point LOG: connection ready: setup total=50.828 ms, fork=10.139 ms, authentication=0.341 ms 2025-11-17 08:40:47.245 UTC client backend[22164] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.245 UTC client backend[22164] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/md5 2025-11-17 08:40:47.247 UTC client backend[22168] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.247 UTC client backend[22168] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/box 2025-11-17 08:40:47.248 UTC unrecognized[22169] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.249 UTC client backend[22169] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.249 UTC client backend[22169] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/path 2025-11-17 08:40:47.250 UTC client backend[22165] pg_regress/lseg LOG: connection ready: setup total=38.081 ms, fork=12.945 ms, authentication=0.367 ms 2025-11-17 08:40:47.254 UTC client backend[22163] pg_regress/point ERROR: invalid input syntax for type point: "asdfasdf" at character 35 2025-11-17 08:40:47.254 UTC client backend[22163] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf'); 2025-11-17 08:40:47.255 UTC client backend[22163] pg_regress/point ERROR: invalid input syntax for type point: "(10.0 10.0)" at character 35 2025-11-17 08:40:47.255 UTC client backend[22163] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)'); 2025-11-17 08:40:47.255 UTC client backend[22166] pg_regress/numerology LOG: connection ready: setup total=41.530 ms, fork=14.100 ms, authentication=0.339 ms 2025-11-17 08:40:47.255 UTC client backend[22163] pg_regress/point ERROR: invalid input syntax for type point: "(10.0, 10.0) x" at character 35 2025-11-17 08:40:47.255 UTC client backend[22163] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x'); 2025-11-17 08:40:47.260 UTC client backend[22163] pg_regress/point ERROR: invalid input syntax for type point: "(10.0,10.0" at character 35 2025-11-17 08:40:47.260 UTC client backend[22163] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0'); 2025-11-17 08:40:47.260 UTC client backend[22163] pg_regress/point ERROR: "1e+500" is out of range for type double precision at character 35 2025-11-17 08:40:47.260 UTC client backend[22163] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)'); 2025-11-17 08:40:47.260 UTC client backend[22164] pg_regress/md5 LOG: connection ready: setup total=65.025 ms, fork=28.815 ms, authentication=0.390 ms 2025-11-17 08:40:47.260 UTC client backend[22161] pg_regress/strings ERROR: syntax error at or near "' - third line'" at character 75 2025-11-17 08:40:47.260 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT 'first line' ' - next line' /* this comment is not allowed here */ ' - third line' AS "Illegal comment within continuation"; 2025-11-17 08:40:47.264 UTC client backend[22168] pg_regress/box LOG: connection ready: setup total=24.507 ms, fork=2.921 ms, authentication=0.331 ms 2025-11-17 08:40:47.268 UTC unrecognized[22176] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.269 UTC client backend[22169] pg_regress/path LOG: connection ready: setup total=27.786 ms, fork=1.938 ms, authentication=0.319 ms 2025-11-17 08:40:47.269 UTC client backend[22176] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.269 UTC client backend[22176] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/time 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings ERROR: UESCAPE must be followed by a simple string literal at or near "+" at character 33 2025-11-17 08:40:47.270 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE +; 2025-11-17 08:40:47.271 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape character at or near "'+'" at character 33 2025-11-17 08:40:47.271 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-11-17 08:40:47.271 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-17 08:40:47.271 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99'; 2025-11-17 08:40:47.272 UTC client backend[22176] pg_regress/time LOG: connection ready: setup total=29.091 ms, fork=24.697 ms, authentication=0.349 ms 2025-11-17 08:40:47.273 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-17 08:40:47.273 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99xy'; 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\\'; 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\0061'; 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 26 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \+00db99\+000061'; 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape value at character 18 2025-11-17 08:40:47.292 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \+2FFFFF'; 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \u061'; 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \U0061'; 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "'" at character 23 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99'; 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "x" at character 23 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99xy'; 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\" at character 23 2025-11-17 08:40:47.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\\'; 2025-11-17 08:40:47.296 UTC unrecognized[22186] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.296 UTC unrecognized[22185] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "123abc" at character 8 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 123abc; 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0o" at character 8 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0x0o; 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.a" at character 8 2025-11-17 08:40:47.297 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0.a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0a" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0.0a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near ".0a" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT .0a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e1a" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0.0e1a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0.0e; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e+" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0.0e+a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after parameter at or near "$1a" at character 22 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $1a; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: parameter number too large at or near "$2147483648" at character 22 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $2147483648; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: invalid binary integer at or near "0b" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0b; 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1b" at character 8 2025-11-17 08:40:47.298 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1b; 2025-11-17 08:40:47.300 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\u0061" at character 23 2025-11-17 08:40:47.300 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\u0061'; 2025-11-17 08:40:47.276 UTC unrecognized[22177] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.301 UTC client backend[22177] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.301 UTC client backend[22177] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr 2025-11-17 08:40:47.301 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0b0x" at character 8 2025-11-17 08:40:47.301 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0b0x; 2025-11-17 08:40:47.302 UTC client backend[22186] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.302 UTC client backend[22186] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/date 2025-11-17 08:40:47.304 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\U00000061" at character 27 2025-11-17 08:40:47.304 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \U0000db99\U00000061'; 2025-11-17 08:40:47.304 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape value at or near "\U002FFFFF" at character 17 2025-11-17 08:40:47.304 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'wrong: \U002FFFFF'; 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology ERROR: invalid octal integer at or near "0o" at character 8 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0o; 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1o" at character 8 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1o; 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0o0x" at character 8 2025-11-17 08:40:47.307 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0o0x; 2025-11-17 08:40:47.307 UTC unrecognized[22187] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061"; 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.308 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*'; 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology ERROR: invalid hexadecimal integer at or near "0x" at character 8 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0x; 2025-11-17 08:40:47.308 UTC client backend[22185] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.308 UTC client backend[22185] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/circle 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1x" at character 8 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1x; 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0y" at character 8 2025-11-17 08:40:47.308 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 0x0y; 2025-11-17 08:40:47.309 UTC unrecognized[22188] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.310 UTC client backend[22188] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.310 UTC client backend[22188] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamp 2025-11-17 08:40:47.311 UTC client backend[22185] pg_regress/circle LOG: connection ready: setup total=22.927 ms, fork=1.300 ms, authentication=11.173 ms 2025-11-17 08:40:47.311 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.311 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.311 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&' \' UESCAPE '!' AS "tricky"; 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-11-17 08:40:47.313 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-11-17 08:40:47.314 UTC client backend[22186] pg_regress/date LOG: connection ready: setup total=24.789 ms, fork=1.311 ms, authentication=4.833 ms 2025-11-17 08:40:47.314 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal data: odd number of digits at character 8 2025-11-17 08:40:47.314 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeE'::bytea; 2025-11-17 08:40:47.314 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "x" at character 8 2025-11-17 08:40:47.314 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeEx'::bytea; 2025-11-17 08:40:47.315 UTC client backend[22177] pg_regress/macaddr LOG: connection ready: setup total=48.574 ms, fork=6.214 ms, authentication=0.386 ms 2025-11-17 08:40:47.316 UTC client backend[22168] pg_regress/box ERROR: invalid input syntax for type box: "(2.3, 4.5)" at character 34 2025-11-17 08:40:47.316 UTC client backend[22168] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)'); 2025-11-17 08:40:47.316 UTC client backend[22161] pg_regress/strings ERROR: invalid input syntax for type bytea at character 8 2025-11-17 08:40:47.316 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT E'De\\678dBeEf'::bytea; 2025-11-17 08:40:47.317 UTC client backend[22168] pg_regress/box ERROR: invalid input syntax for type box: "[1, 2, 3, 4)" at character 34 2025-11-17 08:40:47.317 UTC client backend[22168] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)'); 2025-11-17 08:40:47.318 UTC client backend[22168] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4]" at character 34 2025-11-17 08:40:47.318 UTC client backend[22168] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]'); 2025-11-17 08:40:47.280 UTC unrecognized[22179] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.319 UTC client backend[22179] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.319 UTC client backend[22179] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/line 2025-11-17 08:40:47.322 UTC client backend[22187] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.322 UTC client backend[22187] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timetz 2025-11-17 08:40:47.322 UTC client backend[22179] pg_regress/line LOG: connection ready: setup total=54.432 ms, fork=8.950 ms, authentication=0.350 ms 2025-11-17 08:40:47.324 UTC unrecognized[22192] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.324 UTC unrecognized[22193] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.325 UTC client backend[22168] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34 2025-11-17 08:40:47.325 UTC client backend[22168] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x'); 2025-11-17 08:40:47.325 UTC client backend[22168] pg_regress/box ERROR: invalid input syntax for type box: "asdfasdf(ad" at character 34 2025-11-17 08:40:47.325 UTC client backend[22168] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad'); 2025-11-17 08:40:47.325 UTC client backend[22192] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.325 UTC client backend[22192] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/polygon 2025-11-17 08:40:47.325 UTC client backend[22193] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.325 UTC client backend[22193] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/multirangetypes 2025-11-17 08:40:47.282 UTC unrecognized[22181] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.329 UTC client backend[22181] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.329 UTC client backend[22181] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/interval 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path ERROR: invalid input syntax for type path: "[]" at character 30 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[]'); 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path ERROR: invalid input syntax for type path: "[(,2),(3,4)]" at character 30 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]'); 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path ERROR: invalid input syntax for type path: "[(1,2),(3,4)" at character 30 2025-11-17 08:40:47.333 UTC client backend[22169] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)'); 2025-11-17 08:40:47.334 UTC client backend[22169] pg_regress/path ERROR: invalid input syntax for type path: "(1,2,3,4" at character 30 2025-11-17 08:40:47.334 UTC client backend[22169] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2,3,4'); 2025-11-17 08:40:47.334 UTC client backend[22169] pg_regress/path ERROR: invalid input syntax for type path: "(1,2),(3,4)]" at character 30 2025-11-17 08:40:47.334 UTC client backend[22169] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]'); 2025-11-17 08:40:47.335 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "!" 2025-11-17 08:40:47.335 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('!', 32))::bytea; 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: column "_100" does not exist at character 8 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT _100; 2025-11-17 08:40:47.336 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "/" 2025-11-17 08:40:47.336 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('/', 34))::bytea; 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100_" at character 8 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 100_; 2025-11-17 08:40:47.336 UTC client backend[22176] pg_regress/time ERROR: invalid input syntax for type time: "15:36:39 America/New_York" at character 30 2025-11-17 08:40:47.336 UTC client backend[22176] pg_regress/time STATEMENT: INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York'); 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100__000" at character 8 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 100__000; 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: syntax error at or near ".5" at character 14 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT _1_000.5; 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000_" at character 8 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1_000_.5; 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000._5" at character 8 2025-11-17 08:40:47.336 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1_000._5; 2025-11-17 08:40:47.341 UTC client backend[22188] pg_regress/timestamp LOG: connection ready: setup total=35.554 ms, fork=2.670 ms, authentication=0.330 ms 2025-11-17 08:40:47.341 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5_" at character 8 2025-11-17 08:40:47.341 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1_000.5_; 2025-11-17 08:40:47.286 UTC client backend[22165] pg_regress/lseg ERROR: invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30 2025-11-17 08:40:47.286 UTC client backend[22165] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-11-17 08:40:47.290 UTC client backend[22164] pg_regress/md5 LOG: disconnection: session time: 0:00:00.065 user=postgres database=regression host=[local] 2025-11-17 08:40:47.343 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5e_1" at character 8 2025-11-17 08:40:47.343 UTC client backend[22166] pg_regress/numerology STATEMENT: SELECT 1_000.5e_1; 2025-11-17 08:40:47.344 UTC client backend[22187] pg_regress/timetz LOG: connection ready: setup total=40.819 ms, fork=2.673 ms, authentication=0.346 ms 2025-11-17 08:40:47.344 UTC client backend[22166] pg_regress/numerology ERROR: trailing junk after parameter at or near "$0_1" at character 22 2025-11-17 08:40:47.344 UTC client backend[22166] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $0_1; 2025-11-17 08:40:47.347 UTC client backend[22169] pg_regress/path LOG: disconnection: session time: 0:00:00.104 user=postgres database=regression host=[local] 2025-11-17 08:40:47.347 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: ":" 2025-11-17 08:40:47.347 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat(':', 32))::bytea; 2025-11-17 08:40:47.347 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "@" 2025-11-17 08:40:47.347 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('@', 34))::bytea; 2025-11-17 08:40:47.348 UTC unrecognized[22199] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.349 UTC client backend[22199] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.349 UTC client backend[22199] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr8 2025-11-17 08:40:47.350 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "G" 2025-11-17 08:40:47.350 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('G', 32))::bytea; 2025-11-17 08:40:47.350 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "`" 2025-11-17 08:40:47.350 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('`', 34))::bytea; 2025-11-17 08:40:47.352 UTC client backend[22165] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[1,2,3, 4" at character 30 2025-11-17 08:40:47.352 UTC client backend[22165] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4'); 2025-11-17 08:40:47.352 UTC client backend[22165] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30 2025-11-17 08:40:47.352 UTC client backend[22165] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]'); 2025-11-17 08:40:47.290 UTC unrecognized[22183] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.353 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "g" 2025-11-17 08:40:47.353 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('g', 32))::bytea; 2025-11-17 08:40:47.354 UTC client backend[22183] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.354 UTC client backend[22183] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamptz 2025-11-17 08:40:47.354 UTC client backend[22161] pg_regress/strings ERROR: invalid hexadecimal digit: "~" 2025-11-17 08:40:47.354 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT ('\x' || repeat('~', 34))::bytea; 2025-11-17 08:40:47.354 UTC client backend[22165] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30 2025-11-17 08:40:47.354 UTC client backend[22165] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)'); 2025-11-17 08:40:47.354 UTC client backend[22192] pg_regress/polygon LOG: connection ready: setup total=36.074 ms, fork=2.155 ms, authentication=0.326 ms 2025-11-17 08:40:47.356 UTC unrecognized[22198] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:47.356 UTC client backend[22181] pg_regress/interval LOG: connection ready: setup total=80.010 ms, fork=1.432 ms, authentication=0.326 ms 2025-11-17 08:40:47.357 UTC client backend[22198] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:47.357 UTC client backend[22198] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/inet 2025-11-17 08:40:47.359 UTC client backend[22176] pg_regress/time ERROR: date/time field value out of range: "24:00:00.01" at character 8 2025-11-17 08:40:47.359 UTC client backend[22176] pg_regress/time STATEMENT: SELECT '24:00:00.01'::time; 2025-11-17 08:40:47.360 UTC client backend[22193] pg_regress/multirangetypes LOG: connection ready: setup total=40.459 ms, fork=4.165 ms, authentication=0.312 ms 2025-11-17 08:40:47.362 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "1997-02-29" at character 30 2025-11-17 08:40:47.362 UTC client backend[22186] pg_regress/date STATEMENT: INSERT INTO DATE_TBL VALUES ('1997-02-29'); 2025-11-17 08:40:47.364 UTC client backend[22176] pg_regress/time ERROR: date/time field value out of range: "23:59:60.01" at character 8 2025-11-17 08:40:47.364 UTC client backend[22176] pg_regress/time STATEMENT: SELECT '23:59:60.01'::time; 2025-11-17 08:40:47.365 UTC client backend[22176] pg_regress/time ERROR: date/time field value out of range: "24:01:00" at character 8 2025-11-17 08:40:47.365 UTC client backend[22176] pg_regress/time STATEMENT: SELECT '24:01:00'::time; 2025-11-17 08:40:47.365 UTC client backend[22176] pg_regress/time ERROR: date/time field value out of range: "25:00:00" at character 8 2025-11-17 08:40:47.365 UTC client backend[22176] pg_regress/time STATEMENT: SELECT '25:00:00'::time; 2025-11-17 08:40:47.368 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "{}" at character 30 2025-11-17 08:40:47.368 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{}'); 2025-11-17 08:40:47.368 UTC client backend[22185] pg_regress/circle ERROR: invalid input syntax for type circle: "<(-100,0),-100>" at character 32 2025-11-17 08:40:47.368 UTC client backend[22185] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>'); 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10" at character 32 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10'); 2025-11-17 08:40:47.369 UTC client backend[22165] pg_regress/lseg LOG: disconnection: session time: 0:00:00.143 user=postgres database=regression host=[local] 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10> x" at character 32 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x'); 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle ERROR: invalid input syntax for type circle: "1abc,3,5" at character 32 2025-11-17 08:40:47.369 UTC client backend[22185] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5'); 2025-11-17 08:40:47.370 UTC client backend[22185] pg_regress/circle ERROR: invalid input syntax for type circle: "(3,(1,2),3)" at character 32 2025-11-17 08:40:47.370 UTC client backend[22185] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)'); 2025-11-17 08:40:47.372 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "{0" at character 30 2025-11-17 08:40:47.372 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0'); 2025-11-17 08:40:47.375 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "{0,0}" at character 30 2025-11-17 08:40:47.375 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0}'); 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1" at character 30 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1'); 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "1/8/1999" at character 13 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1/8/1999'; 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line ERROR: invalid line specification: A and B cannot both be zero at character 30 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1}'); 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1} x" at character 30 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1} x'); 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30 2025-11-17 08:40:47.377 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.377 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "[1,2,3, 4" at character 30 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[1,2,3, 4'); 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "[(,2),(3,4)]" at character 30 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]'); 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line ERROR: invalid input syntax for type line: "[(1,2),(3,4)" at character 30 2025-11-17 08:40:47.378 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)'); 2025-11-17 08:40:47.379 UTC client backend[22179] pg_regress/line ERROR: invalid line specification: must be two distinct points at character 30 2025-11-17 08:40:47.379 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]'); 2025-11-17 08:40:47.379 UTC client backend[22179] pg_regress/line ERROR: invalid line specification: must be two distinct points 2025-11-17 08:40:47.379 UTC client backend[22179] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)')); 2025-11-17 08:40:47.379 UTC client backend[22177] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "0800:2b01:0203" at character 37 2025-11-17 08:40:47.379 UTC client backend[22177] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203'); 2025-11-17 08:40:47.381 UTC client backend[22177] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "not even close" at character 37 2025-11-17 08:40:47.381 UTC client backend[22177] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (9, 'not even close'); 2025-11-17 08:40:47.381 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "" at character 8 2025-11-17 08:40:47.381 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Missing left brace. 2025-11-17 08:40:47.381 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select ''::textmultirange; 2025-11-17 08:40:47.382 UTC client backend[22183] pg_regress/timestamptz LOG: connection ready: setup total=99.499 ms, fork=4.376 ms, authentication=0.419 ms 2025-11-17 08:40:47.383 UTC client backend[22176] pg_regress/time ERROR: operator is not unique: time without time zone + time without time zone at character 11 2025-11-17 08:40:47.383 UTC client backend[22176] pg_regress/time DETAIL: Could not choose a best candidate operator. 2025-11-17 08:40:47.383 UTC client backend[22176] pg_regress/time HINT: You might need to add explicit type casts. 2025-11-17 08:40:47.383 UTC client backend[22176] pg_regress/time STATEMENT: SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL; 2025-11-17 08:40:47.384 UTC client backend[22198] pg_regress/inet LOG: connection ready: setup total=43.357 ms, fork=5.115 ms, authentication=0.370 ms 2025-11-17 08:40:47.384 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,}" at character 8 2025-11-17 08:40:47.384 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-17 08:40:47.384 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{,}'::textmultirange; 2025-11-17 08:40:47.385 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "January 8, 99 BC" at character 13 2025-11-17 08:40:47.385 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.385 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date 'January 8, 99 BC'; 2025-11-17 08:40:47.385 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(,)}." at character 8 2025-11-17 08:40:47.385 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Junk after closing right brace. 2025-11-17 08:40:47.385 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(,)}.'::textmultirange; 2025-11-17 08:40:47.386 UTC client backend[22199] pg_regress/macaddr8 LOG: connection ready: setup total=43.487 ms, fork=5.048 ms, authentication=0.343 ms 2025-11-17 08:40:47.386 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,c),}" at character 8 2025-11-17 08:40:47.386 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-17 08:40:47.386 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{[a,c),}'::textmultirange; 2025-11-17 08:40:47.388 UTC client backend[22198] pg_regress/inet ERROR: table "inet_tbl" does not exist 2025-11-17 08:40:47.388 UTC client backend[22198] pg_regress/inet STATEMENT: DROP TABLE INET_TBL; 2025-11-17 08:40:47.388 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08-Jan-99" at character 13 2025-11-17 08:40:47.388 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.388 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08-Jan-99'; 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "Jan-08-99" at character 13 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date 'Jan-08-99'; 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-17 08:40:47.389 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-17 08:40:47.390 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08 Jan 99" at character 13 2025-11-17 08:40:47.390 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.390 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08 Jan 99'; 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,[a,c)}" at character 8 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{,[a,c)}'::textmultirange; 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{-[a,z)}" at character 8 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected range start. 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{-[a,z)}'::textmultirange; 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,z) - }" at character 8 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-17 08:40:47.392 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{[a,z) - }'::textmultirange; 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(",a)}" at character 8 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Unexpected end of input. 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(",a)}'::textmultirange; 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Too many commas. 2025-11-17 08:40:47.393 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(,,a)}'::textmultirange; 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed range literal: "()" at character 8 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(),a)}'::textmultirange; 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,))}" at character 8 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(a,))}'::textmultirange; 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed range literal: "(]" at character 8 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(],a)}'::textmultirange; 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,])}" at character 8 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-11-17 08:40:47.394 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{(a,])}'::textmultirange; 2025-11-17 08:40:47.395 UTC client backend[22193] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-11-17 08:40:47.395 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{[z,a]}'::textmultirange; 2025-11-17 08:40:47.396 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "Jan 08 99" at character 13 2025-11-17 08:40:47.396 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.396 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date 'Jan 08 99'; 2025-11-17 08:40:47.396 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "badly formatted interval" at character 39 2025-11-17 08:40:47.396 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval'); 2025-11-17 08:40:47.396 UTC client backend[22179] pg_regress/line LOG: disconnection: session time: 0:00:00.119 user=postgres database=regression host=[local] 2025-11-17 08:40:47.400 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "@ 30 eons ago" at character 39 2025-11-17 08:40:47.400 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago'); 2025-11-17 08:40:47.402 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08-01-99" at character 13 2025-11-17 08:40:47.402 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.402 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08-01-99'; 2025-11-17 08:40:47.408 UTC client backend[22187] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32 2025-11-17 08:40:47.408 UTC client backend[22187] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York'); 2025-11-17 08:40:47.408 UTC client backend[22176] pg_regress/time ERROR: unit "day" not supported for type time without time zone 2025-11-17 08:40:47.408 UTC client backend[22176] pg_regress/time STATEMENT: SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-17 08:40:47.409 UTC client backend[22176] pg_regress/time ERROR: unit "fortnight" not recognized for type time without time zone 2025-11-17 08:40:47.409 UTC client backend[22176] pg_regress/time STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-17 08:40:47.410 UTC client backend[22176] pg_regress/time ERROR: unit "timezone" not supported for type time without time zone 2025-11-17 08:40:47.410 UTC client backend[22176] pg_regress/time STATEMENT: SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); 2025-11-17 08:40:47.411 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08-01-1999" at character 13 2025-11-17 08:40:47.411 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.411 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08-01-1999'; 2025-11-17 08:40:47.412 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03" at character 8 2025-11-17 08:40:47.412 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03'::macaddr8; 2025-11-17 08:40:47.412 UTC client backend[22187] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 m2" at character 32 2025-11-17 08:40:47.412 UTC client backend[22187] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2'); 2025-11-17 08:40:47.412 UTC client backend[22187] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32 2025-11-17 08:40:47.412 UTC client backend[22187] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2'); 2025-11-17 08:40:47.412 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03 123" at character 8 2025-11-17 08:40:47.412 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03 123'::macaddr8; 2025-11-17 08:40:47.413 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03:04:05" at character 8 2025-11-17 08:40:47.413 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03:04:05'::macaddr8; 2025-11-17 08:40:47.413 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05 123" at character 8 2025-11-17 08:40:47.413 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05 123'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "01-08-99" at character 13 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '01-08-99'; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08002b:01020304050607'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "01-08-1999" at character 13 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.414 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '01-08-1999'; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b01020304050607" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08002b01020304050607'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "0z002b0102030405" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '0z002b0102030405'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b010203xyza" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08002b010203xyza'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-11-17 08:40:47.414 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08 01 99" at character 13 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08 01 99'; 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "08 01 1999" at character 13 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '08 01 1999'; 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "01 08 99" at character 13 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '01 08 99'; 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "01 08 1999" at character 13 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.416 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '01 08 1999'; 2025-11-17 08:40:47.417 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-11-17 08:40:47.417 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-11-17 08:40:47.418 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-11-17 08:40:47.418 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.418 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-11-17 08:40:47.418 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-11-17 08:40:47.418 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-11-17 08:40:47.421 UTC client backend[22187] pg_regress/timetz ERROR: date/time field value out of range: "24:00:00.01 PDT" at character 8 2025-11-17 08:40:47.421 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT '24:00:00.01 PDT'::timetz; 2025-11-17 08:40:47.424 UTC client backend[22187] pg_regress/timetz ERROR: date/time field value out of range: "23:59:60.01 PDT" at character 8 2025-11-17 08:40:47.424 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT '23:59:60.01 PDT'::timetz; 2025-11-17 08:40:47.424 UTC client backend[22187] pg_regress/timetz ERROR: date/time field value out of range: "24:01:00 PDT" at character 8 2025-11-17 08:40:47.424 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT '24:01:00 PDT'::timetz; 2025-11-17 08:40:47.425 UTC client backend[22187] pg_regress/timetz ERROR: date/time field value out of range: "25:00:00 PDT" at character 8 2025-11-17 08:40:47.425 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT '25:00:00 PDT'::timetz; 2025-11-17 08:40:47.428 UTC client backend[22176] pg_regress/time LOG: disconnection: session time: 0:00:00.160 user=postgres database=regression host=[local] 2025-11-17 08:40:47.432 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-11-17 08:40:47.432 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.432 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-11-17 08:40:47.434 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-17 08:40:47.434 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-17 08:40:47.435 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-17 08:40:47.435 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-17 08:40:47.435 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99 Jan 08" at character 13 2025-11-17 08:40:47.435 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.435 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-11-17 08:40:47.436 UTC client backend[22187] pg_regress/timetz ERROR: operator does not exist: time with time zone + time with time zone at character 11 2025-11-17 08:40:47.436 UTC client backend[22187] pg_regress/timetz DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:47.436 UTC client backend[22187] pg_regress/timetz HINT: You might need to add explicit type casts. 2025-11-17 08:40:47.436 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL; 2025-11-17 08:40:47.437 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-11-17 08:40:47.437 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-11-17 08:40:47.438 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-11-17 08:40:47.438 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.438 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-11-17 08:40:47.441 UTC client backend[22192] pg_regress/polygon ERROR: invalid input syntax for type polygon: "0.0" at character 37 2025-11-17 08:40:47.441 UTC client backend[22192] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('0.0'); 2025-11-17 08:40:47.442 UTC client backend[22199] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "not even close" at character 38 2025-11-17 08:40:47.442 UTC client backend[22199] pg_regress/macaddr8 STATEMENT: INSERT INTO macaddr8_data VALUES (9, 'not even close'); 2025-11-17 08:40:47.442 UTC client backend[22192] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0.0 0.0" at character 37 2025-11-17 08:40:47.442 UTC client backend[22192] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0'); 2025-11-17 08:40:47.442 UTC client backend[22192] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2)" at character 37 2025-11-17 08:40:47.442 UTC client backend[22192] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)'); 2025-11-17 08:40:47.443 UTC client backend[22192] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2,3" at character 37 2025-11-17 08:40:47.443 UTC client backend[22192] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3'); 2025-11-17 08:40:47.443 UTC client backend[22187] pg_regress/timetz ERROR: unit "day" not supported for type time with time zone 2025-11-17 08:40:47.443 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT EXTRACT(DAY FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-11-17 08:40:47.443 UTC client backend[22192] pg_regress/polygon ERROR: invalid input syntax for type polygon: "asdf" at character 37 2025-11-17 08:40:47.443 UTC client backend[22192] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('asdf'); 2025-11-17 08:40:47.444 UTC client backend[22187] pg_regress/timetz ERROR: unit "fortnight" not recognized for type time with time zone 2025-11-17 08:40:47.444 UTC client backend[22187] pg_regress/timetz STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-11-17 08:40:47.449 UTC client backend[22161] pg_regress/strings ERROR: negative substring length not allowed 2025-11-17 08:40:47.449 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error"; 2025-11-17 08:40:47.452 UTC client backend[22198] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 37 2025-11-17 08:40:47.452 UTC client backend[22198] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-17 08:40:47.452 UTC client backend[22198] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226'); 2025-11-17 08:40:47.453 UTC client backend[22198] pg_regress/inet ERROR: invalid input syntax for type cidr: "1234::1234::1234" at character 37 2025-11-17 08:40:47.453 UTC client backend[22198] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4'); 2025-11-17 08:40:47.453 UTC client backend[22198] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 42 2025-11-17 08:40:47.453 UTC client backend[22198] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-17 08:40:47.453 UTC client backend[22198] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226'); 2025-11-17 08:40:47.453 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-11-17 08:40:47.453 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.453 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-11-17 08:40:47.454 UTC client backend[22198] pg_regress/inet ERROR: invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42 2025-11-17 08:40:47.454 UTC client backend[22198] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-11-17 08:40:47.454 UTC client backend[22198] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226'); 2025-11-17 08:40:47.454 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-11-17 08:40:47.454 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.454 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-11-17 08:40:47.455 UTC client backend[22185] pg_regress/circle LOG: disconnection: session time: 0:00:00.165 user=postgres database=regression host=[local] 2025-11-17 08:40:47.456 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-11-17 08:40:47.456 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.456 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-11-17 08:40:47.460 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-11-17 08:40:47.460 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.460 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-11-17 08:40:47.473 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-11-17 08:40:47.473 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.473 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-11-17 08:40:47.474 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-11-17 08:40:47.474 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-11-17 08:40:47.476 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-11-17 08:40:47.476 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-11-17 08:40:47.476 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99 Jan 08" at character 13 2025-11-17 08:40:47.476 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-11-17 08:40:47.488 UTC client backend[22186] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-11-17 08:40:47.488 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-11-17 08:40:47.488 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-11-17 08:40:47.488 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.488 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-11-17 08:40:47.493 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-11-17 08:40:47.493 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.493 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-11-17 08:40:47.493 UTC client backend[22161] pg_regress/strings ERROR: SQL regular expression may not contain more than two escape-double-quote separators 2025-11-17 08:40:47.493 UTC client backend[22161] pg_regress/strings CONTEXT: SQL function "substring" statement 1 2025-11-17 08:40:47.493 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error"; 2025-11-17 08:40:47.496 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-11-17 08:40:47.496 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.496 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-11-17 08:40:47.500 UTC client backend[22187] pg_regress/timetz LOG: disconnection: session time: 0:00:00.193 user=postgres database=regression host=[local] 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date ERROR: date out of range: "4714-11-23 BC" at character 13 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '4714-11-23 BC'; 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date ERROR: date out of range: "5874898-01-01" at character 13 2025-11-17 08:40:47.500 UTC client backend[22186] pg_regress/date STATEMENT: SELECT date '5874898-01-01'; 2025-11-17 08:40:47.519 UTC client backend[22161] pg_regress/strings ERROR: invalid escape string 2025-11-17 08:40:47.519 UTC client backend[22161] pg_regress/strings HINT: Escape string must be empty or one character. 2025-11-17 08:40:47.519 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error; 2025-11-17 08:40:47.527 UTC client backend[22166] pg_regress/numerology LOG: disconnection: session time: 0:00:00.299 user=postgres database=regression host=[local] 2025-11-17 08:40:47.528 UTC client backend[22177] pg_regress/macaddr LOG: disconnection: session time: 0:00:00.255 user=postgres database=regression host=[local] 2025-11-17 08:40:47.536 UTC client backend[22198] pg_regress/inet ERROR: invalid mask length: 33 2025-11-17 08:40:47.536 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT set_masklen(inet(text(i)), 33) FROM INET_TBL; 2025-11-17 08:40:47.539 UTC client backend[22198] pg_regress/inet ERROR: invalid mask length: 33 2025-11-17 08:40:47.539 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT set_masklen(cidr(text(c)), 33) FROM INET_TBL; 2025-11-17 08:40:47.563 UTC client backend[22199] pg_regress/macaddr8 LOG: disconnection: session time: 0:00:00.215 user=postgres database=regression host=[local] 2025-11-17 08:40:47.576 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-17 08:40:47.576 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z'); 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date ERROR: unit "microseconds" not supported for type date 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSECONDS FROM DATE '2020-08-11'); 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date ERROR: unit "milliseconds" not supported for type date 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(MILLISECONDS FROM DATE '2020-08-11'); 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date ERROR: unit "second" not supported for type date 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(SECOND FROM DATE '2020-08-11'); 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date ERROR: unit "minute" not supported for type date 2025-11-17 08:40:47.576 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(MINUTE FROM DATE '2020-08-11'); 2025-11-17 08:40:47.577 UTC client backend[22186] pg_regress/date ERROR: unit "hour" not supported for type date 2025-11-17 08:40:47.577 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(HOUR FROM DATE '2020-08-11'); 2025-11-17 08:40:47.587 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.587 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT -('-2147483648 months'::interval); 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT -('-2147483648 days'::interval); 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT -('-9223372036854775808 us'::interval); 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.588 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval); 2025-11-17 08:40:47.596 UTC client backend[22186] pg_regress/date ERROR: unit "timezone" not supported for type date 2025-11-17 08:40:47.596 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE FROM DATE '2020-08-11'); 2025-11-17 08:40:47.596 UTC client backend[22186] pg_regress/date ERROR: unit "timezone_m" not supported for type date 2025-11-17 08:40:47.596 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_M FROM DATE '2020-08-11'); 2025-11-17 08:40:47.597 UTC client backend[22186] pg_regress/date ERROR: unit "timezone_h" not supported for type date 2025-11-17 08:40:47.597 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_H FROM DATE '2020-08-11'); 2025-11-17 08:40:47.601 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 42 2025-11-17 08:40:47.601 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days'); 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 42 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days'); 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval ERROR: interval out of range at character 42 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years'); 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval ERROR: interval out of range at character 42 2025-11-17 08:40:47.602 UTC client backend[22181] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years'); 2025-11-17 08:40:47.603 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "start": -1 2025-11-17 08:40:47.603 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i'); 2025-11-17 08:40:47.603 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.603 UTC client backend[22181] pg_regress/interval STATEMENT: select extract(epoch from '256 microseconds'::interval * (2^55)::float8); 2025-11-17 08:40:47.606 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "n": -1 2025-11-17 08:40:47.606 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i'); 2025-11-17 08:40:47.606 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression option: "1" 2025-11-17 08:40:47.606 UTC client backend[22161] pg_regress/strings HINT: If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly. 2025-11-17 08:40:47.606 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1'); 2025-11-17 08:40:47.618 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-17 08:40:47.618 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', 0); 2025-11-17 08:40:47.618 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "start": -3 2025-11-17 08:40:47.618 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', -3); 2025-11-17 08:40:47.632 UTC client backend[22161] pg_regress/strings ERROR: regexp_like() does not support the "global" option 2025-11-17 08:40:47.632 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_like('abc', 'a.c', 'g'); 2025-11-17 08:40:47.645 UTC client backend[22186] pg_regress/date ERROR: unit "microsec" not recognized for type date 2025-11-17 08:40:47.645 UTC client backend[22186] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSEC FROM DATE 'infinity'); 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date ERROR: date field value out of range: 0-07-15 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date STATEMENT: select make_date(0, 7, 15); 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date ERROR: date field value out of range: 2013-02-30 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date STATEMENT: select make_date(2013, 2, 30); 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date ERROR: date field value out of range: 2013-13-01 2025-11-17 08:40:47.648 UTC client backend[22186] pg_regress/date STATEMENT: select make_date(2013, 13, 1); 2025-11-17 08:40:47.649 UTC client backend[22186] pg_regress/date ERROR: date field value out of range: 2013-11--1 2025-11-17 08:40:47.649 UTC client backend[22186] pg_regress/date STATEMENT: select make_date(2013, 11, -1); 2025-11-17 08:40:47.651 UTC client backend[22186] pg_regress/date ERROR: date field value out of range: -2147483648-01-01 2025-11-17 08:40:47.651 UTC client backend[22186] pg_regress/date STATEMENT: SELECT make_date(-2147483648, 1, 1); 2025-11-17 08:40:47.652 UTC client backend[22186] pg_regress/date ERROR: time field value out of range: 10:55:100.1 2025-11-17 08:40:47.652 UTC client backend[22186] pg_regress/date STATEMENT: select make_time(10, 55, 100.1); 2025-11-17 08:40:47.652 UTC client backend[22186] pg_regress/date ERROR: time field value out of range: 24:00:2.1 2025-11-17 08:40:47.652 UTC client backend[22186] pg_regress/date STATEMENT: select make_time(24, 0, 2.1); 2025-11-17 08:40:47.655 UTC client backend[22186] pg_regress/date LOG: disconnection: session time: 0:00:00.364 user=postgres database=regression host=[local] 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 0, 1); 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 0); 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "endoption": -1 2025-11-17 08:40:47.657 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1); 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "endoption": 2 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2); 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings ERROR: regexp_instr() does not support the "global" option 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g'); 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-11-17 08:40:47.664 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1); 2025-11-17 08:40:47.673 UTC client backend[22193] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:47.673 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select nummultirange(numrange(2.0, 1.0)); 2025-11-17 08:40:47.676 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.676 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval * 1000; 2025-11-17 08:40:47.680 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.680 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval / 0.001; 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval * 1000; 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval / 0.001; 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '1 month 2146410 days'::interval * 1000.5002; 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 0, 1); 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.688 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '4611686018427387904 usec'::interval / 0.1; 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 0); 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings ERROR: regexp_substr() does not support the "global" option 2025-11-17 08:40:47.688 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g'); 2025-11-17 08:40:47.689 UTC client backend[22161] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-11-17 08:40:47.689 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1); 2025-11-17 08:40:47.698 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.698 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_hours(interval '2147483647 days 24 hrs'); 2025-11-17 08:40:47.698 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.698 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_days(interval '2147483647 months 30 days'); 2025-11-17 08:40:47.699 UTC client backend[22198] pg_regress/inet ERROR: result is out of range 2025-11-17 08:40:47.699 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet + 10000000000; 2025-11-17 08:40:47.699 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.699 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months 30 days'); 2025-11-17 08:40:47.699 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.699 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months -30 days'); 2025-11-17 08:40:47.699 UTC client backend[22198] pg_regress/inet ERROR: result is out of range 2025-11-17 08:40:47.699 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet - 10000000000; 2025-11-17 08:40:47.700 UTC client backend[22198] pg_regress/inet ERROR: result is out of range 2025-11-17 08:40:47.700 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT '126::1'::inet - '127::2'::inet; 2025-11-17 08:40:47.700 UTC client backend[22198] pg_regress/inet ERROR: result is out of range 2025-11-17 08:40:47.700 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT '127::1'::inet - '126::2'::inet; 2025-11-17 08:40:47.701 UTC client backend[22198] pg_regress/inet ERROR: cannot merge addresses from different families 2025-11-17 08:40:47.701 UTC client backend[22198] pg_regress/inet STATEMENT: SELECT inet_merge(c, i) FROM INET_TBL; 2025-11-17 08:40:47.705 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.705 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs'); 2025-11-17 08:40:47.705 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.705 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs'); 2025-11-17 08:40:47.710 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-17 08:40:47.710 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz'); 2025-11-17 08:40:47.711 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression: parentheses () not balanced 2025-11-17 08:40:47.711 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$); 2025-11-17 08:40:47.712 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression: invalid repetition count(s) 2025-11-17 08:40:47.712 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$); 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 second 2 seconds" at character 8 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '1 second 2 seconds'::interval; 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '10 milliseconds 20 milliseconds'::interval; 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '5.5 seconds 3 milliseconds'::interval; 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '1:20:05 5 microseconds'::interval; 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 day 1 day" at character 8 2025-11-17 08:40:47.716 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '1 day 1 day'::interval; 2025-11-17 08:40:47.721 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-17 08:40:47.721 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2' day to minute; 2025-11-17 08:40:47.732 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-17 08:40:47.732 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2' day to second; 2025-11-17 08:40:47.732 UTC client backend[22198] pg_regress/inet LOG: disconnection: session time: 0:00:00.385 user=postgres database=regression host=[local] 2025-11-17 08:40:47.736 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-17 08:40:47.736 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to minute; 2025-11-17 08:40:47.737 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-17 08:40:47.737 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to second; 2025-11-17 08:40:47.737 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-11-17 08:40:47.737 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2' minute to second; 2025-11-17 08:40:47.740 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-17 08:40:47.740 UTC client backend[22161] 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; 2025-11-17 08:40:47.741 UTC client backend[22161] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-11-17 08:40:47.741 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz'); 2025-11-17 08:40:47.741 UTC client backend[22161] pg_regress/strings ERROR: regexp_split_to_table() does not support the "global" option 2025-11-17 08:40:47.741 UTC client backend[22161] 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; 2025-11-17 08:40:47.742 UTC client backend[22161] pg_regress/strings ERROR: regexp_split_to_array() does not support the "global" option 2025-11-17 08:40:47.742 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g'); 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '123 11' day; 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '123 11'; 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "123 2:03 -2:04" at character 17 2025-11-17 08:40:47.742 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '123 2:03 -2:04'; 2025-11-17 08:40:47.744 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-11-17 08:40:47.744 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2.345' day to second(2); 2025-11-17 08:40:47.752 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-11-17 08:40:47.752 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2.345' hour to second(2); 2025-11-17 08:40:47.753 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.3456" at character 17 2025-11-17 08:40:47.753 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '1 2.3456' minute to second(2); 2025-11-17 08:40:47.756 UTC client backend[22181] pg_regress/interval ERROR: interval out of range at character 17 2025-11-17 08:40:47.756 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '2562047788:00:54.775807' second(2); 2025-11-17 08:40:47.756 UTC client backend[22181] pg_regress/interval ERROR: interval out of range at character 17 2025-11-17 08:40:47.756 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-2562047788:00:54.775807' second(2); 2025-11-17 08:40:47.763 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "" at character 18 2025-11-17 08:40:47.763 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval ''; 2025-11-17 08:40:47.773 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17 2025-11-17 08:40:47.773 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P.Y0M3DT4H5M6S'; 2025-11-17 08:40:47.780 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483648 years" at character 17 2025-11-17 08:40:47.780 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483648 years'; 2025-11-17 08:40:47.780 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483649 years" at character 17 2025-11-17 08:40:47.780 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483649 years'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483648 months" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483648 months'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483649 months" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483649 months'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483648 days'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483649 days'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2562047789 hours" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2562047789 hours'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2562047789 hours" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2562047789 hours'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "153722867281 minutes" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '153722867281 minutes'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-153722867281 minutes" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-153722867281 minutes'; 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036855 seconds" at character 17 2025-11-17 08:40:47.781 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036855 seconds'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036855 seconds" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036855 seconds'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036854777 millisecond" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036854777 millisecond'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854777 millisecond" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854777 millisecond'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036854775808 microsecond" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036854775808 microsecond'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775809 microsecond" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854775809 microsecond'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P2147483648" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P2147483648'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-2147483649" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-2147483649'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval out of range at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P1-2147483647-2147483647'; 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT2562047789" at character 17 2025-11-17 08:40:47.782 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT2562047789'; 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT-2562047789" at character 17 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT-2562047789'; 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 weeks" at character 17 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 weeks'; 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 weeks" at character 17 2025-11-17 08:40:47.783 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 weeks'; 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 decades" at character 17 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 decades'; 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 decades" at character 17 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 decades'; 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 centuries" at character 17 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 centuries'; 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 centuries" at character 17 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 centuries'; 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 millennium" at character 17 2025-11-17 08:40:47.784 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 millennium'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 millennium" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 millennium'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "1 week 2147483647 days" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '1 week 2147483647 days'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-1 week -2147483648 days" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-1 week -2147483648 days'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 1 week" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 days 1 week'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -1 week" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 days -1 week'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P1W2147483647D" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P1W2147483647D'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-1W-2147483648D" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-1W-2147483648D'; 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P2147483647D1W" at character 17 2025-11-17 08:40:47.788 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P2147483647D1W'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-1W" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-2147483648D-1W'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "1 decade 2147483647 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '1 decade 2147483647 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "1 century 2147483647 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '1 century 2147483647 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "1 millennium 2147483647 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '1 millennium 2147483647 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-1 decade -2147483648 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-1 decade -2147483648 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-1 century -2147483648 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-1 century -2147483648 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-1 millennium -2147483648 years" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-1 millennium -2147483648 years'; 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 decade" at character 17 2025-11-17 08:40:47.789 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 years 1 decade'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 century" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 years 1 century'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 millennium" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 years 1 millennium'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 decade" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 decade'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 century" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 century'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 millennium" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 millennium'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 millennium 2147483647 months" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 millennium 2147483647 months'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 centuries 2147483647 months" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 centuries 2147483647 months'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 decades 2147483647 months" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 decades 2147483647 months'; 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 yrs 2147483647 months" at character 17 2025-11-17 08:40:47.790 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 yrs 2147483647 months'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 millennium -2147483648 months" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 millennium -2147483648 months'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 centuries -2147483648 months" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 centuries -2147483648 months'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 decades -2147483648 months" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 decades -2147483648 months'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 yrs -2147483648 months" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 yrs -2147483648 months'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 millennium" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 millennium'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 centuries" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 centuries'; 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 decades" at character 17 2025-11-17 08:40:47.791 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 decades'; 2025-11-17 08:40:47.791 UTC client backend[22188] pg_regress/timestamp ERROR: time zone "america/does_not_exist" not recognized at character 35 2025-11-17 08:40:47.791 UTC client backend[22188] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 yrs" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 yrs'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 millennium" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 millennium'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 centuries" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 centuries'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 decades" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 decades'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 yrs" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 yrs'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 months 2147483647 days" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 months 2147483647 days'; 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 months -2147483648 days" at character 17 2025-11-17 08:40:47.795 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 months -2147483648 days'; 2025-11-17 08:40:47.800 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.1 months" at character 17 2025-11-17 08:40:47.800 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 days 0.1 months'; 2025-11-17 08:40:47.800 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.1 months" at character 17 2025-11-17 08:40:47.800 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.1 months'; 2025-11-17 08:40:47.801 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.5 weeks 2147483647 days" at character 17 2025-11-17 08:40:47.801 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.5 weeks 2147483647 days'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.5 weeks -2147483648 days" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.5 weeks -2147483648 days'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.5 weeks" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2147483647 days 0.5 weeks'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.5 weeks" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.5 weeks'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.01 months 9223372036854775807 microseconds'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.01 months -9223372036854775808 microseconds'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.01 months'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.01 months'; 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17 2025-11-17 08:40:47.802 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 weeks 9223372036854775807 microseconds'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 weeks -9223372036854775808 microseconds'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 weeks'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 weeks'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 days 9223372036854775807 microseconds'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-0.1 days -9223372036854775808 microseconds'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 days'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 days'; 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.1Y2147483647M" at character 17 2025-11-17 08:40:47.803 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.1Y2147483647M'; 2025-11-17 08:40:47.804 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-0.1Y-2147483648M" at character 17 2025-11-17 08:40:47.804 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-0.1Y-2147483648M'; 2025-11-17 08:40:47.804 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P2147483647M0.1Y" at character 17 2025-11-17 08:40:47.804 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P2147483647M0.1Y'; 2025-11-17 08:40:47.805 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-2147483648M-0.1Y" at character 17 2025-11-17 08:40:47.805 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-2147483648M-0.1Y'; 2025-11-17 08:40:47.806 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.1M2147483647D" at character 17 2025-11-17 08:40:47.806 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.1M2147483647D'; 2025-11-17 08:40:47.806 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-0.1M-2147483648D" at character 17 2025-11-17 08:40:47.806 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-0.1M-2147483648D'; 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.1M" at character 17 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P2147483647D0.1M'; 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.1M" at character 17 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.1M'; 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.5W2147483647D" at character 17 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.5W2147483647D'; 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-0.5W-2147483648D" at character 17 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-0.5W-2147483648D'; 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.5W" at character 17 2025-11-17 08:40:47.807 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P2147483647D0.5W'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.5W" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.5W'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.01MT2562047788H54.775807S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-0.01MT-2562047788H-54.775808S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.1DT2562047788H54.775807S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P-0.1DT-2562047788H-54.775808S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1H54.775807S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT2562047788.1H54.775807S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT-2562047788.1H-54.775808S'; 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17 2025-11-17 08:40:47.808 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT2562047788H0.1M54.775807S'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT-2562047788H-0.1M-54.775808S'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P0.1-2147483647-00" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P0.1-2147483647-00'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P00-0.1-2147483647" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P00-0.1-2147483647'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P00-0.01-00T2562047788:00:54.775807'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'P00-00-0.1T2562047788:00:54.775807'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1:00:54.775807" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT2562047788.1:00:54.775807'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "PT2562047788:01.:54.775807" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval 'PT2562047788:01.:54.775807'; 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775807" at character 17 2025-11-17 08:40:47.809 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775807'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775808 ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775807" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775807'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775808 ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775807'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775808 ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 days ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds ago'; 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17 2025-11-17 08:40:47.810 UTC client backend[22181] pg_regress/interval STATEMENT: select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago'; 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(years := 178956971); 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(years := -178956971); 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(years := 1, months := 2147483647); 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.811 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(years := -1, months := -2147483648); 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(weeks := 306783379); 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(weeks := -306783379); 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(weeks := 1, days := 2147483647); 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(weeks := -1, days := -2147483648); 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval ERROR: value out of range: overflow 2025-11-17 08:40:47.812 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(secs := 1e308); 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(secs := 1e18); 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(secs := -1e18); 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(mins := 1, secs := 9223372036800.0); 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.813 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(mins := -1, secs := -9223372036800.0); 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval ERROR: integer out of range 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(years := 'inf'::float::int); 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval ERROR: integer out of range 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(months := 'NaN'::float::int); 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(secs := 'inf'); 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.817 UTC client backend[22181] pg_regress/interval STATEMENT: select make_interval(secs := 'NaN'); 2025-11-17 08:40:47.819 UTC client backend[22188] pg_regress/timestamp ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 35 2025-11-17 08:40:47.819 UTC client backend[22188] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-11-17 08:40:47.819 UTC client backend[22181] pg_regress/interval ERROR: unit "fortnight" not recognized for type interval 2025-11-17 08:40:47.819 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days'); 2025-11-17 08:40:47.819 UTC client backend[22181] pg_regress/interval ERROR: unit "timezone" not supported for type interval 2025-11-17 08:40:47.819 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days'); 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp ERROR: timestamp out of range: "4714-11-23 23:59:59 BC" at character 8 2025-11-17 08:40:47.828 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT '4714-11-23 23:59:59 BC'::timestamp; 2025-11-17 08:40:47.829 UTC client backend[22188] pg_regress/timestamp ERROR: timestamp out of range: "294277-01-01 00:00:00" at character 8 2025-11-17 08:40:47.829 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT '294277-01-01 00:00:00'::timestamp; 2025-11-17 08:40:47.841 UTC client backend[22188] pg_regress/timestamp ERROR: unit "timezone" not supported for type timestamp without time zone 2025-11-17 08:40:47.841 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'timezone', timestamp '2004-02-29 15:44:17.71393' ) AS notsupp_trunc; 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us'; 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us'; 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us'; 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.844 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us'; 2025-11-17 08:40:47.847 UTC client backend[22188] pg_regress/timestamp ERROR: unit "timezone" not supported for type timestamp without time zone 2025-11-17 08:40:47.847 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'timezone', timestamp 'infinity' ) AS notsupp_inf_trunc; 2025-11-17 08:40:47.847 UTC client backend[22188] pg_regress/timestamp ERROR: unit "ago" not recognized for type timestamp without time zone 2025-11-17 08:40:47.847 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'ago', timestamp 'infinity' ) AS invalid_trunc; 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval 'infinity'; 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval '-infinity'; 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval 'infinity'; 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-17 08:40:47.853 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval '-infinity'; 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval 'infinity'; 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval ERROR: cannot add infinite interval to time 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval '-infinity'; 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval 'infinity'; 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-11-17 08:40:47.854 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval '-infinity'; 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_bin('5 years'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp ERROR: stride must be greater than zero 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_bin('0 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00'); 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp ERROR: stride must be greater than zero 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT date_bin('-2 days'::interval, timestamp '1970-01-01 01:00:00' , timestamp '1970-01-01 00:00:00'); 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.856 UTC client backend[22188] pg_regress/timestamp STATEMENT: select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC'); 2025-11-17 08:40:47.859 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.859 UTC client backend[22188] pg_regress/timestamp STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp); 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us'; 2025-11-17 08:40:47.860 UTC client backend[22188] pg_regress/timestamp ERROR: timestamp out of range 2025-11-17 08:40:47.860 UTC client backend[22188] pg_regress/timestamp STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp); 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 'nan'; 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 'nan'; 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2; 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 0; 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 0; 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.860 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '0 days' * 'infinity'::float; 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '0 days' * '-infinity'::float; 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'infinity'; 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.861 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval 'infinity' / '-infinity'; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'nan'; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'infinity'; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-infinity' / '-infinity'; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'nan'; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: interval out of range 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5; 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-11-17 08:40:47.862 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-11-17 08:40:47.863 UTC client backend[22181] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-11-17 08:40:47.863 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-11-17 08:40:47.864 UTC client backend[22181] pg_regress/interval ERROR: unit "week" not supported for type interval 2025-11-17 08:40:47.864 UTC client backend[22181] pg_regress/interval DETAIL: Months usually have fractional weeks. 2025-11-17 08:40:47.864 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('week', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-11-17 08:40:47.864 UTC client backend[22181] pg_regress/interval ERROR: unit "ago" not recognized for type interval 2025-11-17 08:40:47.864 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('ago', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-17 08:40:47.868 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::time); 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::time); 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::timetz); 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-11-17 08:40:47.872 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::timetz); 2025-11-17 08:40:47.873 UTC client backend[22181] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-11-17 08:40:47.873 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT 'infinity'::interval::time; 2025-11-17 08:40:47.873 UTC client backend[22181] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-11-17 08:40:47.873 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT '-infinity'::interval::time; 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL '42 days 2 seconds ago ago'; 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "2 minutes ago 5 days" at character 17 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL '2 minutes ago 5 days'; 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "hour 5 months" at character 17 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'hour 5 months'; 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "1 year months days 5 hours" at character 17 2025-11-17 08:40:47.874 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL '1 year months days 5 hours'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "now" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'now'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "today" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'today'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "tomorrow" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'tomorrow'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "allballs" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'allballs'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "epoch" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'epoch'; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "yesterday" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'yesterday'; 2025-11-17 08:40:47.876 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.876 UTC client backend[22188] pg_regress/timestamp STATEMENT: SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows; 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity years" at character 17 2025-11-17 08:40:47.876 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity years'; 2025-11-17 08:40:47.877 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity ago" at character 17 2025-11-17 08:40:47.877 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity ago'; 2025-11-17 08:40:47.877 UTC client backend[22181] pg_regress/interval ERROR: invalid input syntax for type interval: "+infinity -infinity" at character 17 2025-11-17 08:40:47.877 UTC client backend[22181] pg_regress/interval STATEMENT: SELECT INTERVAL '+infinity -infinity'; 2025-11-17 08:40:47.877 UTC client backend[22181] pg_regress/interval LOG: disconnection: session time: 0:00:00.599 user=postgres database=regression host=[local] 2025-11-17 08:40:47.888 UTC client backend[22183] pg_regress/timestamptz ERROR: time zone "america/does_not_exist" not recognized at character 37 2025-11-17 08:40:47.888 UTC client backend[22183] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-11-17 08:40:47.900 UTC client backend[22183] pg_regress/timestamptz ERROR: time zone "America/Does_not_exist" not recognized 2025-11-17 08:40:47.900 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist'; 2025-11-17 08:40:47.912 UTC client backend[22188] pg_regress/timestamp ERROR: date field value out of range: 0-07-15 2025-11-17 08:40:47.912 UTC client backend[22188] pg_regress/timestamp STATEMENT: select make_timestamp(0, 7, 15, 12, 30, 15); 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp ERROR: step size cannot equal zero 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamp, '2020-01-02 03:00'::timestamp, '0 hour'::interval); 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp ERROR: step size cannot be infinite 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity'); 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp ERROR: step size cannot be infinite 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity'); 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.913 UTC client backend[22188] pg_regress/timestamp STATEMENT: select timestamp 'infinity' - timestamp 'infinity'; 2025-11-17 08:40:47.914 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.914 UTC client backend[22188] pg_regress/timestamp STATEMENT: select timestamp '-infinity' - timestamp '-infinity'; 2025-11-17 08:40:47.920 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.920 UTC client backend[22188] pg_regress/timestamp STATEMENT: select age(timestamp 'infinity', timestamp 'infinity'); 2025-11-17 08:40:47.920 UTC client backend[22183] pg_regress/timestamptz ERROR: invalid input syntax for type timestamp with time zone: "Jan 01 00:00:00 2024 LMT" at character 8 2025-11-17 08:40:47.920 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT 'Jan 01 00:00:00 2024 LMT'::timestamptz; 2025-11-17 08:40:47.920 UTC client backend[22188] pg_regress/timestamp ERROR: interval out of range 2025-11-17 08:40:47.920 UTC client backend[22188] pg_regress/timestamp STATEMENT: select age(timestamp '-infinity', timestamp '-infinity'); 2025-11-17 08:40:47.924 UTC client backend[22188] pg_regress/timestamp LOG: disconnection: session time: 0:00:00.615 user=postgres database=regression host=[local] 2025-11-17 08:40:47.975 UTC client backend[22183] pg_regress/timestamptz ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 37 2025-11-17 08:40:47.975 UTC client backend[22183] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-11-17 08:40:47.981 UTC client backend[22183] pg_regress/timestamptz ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37 2025-11-17 08:40:47.981 UTC client backend[22183] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-11-17 08:40:47.981 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37 2025-11-17 08:40:47.981 UTC client backend[22183] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-11-17 08:40:47.998 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8 2025-11-17 08:40:47.998 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT '4714-11-23 23:59:59+00 BC'::timestamptz; 2025-11-17 08:40:48.005 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp out of range: "294277-01-01 00:00:00+00" at character 8 2025-11-17 08:40:48.005 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT '294277-01-01 00:00:00+00'::timestamptz; 2025-11-17 08:40:48.005 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp out of range: "294277-12-31 16:00:00-08" at character 8 2025-11-17 08:40:48.005 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT '294277-12-31 16:00:00-08'::timestamptz; 2025-11-17 08:40:48.010 UTC client backend[22161] pg_regress/strings ERROR: negative substring length not allowed 2025-11-17 08:40:48.010 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-11-17 08:40:48.019 UTC client backend[22183] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-17 08:40:48.019 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'timezone', timestamp with time zone '2004-02-29 15:44:17.71393' ) AS notsupp_trunc; 2025-11-17 08:40:48.020 UTC client backend[22183] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-17 08:40:48.020 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'timezone', timestamp with time zone 'infinity' ) AS notsupp_inf_trunc; 2025-11-17 08:40:48.024 UTC client backend[22183] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-11-17 08:40:48.024 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'ago', timestamp with time zone 'infinity' ) AS invalid_trunc; 2025-11-17 08:40:48.032 UTC client backend[22183] pg_regress/timestamptz ERROR: unit "timezone" not supported for type timestamp with time zone 2025-11-17 08:40:48.032 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT date_trunc('timezone', timestamp with time zone 'infinity', 'GMT') AS notsupp_zone_trunc; 2025-11-17 08:40:48.036 UTC client backend[22183] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-11-17 08:40:48.036 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT date_trunc('ago', timestamp with time zone 'infinity', 'GMT') AS invalid_zone_trunc; 2025-11-17 08:40:48.046 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-17 08:40:48.046 UTC client backend[22183] 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'); 2025-11-17 08:40:48.046 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-11-17 08:40:48.046 UTC client backend[22183] 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'); 2025-11-17 08:40:48.046 UTC client backend[22183] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-11-17 08:40:48.046 UTC client backend[22183] 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'); 2025-11-17 08:40:48.047 UTC client backend[22183] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-11-17 08:40:48.047 UTC client backend[22183] 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'); 2025-11-17 08:40:48.047 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.047 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC'); 2025-11-17 08:40:48.052 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.052 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz); 2025-11-17 08:40:48.053 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp out of range 2025-11-17 08:40:48.053 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz); 2025-11-17 08:40:48.073 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.073 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT timestamptz '294276-12-31 23:59:59 UTC' - timestamptz '1999-12-23 19:59:04.224192 UTC' AS overflows; 2025-11-17 08:40:48.097 UTC client backend[22163] pg_regress/point LOG: disconnection: session time: 0:00:00.893 user=postgres database=regression host=[local] 2025-11-17 08:40:48.109 UTC client backend[22161] pg_regress/strings ERROR: negative substring length not allowed 2025-11-17 08:40:48.109 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-11-17 08:40:48.165 UTC client backend[22183] pg_regress/timestamptz ERROR: invalid input syntax for type numeric time zone: "2" 2025-11-17 08:40:48.165 UTC client backend[22183] pg_regress/timestamptz HINT: Numeric time zones must have "-" or "+" as first character. 2025-11-17 08:40:48.165 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2'); 2025-11-17 08:40:48.166 UTC client backend[22183] pg_regress/timestamptz ERROR: numeric time zone "+16" out of range 2025-11-17 08:40:48.166 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16'); 2025-11-17 08:40:48.166 UTC client backend[22183] pg_regress/timestamptz ERROR: numeric time zone "-16" out of range 2025-11-17 08:40:48.166 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16'); 2025-11-17 08:40:48.176 UTC client backend[22183] pg_regress/timestamptz ERROR: time zone "Nehwon/Lankhmar" not recognized 2025-11-17 08:40:48.176 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar'); 2025-11-17 08:40:48.185 UTC client backend[22161] pg_regress/strings ERROR: field position must not be zero 2025-11-17 08:40:48.185 UTC client backend[22161] pg_regress/strings STATEMENT: select split_part('joeuser@mydatabase','@',0) AS "an error"; 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz ERROR: step size cannot equal zero 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamptz, '2020-01-02 03:00'::timestamptz, '0 hour'::interval); 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity'); 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-11-17 08:40:48.190 UTC client backend[22183] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity'); 2025-11-17 08:40:48.256 UTC client backend[22161] pg_regress/strings ERROR: invalid symbol "@" found while decoding base64url sequence 2025-11-17 08:40:48.256 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT decode('QQ@=', 'base64url'); 2025-11-17 08:40:48.257 UTC client backend[22161] pg_regress/strings ERROR: invalid base64url end sequence 2025-11-17 08:40:48.257 UTC client backend[22161] pg_regress/strings HINT: Input data is missing padding, is truncated, or is otherwise corrupted. 2025-11-17 08:40:48.257 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT decode('QQIDQ', 'base64url'); 2025-11-17 08:40:48.257 UTC client backend[22161] pg_regress/strings ERROR: unexpected "=" while decoding base64url sequence 2025-11-17 08:40:48.257 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT decode('=QQQ', 'base64url'); 2025-11-17 08:40:48.258 UTC client backend[22161] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-11-17 08:40:48.258 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT get_bit('\x1234567890abcdef00'::bytea, 99); 2025-11-17 08:40:48.258 UTC client backend[22161] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-11-17 08:40:48.258 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0); 2025-11-17 08:40:48.259 UTC client backend[22161] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-11-17 08:40:48.259 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT get_byte('\x1234567890abcdef00'::bytea, 99); 2025-11-17 08:40:48.259 UTC client backend[22161] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-11-17 08:40:48.259 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11); 2025-11-17 08:40:48.265 UTC client backend[22183] pg_regress/timestamptz ERROR: timestamp cannot be NaN 2025-11-17 08:40:48.265 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT to_timestamp('NaN'::float); 2025-11-17 08:40:48.266 UTC client backend[22161] pg_regress/strings ERROR: smallint out of range 2025-11-17 08:40:48.266 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT '\x123456'::bytea::int2; 2025-11-17 08:40:48.268 UTC client backend[22161] pg_regress/strings ERROR: integer out of range 2025-11-17 08:40:48.268 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT '\x123456789A'::bytea::int4; 2025-11-17 08:40:48.272 UTC client backend[22161] pg_regress/strings ERROR: bigint out of range 2025-11-17 08:40:48.272 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT '\x112233445566778899'::bytea::int8; 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 8 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 24 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 42 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 62 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 80 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 98 2025-11-17 08:40:48.274 UTC client backend[22161] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-11-17 08:40:48.293 UTC client backend[22161] pg_regress/strings ERROR: null character not permitted 2025-11-17 08:40:48.293 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT chr(0); 2025-11-17 08:40:48.300 UTC client backend[22161] pg_regress/strings ERROR: negative substring length not allowed 2025-11-17 08:40:48.300 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error"; 2025-11-17 08:40:48.313 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-17 08:40:48.313 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99'); 2025-11-17 08:40:48.318 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-17 08:40:48.318 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99\0061'); 2025-11-17 08:40:48.318 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-17 08:40:48.318 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+00db99\+000061'); 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+2FFFFF'); 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \udb99\u0061'); 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U0000db99\U00000061'); 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U002FFFFF'); 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings ERROR: invalid Unicode escape 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings HINT: Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX. 2025-11-17 08:40:48.320 UTC client backend[22161] pg_regress/strings STATEMENT: SELECT unistr('wrong: \xyz'); 2025-11-17 08:40:48.324 UTC client backend[22161] pg_regress/strings LOG: disconnection: session time: 0:00:01.127 user=postgres database=regression host=[local] 2025-11-17 08:40:48.346 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.346 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT timestamptz 'infinity' - timestamptz 'infinity'; 2025-11-17 08:40:48.350 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.350 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT timestamptz '-infinity' - timestamptz '-infinity'; 2025-11-17 08:40:48.360 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.360 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz 'infinity', timestamptz 'infinity'); 2025-11-17 08:40:48.361 UTC client backend[22183] pg_regress/timestamptz ERROR: interval out of range 2025-11-17 08:40:48.361 UTC client backend[22183] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz '-infinity', timestamptz '-infinity'); 2025-11-17 08:40:48.366 UTC client backend[22183] pg_regress/timestamptz LOG: disconnection: session time: 0:00:01.078 user=postgres database=regression host=[local] 2025-11-17 08:40:48.379 UTC client backend[22192] pg_regress/polygon LOG: disconnection: session time: 0:00:01.058 user=postgres database=regression host=[local] 2025-11-17 08:40:48.747 UTC client backend[22168] pg_regress/box LOG: disconnection: session time: 0:00:01.504 user=postgres database=regression host=[local] 2025-11-17 08:40:48.779 UTC client backend[22193] pg_regress/multirangetypes ERROR: value for domain restrictedmultirange violates check constraint "restrictedmultirange_check" 2025-11-17 08:40:48.779 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select '{[4,50)}'::restrictedmultirange @> 7; 2025-11-17 08:40:48.796 UTC client backend[22193] pg_regress/multirangetypes ERROR: type "intmultirange" already exists 2025-11-17 08:40:48.796 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intrange". 2025-11-17 08:40:48.796 UTC client backend[22193] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-11-17 08:40:48.796 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create type intrange as range(subtype=int); 2025-11-17 08:40:48.799 UTC client backend[22193] pg_regress/multirangetypes ERROR: type "intr_multirange" already exists 2025-11-17 08:40:48.799 UTC client backend[22193] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intr". 2025-11-17 08:40:48.799 UTC client backend[22193] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-11-17 08:40:48.799 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create type intr as range(subtype=int); 2025-11-17 08:40:48.802 UTC client backend[22193] pg_regress/multirangetypes ERROR: type "int4" already exists 2025-11-17 08:40:48.802 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C"); 2025-11-17 08:40:48.808 UTC client backend[22193] pg_regress/multirangetypes ERROR: function multirange_of_text(textrange2) does not exist at character 8 2025-11-17 08:40:48.808 UTC client backend[22193] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:48.808 UTC client backend[22193] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:48.808 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange2('a','Z')); 2025-11-17 08:40:48.809 UTC client backend[22193] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:48.809 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange1('a','Z')) @> 'b'::text; 2025-11-17 08:40:48.819 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot alter multirange type multitextrange1 2025-11-17 08:40:48.819 UTC client backend[22193] pg_regress/multirangetypes HINT: You can alter type textrange1, which will alter the multirange type as well. 2025-11-17 08:40:48.819 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: alter type multitextrange1 owner to regress_multirange_owner; 2025-11-17 08:40:48.821 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot set privileges of multirange types 2025-11-17 08:40:48.821 UTC client backend[22193] pg_regress/multirangetypes HINT: Set the privileges of the range type instead. 2025-11-17 08:40:48.821 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: revoke usage on type multitextrange1 from public; 2025-11-17 08:40:48.932 UTC client backend[22193] pg_regress/multirangetypes ERROR: permission denied for type multitextrange1 2025-11-17 08:40:48.932 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create temp table test2(f1 multitextrange1[]); 2025-11-17 08:40:48.952 UTC client backend[22193] pg_regress/multirangetypes ERROR: function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8 2025-11-17 08:40:48.952 UTC client backend[22193] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:48.952 UTC client backend[22193] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:48.952 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20))); 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function bogus_func(anyelement) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:48.959 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function bogus_func(int) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-11-17 08:40:48.962 UTC client backend[22193] pg_regress/multirangetypes ERROR: function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8 2025-11-17 08:40:48.962 UTC client backend[22193] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:48.962 UTC client backend[22193] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:48.962 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]); 2025-11-17 08:40:48.969 UTC client backend[22193] pg_regress/multirangetypes ERROR: function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8 2025-11-17 08:40:48.969 UTC client backend[22193] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:48.969 UTC client backend[22193] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:48.969 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20))); 2025-11-17 08:40:48.972 UTC client backend[22193] pg_regress/multirangetypes ERROR: function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8 2025-11-17 08:40:48.972 UTC client backend[22193] pg_regress/multirangetypes DETAIL: No function of that name accepts the given argument types. 2025-11-17 08:40:48.972 UTC client backend[22193] pg_regress/multirangetypes HINT: You might need to add explicit type casts. 2025-11-17 08:40:48.972 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20))); 2025-11-17 08:40:48.976 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:48.976 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-11-17 08:40:48.976 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-11-17 08:40:48.993 UTC client backend[22193] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-11-17 08:40:48.993 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2])); 2025-11-17 08:40:49.050 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:49.050 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:49.050 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function mr_outparam_fail(i anyelement, out r anymultirange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function mr_inoutparam_fail(inout i anyelement, out r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-11-17 08:40:49.051 UTC client backend[22193] pg_regress/multirangetypes STATEMENT: create function mr_table_fail(i anyelement) returns table(i anyelement, r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2025-11-17 08:40:49.056 UTC client backend[22193] pg_regress/multirangetypes LOG: disconnection: session time: 0:00:01.732 user=postgres database=regression host=[local] 2025-11-17 08:40:49.195 UTC unrecognized[22463] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.196 UTC unrecognized[22464] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.197 UTC client backend[22464] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.197 UTC client backend[22464] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/geometry 2025-11-17 08:40:49.202 UTC client backend[22463] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.202 UTC client backend[22463] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/horology 2025-11-17 08:40:49.208 UTC unrecognized[22465] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.209 UTC client backend[22465] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.209 UTC client backend[22465] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tstypes 2025-11-17 08:40:49.211 UTC client backend[22463] pg_regress/horology LOG: connection ready: setup total=19.229 ms, fork=2.555 ms, authentication=0.348 ms 2025-11-17 08:40:49.212 UTC client backend[22464] pg_regress/geometry LOG: connection ready: setup total=18.844 ms, fork=2.344 ms, authentication=0.375 ms 2025-11-17 08:40:49.216 UTC unrecognized[22468] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.216 UTC unrecognized[22471] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.217 UTC client backend[22468] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.217 UTC client backend[22468] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc_sanity 2025-11-17 08:40:49.217 UTC unrecognized[22469] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.217 UTC client backend[22471] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.217 UTC client backend[22471] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/comments 2025-11-17 08:40:49.219 UTC client backend[22469] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.219 UTC client backend[22469] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regex 2025-11-17 08:40:49.222 UTC unrecognized[22473] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.223 UTC client backend[22473] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.223 UTC client backend[22473] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/type_sanity 2025-11-17 08:40:49.229 UTC unrecognized[22475] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.230 UTC client backend[22475] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.230 UTC client backend[22475] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/opr_sanity 2025-11-17 08:40:49.232 UTC unrecognized[22476] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.234 UTC client backend[22476] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.234 UTC client backend[22476] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/expressions 2025-11-17 08:40:49.236 UTC client backend[22465] pg_regress/tstypes LOG: connection ready: setup total=36.368 ms, fork=7.600 ms, authentication=0.369 ms 2025-11-17 08:40:49.237 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33 2025-11-17 08:40:49.237 UTC client backend[22463] pg_regress/horology HINT: Perhaps you need a different "DateStyle" setting. 2025-11-17 08:40:49.237 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone '27/12/2001 04:05:06.789-08'; 2025-11-17 08:40:49.237 UTC client backend[22471] pg_regress/comments LOG: connection ready: setup total=24.721 ms, fork=1.181 ms, authentication=0.337 ms 2025-11-17 08:40:49.240 UTC client backend[22468] pg_regress/misc_sanity LOG: connection ready: setup total=32.127 ms, fork=1.318 ms, authentication=0.414 ms 2025-11-17 08:40:49.243 UTC client backend[22475] pg_regress/opr_sanity LOG: connection ready: setup total=18.240 ms, fork=3.538 ms, authentication=0.327 ms 2025-11-17 08:40:49.245 UTC client backend[22473] pg_regress/type_sanity LOG: connection ready: setup total=24.692 ms, fork=1.668 ms, authentication=0.339 ms 2025-11-17 08:40:49.245 UTC client backend[22469] pg_regress/regex LOG: connection ready: setup total=35.972 ms, fork=7.866 ms, authentication=0.404 ms 2025-11-17 08:40:49.249 UTC unrecognized[22477] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.251 UTC client backend[22477] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.251 UTC client backend[22477] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xid 2025-11-17 08:40:49.254 UTC client backend[22476] pg_regress/expressions LOG: connection ready: setup total=28.218 ms, fork=5.921 ms, authentication=0.371 ms 2025-11-17 08:40:49.256 UTC unrecognized[22478] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.257 UTC client backend[22478] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.257 UTC client backend[22478] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/unicode 2025-11-17 08:40:49.260 UTC client backend[22471] pg_regress/comments LOG: disconnection: session time: 0:00:00.045 user=postgres database=regression host=[local] 2025-11-17 08:40:49.272 UTC client backend[22465] pg_regress/tstypes ERROR: syntax error in tsvector: "'' '1' '2'" at character 8 2025-11-17 08:40:49.272 UTC client backend[22465] pg_regress/tstypes STATEMENT: SELECT $$'' '1' '2'$$::tsvector; 2025-11-17 08:40:49.272 UTC unrecognized[22481] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.273 UTC client backend[22481] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.273 UTC client backend[22481] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/database 2025-11-17 08:40:49.276 UTC client backend[22477] pg_regress/xid LOG: connection ready: setup total=48.505 ms, fork=17.443 ms, authentication=0.378 ms 2025-11-17 08:40:49.276 UTC unrecognized[22479] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.277 UTC unrecognized[22480] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:49.279 UTC client backend[22480] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.279 UTC client backend[22480] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/mvcc 2025-11-17 08:40:49.280 UTC client backend[22478] pg_regress/unicode LOG: connection ready: setup total=32.309 ms, fork=3.721 ms, authentication=0.345 ms 2025-11-17 08:40:49.285 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28 2025-11-17 08:40:49.285 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT time with time zone 'T040506.789 America/Los_Angeles'; 2025-11-17 08:40:49.287 UTC client backend[22479] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:49.287 UTC client backend[22479] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_import 2025-11-17 08:40:49.287 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type xid: "" at character 8 2025-11-17 08:40:49.287 UTC client backend[22477] pg_regress/xid STATEMENT: select ''::xid; 2025-11-17 08:40:49.291 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type xid: "asdf" at character 8 2025-11-17 08:40:49.291 UTC client backend[22477] pg_regress/xid STATEMENT: select 'asdf'::xid; 2025-11-17 08:40:49.292 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type xid8: "" at character 8 2025-11-17 08:40:49.292 UTC client backend[22477] pg_regress/xid STATEMENT: select ''::xid8; 2025-11-17 08:40:49.292 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type xid8: "asdf" at character 8 2025-11-17 08:40:49.292 UTC client backend[22477] pg_regress/xid STATEMENT: select 'asdf'::xid8; 2025-11-17 08:40:49.293 UTC client backend[22479] pg_regress/stats_import LOG: connection ready: setup total=29.153 ms, fork=2.662 ms, authentication=9.690 ms 2025-11-17 08:40:49.293 UTC client backend[22481] pg_regress/database LOG: connection ready: setup total=27.144 ms, fork=2.498 ms, authentication=0.385 ms 2025-11-17 08:40:49.293 UTC client backend[22476] pg_regress/expressions WARNING: TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-17 08:40:49.296 UTC client backend[22480] pg_regress/mvcc LOG: connection ready: setup total=30.816 ms, fork=3.335 ms, authentication=0.335 ms 2025-11-17 08:40:49.296 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type time: "T04" at character 31 2025-11-17 08:40:49.296 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT time without time zone 'T04'; 2025-11-17 08:40:49.297 UTC client backend[22464] pg_regress/geometry ERROR: value out of range: underflow 2025-11-17 08:40:49.297 UTC client backend[22464] 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; 2025-11-17 08:40:49.300 UTC client backend[22476] pg_regress/expressions WARNING: TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-11-17 08:40:49.300 UTC client backend[22476] pg_regress/expressions WARNING: TIME(7) precision reduced to maximum allowed, 6 2025-11-17 08:40:49.301 UTC client backend[22476] pg_regress/expressions WARNING: TIMESTAMP(7) precision reduced to maximum allowed, 6 2025-11-17 08:40:49.306 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T04+08" at character 28 2025-11-17 08:40:49.306 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT time with time zone 'T04+08'; 2025-11-17 08:40:49.308 UTC client backend[22478] pg_regress/unicode ERROR: invalid normalization form: def 2025-11-17 08:40:49.308 UTC client backend[22478] pg_regress/unicode STATEMENT: SELECT "normalize"('abc', 'def'); 2025-11-17 08:40:49.308 UTC client backend[22464] pg_regress/geometry ERROR: value out of range: overflow 2025-11-17 08:40:49.308 UTC client backend[22464] 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; 2025-11-17 08:40:49.310 UTC client backend[22469] pg_regress/regex ERROR: regexp_match() does not support the "global" option 2025-11-17 08:40:49.310 UTC client backend[22469] pg_regress/regex HINT: Use the regexp_matches function instead. 2025-11-17 08:40:49.310 UTC client backend[22469] pg_regress/regex STATEMENT: select regexp_match('abc', 'Bd', 'ig'); 2025-11-17 08:40:49.312 UTC client backend[22464] pg_regress/geometry ERROR: division by zero 2025-11-17 08:40:49.312 UTC client backend[22464] 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; 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 J J J" at character 13 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '1995-08-06 J J J'; 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "J J 1520447" at character 13 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date 'J J 1520447'; 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08'; 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08'; 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456-08" at character 33 2025-11-17 08:40:49.315 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456-08'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456.001e6-08" at character 33 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456.001e6-08'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 epoch" at character 13 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '1995-08-06 epoch'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 infinity" at character 13 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '1995-08-06 infinity'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 -infinity" at character 13 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '1995-08-06 -infinity'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "today infinity" at character 13 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date 'today infinity'; 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type date: "-infinity infinity" at character 13 2025-11-17 08:40:49.316 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '-infinity infinity'; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 epoch'; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 infinity'; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 -infinity'; 2025-11-17 08:40:49.317 UTC client backend[22477] pg_regress/xid ERROR: operator does not exist: xid < xid at character 17 2025-11-17 08:40:49.317 UTC client backend[22477] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.317 UTC client backend[22477] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.317 UTC client backend[22477] pg_regress/xid STATEMENT: select '1'::xid < '2'::xid; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "epoch 01:01:01" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp 'epoch 01:01:01'; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "infinity 01:01:01" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp 'infinity 01:01:01'; 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18 2025-11-17 08:40:49.317 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp '-infinity 01:01:01'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "now epoch" at character 18 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp 'now epoch'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity infinity" at character 18 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp '-infinity infinity'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 epoch'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 infinity'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 -infinity'; 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20 2025-11-17 08:40:49.320 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz 'epoch 01:01:01'; 2025-11-17 08:40:49.321 UTC client backend[22478] pg_regress/unicode ERROR: invalid normalization form: def 2025-11-17 08:40:49.321 UTC client backend[22478] pg_regress/unicode STATEMENT: SELECT is_normalized('abc', 'def'); 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz 'infinity 01:01:01'; 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity 01:01:01'; 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "now epoch" at character 20 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz 'now epoch'; 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20 2025-11-17 08:40:49.324 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity infinity'; 2025-11-17 08:40:49.325 UTC client backend[22478] pg_regress/unicode LOG: disconnection: session time: 0:00:00.072 user=postgres database=regression host=[local] 2025-11-17 08:40:49.328 UTC client backend[22477] pg_regress/xid ERROR: operator does not exist: xid <= xid at character 17 2025-11-17 08:40:49.328 UTC client backend[22477] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.328 UTC client backend[22477] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.328 UTC client backend[22477] pg_regress/xid STATEMENT: select '1'::xid <= '2'::xid; 2025-11-17 08:40:49.329 UTC client backend[22477] pg_regress/xid ERROR: operator does not exist: xid > xid at character 17 2025-11-17 08:40:49.329 UTC client backend[22477] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.329 UTC client backend[22477] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.329 UTC client backend[22477] pg_regress/xid STATEMENT: select '1'::xid > '2'::xid; 2025-11-17 08:40:49.332 UTC client backend[22477] pg_regress/xid ERROR: operator does not exist: xid >= xid at character 17 2025-11-17 08:40:49.332 UTC client backend[22477] pg_regress/xid DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.332 UTC client backend[22477] pg_regress/xid HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.332 UTC client backend[22477] pg_regress/xid STATEMENT: select '1'::xid >= '2'::xid; 2025-11-17 08:40:49.344 UTC client backend[22463] pg_regress/horology ERROR: operator does not exist: date - time with time zone at character 26 2025-11-17 08:40:49.344 UTC client backend[22463] pg_regress/horology DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.344 UTC client backend[22463] pg_regress/horology HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.344 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC"; 2025-11-17 08:40:49.349 UTC client backend[22463] pg_regress/horology ERROR: timestamp out of range 2025-11-17 08:40:49.349 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-11-17 08:40:49.350 UTC client backend[22463] pg_regress/horology ERROR: timestamp out of range 2025-11-17 08:40:49.350 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp without time zone '294276-12-31 23:59:59' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-11-17 08:40:49.376 UTC client backend[22463] pg_regress/horology ERROR: timestamp out of range 2025-11-17 08:40:49.376 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-11-17 08:40:49.378 UTC client backend[22463] pg_regress/horology ERROR: timestamp out of range 2025-11-17 08:40:49.378 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT timestamp with time zone '294276-12-31 23:59:59 UTC' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-11-17 08:40:49.400 UTC client backend[22468] pg_regress/misc_sanity LOG: disconnection: session time: 0:00:00.190 user=postgres database=regression host=[local] 2025-11-17 08:40:49.402 UTC client backend[22463] pg_regress/horology ERROR: cannot cast type time with time zone to interval at character 8 2025-11-17 08:40:49.402 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01"; 2025-11-17 08:40:49.403 UTC client backend[22463] pg_regress/horology ERROR: cannot cast type interval to time with time zone at character 8 2025-11-17 08:40:49.403 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08"; 2025-11-17 08:40:49.448 UTC client backend[22479] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-17 08:40:49.448 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'relname', 'test', 'relpages', 17::integer); 2025-11-17 08:40:49.448 UTC client backend[22479] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-17 08:40:49.448 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relpages', 17::integer); 2025-11-17 08:40:49.448 UTC client backend[22479] pg_regress/stats_import WARNING: argument "schemaname" has type double precision, expected type text 2025-11-17 08:40:49.449 UTC client backend[22464] pg_regress/geometry ERROR: operator does not exist: lseg # point at character 23 2025-11-17 08:40:49.449 UTC client backend[22464] pg_regress/geometry DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.449 UTC client backend[22464] pg_regress/geometry HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.449 UTC client backend[22464] pg_regress/geometry STATEMENT: SELECT p.f1, l.s, l.s # p.f1 AS intersection FROM LSEG_TBL l, POINT_TBL p; 2025-11-17 08:40:49.456 UTC client backend[22479] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-17 08:40:49.456 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 3.6::float, 'relname', 'test', 'relpages', 17::integer); 2025-11-17 08:40:49.456 UTC client backend[22479] pg_regress/stats_import WARNING: argument "relname" has type oid, expected type text 2025-11-17 08:40:49.456 UTC client backend[22479] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-17 08:40:49.456 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 0::oid, 'relpages', 17::integer); 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'nope', 'relpages', 17::integer); 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import ERROR: variadic arguments must be name/value pairs 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import HINT: Provide an even number of variadic arguments that can be divided into pairs. 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', 'relallvisible'); 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import ERROR: name at variadic position 5 is null 2025-11-17 08:40:49.460 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', NULL, '17'::integer); 2025-11-17 08:40:49.474 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-11-17 08:40:49.474 UTC client backend[22477] pg_regress/xid STATEMENT: select '31:12:'::pg_snapshot; 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid STATEMENT: select '0:1:'::pg_snapshot; 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid STATEMENT: select '12:13:0'::pg_snapshot; 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-11-17 08:40:49.475 UTC client backend[22477] pg_regress/xid STATEMENT: select '12:16:14,13'::pg_snapshot; 2025-11-17 08:40:49.522 UTC checkpointer[21525] LOG: checkpoint starting: fast force wait flush-unlogged 2025-11-17 08:40:49.525 UTC client backend[22465] pg_regress/tstypes ERROR: lexeme array may not contain nulls 2025-11-17 08:40:49.525 UTC client backend[22465] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]); 2025-11-17 08:40:49.526 UTC client backend[22465] pg_regress/tstypes ERROR: lexeme array may not contain empty strings 2025-11-17 08:40:49.526 UTC client backend[22465] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']); 2025-11-17 08:40:49.543 UTC client backend[22465] pg_regress/tstypes ERROR: weight array may not contain nulls 2025-11-17 08:40:49.543 UTC client backend[22465] pg_regress/tstypes STATEMENT: SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}'); 2025-11-17 08:40:49.546 UTC client backend[22465] pg_regress/tstypes LOG: disconnection: session time: 0:00:00.338 user=postgres database=regression host=[local] 2025-11-17 08:40:49.552 UTC client backend[22477] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20 2025-11-17 08:40:49.552 UTC client backend[22477] pg_regress/xid STATEMENT: SELECT pg_snapshot '1:9223372036854775808:3'; 2025-11-17 08:40:49.577 UTC client backend[22464] pg_regress/geometry ERROR: open path cannot be converted to polygon 2025-11-17 08:40:49.577 UTC client backend[22464] pg_regress/geometry STATEMENT: SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1); 2025-11-17 08:40:49.598 UTC client backend[22477] pg_regress/xid LOG: disconnection: session time: 0:00:00.353 user=postgres database=regression host=[local] 2025-11-17 08:40:49.598 UTC client backend[22479] pg_regress/stats_import WARNING: argument "relpages" has type text, expected type integer 2025-11-17 08:40:49.616 UTC client backend[22479] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'testseq'); 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-11-17 08:40:49.618 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testseq'); 2025-11-17 08:40:49.624 UTC client backend[22464] pg_regress/geometry ERROR: division by zero 2025-11-17 08:40:49.624 UTC client backend[22464] 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; 2025-11-17 08:40:49.626 UTC client backend[22479] pg_regress/stats_import ERROR: cannot modify statistics for relation "testview" 2025-11-17 08:40:49.626 UTC client backend[22479] pg_regress/stats_import DETAIL: This operation is not supported for views. 2025-11-17 08:40:49.626 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testview'); 2025-11-17 08:40:49.637 UTC client backend[22476] pg_regress/expressions ERROR: operator does not exist: point = box at character 23 2025-11-17 08:40:49.637 UTC client backend[22476] pg_regress/expressions DETAIL: No operator of that name accepts the given argument types. 2025-11-17 08:40:49.637 UTC client backend[22476] pg_regress/expressions HINT: You might need to add explicit type casts. 2025-11-17 08:40:49.637 UTC client backend[22476] pg_regress/expressions STATEMENT: select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0)); 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import ERROR: argument "schemaname" must not be null 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'relname', 'test', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import ERROR: schema "nope" does not exist 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'nope', 'relname', 'test', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-17 08:40:49.648 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'nope', 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import ERROR: argument "relname" must not be null 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', NULL, 'attname', 'id', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import ERROR: must specify either "attname" or "attnum" 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', NULL, 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import ERROR: column "nope" of relation "test" does not exist 2025-11-17 08:40:49.649 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'nope', 'inherited', false::boolean, 'null_frac', 0.1::real, 'avg_width', 2::integer, 'n_distinct', 0.3::real); 2025-11-17 08:40:49.650 UTC client backend[22479] pg_regress/stats_import ERROR: cannot specify both "attname" and "attnum" 2025-11-17 08:40:49.650 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'id', 'attnum', 1::smallint, 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.650 UTC client backend[22479] pg_regress/stats_import ERROR: must specify either "attname" or "attnum" 2025-11-17 08:40:49.650 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.656 UTC client backend[22479] pg_regress/stats_import ERROR: cannot modify statistics on system column "xmin" 2025-11-17 08:40:49.656 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'xmin', 'inherited', false::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.656 UTC client backend[22479] pg_regress/stats_import ERROR: argument "inherited" must not be null 2025-11-17 08:40:49.656 UTC client backend[22479] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_attribute_stats( 'schemaname', 'stats_import', 'relname', 'test', 'attname', 'id', 'inherited', NULL::boolean, 'null_frac', 0.1::real); 2025-11-17 08:40:49.743 UTC client backend[22479] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-11-17 08:40:49.752 UTC client backend[22476] pg_regress/expressions LOG: disconnection: session time: 0:00:00.519 user=postgres database=regression host=[local] 2025-11-17 08:40:49.758 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_vals" must be specified when argument "most_common_freqs" is specified 2025-11-17 08:40:49.772 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_freqs" must be specified when argument "most_common_vals" is specified 2025-11-17 08:40:49.776 UTC checkpointer[21525] LOG: checkpoint complete: wrote 3945 buffers (24.1%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 2 recycled; write=0.242 s, sync=0.001 s, total=0.255 s; sync files=0, longest=0.000 s, average=0.000 s; distance=29256 kB, estimate=29256 kB; lsn=0/03599260, redo lsn=0/03438CB8 2025-11-17 08:40:49.782 UTC client backend[22480] pg_regress/mvcc LOG: disconnection: session time: 0:00:00.513 user=postgres database=regression host=[local] 2025-11-17 08:40:49.788 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_freqs" has type double precision[], expected type real[] 2025-11-17 08:40:49.788 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_freqs" must be specified when argument "most_common_vals" is specified 2025-11-17 08:40:49.804 UTC client backend[22479] pg_regress/stats_import WARNING: invalid input syntax for type integer: "four" 2025-11-17 08:40:49.835 UTC client backend[22479] pg_regress/stats_import WARNING: "histogram_bounds" array must not contain null values 2025-11-17 08:40:49.849 UTC client backend[22464] pg_regress/geometry ERROR: must request at least 2 points 2025-11-17 08:40:49.849 UTC client backend[22464] pg_regress/geometry STATEMENT: SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>'; 2025-11-17 08:40:49.852 UTC client backend[22464] pg_regress/geometry ERROR: cannot convert circle with radius zero to polygon 2025-11-17 08:40:49.852 UTC client backend[22464] pg_regress/geometry STATEMENT: SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>'; 2025-11-17 08:40:49.864 UTC client backend[22479] pg_regress/stats_import WARNING: argument "elem_count_histogram" array must not contain null values 2025-11-17 08:40:49.901 UTC client backend[22479] pg_regress/stats_import WARNING: column "id" is not a range type 2025-11-17 08:40:49.901 UTC client backend[22479] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-11-17 08:40:49.916 UTC client backend[22479] pg_regress/stats_import WARNING: argument "range_empty_frac" must be specified when argument "range_length_histogram" is specified 2025-11-17 08:40:49.931 UTC client backend[22464] pg_regress/geometry ERROR: value out of range: overflow 2025-11-17 08:40:49.931 UTC client backend[22464] 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; 2025-11-17 08:40:49.931 UTC client backend[22464] pg_regress/geometry ERROR: division by zero 2025-11-17 08:40:49.931 UTC client backend[22464] 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; 2025-11-17 08:40:49.940 UTC client backend[22479] pg_regress/stats_import WARNING: argument "range_length_histogram" must be specified when argument "range_empty_frac" is specified 2025-11-17 08:40:49.968 UTC client backend[22479] pg_regress/stats_import WARNING: column "id" is not a range type 2025-11-17 08:40:49.968 UTC client backend[22479] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-11-17 08:40:49.976 UTC client backend[22464] pg_regress/geometry LOG: disconnection: session time: 0:00:00.780 user=postgres database=regression host=[local] 2025-11-17 08:40:50.008 UTC client backend[22479] pg_regress/stats_import WARNING: could not determine element type of column "arange" 2025-11-17 08:40:50.008 UTC client backend[22479] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-17 08:40:50.022 UTC client backend[22479] pg_regress/stats_import WARNING: could not determine element type of column "id" 2025-11-17 08:40:50.022 UTC client backend[22479] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-17 08:40:50.036 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_elem_freqs" must be specified when argument "most_common_elems" is specified 2025-11-17 08:40:50.060 UTC client backend[22479] pg_regress/stats_import WARNING: argument "most_common_elems" must be specified when argument "most_common_elem_freqs" is specified 2025-11-17 08:40:50.092 UTC client backend[22479] pg_regress/stats_import WARNING: could not determine element type of column "id" 2025-11-17 08:40:50.092 UTC client backend[22479] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-11-17 08:40:50.283 UTC client backend[22473] pg_regress/type_sanity LOG: disconnection: session time: 0:00:01.060 user=postgres database=regression host=[local] 2025-11-17 08:40:50.360 UTC checkpointer[21525] LOG: checkpoint starting: fast force wait 2025-11-17 08:40:50.362 UTC checkpointer[21525] LOG: checkpoint complete: wrote 122 buffers (0.7%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.003 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1561 kB, estimate=26486 kB; lsn=0/035C2268, redo lsn=0/035BF400 2025-11-17 08:40:50.384 UTC checkpointer[21525] LOG: checkpoint starting: fast force wait flush-unlogged 2025-11-17 08:40:50.385 UTC checkpointer[21525] LOG: checkpoint complete: wrote 18 buffers (0.1%), wrote 1 SLRU buffers; 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=92 kB, estimate=23847 kB; lsn=0/035D6900, redo lsn=0/035D67B8 2025-11-17 08:40:50.398 UTC client backend[22479] pg_regress/stats_import LOG: disconnection: session time: 0:00:01.131 user=postgres database=regression host=[local] 2025-11-17 08:40:50.517 UTC checkpointer[21525] LOG: checkpoint starting: fast force wait 2025-11-17 08:40:50.518 UTC checkpointer[21525] LOG: checkpoint complete: wrote 10 buffers (0.1%), wrote 1 SLRU buffers; 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=62 kB, estimate=21469 kB; lsn=0/035E6328, redo lsn=0/035E62D0 2025-11-17 08:40:50.575 UTC client backend[22469] pg_regress/regex ERROR: invalid regular expression: regular expression is too complex 2025-11-17 08:40:50.575 UTC client backend[22469] pg_regress/regex STATEMENT: select 'x' ~ repeat('x*y*z*', 1000); 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=\1)'; 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=(\1))'; 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex ERROR: invalid regular expression: invalid escape \ sequence 2025-11-17 08:40:50.639 UTC client backend[22469] pg_regress/regex STATEMENT: select 'a' ~ '\x7fffffff'; 2025-11-17 08:40:50.642 UTC client backend[22469] pg_regress/regex LOG: disconnection: session time: 0:00:01.425 user=postgres database=regression host=[local] 2025-11-17 08:40:50.679 UTC client backend[22463] pg_regress/horology ERROR: date out of range for timestamp 2025-11-17 08:40:50.679 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamp; 2025-11-17 08:40:50.684 UTC client backend[22463] pg_regress/horology ERROR: date out of range for timestamp 2025-11-17 08:40:50.684 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamptz; 2025-11-17 08:40:50.685 UTC client backend[22463] pg_regress/horology ERROR: date out of range for timestamp 2025-11-17 08:40:50.685 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT '4714-11-24 BC'::date::timestamptz; 2025-11-17 08:40:50.702 UTC client backend[22463] pg_regress/horology ERROR: invalid value "/Feb/16" for "Mon" 2025-11-17 08:40:50.702 UTC client backend[22463] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-11-17 08:40:50.702 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('97/Feb/16', 'YYMonDD'); 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology ERROR: invalid value "JUNK" for "TZ" 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology DETAIL: Time zone abbreviation is not recognized. 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ'); 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology ERROR: invalid value ".." for "TZ" 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ'); 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.711 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-11-17 08:40:50.712 UTC client backend[22463] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-11-17 08:40:50.712 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.712 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-11-17 08:40:50.716 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2018-11-02 12:34:56.123456789" 2025-11-17 08:40:50.716 UTC client backend[22463] 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; 2025-11-17 08:40:50.723 UTC client backend[22463] pg_regress/horology ERROR: invalid value "+" for "MON" 2025-11-17 08:40:50.723 UTC client backend[22463] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-11-17 08:40:50.723 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2000 + + JUN', 'YYYY MON'); 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology ERROR: invalid value "x1" for "MM" 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2011 x12 x18', 'YYYYxMMxDD'); 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology ERROR: invalid combination of date conventions 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology HINT: Do not mix Gregorian and ISO week date conventions in a formatting template. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2005527', 'YYYYIWID'); 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology ERROR: source string too short for "MM" formatting field 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 remain. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('19971', 'YYYYMMDD'); 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology ERROR: invalid value "1)" for "MM" 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 could be parsed. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-11-17 08:40:50.732 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('19971)24', 'YYYYMMDD'); 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology ERROR: invalid value "da" for "DD" 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY'); 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology ERROR: invalid value "uary" for "YYYY" 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY'); 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology ERROR: conflicting values for "Mon" field in formatting string 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology DETAIL: This value contradicts a previous setting for the same field type. 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD'); 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology ERROR: invalid value "xy" for "DD" 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology DETAIL: Value must be an integer. 2025-11-17 08:40:50.733 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('199711xy', 'YYYYMMDD'); 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology ERROR: value for "YYYY" in source string is out of range 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology DETAIL: Value must be in the range -2147483648 to 2147483647. 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('10000000000', 'FMYYYY'); 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 25:00:00" 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:60:00" 2025-11-17 08:40:50.734 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.737 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:50:60" 2025-11-17 08:40:50.737 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology ERROR: hour "15" is invalid for the 12-hour clock 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology HINT: Use the 24-hour clock, or give an hour between 1 and 12. 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS'); 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-13-01 15:50:55" 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30 15:50:55" 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29 15:50:55" 2025-11-17 08:40:50.738 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-11-17 08:40:50.739 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-11-17 08:40:50.739 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS'); 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS'); 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology ERROR: value for "Y,YYY" in source string is out of range 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('1000000000,999', 'Y,YYY'); 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "0.-2147483648" 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('0.-2147483648', 'SS.MS'); 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "613566758" 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('613566758', 'W'); 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2024 613566758 1" 2025-11-17 08:40:50.748 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_timestamp('2024 613566758 1', 'YYYY WW D'); 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-13-10" 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2016-13-10', 'YYYY-MM-DD'); 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30" 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2016-02-30', 'YYYY-MM-DD'); 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29" 2025-11-17 08:40:50.749 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2015-02-29', 'YYYY-MM-DD'); 2025-11-17 08:40:50.750 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2015 366" 2025-11-17 08:40:50.750 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2015 366', 'YYYY DDD'); 2025-11-17 08:40:50.758 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2016 367" 2025-11-17 08:40:50.758 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2016 367', 'YYYY DDD'); 2025-11-17 08:40:50.758 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "100000000" 2025-11-17 08:40:50.758 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('100000000', 'CC'); 2025-11-17 08:40:50.759 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "-100000000" 2025-11-17 08:40:50.759 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('-100000000', 'CC'); 2025-11-17 08:40:50.760 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "-2147483648 01" 2025-11-17 08:40:50.760 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('-2147483648 01', 'CC YY'); 2025-11-17 08:40:50.760 UTC client backend[22463] pg_regress/horology ERROR: date/time field value out of range: "2147483647 01" 2025-11-17 08:40:50.760 UTC client backend[22463] pg_regress/horology STATEMENT: SELECT to_date('2147483647 01', 'CC YY'); 2025-11-17 08:40:50.767 UTC client backend[22463] pg_regress/horology LOG: disconnection: session time: 0:00:01.573 user=postgres database=regression host=[local] 2025-11-17 08:40:50.932 UTC checkpointer[21525] LOG: checkpoint starting: fast force wait 2025-11-17 08:40:50.933 UTC checkpointer[21525] LOG: checkpoint complete: wrote 41 buffers (0.3%), wrote 1 SLRU buffers; 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=247 kB, estimate=19346 kB; lsn=0/03623FC8, redo lsn=0/03623F70 2025-11-17 08:40:50.995 UTC client backend[22481] pg_regress/database LOG: disconnection: session time: 0:00:01.726 user=postgres database=regression host=[local] 2025-11-17 08:40:52.043 UTC client backend[22475] pg_regress/opr_sanity LOG: disconnection: session time: 0:00:02.815 user=postgres database=regression host=[local] 2025-11-17 08:40:52.157 UTC unrecognized[22818] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.160 UTC unrecognized[22817] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.160 UTC unrecognized[22819] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.161 UTC client backend[22817] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.161 UTC client backend[22817] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copydml 2025-11-17 08:40:52.162 UTC client backend[22819] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.162 UTC client backend[22819] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copy 2025-11-17 08:40:52.165 UTC client backend[22818] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.165 UTC client backend[22818] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyencoding 2025-11-17 08:40:52.168 UTC unrecognized[22820] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.169 UTC client backend[22820] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.169 UTC client backend[22820] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert 2025-11-17 08:40:52.174 UTC client backend[22817] pg_regress/copydml LOG: connection ready: setup total=20.716 ms, fork=2.331 ms, authentication=0.377 ms 2025-11-17 08:40:52.174 UTC client backend[22818] pg_regress/copyencoding LOG: connection ready: setup total=19.758 ms, fork=1.192 ms, authentication=6.658 ms 2025-11-17 08:40:52.180 UTC unrecognized[22821] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.182 UTC client backend[22821] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.182 UTC client backend[22821] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyselect 2025-11-17 08:40:52.182 UTC client backend[22820] pg_regress/insert LOG: connection ready: setup total=18.295 ms, fork=4.207 ms, authentication=0.326 ms 2025-11-17 08:40:52.184 UTC unrecognized[22822] [unknown] LOG: connection received: host=[local] 2025-11-17 08:40:52.185 UTC client backend[22822] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-11-17 08:40:52.185 UTC client backend[22822] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert_conflict 2025-11-17 08:40:52.189 UTC client backend[22819] pg_regress/copy LOG: connection ready: setup total=32.748 ms, fork=3.845 ms, authentication=0.386 ms 2025-11-17 08:40:52.194 UTC client backend[22821] pg_regress/copyselect LOG: connection ready: setup total=22.103 ms, fork=2.519 ms, authentication=0.391 ms 2025-11-17 08:40:52.200 UTC client backend[22822] pg_regress/insert_conflict LOG: connection ready: setup total=27.529 ms, fork=1.778 ms, authentication=0.344 ms 2025-11-17 08:40:52.204 UTC client backend[22818] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-11-17 08:40:52.204 UTC client backend[22818] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-11-17 08:40:52.204 UTC client backend[22818] pg_regress/copyencoding STATEMENT: COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/src/test/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv, ENCODING 'EUC_JP'); 2025-11-17 08:40:52.205 UTC client backend[22818] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-11-17 08:40:52.205 UTC client backend[22818] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-11-17 08:40:52.205 UTC client backend[22818] pg_regress/copyencoding STATEMENT: COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/src/test/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv); 2025-11-17 08:40:52.212 UTC client backend[22820] pg_regress/insert ERROR: null value in column "col2" of relation "inserttest" violates not-null constraint 2025-11-17 08:40:52.212 UTC client backend[22820] pg_regress/insert DETAIL: Failing row contains (null, null, testing). 2025-11-17 08:40:52.212 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT); 2025-11-17 08:40:52.218 UTC client backend[22820] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-11-17 08:40:52.218 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT); 2025-11-17 08:40:52.218 UTC client backend[22820] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-11-17 08:40:52.218 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (1, 2); 2025-11-17 08:40:52.219 UTC client backend[22820] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 42 2025-11-17 08:40:52.219 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (col1) values (1, 2); 2025-11-17 08:40:52.219 UTC client backend[22820] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 48 2025-11-17 08:40:52.219 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (col1) values (DEFAULT, DEFAULT); 2025-11-17 08:40:52.227 UTC client backend[22818] pg_regress/copyencoding LOG: disconnection: session time: 0:00:00.071 user=postgres database=regression host=[local] 2025-11-17 08:40:52.258 UTC client backend[22817] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-17 08:40:52.258 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.260 UTC client backend[22817] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-17 08:40:52.260 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'g') to stdout; 2025-11-17 08:40:52.260 UTC client backend[22817] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-11-17 08:40:52.260 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-17 08:40:52.261 UTC client backend[22817] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-17 08:40:52.261 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.267 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.267 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing; 2025-11-17 08:40:52.267 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.267 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing; 2025-11-17 08:40:52.277 UTC client backend[22817] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-17 08:40:52.277 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.280 UTC client backend[22820] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 32 2025-11-17 08:40:52.280 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (f2[1], f2[2]) values (1,default); 2025-11-17 08:40:52.286 UTC client backend[22820] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 33 2025-11-17 08:40:52.286 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttest (f3.if1, f3.if2) values (1,default); 2025-11-17 08:40:52.292 UTC client backend[22821] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-11-17 08:40:52.292 UTC client backend[22821] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-11-17 08:40:52.292 UTC client backend[22821] pg_regress/copyselect STATEMENT: copy v_test1 to stdout; 2025-11-17 08:40:52.293 UTC client backend[22821] pg_regress/copyselect ERROR: COPY (SELECT INTO) is not supported 2025-11-17 08:40:52.293 UTC client backend[22821] pg_regress/copyselect STATEMENT: copy (select t into temp test3 from test1 where id=3) to stdout; 2025-11-17 08:40:52.294 UTC client backend[22821] pg_regress/copyselect ERROR: syntax error at or near "from" at character 28 2025-11-17 08:40:52.294 UTC client backend[22821] pg_regress/copyselect STATEMENT: copy (select * from test1) from stdin; 2025-11-17 08:40:52.294 UTC client backend[22821] pg_regress/copyselect ERROR: syntax error at or near "(" at character 28 2025-11-17 08:40:52.294 UTC client backend[22821] pg_regress/copyselect STATEMENT: copy (select * from test1) (t,id) to stdout; 2025-11-17 08:40:52.295 UTC client backend[22817] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.295 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.298 UTC client backend[22817] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.298 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-11-17 08:40:52.301 UTC client backend[22819] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-11-17 08:40:52.305 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.305 UTC client backend[22822] 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; 2025-11-17 08:40:52.308 UTC client backend[22817] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-17 08:40:52.308 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-17 08:40:52.313 UTC client backend[22817] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-17 08:40:52.313 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-17 08:40:52.315 UTC client backend[22817] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.315 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-17 08:40:52.320 UTC client backend[22817] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.320 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-11-17 08:40:52.320 UTC client backend[22821] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-11-17 08:40:52.320 UTC client backend[22821] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-11-17 08:40:52.320 UTC client backend[22821] pg_regress/copyselect STATEMENT: COPY v_test1 TO STDOUT 2025-11-17 08:40:52.320 UTC client backend[22822] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52 2025-11-17 08:40:52.320 UTC client backend[22822] pg_regress/insert_conflict HINT: For example, ON CONFLICT (column_name). 2025-11-17 08:40:52.320 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit; 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "excluded" at character 117 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict DETAIL: There is an entry for table "excluded", but it cannot be referenced from this part of the query. 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit; 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict ERROR: column "keyy" does not exist at character 64 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key". 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict ERROR: column excluded.fruitt does not exist at character 92 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "excluded.fruit". 2025-11-17 08:40:52.322 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt; 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.323 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.324 UTC client backend[22817] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-11-17 08:40:52.324 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "insertconflicttest" at character 106 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict HINT: Perhaps you meant to reference the table alias "ict". 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit; 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict ERROR: column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict HINT: SET target columns cannot be qualified with the relation name. 2025-11-17 08:40:52.324 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango'; 2025-11-17 08:40:52.328 UTC client backend[22817] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-11-17 08:40:52.328 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.332 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.333 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.333 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.334 UTC client backend[22817] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.334 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-17 08:40:52.342 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.342 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.342 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.342 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.343 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.343 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.345 UTC client backend[22817] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-11-17 08:40:52.345 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-11-17 08:40:52.346 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.346 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.346 UTC client backend[22817] pg_regress/copydml ERROR: COPY query must not be a utility command 2025-11-17 08:40:52.346 UTC client backend[22817] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-11-17 08:40:52.346 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.346 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.347 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.347 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.360 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.360 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.368 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.368 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.376 UTC client backend[22821] pg_regress/copyselect ERROR: division by zero 2025-11-17 08:40:52.376 UTC client backend[22821] pg_regress/copyselect STATEMENT: copy (select 1) to stdout; select 1/0; 2025-11-17 08:40:52.377 UTC client backend[22821] pg_regress/copyselect ERROR: division by zero 2025-11-17 08:40:52.377 UTC client backend[22821] pg_regress/copyselect STATEMENT: select 1/0; copy (select 1) to stdout; 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.380 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.400 UTC client backend[22821] pg_regress/copyselect LOG: disconnection: session time: 0:00:00.225 user=postgres database=regression host=[local] 2025-11-17 08:40:52.400 UTC client backend[22822] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "fruit_index" 2025-11-17 08:40:52.400 UTC client backend[22822] pg_regress/insert_conflict DETAIL: Key (fruit)=(Peach) already exists. 2025-11-17 08:40:52.400 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.413 UTC client backend[22817] pg_regress/copydml LOG: disconnection: session time: 0:00:00.257 user=postgres database=regression host=[local] 2025-11-17 08:40:52.420 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.420 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit; 2025-11-17 08:40:52.420 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.420 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing; 2025-11-17 08:40:52.423 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.423 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) where fruit like '%berry' do update set fruit = excluded.fruit; 2025-11-17 08:40:52.443 UTC client backend[22819] pg_regress/copy ERROR: cannot perform COPY FREEZE on a partitioned table 2025-11-17 08:40:52.443 UTC client backend[22819] pg_regress/copy STATEMENT: copy parted_copytest from '/tmp/cirrus-ci-build/src/test/regress/results/parted_copytest.csv' (freeze); 2025-11-17 08:40:52.460 UTC client backend[22822] pg_regress/insert_conflict ERROR: column excluded.ctid does not exist at character 82 2025-11-17 08:40:52.460 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text; 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 33 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (1,default); 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (0,2); 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-17 08:40:52.481 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6); 2025-11-17 08:40:52.482 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-11-17 08:40:52.482 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) select 0,8; 2025-11-17 08:40:52.486 UTC client backend[22820] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 34 2025-11-17 08:40:52.486 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,default); 2025-11-17 08:40:52.487 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-17 08:40:52.487 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,array[null]); 2025-11-17 08:40:52.487 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-17 08:40:52.487 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}'); 2025-11-17 08:40:52.493 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-17 08:40:52.493 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}'; 2025-11-17 08:40:52.628 UTC client backend[22819] pg_regress/copy ERROR: cannot use "match" with HEADER in COPY TO 2025-11-17 08:40:52.628 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest to stdout with (header match); 2025-11-17 08:40:52.628 UTC client backend[22819] pg_regress/copy ERROR: header requires a Boolean value, a non-negative integer, or the string "match" 2025-11-17 08:40:52.628 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header wrong_choice); 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy ERROR: column name mismatch in header line field 1: got "a", expected "c" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest (c, b, a) from stdin with (header match); 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy ERROR: column name mismatch in header line field 3: got null value ("\N"), expected "c" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b \N" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy ERROR: wrong number of fields in header line: got 2, expected 3 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy ERROR: wrong number of fields in header line: got 4, expected 3 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c d" 2025-11-17 08:40:52.630 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-17 08:40:52.631 UTC client backend[22819] pg_regress/copy ERROR: column name mismatch in header line field 3: got "d", expected "c" 2025-11-17 08:40:52.631 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b d" 2025-11-17 08:40:52.631 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a ........pg.dropped.2........ c" 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a c b" 2025-11-17 08:40:52.633 UTC client backend[22819] pg_regress/copy STATEMENT: copy header_copytest (a, c) from stdin with (header match); 2025-11-17 08:40:52.637 UTC client backend[22822] pg_regress/insert_conflict ERROR: table reference "excluded" is ambiguous at character 76 2025-11-17 08:40:52.637 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *; 2025-11-17 08:40:52.638 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_nnarray violates check constraint "insert_nnarray_check" 2025-11-17 08:40:52.638 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttesta (f1[1]) values (1); 2025-11-17 08:40:52.639 UTC client backend[22819] pg_regress/copy ERROR: value too long for type character varying(5) 2025-11-17 08:40:52.639 UTC client backend[22819] pg_regress/copy STATEMENT: copy oversized_column_default (col2) from stdin; 2025-11-17 08:40:52.640 UTC client backend[22819] pg_regress/copy ERROR: value too long for type character varying(5) 2025-11-17 08:40:52.640 UTC client backend[22819] pg_regress/copy STATEMENT: copy oversized_column_default from stdin (default ''); 2025-11-17 08:40:52.650 UTC client backend[22820] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-11-17 08:40:52.650 UTC client backend[22820] pg_regress/insert STATEMENT: insert into inserttestb (f1.if1) values (1); TRAP: failed Assert("false"), File: "../../../../src/include/varatt.h", Line: 112, PID: 22820 /lib/x86_64-linux-gnu/libasan.so.8(+0x7e403) [0x7f644327e403] postgres: postgres regression [local] CREATE TABLE(ExceptionalCondition+0xe6) [0x55a6fa68ff06] postgres: postgres regression [local] CREATE TABLE(+0x468cea) [0x55a6f98fecea] postgres: postgres regression [local] CREATE TABLE(+0x468d59) [0x55a6f98fed59] postgres: postgres regression [local] CREATE TABLE(heap_compute_data_size+0x36d) [0x55a6f990126f] postgres: postgres regression [local] CREATE TABLE(heap_form_tuple+0x11a) [0x55a6f9902df1] postgres: postgres regression [local] CREATE TABLE(StorePartitionKey+0x35e) [0x55a6f9b3c968] postgres: postgres regression [local] CREATE TABLE(DefineRelation+0x19cc) [0x55a6f9d78423] postgres: postgres regression [local] CREATE TABLE(+0xee7c53) [0x55a6fa37dc53] postgres: postgres regression [local] CREATE TABLE(standard_ProcessUtility+0x11af) [0x55a6fa37d590] postgres: postgres regression [local] CREATE TABLE(ProcessUtility+0x15b) [0x55a6fa37d762] postgres: postgres regression [local] CREATE TABLE(+0xee267a) [0x55a6fa37867a] postgres: postgres regression [local] CREATE TABLE(+0xee2b90) [0x55a6fa378b90] postgres: postgres regression [local] CREATE TABLE(PortalRun+0x3bd) [0x55a6fa379610] postgres: postgres regression [local] CREATE TABLE(+0xeda8b1) [0x55a6fa3708b1] postgres: postgres regression [local] CREATE TABLE(PostgresMain+0x1419) [0x55a6fa374f7e] postgres: postgres regression [local] CREATE TABLE(BackendMain+0x11b) [0x55a6fa36657f] postgres: postgres regression [local] CREATE TABLE(postmaster_child_launch+0x23e) [0x55a6fa1a13a5] postgres: postgres regression [local] CREATE TABLE(+0xd11442) [0x55a6fa1a7442] postgres: postgres regression [local] CREATE TABLE(+0xd144cb) [0x55a6fa1aa4cb] postgres: postgres regression [local] CREATE TABLE(PostmasterMain+0x1d4c) [0x55a6fa1ac715] postgres: postgres regression [local] CREATE TABLE(main+0x2a8) [0x55a6f9f2ccbd] /lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7f6441c33ca8] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f6441c33d65] postgres: postgres regression [local] CREATE TABLE(_start+0x21) [0x55a6f98da461] 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "twoconstraints_f1_key" 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict DETAIL: Key (f1)=(1) already exists. 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(1, '((2,2),(3,3))'); 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-11-17 08:40:52.713 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))'); 2025-11-17 08:40:52.714 UTC client backend[22822] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-11-17 08:40:52.714 UTC client backend[22822] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-11-17 08:40:52.714 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))') on conflict on constraint twoconstraints_f1_key do nothing; 2025-11-17 08:40:52.752 UTC client backend[22822] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-17 08:40:52.752 UTC client backend[22822] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-17 08:40:52.752 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0; 2025-11-17 08:40:52.760 UTC client backend[22822] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-17 08:40:52.760 UTC client backend[22822] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-17 08:40:52.760 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0; 2025-11-17 08:40:52.761 UTC client backend[22822] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-11-17 08:40:52.761 UTC client backend[22822] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-11-17 08:40:52.761 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0; 2025-11-17 08:40:52.797 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:52.797 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a; 2025-11-17 08:40:52.852 UTC client backend[22819] pg_regress/copy ERROR: cannot perform COPY FREEZE on a foreign table 2025-11-17 08:40:52.852 UTC client backend[22819] pg_regress/copy STATEMENT: copy copytest_foreign_table from stdin (freeze); 2025-11-17 08:40:52.860 UTC client backend[22819] pg_regress/copy ERROR: cannot copy from unpopulated materialized view "copytest_mv" 2025-11-17 08:40:52.860 UTC client backend[22819] pg_regress/copy HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-11-17 08:40:52.860 UTC client backend[22819] pg_regress/copy STATEMENT: COPY copytest_mv(id) TO stdout WITH (header); 2025-11-17 08:40:52.973 UTC client backend[22819] pg_regress/copy LOG: disconnection: session time: 0:00:00.812 user=postgres database=regression host=[local] 2025-11-17 08:40:53.090 UTC client backend[22822] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-11-17 08:40:53.090 UTC client backend[22822] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_1 values (40, 'cuarenta') on conflict (a) do update set b = excluded.b; 2025-11-17 08:40:53.176 UTC client backend[22822] pg_regress/insert_conflict LOG: disconnection: session time: 0:00:01.000 user=postgres database=regression host=[local] 2025-11-17 08:40:53.245 UTC postmaster[21503] LOG: client backend (PID 22820) was terminated by signal 6: Aborted 2025-11-17 08:40:53.245 UTC postmaster[21503] DETAIL: Failed process was running: create table range_parted ( a text, b int ) partition by range (a, (b+0)); 2025-11-17 08:40:53.245 UTC postmaster[21503] LOG: terminating any other active server processes 2025-11-17 08:40:53.277 UTC postmaster[21503] LOG: shutting down because "restart_after_crash" is off 2025-11-17 08:40:53.335 UTC postmaster[21503] LOG: database system is shut down