2025-07-03 22:04:56.532 UTC postmaster[14495] LOG: starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit 2025-07-03 22:04:56.532 UTC postmaster[14495] LOG: listening on Unix socket "/tmp/pg_regress-kfhHRd/.s.PGSQL.58928" 2025-07-03 22:04:56.556 UTC startup[14513] LOG: database system was shut down at 2025-07-03 22:04:56 UTC 2025-07-03 22:04:56.568 UTC postmaster[14495] LOG: database system is ready to accept connections 2025-07-03 22:04:56.573 UTC not initialized[14518] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:56.573 UTC client backend[14518] [unknown] FATAL: the database system is starting up 2025-07-03 22:04:56.637 UTC not initialized[14544] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:56.642 UTC client backend[14544] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:56.642 UTC client backend[14544] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-07-03 22:04:56.690 UTC client backend[14544] pg_regress LOG: connection ready: setup total=66.537 ms, fork=10.825 ms, authentication=3.741 ms 2025-07-03 22:04:56.690 UTC client backend[14544] pg_regress LOG: disconnection: session time: 0:00:00.055 user=postgres database=postgres host=[local] 2025-07-03 22:04:56.723 UTC not initialized[14570] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:56.725 UTC client backend[14570] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:56.725 UTC client backend[14570] [unknown] LOG: connection authorized: user=postgres database=postgres application_name=pg_regress 2025-07-03 22:04:56.728 UTC client backend[14570] pg_regress LOG: connection ready: setup total=14.212 ms, fork=9.403 ms, authentication=0.546 ms 2025-07-03 22:04:56.849 UTC client backend[14570] pg_regress LOG: disconnection: session time: 0:00:00.126 user=postgres database=postgres host=[local] 2025-07-03 22:04:56.913 UTC not initialized[14594] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:56.916 UTC client backend[14594] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:56.916 UTC client backend[14594] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/test_setup 2025-07-03 22:04:56.965 UTC client backend[14594] pg_regress/test_setup LOG: connection ready: setup total=61.551 ms, fork=8.481 ms, authentication=1.192 ms 2025-07-03 22:04:57.811 UTC client backend[14594] pg_regress/test_setup LOG: disconnection: session time: 0:00:00.899 user=postgres database=regression host=[local] 2025-07-03 22:04:57.922 UTC not initialized[14764] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.924 UTC client backend[14764] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.924 UTC client backend[14764] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/varchar 2025-07-03 22:04:57.931 UTC not initialized[14765] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.932 UTC client backend[14765] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.933 UTC client backend[14765] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int4 2025-07-03 22:04:57.937 UTC not initialized[14766] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.939 UTC client backend[14764] pg_regress/varchar LOG: connection ready: setup total=20.985 ms, fork=14.364 ms, authentication=0.437 ms 2025-07-03 22:04:57.940 UTC not initialized[14767] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.941 UTC client backend[14766] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.941 UTC client backend[14766] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/name 2025-07-03 22:04:57.948 UTC client backend[14767] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.948 UTC client backend[14767] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/uuid 2025-07-03 22:04:57.954 UTC client backend[14767] pg_regress/uuid LOG: connection ready: setup total=26.271 ms, fork=10.282 ms, authentication=6.831 ms 2025-07-03 22:04:57.958 UTC not initialized[14770] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.959 UTC not initialized[14769] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.959 UTC not initialized[14771] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.961 UTC client backend[14771] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.961 UTC client backend[14769] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.961 UTC client backend[14771] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/text 2025-07-03 22:04:57.961 UTC client backend[14769] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float8 2025-07-03 22:04:57.964 UTC client backend[14766] pg_regress/name LOG: connection ready: setup total=41.127 ms, fork=7.830 ms, authentication=3.142 ms 2025-07-03 22:04:57.964 UTC client backend[14770] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.964 UTC client backend[14770] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/float4 2025-07-03 22:04:57.964 UTC not initialized[14772] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.966 UTC client backend[14772] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.966 UTC client backend[14772] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/oid 2025-07-03 22:04:57.967 UTC client backend[14765] pg_regress/int4 LOG: connection ready: setup total=46.171 ms, fork=8.815 ms, authentication=0.399 ms 2025-07-03 22:04:57.968 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "34.5" at character 34 2025-07-03 22:04:57.968 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('34.5'); 2025-07-03 22:04:57.968 UTC client backend[14765] pg_regress/int4 ERROR: value "1000000000000" is out of range for type integer at character 34 2025-07-03 22:04:57.968 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('1000000000000'); 2025-07-03 22:04:57.971 UTC client backend[14770] pg_regress/float4 LOG: connection ready: setup total=36.379 ms, fork=21.604 ms, authentication=5.083 ms 2025-07-03 22:04:57.973 UTC client backend[14769] pg_regress/float8 LOG: connection ready: setup total=39.690 ms, fork=20.502 ms, authentication=0.437 ms 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "asdf" at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('asdf'); 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: " " at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' '); 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: " asdf " at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (' asdf '); 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "- 1234" at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('- 1234'); 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "123 5" at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES ('123 5'); 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "" at character 34 2025-07-03 22:04:57.973 UTC client backend[14765] pg_regress/int4 STATEMENT: INSERT INTO INT4_TBL(f1) VALUES (''); 2025-07-03 22:04:57.974 UTC not initialized[14773] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.979 UTC client backend[14773] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.979 UTC client backend[14773] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int8 2025-07-03 22:04:57.980 UTC not initialized[14776] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.981 UTC not initialized[14775] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.982 UTC client backend[14776] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.982 UTC client backend[14776] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/int2 2025-07-03 22:04:57.982 UTC client backend[14775] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.982 UTC client backend[14775] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/txid 2025-07-03 22:04:57.982 UTC client backend[14773] pg_regress/int8 LOG: connection ready: setup total=37.772 ms, fork=26.837 ms, authentication=3.942 ms 2025-07-03 22:04:57.984 UTC client backend[14764] pg_regress/varchar ERROR: value too long for type character varying(1) 2025-07-03 22:04:57.984 UTC client backend[14764] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('cd'); 2025-07-03 22:04:57.990 UTC client backend[14772] pg_regress/oid LOG: connection ready: setup total=50.770 ms, fork=19.718 ms, authentication=0.372 ms 2025-07-03 22:04:57.990 UTC client backend[14771] pg_regress/text LOG: connection ready: setup total=52.651 ms, fork=20.018 ms, authentication=0.398 ms 2025-07-03 22:04:57.991 UTC not initialized[14779] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:57.993 UTC client backend[14779] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:57.993 UTC client backend[14779] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/boolean 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: " " at character 34 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' '); 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "xxx" at character 34 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('xxx'); 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 ERROR: value "3908203590239580293850293850329485" is out of range for type bigint at character 34 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485'); 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 ERROR: value "-1204982019841029840928340329840934" is out of range for type bigint at character 34 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934'); 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "- 123" at character 34 2025-07-03 22:04:57.996 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES ('- 123'); 2025-07-03 22:04:57.997 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: " 345 5" at character 34 2025-07-03 22:04:57.997 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (' 345 5'); 2025-07-03 22:04:57.997 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "" at character 34 2025-07-03 22:04:57.997 UTC client backend[14773] pg_regress/int8 STATEMENT: INSERT INTO INT8_TBL(q1) VALUES (''); 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 ERROR: "10e70" is out of range for type real at character 36 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'); 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 ERROR: "-10e70" is out of range for type real at character 36 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'); 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 ERROR: "10e-70" is out of range for type real at character 36 2025-07-03 22:04:57.998 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'); 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 ERROR: "-10e-70" is out of range for type real at character 36 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'); 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 ERROR: value out of range: overflow 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8); 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 ERROR: value out of range: overflow 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8); 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 ERROR: value out of range: underflow 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8); 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 ERROR: value out of range: underflow 2025-07-03 22:04:57.999 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: "10e400" is out of range for type real at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400'); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: "-10e400" is out of range for type real at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400'); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: "10e-400" is out of range for type real at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400'); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: "-10e-400" is out of range for type real at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400'); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "" at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (''); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: " " at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' '); 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "xyz" at character 36 2025-07-03 22:04:58.000 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz'); 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "5.0.0" at character 36 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0'); 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "5 . 0" at character 36 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0'); 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "5. 0" at character 36 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('5. 0'); 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: " - 3.0" at character 36 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES (' - 3.0'); 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "123 5" at character 36 2025-07-03 22:04:58.001 UTC client backend[14770] pg_regress/float4 STATEMENT: INSERT INTO FLOAT4_TBL(f1) VALUES ('123 5'); 2025-07-03 22:04:58.003 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "N A N" at character 8 2025-07-03 22:04:58.003 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT 'N A N'::float4; 2025-07-03 22:04:58.003 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: "NaN x" at character 8 2025-07-03 22:04:58.003 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT 'NaN x'::float4; 2025-07-03 22:04:58.004 UTC client backend[14770] pg_regress/float4 ERROR: invalid input syntax for type real: " INFINITY x" at character 8 2025-07-03 22:04:58.004 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT ' INFINITY x'::float4; 2025-07-03 22:04:58.005 UTC not initialized[14777] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.006 UTC client backend[14777] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.006 UTC client backend[14777] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/char 2025-07-03 22:04:58.006 UTC client backend[14776] pg_regress/int2 LOG: connection ready: setup total=42.179 ms, fork=15.475 ms, authentication=0.394 ms 2025-07-03 22:04:58.009 UTC client backend[14771] pg_regress/text ERROR: function length(integer) does not exist at character 8 2025-07-03 22:04:58.009 UTC client backend[14771] pg_regress/text HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:04:58.009 UTC client backend[14771] pg_regress/text STATEMENT: select length(42); 2025-07-03 22:04:58.009 UTC client backend[14769] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 8 2025-07-03 22:04:58.009 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '10e400'::float8; 2025-07-03 22:04:58.009 UTC client backend[14775] pg_regress/txid LOG: connection ready: setup total=58.351 ms, fork=26.823 ms, authentication=0.381 ms 2025-07-03 22:04:58.009 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "34.5" at character 34 2025-07-03 22:04:58.009 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('34.5'); 2025-07-03 22:04:58.010 UTC client backend[14769] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 8 2025-07-03 22:04:58.010 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '-10e400'::float8; 2025-07-03 22:04:58.011 UTC not initialized[14780] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid STATEMENT: select '31:12:'::txid_snapshot; 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid STATEMENT: select '0:1:'::txid_snapshot; 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid STATEMENT: select '12:13:0'::txid_snapshot; 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-07-03 22:04:58.011 UTC client backend[14775] pg_regress/txid STATEMENT: select '12:16:14,13'::txid_snapshot; 2025-07-03 22:04:58.012 UTC client backend[14780] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.012 UTC client backend[14780] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/bit 2025-07-03 22:04:58.013 UTC client backend[14769] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 8 2025-07-03 22:04:58.013 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '10e-400'::float8; 2025-07-03 22:04:58.013 UTC client backend[14776] pg_regress/int2 ERROR: value "100000" is out of range for type smallint at character 34 2025-07-03 22:04:58.013 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('100000'); 2025-07-03 22:04:58.014 UTC client backend[14769] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 8 2025-07-03 22:04:58.014 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '-10e-400'::float8; 2025-07-03 22:04:58.014 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "asdf" at character 34 2025-07-03 22:04:58.014 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('asdf'); 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: " " at character 34 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (' '); 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "- 1234" at character 34 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('- 1234'); 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "4 444" at character 34 2025-07-03 22:04:58.015 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('4 444'); 2025-07-03 22:04:58.016 UTC client backend[14779] pg_regress/boolean LOG: connection ready: setup total=44.285 ms, fork=12.615 ms, authentication=0.411 ms 2025-07-03 22:04:58.017 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "123 dt" at character 34 2025-07-03 22:04:58.017 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES ('123 dt'); 2025-07-03 22:04:58.017 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "" at character 34 2025-07-03 22:04:58.017 UTC client backend[14776] pg_regress/int2 STATEMENT: INSERT INTO INT2_TBL(f1) VALUES (''); 2025-07-03 22:04:58.017 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "" at character 36 2025-07-03 22:04:58.017 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (''); 2025-07-03 22:04:58.018 UTC not initialized[14781] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: " " at character 36 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' '); 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "xyz" at character 36 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz'); 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5.0.0" at character 36 2025-07-03 22:04:58.018 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0'); 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5 . 0" at character 36 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0'); 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "5. 0" at character 36 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('5. 0'); 2025-07-03 22:04:58.019 UTC client backend[14781] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.019 UTC client backend[14781] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numeric 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: " - 3" at character 36 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES (' - 3'); 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "123 5" at character 36 2025-07-03 22:04:58.019 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('123 5'); 2025-07-03 22:04:58.022 UTC client backend[14781] pg_regress/numeric LOG: connection ready: setup total=38.908 ms, fork=26.976 ms, authentication=0.535 ms 2025-07-03 22:04:58.023 UTC client backend[14771] pg_regress/text ERROR: operator does not exist: integer || numeric at character 10 2025-07-03 22:04:58.023 UTC client backend[14771] pg_regress/text HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:04:58.023 UTC client backend[14771] pg_regress/text STATEMENT: select 3 || 4.0; 2025-07-03 22:04:58.024 UTC client backend[14777] pg_regress/char LOG: connection ready: setup total=58.113 ms, fork=33.771 ms, authentication=0.386 ms 2025-07-03 22:04:58.024 UTC not initialized[14783] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: "" at character 33 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (''); 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: " " at character 33 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' '); 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: "asdfasd" at character 33 2025-07-03 22:04:58.026 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('asdfasd'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: "99asdfasd" at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('99asdfasd'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: "5 d" at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 d'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: " 5d" at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' 5d'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: "5 5" at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('5 5'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: invalid input syntax for type oid: " - 500" at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES (' - 500'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: value "32958209582039852935" is out of range for type oid at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935'); 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid ERROR: value "-23582358720398502385" is out of range for type oid at character 33 2025-07-03 22:04:58.027 UTC client backend[14772] pg_regress/oid STATEMENT: INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385'); 2025-07-03 22:04:58.032 UTC client backend[14783] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.032 UTC client backend[14783] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rangetypes 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "test" at character 13 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'test' AS error; 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "foo" at character 13 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'foo' AS error; 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "yeah" at character 13 2025-07-03 22:04:58.032 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'yeah' AS error; 2025-07-03 22:04:58.033 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "nay" at character 13 2025-07-03 22:04:58.033 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'nay' AS error; 2025-07-03 22:04:58.033 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "o" at character 13 2025-07-03 22:04:58.033 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'o' AS error; 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "on_" at character 13 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'on_' AS error; 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "off_" at character 13 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool 'off_' AS error; 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "11" at character 13 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool '11' AS error; 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "N A N" at character 8 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT 'N A N'::float8; 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "000" at character 13 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool '000' AS error; 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: "NaN x" at character 8 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT 'NaN x'::float8; 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" at character 13 2025-07-03 22:04:58.034 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT bool '' AS error; 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 ERROR: invalid input syntax for type double precision: " INFINITY x" at character 8 2025-07-03 22:04:58.034 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT ' INFINITY x'::float8; 2025-07-03 22:04:58.036 UTC client backend[14770] pg_regress/float4 ERROR: division by zero 2025-07-03 22:04:58.036 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT f.f1 / '0.0' from FLOAT4_TBL f; 2025-07-03 22:04:58.036 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.036 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.037 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.037 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.038 UTC not initialized[14782] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.039 UTC client backend[14776] pg_regress/int2 ERROR: table "f" has 1 columns available but 2 columns specified 2025-07-03 22:04:58.039 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT * FROM INT2_TBL AS f(a, b); 2025-07-03 22:04:58.039 UTC client backend[14776] pg_regress/int2 ERROR: table "s" has 1 columns available but 2 columns specified 2025-07-03 22:04:58.039 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT * FROM (TABLE int2_tbl) AS s (a, b); 2025-07-03 22:04:58.048 UTC client backend[14780] pg_regress/bit LOG: connection ready: setup total=74.172 ms, fork=34.952 ms, authentication=0.374 ms 2025-07-03 22:04:58.048 UTC client backend[14782] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.048 UTC client backend[14782] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/pg_lsn 2025-07-03 22:04:58.049 UTC client backend[14771] pg_regress/text ERROR: VARIADIC argument must be an array at character 32 2025-07-03 22:04:58.049 UTC client backend[14771] pg_regress/text STATEMENT: select concat_ws(',', variadic 10); 2025-07-03 22:04:58.050 UTC client backend[14770] pg_regress/float4 ERROR: smallint out of range 2025-07-03 22:04:58.050 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '32767.6'::float4::int2; 2025-07-03 22:04:58.051 UTC client backend[14770] pg_regress/float4 ERROR: smallint out of range 2025-07-03 22:04:58.051 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '-32768.6'::float4::int2; 2025-07-03 22:04:58.051 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.051 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.052 UTC client backend[14771] pg_regress/text ERROR: too few arguments for format() 2025-07-03 22:04:58.052 UTC client backend[14771] pg_regress/text STATEMENT: select format('Hello %s %s', 'World'); 2025-07-03 22:04:58.052 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.052 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.052 UTC client backend[14770] pg_regress/float4 ERROR: integer out of range 2025-07-03 22:04:58.052 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '2147483647'::float4::int4; 2025-07-03 22:04:58.052 UTC not initialized[14786] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.053 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.053 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.053 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.053 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i; 2025-07-03 22:04:58.054 UTC client backend[14786] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.054 UTC client backend[14786] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/enum 2025-07-03 22:04:58.055 UTC client backend[14783] pg_regress/rangetypes LOG: connection ready: setup total=52.911 ms, fork=16.980 ms, authentication=4.968 ms 2025-07-03 22:04:58.056 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "" at character 8 2025-07-03 22:04:58.056 UTC client backend[14783] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-07-03 22:04:58.056 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select ''::textrange; 2025-07-03 22:04:58.057 UTC client backend[14786] pg_regress/enum LOG: connection ready: setup total=32.693 ms, fork=23.388 ms, authentication=0.469 ms 2025-07-03 22:04:58.057 UTC not initialized[14785] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.059 UTC client backend[14785] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.059 UTC client backend[14785] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regproc 2025-07-03 22:04:58.059 UTC client backend[14771] pg_regress/text ERROR: too few arguments for format() 2025-07-03 22:04:58.059 UTC client backend[14771] pg_regress/text STATEMENT: select format('Hello %s'); 2025-07-03 22:04:58.059 UTC client backend[14771] pg_regress/text ERROR: unrecognized format() type specifier "x" 2025-07-03 22:04:58.059 UTC client backend[14771] pg_regress/text HINT: For a single "%" use "%%". 2025-07-03 22:04:58.059 UTC client backend[14771] pg_regress/text STATEMENT: select format('Hello %x', 20); 2025-07-03 22:04:58.060 UTC client backend[14770] pg_regress/float4 ERROR: integer out of range 2025-07-03 22:04:58.060 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '-2147483900'::float4::int4; 2025-07-03 22:04:58.061 UTC client backend[14770] pg_regress/float4 ERROR: bigint out of range 2025-07-03 22:04:58.061 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '9223372036854775807'::float4::int8; 2025-07-03 22:04:58.062 UTC client backend[14785] pg_regress/regproc LOG: connection ready: setup total=58.486 ms, fork=47.938 ms, authentication=0.387 ms 2025-07-03 22:04:58.062 UTC not initialized[14787] [unknown] LOG: connection received: host=[local] 2025-07-03 22:04:58.063 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "-[a,z)" at character 8 2025-07-03 22:04:58.063 UTC client backend[14783] pg_regress/rangetypes DETAIL: Missing left parenthesis or bracket. 2025-07-03 22:04:58.063 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '-[a,z)'::textrange; 2025-07-03 22:04:58.063 UTC client backend[14787] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:04:58.063 UTC client backend[14787] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/money 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "[a,z) - " at character 8 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '[a,z) - '::textrange; 2025-07-03 22:04:58.064 UTC client backend[14770] pg_regress/float4 ERROR: bigint out of range 2025-07-03 22:04:58.064 UTC client backend[14770] pg_regress/float4 STATEMENT: SELECT '-9223380000000000000'::float4::int8; 2025-07-03 22:04:58.064 UTC client backend[14771] pg_regress/text ERROR: null values cannot be formatted as an SQL identifier 2025-07-03 22:04:58.064 UTC client backend[14771] pg_regress/text STATEMENT: select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello'); 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(",a)" at character 8 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes DETAIL: Unexpected end of input. 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(",a)'::textrange; 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes DETAIL: Too many commas. 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(,,a)'::textrange; 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(),a)" at character 8 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(),a)'::textrange; 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(a,))" at character 8 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-07-03 22:04:58.064 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(a,))'::textrange; 2025-07-03 22:04:58.065 UTC client backend[14771] pg_regress/text ERROR: too few arguments for format() 2025-07-03 22:04:58.065 UTC client backend[14771] pg_regress/text STATEMENT: select format('%1$s %4$s', 1, 2, 3); 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(],a)" at character 8 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes DETAIL: Missing comma after lower bound. 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(],a)'::textrange; 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes ERROR: malformed range literal: "(a,])" at character 8 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes DETAIL: Junk after right parenthesis or bracket. 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '(a,])'::textrange; 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-07-03 22:04:58.066 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '[z,a]'::textrange; 2025-07-03 22:04:58.067 UTC client backend[14771] pg_regress/text ERROR: too few arguments for format() 2025-07-03 22:04:58.067 UTC client backend[14771] pg_regress/text STATEMENT: select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12); 2025-07-03 22:04:58.068 UTC client backend[14777] pg_regress/char ERROR: value too long for type character(1) 2025-07-03 22:04:58.068 UTC client backend[14777] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('cd'); 2025-07-03 22:04:58.068 UTC client backend[14771] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-07-03 22:04:58.068 UTC client backend[14771] pg_regress/text STATEMENT: select format('%0$s', 'Hello'); 2025-07-03 22:04:58.069 UTC client backend[14771] pg_regress/text ERROR: format specifies argument 0, but arguments are numbered from 1 2025-07-03 22:04:58.069 UTC client backend[14771] pg_regress/text STATEMENT: select format('%*0$s', 'Hello'); 2025-07-03 22:04:58.069 UTC client backend[14771] pg_regress/text ERROR: unterminated format() type specifier 2025-07-03 22:04:58.069 UTC client backend[14771] pg_regress/text HINT: For a single "%" use "%%". 2025-07-03 22:04:58.069 UTC client backend[14771] pg_regress/text STATEMENT: select format('%1$', 1); 2025-07-03 22:04:58.070 UTC client backend[14771] pg_regress/text ERROR: unterminated format() type specifier 2025-07-03 22:04:58.070 UTC client backend[14771] pg_regress/text HINT: For a single "%" use "%%". 2025-07-03 22:04:58.070 UTC client backend[14771] pg_regress/text STATEMENT: select format('%1$1', 1); 2025-07-03 22:04:58.071 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: " tru e " 2025-07-03 22:04:58.071 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT ' tru e '::text::boolean AS invalid; 2025-07-03 22:04:58.077 UTC client backend[14780] pg_regress/bit ERROR: bit string length 2 does not match type bit(11) 2025-07-03 22:04:58.077 UTC client backend[14780] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'10'); 2025-07-03 22:04:58.077 UTC client backend[14776] pg_regress/int2 ERROR: smallint out of range 2025-07-03 22:04:58.077 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i; 2025-07-03 22:04:58.078 UTC client backend[14782] pg_regress/pg_lsn LOG: connection ready: setup total=83.115 ms, fork=33.553 ms, authentication=0.444 ms 2025-07-03 22:04:58.078 UTC client backend[14780] pg_regress/bit ERROR: bit string length 12 does not match type bit(11) 2025-07-03 22:04:58.078 UTC client backend[14780] pg_regress/bit STATEMENT: INSERT INTO BIT_TABLE VALUES (B'101011111010'); 2025-07-03 22:04:58.080 UTC client backend[14764] pg_regress/varchar ERROR: value too long for type character varying(4) 2025-07-03 22:04:58.080 UTC client backend[14764] pg_regress/varchar STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde'); 2025-07-03 22:04:58.081 UTC client backend[14787] pg_regress/money LOG: connection ready: setup total=55.334 ms, fork=25.801 ms, authentication=0.419 ms 2025-07-03 22:04:58.083 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "" 2025-07-03 22:04:58.083 UTC client backend[14779] pg_regress/boolean STATEMENT: SELECT ''::text::boolean AS invalid; 2025-07-03 22:04:58.086 UTC client backend[14776] pg_regress/int2 ERROR: smallint out of range 2025-07-03 22:04:58.086 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i; 2025-07-03 22:04:58.092 UTC client backend[14776] pg_regress/int2 ERROR: smallint out of range 2025-07-03 22:04:58.092 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i; 2025-07-03 22:04:58.096 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.096 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int4; 2025-07-03 22:04:58.096 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.096 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int4; 2025-07-03 22:04:58.097 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "foo.boo[]" 2025-07-03 22:04:58.097 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('foo.boo[]'); 2025-07-03 22:04:58.097 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.097 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL; 2025-07-03 22:04:58.097 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.097 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 * (-1)::int2; 2025-07-03 22:04:58.098 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.098 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT (-2147483648)::int4 / (-1)::int2; 2025-07-03 22:04:58.099 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: " " 2025-07-03 22:04:58.099 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident(' '); 2025-07-03 22:04:58.100 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: " .aaa" 2025-07-03 22:04:58.100 UTC client backend[14766] pg_regress/name DETAIL: No valid identifier before ".". 2025-07-03 22:04:58.100 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident(' .aaa'); 2025-07-03 22:04:58.101 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: " aaa . " 2025-07-03 22:04:58.101 UTC client backend[14766] pg_regress/name DETAIL: No valid identifier after ".". 2025-07-03 22:04:58.101 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident(' aaa . '); 2025-07-03 22:04:58.102 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "aaa.a%b" 2025-07-03 22:04:58.102 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('aaa.a%b'); 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit ERROR: bit string too long for type bit varying(11) 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit STATEMENT: INSERT INTO VARBIT_TABLE VALUES (B'101011111010'); 2025-07-03 22:04:58.102 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" 2025-07-03 22:04:58.102 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'); 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT b' 0'; 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit ERROR: " " is not a valid binary digit at character 8 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT b'0 '; 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT x' 0'; 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit ERROR: " " is not a valid hexadecimal digit at character 8 2025-07-03 22:04:58.102 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT x'0 '; 2025-07-03 22:04:58.103 UTC client backend[14764] pg_regress/varchar LOG: disconnection: session time: 0:00:00.182 user=postgres database=regression host=[local] 2025-07-03 22:04:58.108 UTC client backend[14782] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "G/0" at character 32 2025-07-03 22:04:58.108 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('G/0'); 2025-07-03 22:04:58.108 UTC client backend[14782] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "-1/0" at character 32 2025-07-03 22:04:58.108 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('-1/0'); 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: " 0/12345678" at character 32 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES (' 0/12345678'); 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "ABCD/" at character 32 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('ABCD/'); 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn ERROR: invalid input syntax for type pg_lsn: "/ABCD" at character 32 2025-07-03 22:04:58.109 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: INSERT INTO PG_LSN_TBL VALUES ('/ABCD'); 2025-07-03 22:04:58.114 UTC client backend[14776] pg_regress/int2 ERROR: smallint out of range 2025-07-03 22:04:58.114 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 * (-1)::int2; 2025-07-03 22:04:58.114 UTC client backend[14776] pg_regress/int2 ERROR: smallint out of range 2025-07-03 22:04:58.114 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT (-32768)::int2 / (-1)::int2; 2025-07-03 22:04:58.117 UTC client backend[14771] pg_regress/text LOG: disconnection: session time: 0:00:00.159 user=postgres database=regression host=[local] 2025-07-03 22:04:58.121 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.121 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, 0::int4); 2025-07-03 22:04:58.121 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.121 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT gcd((-2147483648)::int4, (-2147483648)::int4); 2025-07-03 22:04:58.122 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.122 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT lcm((-2147483648)::int4, 1::int4); 2025-07-03 22:04:58.122 UTC client backend[14765] pg_regress/int4 ERROR: integer out of range 2025-07-03 22:04:58.122 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT lcm(2147483647::int4, 2147483646::int4); 2025-07-03 22:04:58.122 UTC client backend[14769] pg_regress/float8 ERROR: zero raised to a negative power is undefined 2025-07-03 22:04:58.122 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT power(float8 '0', float8 '-inf'); 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "0b" at character 13 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0b'; 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "0o" at character 13 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0o'; 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "0x" at character 13 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0x'; 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 ERROR: value "0b10000000000000000000000000000000" is out of range for type integer at character 13 2025-07-03 22:04:58.123 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0b10000000000000000000000000000000'; 2025-07-03 22:04:58.124 UTC client backend[14765] pg_regress/int4 ERROR: value "0o20000000000" is out of range for type integer at character 13 2025-07-03 22:04:58.124 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0o20000000000'; 2025-07-03 22:04:58.124 UTC client backend[14765] pg_regress/int4 ERROR: value "0x80000000" is out of range for type integer at character 13 2025-07-03 22:04:58.124 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '0x80000000'; 2025-07-03 22:04:58.125 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: ""c".X XXXXXXXXXX" 2025-07-03 22:04:58.125 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident(E'"c".X XXXX\002XXXXXX'); 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "1020" 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('1020'); 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "10.20" 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('10.20'); 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "." 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name DETAIL: No valid identifier before ".". 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('.'); 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: ".1020" 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name DETAIL: No valid identifier before ".". 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('.1020'); 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name ERROR: string is not a valid identifier: "xxx.1020" 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name DETAIL: No valid identifier after ".". 2025-07-03 22:04:58.126 UTC client backend[14766] pg_regress/name STATEMENT: SELECT parse_ident('xxx.1020'); 2025-07-03 22:04:58.126 UTC client backend[14777] pg_regress/char ERROR: value too long for type character(4) 2025-07-03 22:04:58.126 UTC client backend[14777] pg_regress/char STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('abcde'); 2025-07-03 22:04:58.127 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0b" at character 13 2025-07-03 22:04:58.127 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0b'; 2025-07-03 22:04:58.128 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0o" at character 13 2025-07-03 22:04:58.128 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0o'; 2025-07-03 22:04:58.128 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "0x" at character 13 2025-07-03 22:04:58.128 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0x'; 2025-07-03 22:04:58.129 UTC client backend[14766] pg_regress/name LOG: disconnection: session time: 0:00:00.198 user=postgres database=regression host=[local] 2025-07-03 22:04:58.130 UTC client backend[14776] pg_regress/int2 ERROR: value "0b1000000000000000" is out of range for type smallint at character 13 2025-07-03 22:04:58.130 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0b1000000000000000'; 2025-07-03 22:04:58.131 UTC client backend[14776] pg_regress/int2 ERROR: value "0o100000" is out of range for type smallint at character 13 2025-07-03 22:04:58.131 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0o100000'; 2025-07-03 22:04:58.132 UTC client backend[14776] pg_regress/int2 ERROR: value "0x8000" is out of range for type smallint at character 13 2025-07-03 22:04:58.132 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '0x8000'; 2025-07-03 22:04:58.133 UTC client backend[14776] pg_regress/int2 ERROR: value "-0b1000000000000001" is out of range for type smallint at character 13 2025-07-03 22:04:58.133 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '-0b1000000000000001'; 2025-07-03 22:04:58.135 UTC client backend[14776] pg_regress/int2 ERROR: value "-0o100001" is out of range for type smallint at character 13 2025-07-03 22:04:58.135 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '-0o100001'; 2025-07-03 22:04:58.137 UTC client backend[14776] pg_regress/int2 ERROR: value "-0x8001" is out of range for type smallint at character 13 2025-07-03 22:04:58.137 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '-0x8001'; 2025-07-03 22:04:58.138 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38 2025-07-03 22:04:58.138 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F'); 2025-07-03 22:04:58.139 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38 2025-07-03 22:04:58.139 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}'); 2025-07-03 22:04:58.139 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38 2025-07-03 22:04:58.139 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111'); 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 '); 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111'); 2025-07-03 22:04:58.140 UTC client backend[14777] pg_regress/char LOG: disconnection: session time: 0:00:00.140 user=postgres database=regression host=[local] 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid ERROR: invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38 2025-07-03 22:04:58.140 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111'); 2025-07-03 22:04:58.144 UTC client backend[14779] pg_regress/boolean ERROR: invalid input syntax for type boolean: "XXX" at character 43 2025-07-03 22:04:58.144 UTC client backend[14779] pg_regress/boolean STATEMENT: INSERT INTO BOOLTBL2 (f1) VALUES (bool 'XXX'); 2025-07-03 22:04:58.148 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "_100" at character 13 2025-07-03 22:04:58.148 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '_100'; 2025-07-03 22:04:58.148 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "100_" at character 13 2025-07-03 22:04:58.148 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '100_'; 2025-07-03 22:04:58.149 UTC client backend[14769] pg_regress/float8 ERROR: a negative number raised to a non-integer power yields a complex result 2025-07-03 22:04:58.149 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT power(float8 '-inf', float8 '3.5'); 2025-07-03 22:04:58.149 UTC client backend[14776] pg_regress/int2 ERROR: invalid input syntax for type smallint: "10__000" at character 13 2025-07-03 22:04:58.149 UTC client backend[14776] pg_regress/int2 STATEMENT: SELECT int2 '10__000'; 2025-07-03 22:04:58.149 UTC client backend[14775] pg_regress/txid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22 2025-07-03 22:04:58.149 UTC client backend[14775] pg_regress/txid STATEMENT: SELECT txid_snapshot '1:9223372036854775808:3'; 2025-07-03 22:04:58.152 UTC client backend[14776] pg_regress/int2 LOG: disconnection: session time: 0:00:00.172 user=postgres database=regression host=[local] 2025-07-03 22:04:58.153 UTC client backend[14786] pg_regress/enum ERROR: invalid input value for enum rainbow: "mauve" at character 8 2025-07-03 22:04:58.153 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT 'mauve'::rainbow; 2025-07-03 22:04:58.155 UTC client backend[14765] pg_regress/int4 ERROR: value "-0b10000000000000000000000000000001" is out of range for type integer at character 13 2025-07-03 22:04:58.155 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '-0b10000000000000000000000000000001'; 2025-07-03 22:04:58.155 UTC client backend[14765] pg_regress/int4 ERROR: value "-0o20000000001" is out of range for type integer at character 13 2025-07-03 22:04:58.155 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '-0o20000000001'; 2025-07-03 22:04:58.156 UTC client backend[14765] pg_regress/int4 ERROR: value "-0x80000001" is out of range for type integer at character 13 2025-07-03 22:04:58.156 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '-0x80000001'; 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "_100" at character 13 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '_100'; 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "100_" at character 13 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '100_'; 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 ERROR: invalid input syntax for type integer: "100__000" at character 13 2025-07-03 22:04:58.157 UTC client backend[14765] pg_regress/int4 STATEMENT: SELECT int4 '100__000'; 2025-07-03 22:04:58.161 UTC client backend[14765] pg_regress/int4 LOG: disconnection: session time: 0:00:00.230 user=postgres database=regression host=[local] 2025-07-03 22:04:58.167 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.167 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT f.f1 * '1e200' from FLOAT8_TBL f; 2025-07-03 22:04:58.172 UTC client backend[14772] pg_regress/oid LOG: disconnection: session time: 0:00:00.212 user=postgres database=regression host=[local] 2025-07-03 22:04:58.174 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.174 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT f.f1 ^ '1e200' from FLOAT8_TBL f; 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 ERROR: cannot take logarithm of zero 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ; 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ; 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: underflow 2025-07-03 22:04:58.176 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT exp(f.f1) from FLOAT8_TBL f; 2025-07-03 22:04:58.177 UTC client backend[14769] pg_regress/float8 ERROR: division by zero 2025-07-03 22:04:58.177 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT f.f1 / '0.0' from FLOAT8_TBL f; 2025-07-03 22:04:58.187 UTC client backend[14770] pg_regress/float4 LOG: disconnection: session time: 0:00:00.231 user=postgres database=regression host=[local] 2025-07-03 22:04:58.188 UTC client backend[14782] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-07-03 22:04:58.188 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric; 2025-07-03 22:04:58.188 UTC client backend[14782] pg_regress/pg_lsn ERROR: pg_lsn out of range 2025-07-03 22:04:58.188 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: SELECT '0/1'::pg_lsn - 2::numeric; 2025-07-03 22:04:58.198 UTC client backend[14782] pg_regress/pg_lsn ERROR: cannot add NaN to pg_lsn 2025-07-03 22:04:58.198 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric; 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum ERROR: invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto" 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum DETAIL: Labels must be 63 bytes or less. 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto'; 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum ERROR: "zeus" is not an existing enum label 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus'; 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum ERROR: enum label "mercury" already exists 2025-07-03 22:04:58.199 UTC client backend[14786] pg_regress/enum STATEMENT: ALTER TYPE planets ADD VALUE 'mercury'; 2025-07-03 22:04:58.201 UTC client backend[14782] pg_regress/pg_lsn ERROR: cannot subtract NaN from pg_lsn 2025-07-03 22:04:58.201 UTC client backend[14782] pg_regress/pg_lsn STATEMENT: SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric; 2025-07-03 22:04:58.212 UTC client backend[14773] pg_regress/int8 ERROR: value "-9223372036854775809" is out of range for type bigint at character 8 2025-07-03 22:04:58.212 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775809'::int8; 2025-07-03 22:04:58.212 UTC client backend[14773] pg_regress/int8 ERROR: value "9223372036854775808" is out of range for type bigint at character 8 2025-07-03 22:04:58.212 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775808'::int8; 2025-07-03 22:04:58.213 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.213 UTC client backend[14773] pg_regress/int8 STATEMENT: select -('-9223372036854775808'::int8); 2025-07-03 22:04:58.213 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.213 UTC client backend[14773] pg_regress/int8 STATEMENT: select 0::int8 - '-9223372036854775808'::int8; 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '9223372036854775800'::int8; 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 - '-9223372036854775800'::int8; 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.214 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '9223372036854775800'::int8; 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '9223372036854775800'::int8; 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 ERROR: division by zero 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 / '0'::int8; 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 ERROR: division by zero 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 % '0'::int8; 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.215 UTC client backend[14773] pg_regress/int8 STATEMENT: select abs('-9223372036854775808'::int8); 2025-07-03 22:04:58.216 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.216 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int4; 2025-07-03 22:04:58.217 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.217 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int4; 2025-07-03 22:04:58.217 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.217 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int4; 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 STATEMENT: select '100'::int4 + '9223372036854775800'::int8; 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-100'::int4 - '9223372036854775800'::int8; 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 STATEMENT: select '100'::int4 * '9223372036854775800'::int8; 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.218 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 + '100'::int2; 2025-07-03 22:04:58.219 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.219 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775800'::int8 - '100'::int2; 2025-07-03 22:04:58.219 UTC client backend[14769] pg_regress/float8 ERROR: input is out of range 2025-07-03 22:04:58.219 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT acosh(float8 '-infinity'); 2025-07-03 22:04:58.219 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.219 UTC client backend[14773] pg_regress/int8 STATEMENT: select '9223372036854775800'::int8 * '100'::int2; 2025-07-03 22:04:58.220 UTC client backend[14773] pg_regress/int8 ERROR: division by zero 2025-07-03 22:04:58.220 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-9223372036854775808'::int8 / '0'::int2; 2025-07-03 22:04:58.220 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.220 UTC client backend[14773] pg_regress/int8 STATEMENT: select '100'::int2 + '9223372036854775800'::int8; 2025-07-03 22:04:58.220 UTC client backend[14769] pg_regress/float8 ERROR: input is out of range 2025-07-03 22:04:58.220 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT atanh(float8 'infinity'); 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 STATEMENT: select '-100'::int2 - '9223372036854775800'::int8; 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 STATEMENT: select '100'::int2 * '9223372036854775800'::int8; 2025-07-03 22:04:58.221 UTC client backend[14769] pg_regress/float8 ERROR: input is out of range 2025-07-03 22:04:58.221 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT atanh(float8 '-infinity'); 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 ERROR: division by zero 2025-07-03 22:04:58.221 UTC client backend[14773] pg_regress/int8 STATEMENT: select '100'::int2 / '0'::int8; 2025-07-03 22:04:58.223 UTC client backend[14775] pg_regress/txid LOG: disconnection: session time: 0:00:00.245 user=postgres database=regression host=[local] 2025-07-03 22:04:58.226 UTC client backend[14773] pg_regress/int8 ERROR: integer out of range 2025-07-03 22:04:58.226 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456; 2025-07-03 22:04:58.227 UTC client backend[14785] pg_regress/regproc ERROR: constant of the type regrole cannot be used here 2025-07-03 22:04:58.227 UTC client backend[14785] pg_regress/regproc STATEMENT: CREATE TABLE regrole_test (rolid OID DEFAULT 'regress_regrole_test'::regrole); 2025-07-03 22:04:58.227 UTC client backend[14787] pg_regress/money ERROR: value "123456789012345678" is out of range for type money at character 8 2025-07-03 22:04:58.227 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '123456789012345678'::money; 2025-07-03 22:04:58.227 UTC client backend[14787] pg_regress/money ERROR: value "9223372036854775807" is out of range for type money at character 8 2025-07-03 22:04:58.227 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '9223372036854775807'::money; 2025-07-03 22:04:58.228 UTC client backend[14773] pg_regress/int8 ERROR: smallint out of range 2025-07-03 22:04:58.228 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456; 2025-07-03 22:04:58.230 UTC client backend[14787] pg_regress/money ERROR: value "-123456789012345678" is out of range for type money at character 8 2025-07-03 22:04:58.230 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-123456789012345678'::money; 2025-07-03 22:04:58.230 UTC client backend[14787] pg_regress/money ERROR: value "-9223372036854775808" is out of range for type money at character 8 2025-07-03 22:04:58.230 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-9223372036854775808'::money; 2025-07-03 22:04:58.231 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.231 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-infinity'); 2025-07-03 22:04:58.232 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: underflow 2025-07-03 22:04:58.232 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1000.5'); 2025-07-03 22:04:58.233 UTC client backend[14782] pg_regress/pg_lsn LOG: disconnection: session time: 0:00:00.204 user=postgres database=regression host=[local] 2025-07-03 22:04:58.234 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.234 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT gamma(float8 '-1'); 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '-1'); 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT gamma(float8 '0'); 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '0'); 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.235 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT gamma(float8 '1000'); 2025-07-03 22:04:58.236 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.236 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT CAST('922337203685477580700.0'::float8 AS int8); 2025-07-03 22:04:58.237 UTC client backend[14767] pg_regress/uuid ERROR: duplicate key value violates unique constraint "guid1_unique_btree" 2025-07-03 22:04:58.237 UTC client backend[14767] pg_regress/uuid DETAIL: Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists. 2025-07-03 22:04:58.237 UTC client backend[14767] pg_regress/uuid STATEMENT: INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111'); 2025-07-03 22:04:58.237 UTC client backend[14773] pg_regress/int8 ERROR: OID out of range 2025-07-03 22:04:58.237 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT CAST(q1 AS oid) FROM INT8_TBL; 2025-07-03 22:04:58.237 UTC client backend[14769] pg_regress/float8 ERROR: value out of range: overflow 2025-07-03 22:04:58.237 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT lgamma(float8 '1e308'); 2025-07-03 22:04:58.237 UTC client backend[14769] pg_regress/float8 ERROR: "10e400" is out of range for type double precision at character 36 2025-07-03 22:04:58.237 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400'); 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 ERROR: "-10e400" is out of range for type double precision at character 36 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400'); 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 ERROR: "10e-400" is out of range for type double precision at character 36 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400'); 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 ERROR: "-10e-400" is out of range for type double precision at character 36 2025-07-03 22:04:58.238 UTC client backend[14769] pg_regress/float8 STATEMENT: INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400'); 2025-07-03 22:04:58.240 UTC client backend[14787] pg_regress/money ERROR: value "-92233720368547758.09" is out of range for type money at character 8 2025-07-03 22:04:58.240 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-92233720368547758.09'::money; 2025-07-03 22:04:58.240 UTC client backend[14787] pg_regress/money ERROR: value "92233720368547758.08" is out of range for type money at character 8 2025-07-03 22:04:58.240 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '92233720368547758.08'::money; 2025-07-03 22:04:58.241 UTC client backend[14787] pg_regress/money ERROR: value "-92233720368547758.085" is out of range for type money at character 8 2025-07-03 22:04:58.241 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-92233720368547758.085'::money; 2025-07-03 22:04:58.241 UTC client backend[14785] pg_regress/regproc ERROR: constant of the type regdatabase cannot be used here 2025-07-03 22:04:58.241 UTC client backend[14785] pg_regress/regproc STATEMENT: CREATE TABLE regdatabase_test (datid OID DEFAULT 'template1'::regdatabase); 2025-07-03 22:04:58.241 UTC client backend[14787] pg_regress/money ERROR: value "92233720368547758.075" is out of range for type money at character 8 2025-07-03 22:04:58.241 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '92233720368547758.075'::money; 2025-07-03 22:04:58.249 UTC client backend[14785] pg_regress/regproc ERROR: operator does not exist: ||// at character 16 2025-07-03 22:04:58.249 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regoper('||//'); 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc ERROR: operator does not exist: ++(int4,int4) at character 20 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regoperator('++(int4,int4)'); 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc ERROR: function "know" does not exist at character 16 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regproc('know'); 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc ERROR: function "absinthe(numeric)" does not exist at character 21 2025-07-03 22:04:58.251 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regprocedure('absinthe(numeric)'); 2025-07-03 22:04:58.252 UTC client backend[14785] pg_regress/regproc ERROR: relation "pg_classes" does not exist at character 17 2025-07-03 22:04:58.252 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regclass('pg_classes'); 2025-07-03 22:04:58.254 UTC client backend[14785] pg_regress/regproc ERROR: type "int3" does not exist at character 16 2025-07-03 22:04:58.254 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regtype('int3'); 2025-07-03 22:04:58.255 UTC client backend[14785] pg_regress/regproc ERROR: operator does not exist: ng_catalog.||/ at character 16 2025-07-03 22:04:58.255 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regoper('ng_catalog.||/'); 2025-07-03 22:04:58.255 UTC client backend[14773] pg_regress/int8 ERROR: step size cannot equal zero 2025-07-03 22:04:58.255 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0); 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc ERROR: operator does not exist: ng_catalog.+(int4,int4) at character 20 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regoperator('ng_catalog.+(int4,int4)'); 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc ERROR: function "ng_catalog.now" does not exist at character 16 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regproc('ng_catalog.now'); 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc ERROR: function "ng_catalog.abs(numeric)" does not exist at character 21 2025-07-03 22:04:58.256 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regprocedure('ng_catalog.abs(numeric)'); 2025-07-03 22:04:58.259 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.259 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int8; 2025-07-03 22:04:58.259 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.259 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int8; 2025-07-03 22:04:58.260 UTC client backend[14785] pg_regress/regproc ERROR: relation "ng_catalog.pg_class" does not exist at character 17 2025-07-03 22:04:58.260 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regclass('ng_catalog.pg_class'); 2025-07-03 22:04:58.260 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.260 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int4; 2025-07-03 22:04:58.260 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.260 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int4; 2025-07-03 22:04:58.261 UTC client backend[14785] pg_regress/regproc ERROR: schema "ng_catalog" does not exist at character 16 2025-07-03 22:04:58.261 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regtype('ng_catalog.int4'); 2025-07-03 22:04:58.261 UTC client backend[14785] pg_regress/regproc ERROR: collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21 2025-07-03 22:04:58.261 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regcollation('ng_catalog."POSIX"'); 2025-07-03 22:04:58.262 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.262 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 * (-1)::int2; 2025-07-03 22:04:58.262 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.262 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money + '0.01'::money; 2025-07-03 22:04:58.263 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.263 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-92233720368547758.08'::money - '0.01'::money; 2025-07-03 22:04:58.263 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.263 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT (-9223372036854775808)::int8 / (-1)::int2; 2025-07-03 22:04:58.263 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.263 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::float8; 2025-07-03 22:04:58.263 UTC client backend[14785] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-07-03 22:04:58.263 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regrole('regress_regrole_test'); 2025-07-03 22:04:58.264 UTC client backend[14769] pg_regress/float8 ERROR: smallint out of range 2025-07-03 22:04:58.264 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '32767.6'::float8::int2; 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc ERROR: role "regress_regrole_test" does not exist at character 16 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regrole('"regress_regrole_test"'); 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc ERROR: role "nonexistent" does not exist at character 16 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regrole('Nonexistent'); 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc ERROR: role "Nonexistent" does not exist at character 16 2025-07-03 22:04:58.265 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regrole('"Nonexistent"'); 2025-07-03 22:04:58.265 UTC client backend[14769] pg_regress/float8 ERROR: smallint out of range 2025-07-03 22:04:58.265 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '-32768.6'::float8::int2; 2025-07-03 22:04:58.266 UTC client backend[14785] pg_regress/regproc ERROR: invalid name syntax at character 16 2025-07-03 22:04:58.266 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regrole('foo.bar'); 2025-07-03 22:04:58.266 UTC client backend[14785] pg_regress/regproc ERROR: schema "nonexistent" does not exist at character 21 2025-07-03 22:04:58.266 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regnamespace('Nonexistent'); 2025-07-03 22:04:58.267 UTC client backend[14785] pg_regress/regproc ERROR: schema "Nonexistent" does not exist at character 21 2025-07-03 22:04:58.267 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regnamespace('"Nonexistent"'); 2025-07-03 22:04:58.267 UTC client backend[14785] pg_regress/regproc ERROR: invalid name syntax at character 21 2025-07-03 22:04:58.267 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regnamespace('foo.bar'); 2025-07-03 22:04:58.268 UTC client backend[14769] pg_regress/float8 ERROR: integer out of range 2025-07-03 22:04:58.268 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '2147483647.6'::float8::int4; 2025-07-03 22:04:58.268 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.268 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '-1'::money / 1.175494e-38::float4; 2025-07-03 22:04:58.268 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.268 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '92233720368547758.07'::money * 2::int4; 2025-07-03 22:04:58.271 UTC client backend[14787] pg_regress/money ERROR: division by zero 2025-07-03 22:04:58.271 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '1'::money / 0::int2; 2025-07-03 22:04:58.271 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.271 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '42'::money * 'inf'::float8; 2025-07-03 22:04:58.272 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.272 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '42'::money * '-inf'::float8; 2025-07-03 22:04:58.272 UTC client backend[14787] pg_regress/money ERROR: money out of range 2025-07-03 22:04:58.272 UTC client backend[14787] pg_regress/money STATEMENT: SELECT '42'::money * 'nan'::float4; 2025-07-03 22:04:58.273 UTC client backend[14785] pg_regress/regproc ERROR: database "nonexistent" does not exist at character 20 2025-07-03 22:04:58.273 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regdatabase('Nonexistent'); 2025-07-03 22:04:58.274 UTC client backend[14785] pg_regress/regproc ERROR: database "Nonexistent" does not exist at character 20 2025-07-03 22:04:58.274 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regdatabase('"Nonexistent"'); 2025-07-03 22:04:58.274 UTC client backend[14785] pg_regress/regproc ERROR: invalid name syntax at character 20 2025-07-03 22:04:58.274 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT regdatabase('foo.bar'); 2025-07-03 22:04:58.275 UTC client backend[14769] pg_regress/float8 ERROR: integer out of range 2025-07-03 22:04:58.275 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '-2147483648.6'::float8::int4; 2025-07-03 22:04:58.275 UTC client backend[14787] pg_regress/money LOG: disconnection: session time: 0:00:00.223 user=postgres database=regression host=[local] 2025-07-03 22:04:58.277 UTC client backend[14769] pg_regress/float8 ERROR: bigint out of range 2025-07-03 22:04:58.277 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '9223372036854775807'::float8::int8; 2025-07-03 22:04:58.278 UTC client backend[14769] pg_regress/float8 ERROR: bigint out of range 2025-07-03 22:04:58.278 UTC client backend[14769] pg_regress/float8 STATEMENT: SELECT '-9223372036854780000'::float8::int8; 2025-07-03 22:04:58.280 UTC client backend[14783] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:04:58.280 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select numrange(2.0, 1.0); 2025-07-03 22:04:58.282 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.282 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, 0::int8); 2025-07-03 22:04:58.282 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.282 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8); 2025-07-03 22:04:58.284 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.284 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT lcm((-9223372036854775808)::int8, 1::int8); 2025-07-03 22:04:58.284 UTC client backend[14773] pg_regress/int8 ERROR: bigint out of range 2025-07-03 22:04:58.284 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8); 2025-07-03 22:04:58.285 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0b" at character 13 2025-07-03 22:04:58.285 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0b'; 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0o" at character 13 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0o'; 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "0x" at character 13 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0x'; 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 ERROR: value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13 2025-07-03 22:04:58.287 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000'; 2025-07-03 22:04:58.288 UTC client backend[14773] pg_regress/int8 ERROR: value "0o1000000000000000000000" is out of range for type bigint at character 13 2025-07-03 22:04:58.288 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0o1000000000000000000000'; 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 ERROR: value "0x8000000000000000" is out of range for type bigint at character 13 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '0x8000000000000000'; 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 ERROR: value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001'; 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 ERROR: value "-0o1000000000000000000001" is out of range for type bigint at character 13 2025-07-03 22:04:58.289 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '-0o1000000000000000000001'; 2025-07-03 22:04:58.290 UTC client backend[14773] pg_regress/int8 ERROR: value "-0x8000000000000001" is out of range for type bigint at character 13 2025-07-03 22:04:58.290 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '-0x8000000000000001'; 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "_100" at character 13 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '_100'; 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100_" at character 13 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '100_'; 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 ERROR: invalid input syntax for type bigint: "100__000" at character 13 2025-07-03 22:04:58.300 UTC client backend[14773] pg_regress/int8 STATEMENT: SELECT int8 '100__000'; 2025-07-03 22:04:58.304 UTC client backend[14773] pg_regress/int8 LOG: disconnection: session time: 0:00:00.332 user=postgres database=regression host=[local] 2025-07-03 22:04:58.313 UTC client backend[14783] pg_regress/rangetypes ERROR: result of range union would not be contiguous 2025-07-03 22:04:58.313 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select numrange(1.0, 2.0) + numrange(2.5, 3.0); 2025-07-03 22:04:58.315 UTC client backend[14769] pg_regress/float8 ERROR: type "no_such_type" does not exist at character 69 2025-07-03 22:04:58.315 UTC client backend[14769] pg_regress/float8 STATEMENT: create type xfloat8 (input = xfloat8in, output = xfloat8out, like = no_such_type); 2025-07-03 22:04:58.336 UTC client backend[14785] pg_regress/regproc ERROR: syntax error at or near "type" at character 11 2025-07-03 22:04:58.336 UTC client backend[14785] pg_regress/regproc CONTEXT: invalid type name "incorrect type name syntax" 2025-07-03 22:04:58.336 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype'); 2025-07-03 22:04:58.338 UTC client backend[14785] pg_regress/regproc ERROR: invalid NUMERIC type modifier 2025-07-03 22:04:58.338 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype'); 2025-07-03 22:04:58.339 UTC client backend[14785] pg_regress/regproc ERROR: improper qualified name (too many dotted names): way.too.many.names 2025-07-03 22:04:58.339 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype'); 2025-07-03 22:04:58.340 UTC client backend[14785] pg_regress/regproc ERROR: cross-database references are not implemented: no_such_catalog.schema.name 2025-07-03 22:04:58.340 UTC client backend[14785] pg_regress/regproc STATEMENT: SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype'); 2025-07-03 22:04:58.344 UTC client backend[14785] pg_regress/regproc LOG: disconnection: session time: 0:00:00.292 user=postgres database=regression host=[local] 2025-07-03 22:04:58.372 UTC client backend[14769] pg_regress/float8 LOG: disconnection: session time: 0:00:00.418 user=postgres database=regression host=[local] 2025-07-03 22:04:58.415 UTC client backend[14786] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-07-03 22:04:58.415 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT 'purple'::rgb; 2025-07-03 22:04:58.423 UTC client backend[14786] pg_regress/enum ERROR: value for domain rgb violates check constraint "rgb_check" 2025-07-03 22:04:58.423 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT 'purple'::rainbow::rgb; 2025-07-03 22:04:58.498 UTC client backend[14786] pg_regress/enum ERROR: insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey" 2025-07-03 22:04:58.498 UTC client backend[14786] pg_regress/enum DETAIL: Key (parent)=(blue) is not present in table "enumtest_parent". 2025-07-03 22:04:58.498 UTC client backend[14786] pg_regress/enum STATEMENT: INSERT INTO enumtest_child VALUES ('blue'); 2025-07-03 22:04:58.499 UTC client backend[14786] pg_regress/enum ERROR: update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child" 2025-07-03 22:04:58.499 UTC client backend[14786] pg_regress/enum DETAIL: Key (id)=(red) is still referenced from table "enumtest_child". 2025-07-03 22:04:58.499 UTC client backend[14786] pg_regress/enum STATEMENT: DELETE FROM enumtest_parent; 2025-07-03 22:04:58.501 UTC client backend[14786] pg_regress/enum ERROR: foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented 2025-07-03 22:04:58.501 UTC client backend[14786] 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-07-03 22:04:58.501 UTC client backend[14786] pg_regress/enum STATEMENT: CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent); 2025-07-03 22:04:58.515 UTC client backend[14786] pg_regress/enum ERROR: "red" is not an existing enum label 2025-07-03 22:04:58.515 UTC client backend[14786] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson'; 2025-07-03 22:04:58.516 UTC client backend[14786] pg_regress/enum ERROR: enum label "green" already exists 2025-07-03 22:04:58.516 UTC client backend[14786] pg_regress/enum STATEMENT: ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green'; 2025-07-03 22:04:58.525 UTC client backend[14786] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus at character 8 2025-07-03 22:04:58.525 UTC client backend[14786] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-07-03 22:04:58.525 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT 'new'::bogus; 2025-07-03 22:04:58.531 UTC client backend[14786] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-07-03 22:04:58.531 UTC client backend[14786] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-07-03 22:04:58.531 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT enum_last(null::bogus); 2025-07-03 22:04:58.535 UTC client backend[14786] pg_regress/enum ERROR: unsafe use of new value "new" of enum type bogus 2025-07-03 22:04:58.535 UTC client backend[14786] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-07-03 22:04:58.535 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT enum_range(null::bogus); 2025-07-03 22:04:58.539 UTC client backend[14786] pg_regress/enum ERROR: unsafe use of new value "bad" of enum type bogon at character 8 2025-07-03 22:04:58.539 UTC client backend[14786] pg_regress/enum HINT: New enum values must be committed before they can be used. 2025-07-03 22:04:58.539 UTC client backend[14786] pg_regress/enum STATEMENT: SELECT 'bad'::bogon; 2025-07-03 22:04:58.626 UTC client backend[14786] pg_regress/enum LOG: disconnection: session time: 0:00:00.578 user=postgres database=regression host=[local] 2025-07-03 22:04:58.628 UTC client backend[14767] pg_regress/uuid LOG: disconnection: session time: 0:00:00.690 user=postgres database=regression host=[local] 2025-07-03 22:04:58.795 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.795 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric / '0'; 2025-07-03 22:04:58.795 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.795 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric / '0'; 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '0'::numeric / '0'; 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'inf'::numeric % '0'; 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.796 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '-inf'::numeric % '0'; 2025-07-03 22:04:58.803 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.803 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '0'::numeric % '0'; 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT div('inf'::numeric, '0'); 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT div('-inf'::numeric, '0'); 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:58.805 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT div('0'::numeric, '0'); 2025-07-03 22:04:58.811 UTC client backend[14781] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-07-03 22:04:58.811 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT sqrt('-1'::numeric); 2025-07-03 22:04:58.811 UTC client backend[14781] pg_regress/numeric ERROR: cannot take square root of a negative number 2025-07-03 22:04:58.811 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT sqrt('-inf'::numeric); 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT ln('0'::numeric); 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT ln('-1'::numeric); 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.812 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT ln('-inf'::numeric); 2025-07-03 22:04:58.813 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:58.813 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('0'::numeric, '10'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '0'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, '10'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('10'::numeric, '-inf'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '0'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('inf'::numeric, '-inf'); 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:58.815 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT log('-inf'::numeric, 'inf'); 2025-07-03 22:04:58.817 UTC client backend[14781] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-07-03 22:04:58.817 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-1'); 2025-07-03 22:04:58.818 UTC client backend[14781] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-07-03 22:04:58.818 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT power('0'::numeric, '-inf'); 2025-07-03 22:04:58.818 UTC client backend[14781] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-07-03 22:04:58.818 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '3.3'); 2025-07-03 22:04:58.824 UTC client backend[14781] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-07-03 22:04:58.824 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT power('-2'::numeric, '-1.5'); 2025-07-03 22:04:58.829 UTC client backend[14781] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-07-03 22:04:58.829 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT power('-inf'::numeric, '4.5'); 2025-07-03 22:04:58.858 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:58.858 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-07-03 22:04:58.858 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (3, '1.0'); 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 4, scale 4 must round to an absolute value less than 1. 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (6, '0.99995'); 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-07-03 22:04:58.867 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (10, 'Inf'); 2025-07-03 22:04:58.868 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:58.868 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 4, scale 4 cannot hold an infinite value. 2025-07-03 22:04:58.868 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO fract_only VALUES (11, '-Inf'); 2025-07-03 22:04:58.875 UTC client backend[14781] pg_regress/numeric ERROR: bigint out of range 2025-07-03 22:04:58.875 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT (-9223372036854775808.5)::int8; 2025-07-03 22:04:58.878 UTC client backend[14781] pg_regress/numeric ERROR: bigint out of range 2025-07-03 22:04:58.878 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 9223372036854775807.5::int8; 2025-07-03 22:04:58.879 UTC client backend[14781] pg_regress/numeric ERROR: integer out of range 2025-07-03 22:04:58.879 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT (-2147483648.5)::int4; 2025-07-03 22:04:58.880 UTC client backend[14781] pg_regress/numeric ERROR: integer out of range 2025-07-03 22:04:58.880 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 2147483647.5::int4; 2025-07-03 22:04:58.880 UTC client backend[14781] pg_regress/numeric ERROR: smallint out of range 2025-07-03 22:04:58.880 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT (-32768.5)::int2; 2025-07-03 22:04:58.881 UTC client backend[14781] pg_regress/numeric ERROR: smallint out of range 2025-07-03 22:04:58.881 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 32767.5::int2; 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert NaN to smallint 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int2; 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int2; 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to smallint 2025-07-03 22:04:58.893 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int2; 2025-07-03 22:04:58.894 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert NaN to integer 2025-07-03 22:04:58.894 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int4; 2025-07-03 22:04:58.894 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-07-03 22:04:58.894 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int4; 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to integer 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int4; 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert NaN to bigint 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'NaN'::numeric::int8; 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT 'Infinity'::numeric::int8; 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert infinity to bigint 2025-07-03 22:04:58.895 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT '-Infinity'::numeric::int8; 2025-07-03 22:04:58.915 UTC client backend[14780] pg_regress/bit ERROR: negative substring length not allowed 2025-07-03 22:04:58.915 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error"; 2025-07-03 22:04:58.916 UTC client backend[14780] pg_regress/bit ERROR: negative substring length not allowed 2025-07-03 22:04:58.916 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error"; 2025-07-03 22:04:58.941 UTC client backend[14781] pg_regress/numeric ERROR: value overflows numeric format 2025-07-03 22:04:58.941 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT round(5.5e131071, -131072); 2025-07-03 22:04:58.946 UTC client backend[14781] pg_regress/numeric ERROR: count must be greater than zero 2025-07-03 22:04:58.946 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, 0); 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric ERROR: count must be greater than zero 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0, 3.0, 4.0, -5); 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5, 3.0, 3.0, 888); 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric ERROR: count must be greater than zero 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0); 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric ERROR: count must be greater than zero 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5); 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric ERROR: lower bound cannot equal upper bound 2025-07-03 22:04:58.948 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888); 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0, 'NaN', 4.0, 888); 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds cannot be NaN 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888); 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.950 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(2.0, 3.0, '-inf', 888); 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit ERROR: cannot AND bit strings of different sizes 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit STATEMENT: select B'001' & B'10'; 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit ERROR: cannot OR bit strings of different sizes 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit STATEMENT: select B'0111' | B'011'; 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit ERROR: cannot XOR bit strings of different sizes 2025-07-03 22:04:58.951 UTC client backend[14780] pg_regress/bit STATEMENT: select B'0010' # B'011101'; 2025-07-03 22:04:58.955 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.955 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888); 2025-07-03 22:04:58.967 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.967 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10); 2025-07-03 22:04:58.967 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.967 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20); 2025-07-03 22:04:58.971 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.971 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10); 2025-07-03 22:04:58.971 UTC client backend[14781] pg_regress/numeric ERROR: lower and upper bounds must be finite 2025-07-03 22:04:58.971 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20); 2025-07-03 22:04:58.987 UTC client backend[14781] pg_regress/numeric ERROR: integer out of range 2025-07-03 22:04:58.987 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(1::float8, 0, 1, 2147483647); 2025-07-03 22:04:58.987 UTC client backend[14781] pg_regress/numeric ERROR: integer out of range 2025-07-03 22:04:58.987 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT width_bucket(0::float8, 1, 0, 2147483647); 2025-07-03 22:04:59.000 UTC client backend[14780] pg_regress/bit ERROR: bit index 16 out of valid range (0..15) 2025-07-03 22:04:59.000 UTC client backend[14780] pg_regress/bit STATEMENT: SELECT set_bit(B'0101011000100100', 16, 1); 2025-07-03 22:04:59.074 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.074 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('viv', 'RN'); 2025-07-03 22:04:59.074 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.074 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('DCCCD', 'RN'); 2025-07-03 22:04:59.078 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.078 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('XIXL', 'RN'); 2025-07-03 22:04:59.078 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.078 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('MCCM', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('MMMM', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('VV', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('IL', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('VIX', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('LXC', 'RN'); 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.079 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('DCM', 'RN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('MMMDCM', 'RN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('CLXC', 'RN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: "RN" is incompatible with other formats 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric DETAIL: "RN" may only be used together with "FM". 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'MIRN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: cannot use "RN" twice 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('CM', 'RNRN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('qiv', 'RN'); 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " 2025-07-03 22:04:59.080 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number('', 'RN'); 2025-07-03 22:04:59.081 UTC client backend[14781] pg_regress/numeric ERROR: invalid Roman numeral 2025-07-03 22:04:59.081 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT to_number(' ', 'RN'); 2025-07-03 22:04:59.105 UTC client backend[14779] pg_regress/boolean LOG: disconnection: session time: 0:00:01.120 user=postgres database=regression host=[local] 2025-07-03 22:04:59.105 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: " " at character 40 2025-07-03 22:04:59.105 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' '); 2025-07-03 22:04:59.106 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: " 1234 %" at character 40 2025-07-03 22:04:59.106 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' 1234 %'); 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "xyz" at character 40 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('xyz'); 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "- 1234" at character 40 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('- 1234'); 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5 . 0" at character 40 2025-07-03 22:04:59.107 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5 . 0'); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "5. 0 " at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('5. 0 '); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (''); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: " N aN " at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES (' N aN '); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+NaN" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+NaN'); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "-NaN" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('-NaN'); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "+ infinity" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('+ infinity'); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "_123" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('_123'); 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_" at character 40 2025-07-03 22:04:59.108 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "12__34" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('12__34'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123_.456" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123_.456'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "123._456" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('123._456'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e_34" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e_34'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e34_" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e34_'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "1.2e3__4" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('1.2e3__4'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0b1112" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0b1112'); 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0c1112" at character 40 2025-07-03 22:04:59.109 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0c1112'); 2025-07-03 22:04:59.110 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0o12345678" at character 40 2025-07-03 22:04:59.110 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0o12345678'); 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1eg" at character 40 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1eg'); 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12.34" at character 40 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12.34'); 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x__1234" at character 40 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x__1234'); 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x1234_" at character 40 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x1234_'); 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric ERROR: invalid input syntax for type numeric: "0x12__34" at character 40 2025-07-03 22:04:59.115 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_input_test(n1) VALUES ('0x12__34'); 2025-07-03 22:04:59.163 UTC client backend[14780] pg_regress/bit LOG: disconnection: session time: 0:00:01.154 user=postgres database=regression host=[local] 2025-07-03 22:04:59.266 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.266 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale -6 cannot hold an infinite value. 2025-07-03 22:04:59.266 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES ('inf'); 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale -6 must round to an absolute value less than 10^9. 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millions) VALUES (999500000); 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale -3 must round to an absolute value less than 10^6. 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousands) VALUES (999500); 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale 0 must round to an absolute value less than 10^3. 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (units) VALUES (999.5); 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale 3 must round to an absolute value less than 1. 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (thousandths) VALUES (0.9995); 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric ERROR: numeric field overflow 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric DETAIL: A field with precision 3, scale 6 must round to an absolute value less than 10^-3. 2025-07-03 22:04:59.274 UTC client backend[14781] pg_regress/numeric STATEMENT: INSERT INTO num_typemod_test (millionths) VALUES (0.0009995); 2025-07-03 22:04:59.313 UTC client backend[14781] pg_regress/numeric ERROR: value overflows numeric format 2025-07-03 22:04:59.313 UTC client backend[14781] pg_regress/numeric STATEMENT: select 10.0 ^ 2147483647 as overflows; 2025-07-03 22:04:59.313 UTC client backend[14781] pg_regress/numeric ERROR: value overflows numeric format 2025-07-03 22:04:59.313 UTC client backend[14781] pg_regress/numeric STATEMENT: select 117743296169.0 ^ 1000000000 as overflows; 2025-07-03 22:04:59.325 UTC client backend[14781] pg_regress/numeric ERROR: zero raised to a negative power is undefined 2025-07-03 22:04:59.325 UTC client backend[14781] pg_regress/numeric STATEMENT: select 0.0 ^ (-12.34); 2025-07-03 22:04:59.326 UTC client backend[14781] pg_regress/numeric ERROR: a negative number raised to a non-integer power yields a complex result 2025-07-03 22:04:59.326 UTC client backend[14781] pg_regress/numeric STATEMENT: select (-12.34) ^ 1.2; 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric ERROR: step size cannot equal zero 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 0::numeric); 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric ERROR: step size cannot be NaN 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric); 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric ERROR: start value cannot be NaN 2025-07-03 22:04:59.338 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series('nan'::numeric, 100::numeric, 10::numeric); 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric ERROR: stop value cannot be NaN 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric); 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric ERROR: start value cannot be infinity 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric); 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric ERROR: stop value cannot be infinity 2025-07-03 22:04:59.339 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric); 2025-07-03 22:04:59.341 UTC client backend[14781] pg_regress/numeric ERROR: step size cannot be infinity 2025-07-03 22:04:59.341 UTC client backend[14781] pg_regress/numeric STATEMENT: select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric); 2025-07-03 22:04:59.344 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:59.344 UTC client backend[14781] pg_regress/numeric STATEMENT: select ln(-12.34); 2025-07-03 22:04:59.349 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:59.349 UTC client backend[14781] pg_regress/numeric STATEMENT: select ln(0.0); 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(-12.34); 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric CONTEXT: SQL function "log" statement 1 2025-07-03 22:04:59.351 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(0.0); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(-12.34, 56.78); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(-12.34, -56.78); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of a negative number 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(12.34, -56.78); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(0.0, 12.34); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: cannot take logarithm of zero 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(12.34, 0.0); 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric ERROR: division by zero 2025-07-03 22:04:59.359 UTC client backend[14781] pg_regress/numeric STATEMENT: select log(1.0, 12.34); 2025-07-03 22:04:59.501 UTC client backend[14781] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp14781.0", size 1400000 2025-07-03 22:04:59.501 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT SUM(9999::numeric) FROM generate_series(1, 100000); 2025-07-03 22:04:59.672 UTC client backend[14781] pg_regress/numeric LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp14781.1", size 1400000 2025-07-03 22:04:59.672 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT SUM((-9999)::numeric) FROM generate_series(1, 100000); 2025-07-03 22:04:59.930 UTC client backend[14781] pg_regress/numeric ERROR: value overflows numeric format 2025-07-03 22:04:59.930 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2); 2025-07-03 22:04:59.931 UTC client backend[14781] pg_regress/numeric ERROR: value overflows numeric format 2025-07-03 22:04:59.931 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT factorial(100000); 2025-07-03 22:04:59.931 UTC client backend[14781] pg_regress/numeric ERROR: factorial of a negative number is undefined 2025-07-03 22:04:59.931 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT factorial(-4); 2025-07-03 22:04:59.932 UTC client backend[14781] pg_regress/numeric ERROR: pg_lsn out of range 2025-07-03 22:04:59.932 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT pg_lsn(-1::numeric); 2025-07-03 22:04:59.933 UTC client backend[14781] pg_regress/numeric ERROR: pg_lsn out of range 2025-07-03 22:04:59.933 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT pg_lsn(18446744073709551616::numeric); 2025-07-03 22:04:59.934 UTC client backend[14781] pg_regress/numeric ERROR: cannot convert NaN to pg_lsn 2025-07-03 22:04:59.934 UTC client backend[14781] pg_regress/numeric STATEMENT: SELECT pg_lsn('NaN'::numeric); 2025-07-03 22:04:59.938 UTC client backend[14781] pg_regress/numeric LOG: disconnection: session time: 0:00:01.927 user=postgres database=regression host=[local] 2025-07-03 22:05:00.058 UTC client backend[14783] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_room_during_excl" 2025-07-03 22:05:00.058 UTC client backend[14783] 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-07-03 22:05:00.058 UTC client backend[14783] 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-07-03 22:05:00.059 UTC client backend[14783] pg_regress/rangetypes ERROR: conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl" 2025-07-03 22:05:00.059 UTC client backend[14783] 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-07-03 22:05:00.059 UTC client backend[14783] 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-07-03 22:05:00.061 UTC client backend[14783] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-07-03 22:05:00.061 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange; 2025-07-03 22:05:00.062 UTC client backend[14783] pg_regress/rangetypes ERROR: function float4mi(double precision, double precision) does not exist 2025-07-03 22:05:00.062 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi); 2025-07-03 22:05:00.085 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot drop type mydomain because other objects depend on it 2025-07-03 22:05:00.085 UTC client backend[14783] pg_regress/rangetypes DETAIL: type mydomainrange depends on type mydomain 2025-07-03 22:05:00.085 UTC client backend[14783] pg_regress/rangetypes HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:00.085 UTC client backend[14783] pg_regress/rangetypes STATEMENT: drop domain mydomain; 2025-07-03 22:05:00.097 UTC client backend[14783] pg_regress/rangetypes ERROR: value for domain restrictedrange violates check constraint "restrictedrange_check" 2025-07-03 22:05:00.097 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select '[4,50)'::restrictedrange @> 7; 2025-07-03 22:05:00.111 UTC client backend[14783] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:05:00.111 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select textrange1('a','Z') @> 'b'::text; 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes ERROR: function anyarray_anyrange_func(integer[], numrange) does not exist at character 8 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20)); 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:00.130 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function bogus_func(anyelement) returns anyrange as 'select int4range(1,10)' language sql; 2025-07-03 22:05:00.131 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.131 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:00.131 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function bogus_func(int) returns anyrange as 'select int4range(1,10)' language sql; 2025-07-03 22:05:00.136 UTC client backend[14783] pg_regress/rangetypes ERROR: function rangetypes_sql(numrange, integer[]) does not exist at character 8 2025-07-03 22:05:00.136 UTC client backend[14783] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:00.136 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select rangetypes_sql(numrange(1,10), ARRAY[2,20]); 2025-07-03 22:05:00.138 UTC client backend[14783] pg_regress/rangetypes ERROR: function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8 2025-07-03 22:05:00.138 UTC client backend[14783] pg_regress/rangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:00.138 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20)); 2025-07-03 22:05:00.139 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.139 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-07-03 22:05:00.139 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-07-03 22:05:00.165 UTC client backend[14783] pg_regress/rangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:05:00.165 UTC client backend[14783] pg_regress/rangetypes STATEMENT: select arrayrange(ARRAY[2,1], ARRAY[1,2]); 2025-07-03 22:05:00.176 UTC client backend[14783] pg_regress/rangetypes ERROR: composite type two_ints cannot be made a member of itself 2025-07-03 22:05:00.176 UTC client backend[14783] pg_regress/rangetypes STATEMENT: alter type two_ints add attribute c two_ints_range; 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function outparam_fail(i anyelement, out r anyrange, out t text) as $$ select '[1,10]', 'foo' $$ language sql; 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function inoutparam_fail(inout i anyelement, out r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes ERROR: cannot determine result data type 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes DETAIL: A result of type anyrange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:00.210 UTC client backend[14783] pg_regress/rangetypes STATEMENT: create function table_fail(i anyelement) returns table(i anyelement, r anyrange) as $$ select $1, '[1,10]' $$ language sql; 2025-07-03 22:05:00.278 UTC client backend[14783] pg_regress/rangetypes LOG: disconnection: session time: 0:00:02.259 user=postgres database=regression host=[local] 2025-07-03 22:05:00.729 UTC not initialized[15123] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.730 UTC client backend[15123] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.730 UTC client backend[15123] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/strings 2025-07-03 22:05:00.750 UTC client backend[15123] pg_regress/strings LOG: connection ready: setup total=34.101 ms, fork=12.378 ms, authentication=0.423 ms 2025-07-03 22:05:00.755 UTC not initialized[15128] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.757 UTC client backend[15128] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.757 UTC client backend[15128] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/md5 2025-07-03 22:05:00.763 UTC client backend[15123] pg_regress/strings ERROR: syntax error at or near "' - third line'" at character 75 2025-07-03 22:05:00.763 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT 'first line' ' - next line' /* this comment is not allowed here */ ' - third line' AS "Illegal comment within continuation"; 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape at character 18 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings HINT: Unicode escapes must be \XXXX or \+XXXXXX. 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings ERROR: UESCAPE must be followed by a simple string literal at or near "+" at character 33 2025-07-03 22:05:00.765 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE +; 2025-07-03 22:05:00.768 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape character at or near "'+'" at character 33 2025-07-03 22:05:00.768 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-07-03 22:05:00.768 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-07-03 22:05:00.768 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99xy'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\\'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 23 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \db99\0061'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at character 26 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \+00db99\+000061'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape value at character 18 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \+2FFFFF'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \u061'; 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape at character 17 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings HINT: Unicode escapes must be \uXXXX or \UXXXXXXXX. 2025-07-03 22:05:00.769 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \U0061'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "'" at character 23 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "x" at character 23 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99xy'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\" at character 23 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\\'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\u0061" at character 23 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \udb99\u0061'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair at or near "\U00000061" at character 27 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \U0000db99\U00000061'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape value at or near "\U002FFFFF" at character 17 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'wrong: \U002FFFFF'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061"; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*'; 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.770 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&' \' UESCAPE '!' AS "tricky"; 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \061'; 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: \+0061'; 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings ERROR: unsafe use of string constant with Unicode escapes at character 8 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings DETAIL: String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off. 2025-07-03 22:05:00.771 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT U&'wrong: +0061' UESCAPE '+'; 2025-07-03 22:05:00.777 UTC client backend[15128] pg_regress/md5 LOG: connection ready: setup total=40.536 ms, fork=17.827 ms, authentication=0.393 ms 2025-07-03 22:05:00.778 UTC client backend[15123] pg_regress/strings ERROR: invalid hexadecimal data: odd number of digits at character 8 2025-07-03 22:05:00.778 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeE'::bytea; 2025-07-03 22:05:00.778 UTC client backend[15123] pg_regress/strings ERROR: invalid hexadecimal digit: "x" at character 8 2025-07-03 22:05:00.778 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'\\xDeAdBeEx'::bytea; 2025-07-03 22:05:00.779 UTC client backend[15123] pg_regress/strings ERROR: invalid input syntax for type bytea at character 8 2025-07-03 22:05:00.779 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT E'De\\678dBeEf'::bytea; 2025-07-03 22:05:00.794 UTC not initialized[15134] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.799 UTC not initialized[15135] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.808 UTC not initialized[15136] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.809 UTC client backend[15136] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.809 UTC client backend[15136] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/date 2025-07-03 22:05:00.814 UTC not initialized[15137] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.814 UTC client backend[15128] pg_regress/md5 LOG: disconnection: session time: 0:00:00.060 user=postgres database=regression host=[local] 2025-07-03 22:05:00.815 UTC client backend[15134] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.815 UTC client backend[15134] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/numerology 2025-07-03 22:05:00.819 UTC client backend[15135] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.819 UTC client backend[15135] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/lseg 2025-07-03 22:05:00.821 UTC client backend[15134] pg_regress/numerology LOG: connection ready: setup total=48.054 ms, fork=19.359 ms, authentication=6.802 ms 2025-07-03 22:05:00.822 UTC client backend[15135] pg_regress/lseg LOG: connection ready: setup total=38.729 ms, fork=14.394 ms, authentication=10.666 ms 2025-07-03 22:05:00.823 UTC not initialized[15141] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.825 UTC client backend[15137] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.825 UTC client backend[15137] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/point 2025-07-03 22:05:00.828 UTC not initialized[15138] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.830 UTC client backend[15138] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.830 UTC client backend[15138] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/path 2025-07-03 22:05:00.831 UTC not initialized[15140] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.833 UTC client backend[15140] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.833 UTC client backend[15140] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timetz 2025-07-03 22:05:00.835 UTC client backend[15141] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.835 UTC client backend[15141] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/line 2025-07-03 22:05:00.836 UTC client backend[15136] pg_regress/date LOG: connection ready: setup total=49.554 ms, fork=17.213 ms, authentication=0.381 ms 2025-07-03 22:05:00.839 UTC client backend[15137] pg_regress/point LOG: connection ready: setup total=49.406 ms, fork=21.941 ms, authentication=0.429 ms 2025-07-03 22:05:00.839 UTC not initialized[15143] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.839 UTC not initialized[15142] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.841 UTC client backend[15143] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.841 UTC client backend[15142] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.841 UTC client backend[15143] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/inet 2025-07-03 22:05:00.841 UTC client backend[15142] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/box 2025-07-03 22:05:00.843 UTC client backend[15141] pg_regress/line LOG: connection ready: setup total=29.294 ms, fork=8.265 ms, authentication=10.523 ms 2025-07-03 22:05:00.843 UTC client backend[15140] pg_regress/timetz LOG: connection ready: setup total=30.972 ms, fork=10.229 ms, authentication=0.421 ms 2025-07-03 22:05:00.848 UTC client backend[15137] pg_regress/point ERROR: invalid input syntax for type point: "asdfasdf" at character 35 2025-07-03 22:05:00.848 UTC client backend[15137] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf'); 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point ERROR: invalid input syntax for type point: "(10.0 10.0)" at character 35 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)'); 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point ERROR: invalid input syntax for type point: "(10.0, 10.0) x" at character 35 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x'); 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point ERROR: invalid input syntax for type point: "(10.0,10.0" at character 35 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0'); 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point ERROR: "1e+500" is out of range for type double precision at character 35 2025-07-03 22:05:00.849 UTC client backend[15137] pg_regress/point STATEMENT: INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)'); 2025-07-03 22:05:00.850 UTC not initialized[15145] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.852 UTC client backend[15145] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.852 UTC client backend[15145] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/circle 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "123abc" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 123abc; 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0o" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0x0o; 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.a" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0.a; 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0a" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0.0a; 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near ".0a" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT .0a; 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e1a" at character 8 2025-07-03 22:05:00.852 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0.0e1a; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e" at character 8 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0.0e; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0.0e+" at character 8 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0.0e+a; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after parameter at or near "$1a" at character 22 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $1a; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: parameter number too large at or near "$2147483648" at character 22 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $2147483648; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: invalid binary integer at or near "0b" at character 8 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0b; 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1b" at character 8 2025-07-03 22:05:00.853 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1b; 2025-07-03 22:05:00.855 UTC client backend[15145] pg_regress/circle LOG: connection ready: setup total=18.072 ms, fork=11.874 ms, authentication=0.390 ms 2025-07-03 22:05:00.856 UTC client backend[15138] pg_regress/path LOG: connection ready: setup total=58.384 ms, fork=27.143 ms, authentication=0.396 ms 2025-07-03 22:05:00.861 UTC client backend[15123] pg_regress/strings ERROR: negative substring length not allowed 2025-07-03 22:05:00.861 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error"; 2025-07-03 22:05:00.862 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0b0x" at character 8 2025-07-03 22:05:00.862 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0b0x; 2025-07-03 22:05:00.862 UTC client backend[15143] pg_regress/inet LOG: connection ready: setup total=40.660 ms, fork=15.769 ms, authentication=0.405 ms 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology ERROR: invalid octal integer at or near "0o" at character 8 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0o; 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1o" at character 8 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1o; 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0o0x" at character 8 2025-07-03 22:05:00.864 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0o0x; 2025-07-03 22:05:00.865 UTC not initialized[15147] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology ERROR: invalid hexadecimal integer at or near "0x" at character 8 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0x; 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1x" at character 8 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1x; 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "0x0y" at character 8 2025-07-03 22:05:00.865 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 0x0y; 2025-07-03 22:05:00.866 UTC client backend[15147] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.866 UTC client backend[15147] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamp 2025-07-03 22:05:00.867 UTC client backend[15140] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32 2025-07-03 22:05:00.867 UTC client backend[15140] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York'); 2025-07-03 22:05:00.867 UTC client backend[15140] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 m2" at character 32 2025-07-03 22:05:00.867 UTC client backend[15140] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2'); 2025-07-03 22:05:00.867 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "1997-02-29" at character 30 2025-07-03 22:05:00.867 UTC client backend[15136] pg_regress/date STATEMENT: INSERT INTO DATE_TBL VALUES ('1997-02-29'); 2025-07-03 22:05:00.868 UTC not initialized[15146] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.870 UTC client backend[15146] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.870 UTC client backend[15146] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/polygon 2025-07-03 22:05:00.872 UTC client backend[15142] pg_regress/box LOG: connection ready: setup total=54.232 ms, fork=16.442 ms, authentication=0.386 ms 2025-07-03 22:05:00.875 UTC client backend[15143] pg_regress/inet ERROR: table "inet_tbl" does not exist 2025-07-03 22:05:00.875 UTC client backend[15143] pg_regress/inet STATEMENT: DROP TABLE INET_TBL; 2025-07-03 22:05:00.877 UTC not initialized[15149] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.877 UTC client backend[15135] pg_regress/lseg ERROR: invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30 2025-07-03 22:05:00.877 UTC client backend[15135] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[1,2,3, 4" at character 30 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4'); 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]'); 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg ERROR: invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30 2025-07-03 22:05:00.878 UTC client backend[15135] pg_regress/lseg STATEMENT: INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)'); 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology ERROR: column "_100" does not exist at character 8 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT _100; 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100_" at character 8 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 100_; 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "100__000" at character 8 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 100__000; 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology ERROR: syntax error at or near ".5" at character 14 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT _1_000.5; 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000_" at character 8 2025-07-03 22:05:00.881 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1_000_.5; 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000._5" at character 8 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1_000._5; 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5_" at character 8 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1_000.5_; 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after numeric literal at or near "1_000.5e_1" at character 8 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology STATEMENT: SELECT 1_000.5e_1; 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology ERROR: trailing junk after parameter at or near "$0_1" at character 22 2025-07-03 22:05:00.882 UTC client backend[15134] pg_regress/numerology STATEMENT: PREPARE p1 AS SELECT $0_1; 2025-07-03 22:05:00.883 UTC not initialized[15148] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.885 UTC client backend[15123] pg_regress/strings ERROR: SQL regular expression may not contain more than two escape-double-quote separators 2025-07-03 22:05:00.885 UTC client backend[15123] pg_regress/strings CONTEXT: SQL function "substring" statement 1 2025-07-03 22:05:00.885 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error"; 2025-07-03 22:05:00.885 UTC client backend[15149] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.885 UTC client backend[15149] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/timestamptz 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "{}" at character 30 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{}'); 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "{0" at character 30 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0'); 2025-07-03 22:05:00.886 UTC client backend[15140] pg_regress/timetz ERROR: invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32 2025-07-03 22:05:00.886 UTC client backend[15140] pg_regress/timetz STATEMENT: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2'); 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "{0,0}" at character 30 2025-07-03 22:05:00.886 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0}'); 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1" at character 30 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1'); 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line ERROR: invalid line specification: A and B cannot both be zero at character 30 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1}'); 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "{0,0,1} x" at character 30 2025-07-03 22:05:00.887 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('{0,0,1} x'); 2025-07-03 22:05:00.887 UTC client backend[15148] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.887 UTC client backend[15148] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/time 2025-07-03 22:05:00.888 UTC client backend[15135] pg_regress/lseg LOG: disconnection: session time: 0:00:00.090 user=postgres database=regression host=[local] 2025-07-03 22:05:00.890 UTC client backend[15148] pg_regress/time LOG: connection ready: setup total=46.031 ms, fork=34.091 ms, authentication=0.419 ms 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle ERROR: invalid input syntax for type circle: "<(-100,0),-100>" at character 32 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>'); 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10" at character 32 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10'); 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle ERROR: invalid input syntax for type circle: "<(100,200),10> x" at character 32 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x'); 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle ERROR: invalid input syntax for type circle: "1abc,3,5" at character 32 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5'); 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle ERROR: invalid input syntax for type circle: "(3,(1,2),3)" at character 32 2025-07-03 22:05:00.899 UTC client backend[15145] pg_regress/circle STATEMENT: INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)'); 2025-07-03 22:05:00.900 UTC client backend[15146] pg_regress/polygon LOG: connection ready: setup total=60.474 ms, fork=22.277 ms, authentication=0.408 ms 2025-07-03 22:05:00.903 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30 2025-07-03 22:05:00.903 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)'); 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "[1,2,3, 4" at character 30 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[1,2,3, 4'); 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "[(,2),(3,4)]" at character 30 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]'); 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line ERROR: invalid input syntax for type line: "[(1,2),(3,4)" at character 30 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)'); 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line ERROR: invalid line specification: must be two distinct points at character 30 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]'); 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line ERROR: invalid line specification: must be two distinct points 2025-07-03 22:05:00.904 UTC client backend[15141] pg_regress/line STATEMENT: INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)')); 2025-07-03 22:05:00.908 UTC client backend[15147] pg_regress/timestamp LOG: connection ready: setup total=66.268 ms, fork=20.412 ms, authentication=0.540 ms 2025-07-03 22:05:00.912 UTC client backend[15140] pg_regress/timetz ERROR: date/time field value out of range: "24:00:00.01 PDT" at character 8 2025-07-03 22:05:00.912 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT '24:00:00.01 PDT'::timetz; 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz ERROR: date/time field value out of range: "23:59:60.01 PDT" at character 8 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT '23:59:60.01 PDT'::timetz; 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz ERROR: date/time field value out of range: "24:01:00 PDT" at character 8 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT '24:01:00 PDT'::timetz; 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz ERROR: date/time field value out of range: "25:00:00 PDT" at character 8 2025-07-03 22:05:00.913 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT '25:00:00 PDT'::timetz; 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path ERROR: invalid input syntax for type path: "[]" at character 30 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[]'); 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path ERROR: invalid input syntax for type path: "[(,2),(3,4)]" at character 30 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]'); 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path ERROR: invalid input syntax for type path: "[(1,2),(3,4)" at character 30 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)'); 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path ERROR: invalid input syntax for type path: "(1,2,3,4" at character 30 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2,3,4'); 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path ERROR: invalid input syntax for type path: "(1,2),(3,4)]" at character 30 2025-07-03 22:05:00.917 UTC client backend[15138] pg_regress/path STATEMENT: INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]'); 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 37 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226'); 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet ERROR: invalid input syntax for type cidr: "1234::1234::1234" at character 37 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4'); 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet ERROR: invalid cidr value: "192.168.1.2/30" at character 42 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-07-03 22:05:00.923 UTC client backend[15143] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226'); 2025-07-03 22:05:00.923 UTC not initialized[15154] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.924 UTC not initialized[15152] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.924 UTC not initialized[15150] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.925 UTC client backend[15154] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.925 UTC client backend[15154] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/multirangetypes 2025-07-03 22:05:00.925 UTC not initialized[15151] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:00.926 UTC client backend[15151] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.926 UTC client backend[15151] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/interval 2025-07-03 22:05:00.927 UTC client backend[15143] pg_regress/inet ERROR: invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42 2025-07-03 22:05:00.927 UTC client backend[15143] pg_regress/inet DETAIL: Value has bits set to right of mask. 2025-07-03 22:05:00.927 UTC client backend[15143] pg_regress/inet STATEMENT: INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226'); 2025-07-03 22:05:00.929 UTC client backend[15142] pg_regress/box ERROR: invalid input syntax for type box: "(2.3, 4.5)" at character 34 2025-07-03 22:05:00.929 UTC client backend[15142] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)'); 2025-07-03 22:05:00.929 UTC client backend[15123] pg_regress/strings ERROR: invalid escape string 2025-07-03 22:05:00.929 UTC client backend[15123] pg_regress/strings HINT: Escape string must be empty or one character. 2025-07-03 22:05:00.929 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error; 2025-07-03 22:05:00.929 UTC client backend[15142] pg_regress/box ERROR: invalid input syntax for type box: "[1, 2, 3, 4)" at character 34 2025-07-03 22:05:00.929 UTC client backend[15142] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)'); 2025-07-03 22:05:00.930 UTC client backend[15140] pg_regress/timetz ERROR: operator does not exist: time with time zone + time with time zone at character 11 2025-07-03 22:05:00.930 UTC client backend[15140] pg_regress/timetz HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:00.930 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL; 2025-07-03 22:05:00.932 UTC client backend[15140] pg_regress/timetz ERROR: unit "day" not supported for type time with time zone 2025-07-03 22:05:00.932 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT EXTRACT(DAY FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-07-03 22:05:00.932 UTC client backend[15140] pg_regress/timetz ERROR: unit "fortnight" not recognized for type time with time zone 2025-07-03 22:05:00.932 UTC client backend[15140] pg_regress/timetz STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04'); 2025-07-03 22:05:00.933 UTC client backend[15152] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.933 UTC client backend[15152] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4]" at character 34 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]'); 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "1/8/1999" at character 13 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1/8/1999'; 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box ERROR: invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x'); 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.934 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-07-03 22:05:00.934 UTC client backend[15150] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:00.934 UTC client backend[15150] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/macaddr8 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box ERROR: invalid input syntax for type box: "asdfasdf(ad" at character 34 2025-07-03 22:05:00.934 UTC client backend[15142] pg_regress/box STATEMENT: INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad'); 2025-07-03 22:05:00.935 UTC client backend[15149] pg_regress/timestamptz LOG: connection ready: setup total=76.023 ms, fork=16.638 ms, authentication=7.305 ms 2025-07-03 22:05:00.938 UTC client backend[15150] pg_regress/macaddr8 LOG: connection ready: setup total=63.586 ms, fork=44.175 ms, authentication=6.691 ms 2025-07-03 22:05:00.940 UTC client backend[15141] pg_regress/line LOG: disconnection: session time: 0:00:00.117 user=postgres database=regression host=[local] 2025-07-03 22:05:00.943 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "January 8, 99 BC" at character 13 2025-07-03 22:05:00.943 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.943 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date 'January 8, 99 BC'; 2025-07-03 22:05:00.945 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08-Jan-99" at character 13 2025-07-03 22:05:00.945 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.945 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08-Jan-99'; 2025-07-03 22:05:00.946 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "Jan-08-99" at character 13 2025-07-03 22:05:00.946 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.946 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date 'Jan-08-99'; 2025-07-03 22:05:00.947 UTC client backend[15151] pg_regress/interval LOG: connection ready: setup total=68.556 ms, fork=40.858 ms, authentication=0.404 ms 2025-07-03 22:05:00.947 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-07-03 22:05:00.947 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-07-03 22:05:00.947 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-07-03 22:05:00.947 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-07-03 22:05:00.947 UTC client backend[15145] pg_regress/circle LOG: disconnection: session time: 0:00:00.098 user=postgres database=regression host=[local] 2025-07-03 22:05:00.948 UTC client backend[15148] pg_regress/time ERROR: invalid input syntax for type time: "15:36:39 America/New_York" at character 30 2025-07-03 22:05:00.948 UTC client backend[15148] pg_regress/time STATEMENT: INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York'); 2025-07-03 22:05:00.948 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08 Jan 99" at character 13 2025-07-03 22:05:00.948 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.948 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08 Jan 99'; 2025-07-03 22:05:00.949 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "Jan 08 99" at character 13 2025-07-03 22:05:00.949 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.949 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date 'Jan 08 99'; 2025-07-03 22:05:00.949 UTC client backend[15152] pg_regress/macaddr LOG: connection ready: setup total=69.894 ms, fork=38.583 ms, authentication=0.383 ms 2025-07-03 22:05:00.950 UTC client backend[15154] pg_regress/multirangetypes LOG: connection ready: setup total=47.594 ms, fork=18.703 ms, authentication=0.403 ms 2025-07-03 22:05:00.952 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "" at character 8 2025-07-03 22:05:00.952 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Missing left brace. 2025-07-03 22:05:00.952 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select ''::textmultirange; 2025-07-03 22:05:00.953 UTC client backend[15138] pg_regress/path LOG: disconnection: session time: 0:00:00.127 user=postgres database=regression host=[local] 2025-07-03 22:05:00.954 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08-01-99" at character 13 2025-07-03 22:05:00.954 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.954 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08-01-99'; 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08-01-1999" at character 13 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08-01-1999'; 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "01-08-99" at character 13 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '01-08-99'; 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "01-08-1999" at character 13 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.955 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '01-08-1999'; 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08 01 99" at character 13 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08 01 99'; 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "08 01 1999" at character 13 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '08 01 1999'; 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "01 08 99" at character 13 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.957 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '01 08 99'; 2025-07-03 22:05:00.958 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "01 08 1999" at character 13 2025-07-03 22:05:00.958 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.958 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '01 08 1999'; 2025-07-03 22:05:00.958 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-07-03 22:05:00.958 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z'); 2025-07-03 22:05:00.958 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,}" at character 8 2025-07-03 22:05:00.958 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected range start. 2025-07-03 22:05:00.958 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{,}'::textmultirange; 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(,)}." at character 8 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Junk after closing right brace. 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(,)}.'::textmultirange; 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,c),}" at character 8 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected range start. 2025-07-03 22:05:00.959 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{[a,c),}'::textmultirange; 2025-07-03 22:05:00.960 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{,[a,c)}" at character 8 2025-07-03 22:05:00.960 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected range start. 2025-07-03 22:05:00.960 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{,[a,c)}'::textmultirange; 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{-[a,z)}" at character 8 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected range start. 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{-[a,z)}'::textmultirange; 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{[a,z) - }" at character 8 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{[a,z) - }'::textmultirange; 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(",a)}" at character 8 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Unexpected end of input. 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(",a)}'::textmultirange; 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed range literal: "(,,a)" at character 8 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Too many commas. 2025-07-03 22:05:00.961 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(,,a)}'::textmultirange; 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed range literal: "()" at character 8 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(),a)}'::textmultirange; 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,))}" at character 8 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(a,))}'::textmultirange; 2025-07-03 22:05:00.962 UTC client backend[15148] pg_regress/time ERROR: date/time field value out of range: "24:00:00.01" at character 8 2025-07-03 22:05:00.962 UTC client backend[15148] pg_regress/time STATEMENT: SELECT '24:00:00.01'::time; 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed range literal: "(]" at character 8 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Missing comma after lower bound. 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(],a)}'::textmultirange; 2025-07-03 22:05:00.962 UTC client backend[15148] pg_regress/time ERROR: date/time field value out of range: "23:59:60.01" at character 8 2025-07-03 22:05:00.962 UTC client backend[15148] pg_regress/time STATEMENT: SELECT '23:59:60.01'::time; 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes ERROR: malformed multirange literal: "{(a,])}" at character 8 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Expected comma or end of multirange. 2025-07-03 22:05:00.962 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{(a,])}'::textmultirange; 2025-07-03 22:05:00.974 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "1/18/1999" at character 13 2025-07-03 22:05:00.974 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.974 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1/18/1999'; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03 123" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03 123'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "123 08:00:2b:01:02:03:04:05" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '123 08:00:2b:01:02:03:04:05'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05 123" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05 123'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8; 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8 2025-07-03 22:05:00.975 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08002b:01020304050607'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b01020304050607" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08002b01020304050607'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "0z002b0102030405" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '0z002b0102030405'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08002b010203xyza" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08002b010203xyza'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00-2b:01:02:03:04:05'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8 2025-07-03 22:05:00.976 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: SELECT '08:00:2b:01.02:03:04:05'::macaddr8; 2025-07-03 22:05:00.977 UTC client backend[15148] pg_regress/time ERROR: date/time field value out of range: "24:01:00" at character 8 2025-07-03 22:05:00.977 UTC client backend[15148] pg_regress/time STATEMENT: SELECT '24:01:00'::time; 2025-07-03 22:05:00.977 UTC client backend[15154] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound at character 8 2025-07-03 22:05:00.977 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{[z,a]}'::textmultirange; 2025-07-03 22:05:00.977 UTC client backend[15148] pg_regress/time ERROR: date/time field value out of range: "25:00:00" at character 8 2025-07-03 22:05:00.977 UTC client backend[15148] pg_regress/time STATEMENT: SELECT '25:00:00'::time; 2025-07-03 22:05:00.978 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-07-03 22:05:00.978 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.978 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-07-03 22:05:00.979 UTC client backend[15146] pg_regress/polygon ERROR: invalid input syntax for type polygon: "0.0" at character 37 2025-07-03 22:05:00.979 UTC client backend[15146] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('0.0'); 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0.0 0.0" at character 37 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0'); 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2)" at character 37 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)'); 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon ERROR: invalid input syntax for type polygon: "(0,1,2,3" at character 37 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3'); 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon ERROR: invalid input syntax for type polygon: "asdf" at character 37 2025-07-03 22:05:00.980 UTC client backend[15146] pg_regress/polygon STATEMENT: INSERT INTO POLYGON_TBL(f1) VALUES ('asdf'); 2025-07-03 22:05:00.983 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-07-03 22:05:00.983 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-07-03 22:05:00.985 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-07-03 22:05:00.985 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-07-03 22:05:00.985 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99 Jan 08" at character 13 2025-07-03 22:05:00.985 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.985 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-07-03 22:05:00.987 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-07-03 22:05:00.987 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-07-03 22:05:00.988 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-07-03 22:05:00.988 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.988 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-07-03 22:05:00.989 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "start": -1 2025-07-03 22:05:00.989 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i'); 2025-07-03 22:05:00.989 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "n": -1 2025-07-03 22:05:00.989 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i'); 2025-07-03 22:05:00.990 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression option: "1" 2025-07-03 22:05:00.990 UTC client backend[15123] pg_regress/strings HINT: If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly. 2025-07-03 22:05:00.990 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1'); 2025-07-03 22:05:00.991 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-07-03 22:05:00.991 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.991 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-07-03 22:05:00.992 UTC client backend[15152] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "0800:2b01:0203" at character 37 2025-07-03 22:05:00.992 UTC client backend[15152] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203'); 2025-07-03 22:05:00.994 UTC client backend[15152] pg_regress/macaddr ERROR: invalid input syntax for type macaddr: "not even close" at character 37 2025-07-03 22:05:00.994 UTC client backend[15152] pg_regress/macaddr STATEMENT: INSERT INTO macaddr_data VALUES (9, 'not even close'); 2025-07-03 22:05:00.994 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-07-03 22:05:00.994 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.994 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-07-03 22:05:00.997 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-07-03 22:05:00.997 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.997 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-07-03 22:05:00.999 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "18/1/1999" at character 13 2025-07-03 22:05:00.999 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:00.999 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '18/1/1999'; 2025-07-03 22:05:00.999 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-07-03 22:05:00.999 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', 0); 2025-07-03 22:05:01.001 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "start": -3 2025-07-03 22:05:01.001 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_count('123123123123', '123', -3); 2025-07-03 22:05:01.001 UTC client backend[15148] pg_regress/time ERROR: operator is not unique: time without time zone + time without time zone at character 11 2025-07-03 22:05:01.001 UTC client backend[15148] pg_regress/time HINT: Could not choose a best candidate operator. You might need to add explicit type casts. 2025-07-03 22:05:01.001 UTC client backend[15148] pg_regress/time STATEMENT: SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL; 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time ERROR: unit "day" not supported for type time without time zone 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time STATEMENT: SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time ERROR: unit "fortnight" not recognized for type time without time zone 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time STATEMENT: SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time ERROR: unit "timezone" not supported for type time without time zone 2025-07-03 22:05:01.003 UTC client backend[15148] pg_regress/time STATEMENT: SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); 2025-07-03 22:05:01.007 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-Jan-08" at character 13 2025-07-03 22:05:01.007 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:01.007 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-Jan-08'; 2025-07-03 22:05:01.011 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99-08-Jan" at character 13 2025-07-03 22:05:01.011 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-08-Jan'; 2025-07-03 22:05:01.011 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "1999-08-Jan" at character 13 2025-07-03 22:05:01.011 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '1999-08-Jan'; 2025-07-03 22:05:01.012 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99 Jan 08" at character 13 2025-07-03 22:05:01.012 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 Jan 08'; 2025-07-03 22:05:01.012 UTC client backend[15140] pg_regress/timetz LOG: disconnection: session time: 0:00:00.189 user=postgres database=regression host=[local] 2025-07-03 22:05:01.013 UTC client backend[15136] pg_regress/date ERROR: invalid input syntax for type date: "99 08 Jan" at character 13 2025-07-03 22:05:01.013 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 08 Jan'; 2025-07-03 22:05:01.014 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-01-08" at character 13 2025-07-03 22:05:01.014 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:01.014 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-01-08'; 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99-08-01" at character 13 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99-08-01'; 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99 01 08" at character 13 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:01.016 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 01 08'; 2025-07-03 22:05:01.017 UTC client backend[15136] pg_regress/date ERROR: date/time field value out of range: "99 08 01" at character 13 2025-07-03 22:05:01.017 UTC client backend[15136] pg_regress/date HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:01.017 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '99 08 01'; 2025-07-03 22:05:01.019 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "badly formatted interval" at character 39 2025-07-03 22:05:01.019 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval'); 2025-07-03 22:05:01.019 UTC client backend[15136] pg_regress/date ERROR: date out of range: "4714-11-23 BC" at character 13 2025-07-03 22:05:01.019 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '4714-11-23 BC'; 2025-07-03 22:05:01.019 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "@ 30 eons ago" at character 39 2025-07-03 22:05:01.019 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago'); 2025-07-03 22:05:01.020 UTC client backend[15136] pg_regress/date ERROR: date out of range: "5874898-01-01" at character 13 2025-07-03 22:05:01.020 UTC client backend[15136] pg_regress/date STATEMENT: SELECT date '5874898-01-01'; 2025-07-03 22:05:01.023 UTC client backend[15150] pg_regress/macaddr8 ERROR: invalid input syntax for type macaddr8: "not even close" at character 38 2025-07-03 22:05:01.023 UTC client backend[15150] pg_regress/macaddr8 STATEMENT: INSERT INTO macaddr8_data VALUES (9, 'not even close'); 2025-07-03 22:05:01.023 UTC client backend[15148] pg_regress/time LOG: disconnection: session time: 0:00:00.145 user=postgres database=regression host=[local] 2025-07-03 22:05:01.025 UTC client backend[15123] pg_regress/strings ERROR: regexp_like() does not support the "global" option 2025-07-03 22:05:01.025 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_like('abc', 'a.c', 'g'); 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 0, 1); 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 0); 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "endoption": -1 2025-07-03 22:05:01.065 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1); 2025-07-03 22:05:01.066 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "endoption": 2 2025-07-03 22:05:01.066 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2); 2025-07-03 22:05:01.066 UTC client backend[15123] pg_regress/strings ERROR: regexp_instr() does not support the "global" option 2025-07-03 22:05:01.066 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g'); 2025-07-03 22:05:01.068 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-07-03 22:05:01.068 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1); 2025-07-03 22:05:01.074 UTC client backend[15143] pg_regress/inet ERROR: invalid mask length: 33 2025-07-03 22:05:01.074 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT set_masklen(inet(text(i)), 33) FROM INET_TBL; 2025-07-03 22:05:01.075 UTC client backend[15143] pg_regress/inet ERROR: invalid mask length: 33 2025-07-03 22:05:01.075 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT set_masklen(cidr(text(c)), 33) FROM INET_TBL; 2025-07-03 22:05:01.085 UTC client backend[15136] pg_regress/date ERROR: unit "microseconds" not supported for type date 2025-07-03 22:05:01.085 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSECONDS FROM DATE '2020-08-11'); 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date ERROR: unit "milliseconds" not supported for type date 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(MILLISECONDS FROM DATE '2020-08-11'); 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date ERROR: unit "second" not supported for type date 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(SECOND FROM DATE '2020-08-11'); 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date ERROR: unit "minute" not supported for type date 2025-07-03 22:05:01.087 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(MINUTE FROM DATE '2020-08-11'); 2025-07-03 22:05:01.088 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "start": 0 2025-07-03 22:05:01.088 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 0, 1); 2025-07-03 22:05:01.088 UTC client backend[15136] pg_regress/date ERROR: unit "hour" not supported for type date 2025-07-03 22:05:01.088 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(HOUR FROM DATE '2020-08-11'); 2025-07-03 22:05:01.088 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "n": 0 2025-07-03 22:05:01.088 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 0); 2025-07-03 22:05:01.093 UTC client backend[15154] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:05:01.093 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select nummultirange(numrange(2.0, 1.0)); 2025-07-03 22:05:01.093 UTC client backend[15123] pg_regress/strings ERROR: regexp_substr() does not support the "global" option 2025-07-03 22:05:01.093 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g'); 2025-07-03 22:05:01.094 UTC client backend[15123] pg_regress/strings ERROR: invalid value for parameter "subexpr": -1 2025-07-03 22:05:01.094 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1); 2025-07-03 22:05:01.099 UTC client backend[15136] pg_regress/date ERROR: unit "timezone" not supported for type date 2025-07-03 22:05:01.099 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE FROM DATE '2020-08-11'); 2025-07-03 22:05:01.103 UTC client backend[15136] pg_regress/date ERROR: unit "timezone_m" not supported for type date 2025-07-03 22:05:01.103 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_M FROM DATE '2020-08-11'); 2025-07-03 22:05:01.103 UTC client backend[15136] pg_regress/date ERROR: unit "timezone_h" not supported for type date 2025-07-03 22:05:01.103 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(TIMEZONE_H FROM DATE '2020-08-11'); 2025-07-03 22:05:01.118 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-07-03 22:05:01.118 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz'); 2025-07-03 22:05:01.119 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression: parentheses () not balanced 2025-07-03 22:05:01.119 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$); 2025-07-03 22:05:01.121 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression: invalid repetition count(s) 2025-07-03 22:05:01.121 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$); 2025-07-03 22:05:01.129 UTC client backend[15152] pg_regress/macaddr LOG: disconnection: session time: 0:00:00.210 user=postgres database=regression host=[local] 2025-07-03 22:05:01.135 UTC client backend[15136] pg_regress/date ERROR: unit "microsec" not recognized for type date 2025-07-03 22:05:01.135 UTC client backend[15136] pg_regress/date STATEMENT: SELECT EXTRACT(MICROSEC FROM DATE 'infinity'); 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date ERROR: date field value out of range: 0-07-15 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date STATEMENT: select make_date(0, 7, 15); 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date ERROR: date field value out of range: 2013-02-30 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date STATEMENT: select make_date(2013, 2, 30); 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date ERROR: date field value out of range: 2013-13-01 2025-07-03 22:05:01.138 UTC client backend[15136] pg_regress/date STATEMENT: select make_date(2013, 13, 1); 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date ERROR: date field value out of range: 2013-11--1 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date STATEMENT: select make_date(2013, 11, -1); 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date ERROR: date field value out of range: -2147483648-01-01 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date STATEMENT: SELECT make_date(-2147483648, 1, 1); 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date ERROR: time field value out of range: 10:55:100.1 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date STATEMENT: select make_time(10, 55, 100.1); 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date ERROR: time field value out of range: 24:00:2.1 2025-07-03 22:05:01.139 UTC client backend[15136] pg_regress/date STATEMENT: select make_time(24, 0, 2.1); 2025-07-03 22:05:01.142 UTC client backend[15136] pg_regress/date LOG: disconnection: session time: 0:00:00.338 user=postgres database=regression host=[local] 2025-07-03 22:05:01.148 UTC client backend[15134] pg_regress/numerology LOG: disconnection: session time: 0:00:00.355 user=postgres database=regression host=[local] 2025-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-07-03 22:05:01.160 UTC client backend[15123] 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-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings ERROR: invalid regular expression option: "z" 2025-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz'); 2025-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings ERROR: regexp_split_to_table() does not support the "global" option 2025-07-03 22:05:01.160 UTC client backend[15123] 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-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings ERROR: regexp_split_to_array() does not support the "global" option 2025-07-03 22:05:01.160 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g'); 2025-07-03 22:05:01.172 UTC client backend[15150] pg_regress/macaddr8 LOG: disconnection: session time: 0:00:00.253 user=postgres database=regression host=[local] 2025-07-03 22:05:01.206 UTC client backend[15143] pg_regress/inet ERROR: result is out of range 2025-07-03 22:05:01.206 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet + 10000000000; 2025-07-03 22:05:01.206 UTC client backend[15143] pg_regress/inet ERROR: result is out of range 2025-07-03 22:05:01.206 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT '127.0.0.1'::inet - 10000000000; 2025-07-03 22:05:01.211 UTC client backend[15143] pg_regress/inet ERROR: result is out of range 2025-07-03 22:05:01.211 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT '126::1'::inet - '127::2'::inet; 2025-07-03 22:05:01.211 UTC client backend[15143] pg_regress/inet ERROR: result is out of range 2025-07-03 22:05:01.211 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT '127::1'::inet - '126::2'::inet; 2025-07-03 22:05:01.212 UTC client backend[15143] pg_regress/inet ERROR: cannot merge addresses from different families 2025-07-03 22:05:01.212 UTC client backend[15143] pg_regress/inet STATEMENT: SELECT inet_merge(c, i) FROM INET_TBL; 2025-07-03 22:05:01.227 UTC client backend[15143] pg_regress/inet LOG: disconnection: session time: 0:00:00.389 user=postgres database=regression host=[local] 2025-07-03 22:05:01.229 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.229 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT -('-2147483648 months'::interval); 2025-07-03 22:05:01.232 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.232 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT -('-2147483648 days'::interval); 2025-07-03 22:05:01.234 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.234 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT -('-9223372036854775808 us'::interval); 2025-07-03 22:05:01.234 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.234 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval); 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 42 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days'); 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 42 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days'); 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval ERROR: interval out of range at character 42 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years'); 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval ERROR: interval out of range at character 42 2025-07-03 22:05:01.243 UTC client backend[15151] pg_regress/interval STATEMENT: INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years'); 2025-07-03 22:05:01.244 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.244 UTC client backend[15151] pg_regress/interval STATEMENT: select extract(epoch from '256 microseconds'::interval * (2^55)::float8); 2025-07-03 22:05:01.296 UTC client backend[15147] pg_regress/timestamp ERROR: time zone "america/does_not_exist" not recognized at character 35 2025-07-03 22:05:01.296 UTC client backend[15147] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-07-03 22:05:01.300 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.300 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval * 1000; 2025-07-03 22:05:01.303 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.303 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '3000000 months'::interval / 0.001; 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval * 1000; 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '3000000 days'::interval / 0.001; 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '1 month 2146410 days'::interval * 1000.5002; 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.304 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '4611686018427387904 usec'::interval / 0.1; 2025-07-03 22:05:01.309 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.309 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_hours(interval '2147483647 days 24 hrs'); 2025-07-03 22:05:01.309 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.309 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_days(interval '2147483647 months 30 days'); 2025-07-03 22:05:01.312 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.312 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months 30 days'); 2025-07-03 22:05:01.312 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.312 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months -30 days'); 2025-07-03 22:05:01.313 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.313 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs'); 2025-07-03 22:05:01.313 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.313 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs'); 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 second 2 seconds" at character 8 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '1 second 2 seconds'::interval; 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '10 milliseconds 20 milliseconds'::interval; 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8 2025-07-03 22:05:01.318 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '5.5 seconds 3 milliseconds'::interval; 2025-07-03 22:05:01.319 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8 2025-07-03 22:05:01.319 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '1:20:05 5 microseconds'::interval; 2025-07-03 22:05:01.319 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 day 1 day" at character 8 2025-07-03 22:05:01.319 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '1 day 1 day'::interval; 2025-07-03 22:05:01.325 UTC client backend[15147] pg_regress/timestamp ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 35 2025-07-03 22:05:01.325 UTC client backend[15147] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-07-03 22:05:01.329 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-07-03 22:05:01.329 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2' day to minute; 2025-07-03 22:05:01.329 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-07-03 22:05:01.329 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2' day to second; 2025-07-03 22:05:01.331 UTC client backend[15147] pg_regress/timestamp ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35 2025-07-03 22:05:01.331 UTC client backend[15147] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-07-03 22:05:01.332 UTC client backend[15147] pg_regress/timestamp ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35 2025-07-03 22:05:01.332 UTC client backend[15147] pg_regress/timestamp STATEMENT: INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-07-03 22:05:01.332 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-07-03 22:05:01.332 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to minute; 2025-07-03 22:05:01.332 UTC client backend[15147] pg_regress/timestamp ERROR: timestamp out of range: "4714-11-23 23:59:59 BC" at character 8 2025-07-03 22:05:01.332 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT '4714-11-23 23:59:59 BC'::timestamp; 2025-07-03 22:05:01.334 UTC client backend[15147] pg_regress/timestamp ERROR: timestamp out of range: "294277-01-01 00:00:00" at character 8 2025-07-03 22:05:01.334 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT '294277-01-01 00:00:00'::timestamp; 2025-07-03 22:05:01.335 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-07-03 22:05:01.335 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2' hour to second; 2025-07-03 22:05:01.336 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2" at character 17 2025-07-03 22:05:01.336 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2' minute to second; 2025-07-03 22:05:01.344 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-07-03 22:05:01.344 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '123 11' day; 2025-07-03 22:05:01.344 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "123 11" at character 17 2025-07-03 22:05:01.344 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '123 11'; 2025-07-03 22:05:01.345 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "123 2:03 -2:04" at character 17 2025-07-03 22:05:01.345 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '123 2:03 -2:04'; 2025-07-03 22:05:01.347 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-07-03 22:05:01.347 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2.345' day to second(2); 2025-07-03 22:05:01.348 UTC client backend[15147] pg_regress/timestamp ERROR: unit "ago" not recognized for type timestamp without time zone 2025-07-03 22:05:01.348 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT date_trunc( 'ago', timestamp 'infinity' ) AS invalid_trunc; 2025-07-03 22:05:01.349 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.345" at character 17 2025-07-03 22:05:01.349 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2.345' hour to second(2); 2025-07-03 22:05:01.355 UTC client backend[15147] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-07-03 22:05:01.355 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-07-03 22:05:01.355 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 2.3456" at character 17 2025-07-03 22:05:01.355 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '1 2.3456' minute to second(2); 2025-07-03 22:05:01.355 UTC client backend[15147] pg_regress/timestamp ERROR: timestamps cannot be binned into intervals containing months or years 2025-07-03 22:05:01.355 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT date_bin('5 years'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01'); 2025-07-03 22:05:01.356 UTC client backend[15149] pg_regress/timestamptz ERROR: time zone "america/does_not_exist" not recognized at character 37 2025-07-03 22:05:01.356 UTC client backend[15149] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist'); 2025-07-03 22:05:01.356 UTC client backend[15149] pg_regress/timestamptz ERROR: time zone "America/Does_not_exist" not recognized 2025-07-03 22:05:01.356 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist'; 2025-07-03 22:05:01.357 UTC client backend[15147] pg_regress/timestamp ERROR: stride must be greater than zero 2025-07-03 22:05:01.357 UTC client backend[15147] 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-07-03 22:05:01.357 UTC client backend[15147] pg_regress/timestamp ERROR: stride must be greater than zero 2025-07-03 22:05:01.357 UTC client backend[15147] 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-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp STATEMENT: select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC'); 2025-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp); 2025-07-03 22:05:01.358 UTC client backend[15151] pg_regress/interval ERROR: interval out of range at character 17 2025-07-03 22:05:01.358 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '2562047788:00:54.775807' second(2); 2025-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp ERROR: timestamp out of range 2025-07-03 22:05:01.358 UTC client backend[15147] pg_regress/timestamp STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp); 2025-07-03 22:05:01.358 UTC client backend[15151] pg_regress/interval ERROR: interval out of range at character 17 2025-07-03 22:05:01.358 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-2562047788:00:54.775807' second(2); 2025-07-03 22:05:01.359 UTC client backend[15149] pg_regress/timestamptz ERROR: invalid input syntax for type timestamp with time zone: "Jan 01 00:00:00 2024 LMT" at character 8 2025-07-03 22:05:01.359 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT 'Jan 01 00:00:00 2024 LMT'::timestamptz; 2025-07-03 22:05:01.359 UTC client backend[15123] pg_regress/strings ERROR: negative substring length not allowed 2025-07-03 22:05:01.359 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-07-03 22:05:01.368 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "" at character 18 2025-07-03 22:05:01.368 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval ''; 2025-07-03 22:05:01.377 UTC client backend[15149] pg_regress/timestamptz ERROR: date/time field value out of range: "Feb 29 17:32:01 1997" at character 37 2025-07-03 22:05:01.377 UTC client backend[15149] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997'); 2025-07-03 22:05:01.379 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17 2025-07-03 22:05:01.379 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P.Y0M3DT4H5M6S'; 2025-07-03 22:05:01.379 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.379 UTC client backend[15147] pg_regress/timestamp STATEMENT: SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows; 2025-07-03 22:05:01.387 UTC client backend[15149] pg_regress/timestamptz ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37 2025-07-03 22:05:01.387 UTC client backend[15149] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097'); 2025-07-03 22:05:01.387 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37 2025-07-03 22:05:01.387 UTC client backend[15149] pg_regress/timestamptz STATEMENT: INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC'); 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT '4714-11-23 23:59:59+00 BC'::timestamptz; 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp out of range: "294277-01-01 00:00:00+00" at character 8 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT '294277-01-01 00:00:00+00'::timestamptz; 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp out of range: "294277-12-31 16:00:00-08" at character 8 2025-07-03 22:05:01.390 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT '294277-12-31 16:00:00-08'::timestamptz; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483648 years" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483648 years'; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483649 years" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483649 years'; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483648 months" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483648 months'; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483649 months" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483649 months'; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483648 days" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483648 days'; 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483649 days" at character 17 2025-07-03 22:05:01.394 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483649 days'; 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2562047789 hours" at character 17 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2562047789 hours'; 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2562047789 hours" at character 17 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2562047789 hours'; 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "153722867281 minutes" at character 17 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '153722867281 minutes'; 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-153722867281 minutes" at character 17 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-153722867281 minutes'; 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036855 seconds" at character 17 2025-07-03 22:05:01.395 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036855 seconds'; 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036855 seconds" at character 17 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036855 seconds'; 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036854777 millisecond" at character 17 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036854777 millisecond'; 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854777 millisecond" at character 17 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854777 millisecond'; 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036854775808 microsecond" at character 17 2025-07-03 22:05:01.398 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036854775808 microsecond'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775809 microsecond" at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854775809 microsecond'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P2147483648" at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P2147483648'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-2147483649" at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-2147483649'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval out of range at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P1-2147483647-2147483647'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT2562047789" at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT2562047789'; 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT-2562047789" at character 17 2025-07-03 22:05:01.399 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT-2562047789'; 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 weeks" at character 17 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 weeks'; 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 weeks" at character 17 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 weeks'; 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 decades" at character 17 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 decades'; 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 decades" at character 17 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 decades'; 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 centuries" at character 17 2025-07-03 22:05:01.403 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 centuries'; 2025-07-03 22:05:01.404 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 centuries" at character 17 2025-07-03 22:05:01.404 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 centuries'; 2025-07-03 22:05:01.405 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 millennium" at character 17 2025-07-03 22:05:01.405 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 millennium'; 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 millennium" at character 17 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 millennium'; 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "1 week 2147483647 days" at character 17 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '1 week 2147483647 days'; 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-1 week -2147483648 days" at character 17 2025-07-03 22:05:01.406 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-1 week -2147483648 days'; 2025-07-03 22:05:01.407 UTC client backend[15149] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-07-03 22:05:01.407 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT date_trunc( 'ago', timestamp with time zone 'infinity' ) AS invalid_trunc; 2025-07-03 22:05:01.408 UTC client backend[15147] pg_regress/timestamp ERROR: date field value out of range: 0-07-15 2025-07-03 22:05:01.408 UTC client backend[15147] pg_regress/timestamp STATEMENT: select make_timestamp(0, 7, 15, 12, 30, 15); 2025-07-03 22:05:01.408 UTC client backend[15149] pg_regress/timestamptz ERROR: unit "ago" not recognized for type timestamp with time zone 2025-07-03 22:05:01.408 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT date_trunc('ago', timestamp with time zone 'infinity', 'GMT') AS invalid_zone_trunc; 2025-07-03 22:05:01.408 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 1 week" at character 17 2025-07-03 22:05:01.408 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 days 1 week'; 2025-07-03 22:05:01.408 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -1 week" at character 17 2025-07-03 22:05:01.408 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 days -1 week'; 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P1W2147483647D" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P1W2147483647D'; 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-1W-2147483648D" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-1W-2147483648D'; 2025-07-03 22:05:01.409 UTC client backend[15147] pg_regress/timestamp ERROR: step size cannot equal zero 2025-07-03 22:05:01.409 UTC client backend[15147] pg_regress/timestamp STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamp, '2020-01-02 03:00'::timestamp, '0 hour'::interval); 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P2147483647D1W" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P2147483647D1W'; 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-1W" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-2147483648D-1W'; 2025-07-03 22:05:01.409 UTC client backend[15147] pg_regress/timestamp ERROR: step size cannot be infinite 2025-07-03 22:05:01.409 UTC client backend[15147] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity'); 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "1 decade 2147483647 years" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '1 decade 2147483647 years'; 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "1 century 2147483647 years" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '1 century 2147483647 years'; 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "1 millennium 2147483647 years" at character 17 2025-07-03 22:05:01.409 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '1 millennium 2147483647 years'; 2025-07-03 22:05:01.410 UTC client backend[15147] pg_regress/timestamp ERROR: step size cannot be infinite 2025-07-03 22:05:01.410 UTC client backend[15147] pg_regress/timestamp STATEMENT: select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity'); 2025-07-03 22:05:01.410 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.410 UTC client backend[15147] pg_regress/timestamp STATEMENT: select timestamp 'infinity' - timestamp 'infinity'; 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-1 decade -2147483648 years" at character 17 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-1 decade -2147483648 years'; 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-1 century -2147483648 years" at character 17 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-1 century -2147483648 years'; 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-1 millennium -2147483648 years" at character 17 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-1 millennium -2147483648 years'; 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 decade" at character 17 2025-07-03 22:05:01.410 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 years 1 decade'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 century" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 years 1 century'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 years 1 millennium" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 years 1 millennium'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 decade" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 decade'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 century" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 century'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 years -1 millennium" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 years -1 millennium'; 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 millennium 2147483647 months" at character 17 2025-07-03 22:05:01.411 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 millennium 2147483647 months'; 2025-07-03 22:05:01.413 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.413 UTC client backend[15147] pg_regress/timestamp STATEMENT: select timestamp '-infinity' - timestamp '-infinity'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 centuries 2147483647 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 centuries 2147483647 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 decades 2147483647 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 decades 2147483647 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 yrs 2147483647 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 yrs 2147483647 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 millennium -2147483648 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 millennium -2147483648 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 centuries -2147483648 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 centuries -2147483648 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 decades -2147483648 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 decades -2147483648 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 yrs -2147483648 months" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 yrs -2147483648 months'; 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 millennium" at character 17 2025-07-03 22:05:01.414 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 millennium'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 centuries" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 centuries'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 decades" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 decades'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 months 0.1 yrs" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 months 0.1 yrs'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 millennium" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 millennium'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 centuries" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 centuries'; 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 decades" at character 17 2025-07-03 22:05:01.415 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 decades'; 2025-07-03 22:05:01.415 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.415 UTC client backend[15147] pg_regress/timestamp STATEMENT: select age(timestamp 'infinity', timestamp 'infinity'); 2025-07-03 22:05:01.416 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-07-03 22:05:01.416 UTC client backend[15149] 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-07-03 22:05:01.416 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamps cannot be binned into intervals containing months or years 2025-07-03 22:05:01.416 UTC client backend[15149] 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-07-03 22:05:01.416 UTC client backend[15149] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-07-03 22:05:01.416 UTC client backend[15149] 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-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz ERROR: stride must be greater than zero 2025-07-03 22:05:01.417 UTC client backend[15149] 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-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC'); 2025-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz); 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -0.1 yrs" at character 17 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months -0.1 yrs'; 2025-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp out of range 2025-07-03 22:05:01.417 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz); 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 months 2147483647 days" at character 17 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 months 2147483647 days'; 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 months -2147483648 days" at character 17 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 months -2147483648 days'; 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.1 months" at character 17 2025-07-03 22:05:01.417 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 days 0.1 months'; 2025-07-03 22:05:01.418 UTC client backend[15147] pg_regress/timestamp ERROR: interval out of range 2025-07-03 22:05:01.418 UTC client backend[15147] pg_regress/timestamp STATEMENT: select age(timestamp '-infinity', timestamp '-infinity'); 2025-07-03 22:05:01.418 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.1 months" at character 17 2025-07-03 22:05:01.418 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.1 months'; 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.5 weeks 2147483647 days" at character 17 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.5 weeks 2147483647 days'; 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.5 weeks -2147483648 days" at character 17 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.5 weeks -2147483648 days'; 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2147483647 days 0.5 weeks" at character 17 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2147483647 days 0.5 weeks'; 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days -0.5 weeks" at character 17 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 days -0.5 weeks'; 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17 2025-07-03 22:05:01.420 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.01 months 9223372036854775807 microseconds'; 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.01 months -9223372036854775808 microseconds'; 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.01 months'; 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17 2025-07-03 22:05:01.421 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.01 months'; 2025-07-03 22:05:01.422 UTC client backend[15147] pg_regress/timestamp LOG: disconnection: session time: 0:00:00.559 user=postgres database=regression host=[local] 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 weeks 9223372036854775807 microseconds'; 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 weeks -9223372036854775808 microseconds'; 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 weeks'; 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 weeks'; 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17 2025-07-03 22:05:01.424 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 days 9223372036854775807 microseconds'; 2025-07-03 22:05:01.425 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17 2025-07-03 22:05:01.425 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-0.1 days -9223372036854775808 microseconds'; 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '9223372036854775807 microseconds 0.1 days'; 2025-07-03 22:05:01.428 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.428 UTC client backend[15149] 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-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds -0.1 days'; 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.1Y2147483647M" at character 17 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.1Y2147483647M'; 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-0.1Y-2147483648M" at character 17 2025-07-03 22:05:01.428 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-0.1Y-2147483648M'; 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P2147483647M0.1Y" at character 17 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P2147483647M0.1Y'; 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-2147483648M-0.1Y" at character 17 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-2147483648M-0.1Y'; 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.1M2147483647D" at character 17 2025-07-03 22:05:01.429 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.1M2147483647D'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-0.1M-2147483648D" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-0.1M-2147483648D'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.1M" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P2147483647D0.1M'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.1M" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.1M'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.5W2147483647D" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.5W2147483647D'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-0.5W-2147483648D" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-0.5W-2147483648D'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P2147483647D0.5W" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P2147483647D0.5W'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-2147483648D-0.5W" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-2147483648D-0.5W'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.01MT2562047788H54.775807S'; 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17 2025-07-03 22:05:01.430 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-0.01MT-2562047788H-54.775808S'; 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.1DT2562047788H54.775807S'; 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P-0.1DT-2562047788H-54.775808S'; 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1H54.775807S" at character 17 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT2562047788.1H54.775807S'; 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17 2025-07-03 22:05:01.431 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT-2562047788.1H-54.775808S'; 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT2562047788H0.1M54.775807S'; 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT-2562047788H-0.1M-54.775808S'; 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P0.1-2147483647-00" at character 17 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P0.1-2147483647-00'; 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P00-0.1-2147483647" at character 17 2025-07-03 22:05:01.432 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P00-0.1-2147483647'; 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P00-0.01-00T2562047788:00:54.775807'; 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'P00-00-0.1T2562047788:00:54.775807'; 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT2562047788.1:00:54.775807" at character 17 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT2562047788.1:00:54.775807'; 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "PT2562047788:01.:54.775807" at character 17 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval STATEMENT: select interval 'PT2562047788:01.:54.775807'; 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775807" at character 17 2025-07-03 22:05:01.433 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775807'; 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '0.1 2562047788:0:54.775808 ago'; 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775807" at character 17 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775807'; 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2562047788.1:0:54.775808 ago'; 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17 2025-07-03 22:05:01.434 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775807'; 2025-07-03 22:05:01.435 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17 2025-07-03 22:05:01.435 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '2562047788:0.1:54.775808 ago'; 2025-07-03 22:05:01.435 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months ago" at character 17 2025-07-03 22:05:01.435 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months ago'; 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 days ago" at character 17 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 days ago'; 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-9223372036854775808 microseconds ago" at character 17 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-9223372036854775808 microseconds ago'; 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval ERROR: interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17 2025-07-03 22:05:01.438 UTC client backend[15151] pg_regress/interval STATEMENT: select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago'; 2025-07-03 22:05:01.439 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.439 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(years := 178956971); 2025-07-03 22:05:01.439 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.439 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(years := -178956971); 2025-07-03 22:05:01.440 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.440 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(years := 1, months := 2147483647); 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(years := -1, months := -2147483648); 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(weeks := 306783379); 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.444 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(weeks := -306783379); 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(weeks := 1, days := 2147483647); 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(weeks := -1, days := -2147483648); 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval ERROR: value out of range: overflow 2025-07-03 22:05:01.445 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(secs := 1e308); 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(secs := 1e18); 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(secs := -1e18); 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.447 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(mins := 1, secs := 9223372036800.0); 2025-07-03 22:05:01.448 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.448 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(mins := -1, secs := -9223372036800.0); 2025-07-03 22:05:01.458 UTC client backend[15151] pg_regress/interval ERROR: integer out of range 2025-07-03 22:05:01.458 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(years := 'inf'::float::int); 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval ERROR: integer out of range 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(months := 'NaN'::float::int); 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(secs := 'inf'); 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.465 UTC client backend[15151] pg_regress/interval STATEMENT: select make_interval(secs := 'NaN'); 2025-07-03 22:05:01.471 UTC client backend[15151] pg_regress/interval ERROR: unit "fortnight" not recognized for type interval 2025-07-03 22:05:01.471 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days'); 2025-07-03 22:05:01.471 UTC client backend[15151] pg_regress/interval ERROR: unit "timezone" not supported for type interval 2025-07-03 22:05:01.471 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days'); 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz ERROR: invalid input syntax for type numeric time zone: "2" 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz HINT: Numeric time zones must have "-" or "+" as first character. 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2'); 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz ERROR: numeric time zone "+16" out of range 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16'); 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz ERROR: numeric time zone "-16" out of range 2025-07-03 22:05:01.498 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16'); 2025-07-03 22:05:01.504 UTC client backend[15149] pg_regress/timestamptz ERROR: time zone "Nehwon/Lankhmar" not recognized 2025-07-03 22:05:01.504 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar'); 2025-07-03 22:05:01.512 UTC client backend[15149] pg_regress/timestamptz ERROR: step size cannot equal zero 2025-07-03 22:05:01.512 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select * from generate_series('2020-01-01 00:00'::timestamptz, '2020-01-02 03:00'::timestamptz, '0 hour'::interval); 2025-07-03 22:05:01.513 UTC client backend[15149] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-07-03 22:05:01.513 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity'); 2025-07-03 22:05:01.515 UTC client backend[15149] pg_regress/timestamptz ERROR: step size cannot be infinite 2025-07-03 22:05:01.515 UTC client backend[15149] pg_regress/timestamptz STATEMENT: select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity'); 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us'; 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us'; 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.515 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us'; 2025-07-03 22:05:01.516 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.516 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us'; 2025-07-03 22:05:01.528 UTC client backend[15151] pg_regress/interval ERROR: cannot add infinite interval to time 2025-07-03 22:05:01.528 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval 'infinity'; 2025-07-03 22:05:01.534 UTC client backend[15151] pg_regress/interval ERROR: cannot add infinite interval to time 2025-07-03 22:05:01.534 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT time '11:27:42' + interval '-infinity'; 2025-07-03 22:05:01.534 UTC client backend[15151] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-07-03 22:05:01.534 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval 'infinity'; 2025-07-03 22:05:01.535 UTC client backend[15151] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-07-03 22:05:01.535 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT time '11:27:42' - interval '-infinity'; 2025-07-03 22:05:01.536 UTC client backend[15151] pg_regress/interval ERROR: cannot add infinite interval to time 2025-07-03 22:05:01.536 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval 'infinity'; 2025-07-03 22:05:01.536 UTC client backend[15151] pg_regress/interval ERROR: cannot add infinite interval to time 2025-07-03 22:05:01.536 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' + interval '-infinity'; 2025-07-03 22:05:01.538 UTC client backend[15151] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-07-03 22:05:01.538 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval 'infinity'; 2025-07-03 22:05:01.539 UTC client backend[15123] pg_regress/strings ERROR: negative substring length not allowed 2025-07-03 22:05:01.539 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT substr(f1, 5, -1) from toasttest; 2025-07-03 22:05:01.539 UTC client backend[15151] pg_regress/interval ERROR: cannot subtract infinite interval from time 2025-07-03 22:05:01.539 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timetz '11:27:42' - interval '-infinity'; 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us'; 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 'nan'; 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.543 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 'nan'; 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2; 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval 'infinity' * 0; 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-infinity' * 0; 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '0 days' * 'infinity'::float; 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.544 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '0 days' * '-infinity'::float; 2025-07-03 22:05:01.548 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.548 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'infinity'; 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval 'infinity' / '-infinity'; 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval 'infinity' / 'nan'; 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'infinity'; 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-infinity' / '-infinity'; 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.549 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-infinity' / 'nan'; 2025-07-03 22:05:01.550 UTC client backend[15151] pg_regress/interval ERROR: interval out of range 2025-07-03 22:05:01.550 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5; 2025-07-03 22:05:01.551 UTC client backend[15151] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-07-03 22:05:01.551 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-07-03 22:05:01.551 UTC client backend[15151] pg_regress/interval ERROR: timestamps cannot be binned into infinite intervals 2025-07-03 22:05:01.551 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00'); 2025-07-03 22:05:01.552 UTC client backend[15151] pg_regress/interval ERROR: unit "week" not supported for type interval 2025-07-03 22:05:01.552 UTC client backend[15151] pg_regress/interval DETAIL: Months usually have fractional weeks. 2025-07-03 22:05:01.552 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('week', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-07-03 22:05:01.552 UTC client backend[15151] pg_regress/interval ERROR: unit "ago" not recognized for type interval 2025-07-03 22:05:01.552 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT i AS interval, date_trunc('ago', i) FROM INFINITE_INTERVAL_TBL WHERE NOT isfinite(i); 2025-07-03 22:05:01.555 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-07-03 22:05:01.555 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-07-03 22:05:01.556 UTC client backend[15149] pg_regress/timestamptz ERROR: timestamp cannot be NaN 2025-07-03 22:05:01.556 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT to_timestamp('NaN'::float); 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp); 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz); 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-07-03 22:05:01.558 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::time); 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::time); 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "infinity" must be finite 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('infinity'::interval, '12:12:12'::timetz); 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval ERROR: interval time zone "-infinity" must be finite 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT timezone('-infinity'::interval, '12:12:12'::timetz); 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT 'infinity'::interval::time; 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval ERROR: cannot convert infinite interval to time 2025-07-03 22:05:01.559 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT '-infinity'::interval::time; 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL '42 days 2 seconds ago ago'; 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "2 minutes ago 5 days" at character 17 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL '2 minutes ago 5 days'; 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "hour 5 months" at character 17 2025-07-03 22:05:01.565 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'hour 5 months'; 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "1 year months days 5 hours" at character 17 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL '1 year months days 5 hours'; 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "now" at character 17 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'now'; 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "today" at character 17 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'today'; 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "tomorrow" at character 17 2025-07-03 22:05:01.568 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'tomorrow'; 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "allballs" at character 17 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'allballs'; 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "epoch" at character 17 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'epoch'; 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "yesterday" at character 17 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'yesterday'; 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity years" at character 17 2025-07-03 22:05:01.569 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity years'; 2025-07-03 22:05:01.570 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "infinity ago" at character 17 2025-07-03 22:05:01.570 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL 'infinity ago'; 2025-07-03 22:05:01.570 UTC client backend[15151] pg_regress/interval ERROR: invalid input syntax for type interval: "+infinity -infinity" at character 17 2025-07-03 22:05:01.570 UTC client backend[15151] pg_regress/interval STATEMENT: SELECT INTERVAL '+infinity -infinity'; 2025-07-03 22:05:01.574 UTC client backend[15151] pg_regress/interval LOG: disconnection: session time: 0:00:00.654 user=postgres database=regression host=[local] 2025-07-03 22:05:01.600 UTC client backend[15123] pg_regress/strings ERROR: field position must not be zero 2025-07-03 22:05:01.600 UTC client backend[15123] pg_regress/strings STATEMENT: select split_part('joeuser@mydatabase','@',0) AS "an error"; 2025-07-03 22:05:01.619 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.619 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT timestamptz 'infinity' - timestamptz 'infinity'; 2025-07-03 22:05:01.620 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.620 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT timestamptz '-infinity' - timestamptz '-infinity'; 2025-07-03 22:05:01.623 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.623 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz 'infinity', timestamptz 'infinity'); 2025-07-03 22:05:01.624 UTC client backend[15149] pg_regress/timestamptz ERROR: interval out of range 2025-07-03 22:05:01.624 UTC client backend[15149] pg_regress/timestamptz STATEMENT: SELECT age(timestamptz '-infinity', timestamptz '-infinity'); 2025-07-03 22:05:01.633 UTC client backend[15149] pg_regress/timestamptz LOG: disconnection: session time: 0:00:00.757 user=postgres database=regression host=[local] 2025-07-03 22:05:01.635 UTC client backend[15123] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-07-03 22:05:01.635 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT get_bit('\x1234567890abcdef00'::bytea, 99); 2025-07-03 22:05:01.636 UTC client backend[15123] pg_regress/strings ERROR: index 99 out of valid range, 0..71 2025-07-03 22:05:01.636 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0); 2025-07-03 22:05:01.637 UTC client backend[15123] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-07-03 22:05:01.637 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT get_byte('\x1234567890abcdef00'::bytea, 99); 2025-07-03 22:05:01.638 UTC client backend[15123] pg_regress/strings ERROR: index 99 out of valid range, 0..8 2025-07-03 22:05:01.638 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11); 2025-07-03 22:05:01.646 UTC client backend[15123] pg_regress/strings ERROR: smallint out of range 2025-07-03 22:05:01.646 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT '\x123456'::bytea::int2; 2025-07-03 22:05:01.647 UTC client backend[15123] pg_regress/strings ERROR: integer out of range 2025-07-03 22:05:01.647 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT '\x123456789A'::bytea::int4; 2025-07-03 22:05:01.648 UTC client backend[15123] pg_regress/strings ERROR: bigint out of range 2025-07-03 22:05:01.648 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT '\x112233445566778899'::bytea::int8; 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 8 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 24 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 42 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 62 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 80 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings WARNING: nonstandard use of \\ in a string literal at character 98 2025-07-03 22:05:01.650 UTC client backend[15123] pg_regress/strings HINT: Use the escape string syntax for backslashes, e.g., E'\\'. 2025-07-03 22:05:01.661 UTC client backend[15123] pg_regress/strings ERROR: null character not permitted 2025-07-03 22:05:01.661 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT chr(0); 2025-07-03 22:05:01.664 UTC client backend[15123] pg_regress/strings ERROR: negative substring length not allowed 2025-07-03 22:05:01.664 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error"; 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99'); 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \db99\0061'); 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-07-03 22:05:01.674 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+00db99\+000061'); 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \+2FFFFF'); 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \udb99\u0061'); 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode surrogate pair 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U0000db99\U00000061'); 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode code point: 2FFFFF 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \U002FFFFF'); 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings ERROR: invalid Unicode escape 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings HINT: Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX. 2025-07-03 22:05:01.675 UTC client backend[15123] pg_regress/strings STATEMENT: SELECT unistr('wrong: \xyz'); 2025-07-03 22:05:01.679 UTC client backend[15123] pg_regress/strings LOG: disconnection: session time: 0:00:00.950 user=postgres database=regression host=[local] 2025-07-03 22:05:01.680 UTC client backend[15137] pg_regress/point LOG: disconnection: session time: 0:00:00.868 user=postgres database=regression host=[local] 2025-07-03 22:05:01.904 UTC client backend[15146] pg_regress/polygon LOG: disconnection: session time: 0:00:01.041 user=postgres database=regression host=[local] 2025-07-03 22:05:01.958 UTC client backend[15154] pg_regress/multirangetypes ERROR: value for domain restrictedmultirange violates check constraint "restrictedmultirange_check" 2025-07-03 22:05:01.958 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select '{[4,50)}'::restrictedmultirange @> 7; 2025-07-03 22:05:01.976 UTC client backend[15154] pg_regress/multirangetypes ERROR: type "intmultirange" already exists 2025-07-03 22:05:01.976 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intrange". 2025-07-03 22:05:01.976 UTC client backend[15154] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-07-03 22:05:01.976 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create type intrange as range(subtype=int); 2025-07-03 22:05:01.989 UTC client backend[15154] pg_regress/multirangetypes ERROR: type "intr_multirange" already exists 2025-07-03 22:05:01.989 UTC client backend[15154] pg_regress/multirangetypes DETAIL: Failed while creating a multirange type for type "intr". 2025-07-03 22:05:01.989 UTC client backend[15154] pg_regress/multirangetypes HINT: You can manually specify a multirange type name using the "multirange_type_name" attribute. 2025-07-03 22:05:01.989 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create type intr as range(subtype=int); 2025-07-03 22:05:01.992 UTC client backend[15154] pg_regress/multirangetypes ERROR: type "int4" already exists 2025-07-03 22:05:01.992 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C"); 2025-07-03 22:05:02.004 UTC client backend[15154] pg_regress/multirangetypes ERROR: function multirange_of_text(textrange2) does not exist at character 8 2025-07-03 22:05:02.004 UTC client backend[15154] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.004 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange2('a','Z')); 2025-07-03 22:05:02.004 UTC client backend[15154] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:05:02.004 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select multirange_of_text(textrange1('a','Z')) @> 'b'::text; 2025-07-03 22:05:02.036 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot alter multirange type multitextrange1 2025-07-03 22:05:02.036 UTC client backend[15154] pg_regress/multirangetypes HINT: You can alter type textrange1, which will alter the multirange type as well. 2025-07-03 22:05:02.036 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: alter type multitextrange1 owner to regress_multirange_owner; 2025-07-03 22:05:02.037 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot set privileges of multirange types 2025-07-03 22:05:02.037 UTC client backend[15154] pg_regress/multirangetypes HINT: Set the privileges of the range type instead. 2025-07-03 22:05:02.037 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: revoke usage on type multitextrange1 from public; 2025-07-03 22:05:02.125 UTC client backend[15142] pg_regress/box LOG: disconnection: session time: 0:00:01.290 user=postgres database=regression host=[local] 2025-07-03 22:05:02.133 UTC client backend[15154] pg_regress/multirangetypes ERROR: permission denied for type multitextrange1 2025-07-03 22:05:02.133 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create temp table test2(f1 multitextrange1[]); 2025-07-03 22:05:02.151 UTC client backend[15154] pg_regress/multirangetypes ERROR: function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8 2025-07-03 22:05:02.151 UTC client backend[15154] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.151 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20))); 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create function bogus_func(anyelement) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:02.153 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create function bogus_func(int) returns anymultirange as 'select int4multirange(int4range(1,10))' language sql; 2025-07-03 22:05:02.159 UTC client backend[15154] pg_regress/multirangetypes ERROR: function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8 2025-07-03 22:05:02.159 UTC client backend[15154] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.159 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]); 2025-07-03 22:05:02.162 UTC client backend[15154] pg_regress/multirangetypes ERROR: function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8 2025-07-03 22:05:02.162 UTC client backend[15154] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.162 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20))); 2025-07-03 22:05:02.172 UTC client backend[15154] pg_regress/multirangetypes ERROR: function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8 2025-07-03 22:05:02.172 UTC client backend[15154] pg_regress/multirangetypes HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.172 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20))); 2025-07-03 22:05:02.173 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.173 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange. 2025-07-03 22:05:02.173 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create function bogus_func(anycompatible) returns anycompatiblerange as 'select int4range(1,10)' language sql; 2025-07-03 22:05:02.195 UTC client backend[15154] pg_regress/multirangetypes ERROR: range lower bound must be less than or equal to range upper bound 2025-07-03 22:05:02.195 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2])); 2025-07-03 22:05:02.257 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.257 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:02.257 UTC client backend[15154] 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-07-03 22:05:02.258 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.258 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:02.258 UTC client backend[15154] pg_regress/multirangetypes STATEMENT: create function mr_inoutparam_fail(inout i anyelement, out r anymultirange) as $$ select $1, '[1,10]' $$ language sql; 2025-07-03 22:05:02.258 UTC client backend[15154] pg_regress/multirangetypes ERROR: cannot determine result data type 2025-07-03 22:05:02.258 UTC client backend[15154] pg_regress/multirangetypes DETAIL: A result of type anymultirange requires at least one input of type anyrange or anymultirange. 2025-07-03 22:05:02.258 UTC client backend[15154] 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-07-03 22:05:02.262 UTC client backend[15154] pg_regress/multirangetypes LOG: disconnection: session time: 0:00:01.341 user=postgres database=regression host=[local] 2025-07-03 22:05:02.608 UTC not initialized[15390] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.614 UTC client backend[15390] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.614 UTC client backend[15390] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/horology 2025-07-03 22:05:02.617 UTC client backend[15390] pg_regress/horology LOG: connection ready: setup total=15.043 ms, fork=3.963 ms, authentication=4.769 ms 2025-07-03 22:05:02.624 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33 2025-07-03 22:05:02.624 UTC client backend[15390] pg_regress/horology HINT: Perhaps you need a different "DateStyle" setting. 2025-07-03 22:05:02.624 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone '27/12/2001 04:05:06.789-08'; 2025-07-03 22:05:02.629 UTC not initialized[15393] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.634 UTC client backend[15393] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.634 UTC client backend[15393] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/type_sanity 2025-07-03 22:05:02.651 UTC not initialized[15398] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.653 UTC client backend[15398] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.653 UTC client backend[15398] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/geometry 2025-07-03 22:05:02.658 UTC not initialized[15402] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.659 UTC client backend[15402] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.659 UTC client backend[15402] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/unicode 2025-07-03 22:05:02.662 UTC client backend[15402] pg_regress/unicode LOG: connection ready: setup total=6.297 ms, fork=1.605 ms, authentication=0.456 ms 2025-07-03 22:05:02.666 UTC not initialized[15403] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.668 UTC client backend[15403] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.668 UTC client backend[15403] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tstypes 2025-07-03 22:05:02.670 UTC client backend[15403] pg_regress/tstypes LOG: connection ready: setup total=11.697 ms, fork=4.944 ms, authentication=0.382 ms 2025-07-03 22:05:02.674 UTC client backend[15402] pg_regress/unicode ERROR: invalid normalization form: def 2025-07-03 22:05:02.674 UTC client backend[15402] pg_regress/unicode STATEMENT: SELECT "normalize"('abc', 'def'); 2025-07-03 22:05:02.674 UTC not initialized[15404] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.675 UTC not initialized[15405] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.676 UTC client backend[15404] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.676 UTC client backend[15404] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_import 2025-07-03 22:05:02.680 UTC client backend[15405] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.680 UTC client backend[15405] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/comments 2025-07-03 22:05:02.681 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28 2025-07-03 22:05:02.681 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT time with time zone 'T040506.789 America/Los_Angeles'; 2025-07-03 22:05:02.682 UTC client backend[15404] pg_regress/stats_import LOG: connection ready: setup total=16.366 ms, fork=5.990 ms, authentication=0.543 ms 2025-07-03 22:05:02.683 UTC client backend[15405] pg_regress/comments LOG: connection ready: setup total=15.777 ms, fork=6.744 ms, authentication=0.440 ms 2025-07-03 22:05:02.686 UTC client backend[15402] pg_regress/unicode ERROR: invalid normalization form: def 2025-07-03 22:05:02.686 UTC client backend[15402] pg_regress/unicode STATEMENT: SELECT is_normalized('abc', 'def'); 2025-07-03 22:05:02.689 UTC client backend[15402] pg_regress/unicode LOG: disconnection: session time: 0:00:00.031 user=postgres database=regression host=[local] 2025-07-03 22:05:02.689 UTC client backend[15398] pg_regress/geometry LOG: connection ready: setup total=59.554 ms, fork=17.230 ms, authentication=0.411 ms 2025-07-03 22:05:02.693 UTC client backend[15403] pg_regress/tstypes ERROR: syntax error in tsvector: "'' '1' '2'" at character 8 2025-07-03 22:05:02.693 UTC client backend[15403] pg_regress/tstypes STATEMENT: SELECT $$'' '1' '2'$$::tsvector; 2025-07-03 22:05:02.697 UTC client backend[15393] pg_regress/type_sanity LOG: connection ready: setup total=84.636 ms, fork=9.542 ms, authentication=0.417 ms 2025-07-03 22:05:02.703 UTC not initialized[15399] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.705 UTC client backend[15399] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.705 UTC client backend[15399] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/regex 2025-07-03 22:05:02.708 UTC client backend[15405] pg_regress/comments LOG: disconnection: session time: 0:00:00.034 user=postgres database=regression host=[local] 2025-07-03 22:05:02.709 UTC client backend[15404] pg_regress/stats_import ERROR: "schemaname" cannot be NULL 2025-07-03 22:05:02.709 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'relname', 'test', 'relpages', 17::integer); 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import ERROR: "relname" cannot be NULL 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relpages', 17::integer); 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import WARNING: argument "schemaname" has type "double precision", expected type "text" 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import ERROR: "schemaname" cannot be NULL 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 3.6::float, 'relname', 'test', 'relpages', 17::integer); 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import WARNING: argument "relname" has type "oid", expected type "text" 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import ERROR: "relname" cannot be NULL 2025-07-03 22:05:02.710 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 0::oid, 'relpages', 17::integer); 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'nope', 'relpages', 17::integer); 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import ERROR: variadic arguments must be name/value pairs 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import HINT: Provide an even number of variadic arguments that can be divided into pairs. 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', 'relallvisible'); 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import ERROR: name at variadic position 5 is NULL 2025-07-03 22:05:02.711 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'test', NULL, '17'::integer); 2025-07-03 22:05:02.716 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type time: "T04" at character 31 2025-07-03 22:05:02.716 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT time without time zone 'T04'; 2025-07-03 22:05:02.726 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type time with time zone: "T04+08" at character 28 2025-07-03 22:05:02.726 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT time with time zone 'T04+08'; 2025-07-03 22:05:02.727 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 J J J" at character 13 2025-07-03 22:05:02.727 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '1995-08-06 J J J'; 2025-07-03 22:05:02.727 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "J J 1520447" at character 13 2025-07-03 22:05:02.727 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date 'J J 1520447'; 2025-07-03 22:05:02.728 UTC not initialized[15409] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.728 UTC client backend[15399] pg_regress/regex LOG: connection ready: setup total=89.901 ms, fork=60.702 ms, authentication=0.416 ms 2025-07-03 22:05:02.730 UTC client backend[15409] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.730 UTC client backend[15409] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/opr_sanity 2025-07-03 22:05:02.731 UTC not initialized[15407] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.735 UTC client backend[15407] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.735 UTC client backend[15407] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc_sanity 2025-07-03 22:05:02.740 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33 2025-07-03 22:05:02.740 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08'; 2025-07-03 22:05:02.740 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33 2025-07-03 22:05:02.740 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456-08" at character 33 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456-08'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "J2452271 T X03456.001e6-08" at character 33 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone 'J2452271 T X03456.001e6-08'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 epoch" at character 13 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '1995-08-06 epoch'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 infinity" at character 13 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '1995-08-06 infinity'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "1995-08-06 -infinity" at character 13 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '1995-08-06 -infinity'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "today infinity" at character 13 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date 'today infinity'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type date: "-infinity infinity" at character 13 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '-infinity infinity'; 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18 2025-07-03 22:05:02.741 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 epoch'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 infinity'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp '1995-08-06 -infinity'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "epoch 01:01:01" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp 'epoch 01:01:01'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "infinity 01:01:01" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp 'infinity 01:01:01'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp '-infinity 01:01:01'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "now epoch" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp 'now epoch'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp: "-infinity infinity" at character 18 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp '-infinity infinity'; 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 epoch'; 2025-07-03 22:05:02.742 UTC client backend[15409] pg_regress/opr_sanity LOG: connection ready: setup total=23.781 ms, fork=7.847 ms, authentication=0.400 ms 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20 2025-07-03 22:05:02.742 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 infinity'; 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz '1995-08-06 -infinity'; 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz 'epoch 01:01:01'; 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz 'infinity 01:01:01'; 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity 01:01:01'; 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "now epoch" at character 20 2025-07-03 22:05:02.743 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz 'now epoch'; 2025-07-03 22:05:02.749 UTC client backend[15407] pg_regress/misc_sanity LOG: connection ready: setup total=58.354 ms, fork=34.848 ms, authentication=0.393 ms 2025-07-03 22:05:02.763 UTC not initialized[15412] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.766 UTC not initialized[15411] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.769 UTC client backend[15398] pg_regress/geometry ERROR: value out of range: underflow 2025-07-03 22:05:02.769 UTC client backend[15398] 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-07-03 22:05:02.770 UTC client backend[15412] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.770 UTC client backend[15412] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/mvcc 2025-07-03 22:05:02.770 UTC client backend[15399] pg_regress/regex ERROR: regexp_match() does not support the "global" option 2025-07-03 22:05:02.770 UTC client backend[15399] pg_regress/regex HINT: Use the regexp_matches function instead. 2025-07-03 22:05:02.770 UTC client backend[15399] pg_regress/regex STATEMENT: select regexp_match('abc', 'Bd', 'ig'); 2025-07-03 22:05:02.774 UTC client backend[15390] pg_regress/horology ERROR: invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20 2025-07-03 22:05:02.774 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamptz '-infinity infinity'; 2025-07-03 22:05:02.779 UTC client backend[15412] pg_regress/mvcc LOG: connection ready: setup total=29.479 ms, fork=10.206 ms, authentication=0.425 ms 2025-07-03 22:05:02.780 UTC client backend[15404] pg_regress/stats_import WARNING: argument "relpages" has type "text", expected type "integer" 2025-07-03 22:05:02.785 UTC not initialized[15410] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.785 UTC client backend[15398] pg_regress/geometry ERROR: value out of range: overflow 2025-07-03 22:05:02.785 UTC client backend[15398] 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-07-03 22:05:02.786 UTC client backend[15410] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.786 UTC client backend[15410] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/database 2025-07-03 22:05:02.788 UTC client backend[15411] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.788 UTC client backend[15411] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xid 2025-07-03 22:05:02.789 UTC client backend[15398] pg_regress/geometry ERROR: division by zero 2025-07-03 22:05:02.789 UTC client backend[15398] 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-07-03 22:05:02.791 UTC client backend[15411] pg_regress/xid LOG: connection ready: setup total=44.980 ms, fork=18.143 ms, authentication=0.423 ms 2025-07-03 22:05:02.793 UTC client backend[15404] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-07-03 22:05:02.796 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type xid: "" at character 8 2025-07-03 22:05:02.796 UTC client backend[15411] pg_regress/xid STATEMENT: select ''::xid; 2025-07-03 22:05:02.796 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type xid: "asdf" at character 8 2025-07-03 22:05:02.796 UTC client backend[15411] pg_regress/xid STATEMENT: select 'asdf'::xid; 2025-07-03 22:05:02.797 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type xid8: "" at character 8 2025-07-03 22:05:02.797 UTC client backend[15411] pg_regress/xid STATEMENT: select ''::xid8; 2025-07-03 22:05:02.798 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type xid8: "asdf" at character 8 2025-07-03 22:05:02.798 UTC client backend[15411] pg_regress/xid STATEMENT: select 'asdf'::xid8; 2025-07-03 22:05:02.804 UTC client backend[15390] pg_regress/horology ERROR: operator does not exist: date - time with time zone at character 26 2025-07-03 22:05:02.804 UTC client backend[15390] pg_regress/horology HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.804 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC"; 2025-07-03 22:05:02.810 UTC client backend[15410] pg_regress/database LOG: connection ready: setup total=71.815 ms, fork=39.210 ms, authentication=0.418 ms 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_restore_relation_stats( 'schemaname', 'stats_import', 'relname', 'testseq'); 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import ERROR: cannot modify statistics for relation "testseq" 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import DETAIL: This operation is not supported for sequences. 2025-07-03 22:05:02.813 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testseq'); 2025-07-03 22:05:02.815 UTC client backend[15390] pg_regress/horology ERROR: timestamp out of range 2025-07-03 22:05:02.815 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-07-03 22:05:02.816 UTC client backend[15390] pg_regress/horology ERROR: timestamp out of range 2025-07-03 22:05:02.816 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp without time zone '294276-12-31 23:59:59' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-07-03 22:05:02.825 UTC not initialized[15417] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:02.826 UTC client backend[15417] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:02.826 UTC client backend[15417] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/expressions 2025-07-03 22:05:02.830 UTC client backend[15411] pg_regress/xid ERROR: operator does not exist: xid < xid at character 17 2025-07-03 22:05:02.830 UTC client backend[15411] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.830 UTC client backend[15411] pg_regress/xid STATEMENT: select '1'::xid < '2'::xid; 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid ERROR: operator does not exist: xid <= xid at character 17 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid STATEMENT: select '1'::xid <= '2'::xid; 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid ERROR: operator does not exist: xid > xid at character 17 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.831 UTC client backend[15411] pg_regress/xid STATEMENT: select '1'::xid > '2'::xid; 2025-07-03 22:05:02.832 UTC client backend[15411] pg_regress/xid ERROR: operator does not exist: xid >= xid at character 17 2025-07-03 22:05:02.832 UTC client backend[15411] pg_regress/xid HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.832 UTC client backend[15411] pg_regress/xid STATEMENT: select '1'::xid >= '2'::xid; 2025-07-03 22:05:02.833 UTC client backend[15404] pg_regress/stats_import ERROR: cannot modify statistics for relation "testview" 2025-07-03 22:05:02.833 UTC client backend[15404] pg_regress/stats_import DETAIL: This operation is not supported for views. 2025-07-03 22:05:02.833 UTC client backend[15404] pg_regress/stats_import STATEMENT: SELECT pg_catalog.pg_clear_relation_stats(schemaname => 'stats_import', relname => 'testview'); 2025-07-03 22:05:02.833 UTC client backend[15404] pg_regress/stats_import ERROR: "schemaname" cannot be NULL 2025-07-03 22:05:02.833 UTC client backend[15404] 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-07-03 22:05:02.834 UTC client backend[15404] pg_regress/stats_import ERROR: schema "nope" does not exist 2025-07-03 22:05:02.834 UTC client backend[15404] 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-07-03 22:05:02.834 UTC client backend[15404] pg_regress/stats_import ERROR: "relname" cannot be NULL 2025-07-03 22:05:02.834 UTC client backend[15404] 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-07-03 22:05:02.834 UTC client backend[15404] pg_regress/stats_import ERROR: relation "stats_import.nope" does not exist 2025-07-03 22:05:02.834 UTC client backend[15404] 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-07-03 22:05:02.845 UTC client backend[15404] pg_regress/stats_import ERROR: "relname" cannot be NULL 2025-07-03 22:05:02.845 UTC client backend[15404] 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-07-03 22:05:02.845 UTC client backend[15404] pg_regress/stats_import ERROR: must specify either attname or attnum 2025-07-03 22:05:02.845 UTC client backend[15404] 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-07-03 22:05:02.845 UTC client backend[15404] pg_regress/stats_import ERROR: column "nope" of relation "test" does not exist 2025-07-03 22:05:02.845 UTC client backend[15404] 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-07-03 22:05:02.846 UTC client backend[15404] pg_regress/stats_import ERROR: cannot specify both attname and attnum 2025-07-03 22:05:02.846 UTC client backend[15404] 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-07-03 22:05:02.846 UTC client backend[15404] pg_regress/stats_import ERROR: must specify either attname or attnum 2025-07-03 22:05:02.846 UTC client backend[15404] 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-07-03 22:05:02.846 UTC client backend[15404] pg_regress/stats_import ERROR: cannot modify statistics on system column "xmin" 2025-07-03 22:05:02.846 UTC client backend[15404] 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-07-03 22:05:02.846 UTC client backend[15404] pg_regress/stats_import ERROR: "inherited" cannot be NULL 2025-07-03 22:05:02.846 UTC client backend[15404] 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-07-03 22:05:02.853 UTC client backend[15417] pg_regress/expressions LOG: connection ready: setup total=52.234 ms, fork=21.961 ms, authentication=0.408 ms 2025-07-03 22:05:02.859 UTC client backend[15390] pg_regress/horology ERROR: timestamp out of range 2025-07-03 22:05:02.859 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; 2025-07-03 22:05:02.864 UTC client backend[15390] pg_regress/horology ERROR: timestamp out of range 2025-07-03 22:05:02.864 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT timestamp with time zone '294276-12-31 23:59:59 UTC' + interval '9223372036854775807 microseconds' AS "out of range"; 2025-07-03 22:05:02.886 UTC client backend[15407] pg_regress/misc_sanity LOG: disconnection: session time: 0:00:00.160 user=postgres database=regression host=[local] 2025-07-03 22:05:02.887 UTC client backend[15417] pg_regress/expressions WARNING: TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-07-03 22:05:02.888 UTC client backend[15398] pg_regress/geometry ERROR: operator does not exist: lseg # point at character 23 2025-07-03 22:05:02.888 UTC client backend[15398] pg_regress/geometry HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:02.888 UTC client backend[15398] pg_regress/geometry STATEMENT: SELECT p.f1, l.s, l.s # p.f1 AS intersection FROM LSEG_TBL l, POINT_TBL p; 2025-07-03 22:05:02.898 UTC client backend[15417] pg_regress/expressions WARNING: TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6 2025-07-03 22:05:02.899 UTC client backend[15417] pg_regress/expressions WARNING: TIME(7) precision reduced to maximum allowed, 6 2025-07-03 22:05:02.899 UTC client backend[15417] pg_regress/expressions WARNING: TIMESTAMP(7) precision reduced to maximum allowed, 6 2025-07-03 22:05:02.908 UTC client backend[15403] pg_regress/tstypes ERROR: lexeme array may not contain nulls 2025-07-03 22:05:02.908 UTC client backend[15403] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]); 2025-07-03 22:05:02.908 UTC client backend[15403] pg_regress/tstypes ERROR: lexeme array may not contain empty strings 2025-07-03 22:05:02.908 UTC client backend[15403] pg_regress/tstypes STATEMENT: SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']); 2025-07-03 22:05:02.908 UTC client backend[15390] pg_regress/horology ERROR: cannot cast type time with time zone to interval at character 8 2025-07-03 22:05:02.908 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01"; 2025-07-03 22:05:02.910 UTC client backend[15403] pg_regress/tstypes ERROR: weight array may not contain nulls 2025-07-03 22:05:02.910 UTC client backend[15403] pg_regress/tstypes STATEMENT: SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}'); 2025-07-03 22:05:02.914 UTC client backend[15390] pg_regress/horology ERROR: cannot cast type interval to time with time zone at character 8 2025-07-03 22:05:02.914 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08"; 2025-07-03 22:05:02.914 UTC client backend[15403] pg_regress/tstypes LOG: disconnection: session time: 0:00:00.250 user=postgres database=regression host=[local] 2025-07-03 22:05:02.935 UTC client backend[15398] pg_regress/geometry ERROR: open path cannot be converted to polygon 2025-07-03 22:05:02.935 UTC client backend[15398] pg_regress/geometry STATEMENT: SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1); 2025-07-03 22:05:02.960 UTC client backend[15398] pg_regress/geometry ERROR: division by zero 2025-07-03 22:05:02.960 UTC client backend[15398] 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-07-03 22:05:02.975 UTC client backend[15404] pg_regress/stats_import WARNING: unrecognized argument name: "nope" 2025-07-03 22:05:02.984 UTC client backend[15404] pg_regress/stats_import WARNING: "most_common_vals" must be specified when "most_common_freqs" is specified 2025-07-03 22:05:02.999 UTC client backend[15404] pg_regress/stats_import WARNING: "most_common_freqs" must be specified when "most_common_vals" is specified 2025-07-03 22:05:03.028 UTC client backend[15404] pg_regress/stats_import WARNING: argument "most_common_freqs" has type "double precision[]", expected type "real[]" 2025-07-03 22:05:03.028 UTC client backend[15404] pg_regress/stats_import WARNING: "most_common_freqs" must be specified when "most_common_vals" is specified 2025-07-03 22:05:03.048 UTC client backend[15404] pg_regress/stats_import WARNING: invalid input syntax for type integer: "four" 2025-07-03 22:05:03.089 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "31:12:" at character 8 2025-07-03 22:05:03.089 UTC client backend[15411] pg_regress/xid STATEMENT: select '31:12:'::pg_snapshot; 2025-07-03 22:05:03.094 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "0:1:" at character 8 2025-07-03 22:05:03.094 UTC client backend[15411] pg_regress/xid STATEMENT: select '0:1:'::pg_snapshot; 2025-07-03 22:05:03.094 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:13:0" at character 8 2025-07-03 22:05:03.094 UTC client backend[15411] pg_regress/xid STATEMENT: select '12:13:0'::pg_snapshot; 2025-07-03 22:05:03.097 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8 2025-07-03 22:05:03.097 UTC client backend[15411] pg_regress/xid STATEMENT: select '12:16:14,13'::pg_snapshot; 2025-07-03 22:05:03.107 UTC client backend[15404] pg_regress/stats_import WARNING: "histogram_bounds" array cannot contain NULL values 2025-07-03 22:05:03.120 UTC client backend[15398] pg_regress/geometry ERROR: must request at least 2 points 2025-07-03 22:05:03.120 UTC client backend[15398] pg_regress/geometry STATEMENT: SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>'; 2025-07-03 22:05:03.120 UTC client backend[15398] pg_regress/geometry ERROR: cannot convert circle with radius zero to polygon 2025-07-03 22:05:03.120 UTC client backend[15398] pg_regress/geometry STATEMENT: SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>'; 2025-07-03 22:05:03.146 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait flush-all 2025-07-03 22:05:03.151 UTC client backend[15404] pg_regress/stats_import WARNING: "elem_count_histogram" array cannot contain NULL values 2025-07-03 22:05:03.157 UTC client backend[15411] pg_regress/xid ERROR: invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20 2025-07-03 22:05:03.157 UTC client backend[15411] pg_regress/xid STATEMENT: SELECT pg_snapshot '1:9223372036854775808:3'; 2025-07-03 22:05:03.186 UTC client backend[15398] pg_regress/geometry ERROR: value out of range: overflow 2025-07-03 22:05:03.186 UTC client backend[15398] 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-07-03 22:05:03.189 UTC client backend[15398] pg_regress/geometry ERROR: division by zero 2025-07-03 22:05:03.189 UTC client backend[15398] 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-07-03 22:05:03.199 UTC client backend[15411] pg_regress/xid LOG: disconnection: session time: 0:00:00.434 user=postgres database=regression host=[local] 2025-07-03 22:05:03.207 UTC client backend[15404] pg_regress/stats_import WARNING: attribute "id" is not a range type 2025-07-03 22:05:03.207 UTC client backend[15404] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-07-03 22:05:03.223 UTC client backend[15404] pg_regress/stats_import WARNING: "range_empty_frac" must be specified when "range_length_histogram" is specified 2025-07-03 22:05:03.245 UTC client backend[15398] pg_regress/geometry LOG: disconnection: session time: 0:00:00.597 user=postgres database=regression host=[local] 2025-07-03 22:05:03.259 UTC client backend[15404] pg_regress/stats_import WARNING: "range_length_histogram" must be specified when "range_empty_frac" is specified 2025-07-03 22:05:03.264 UTC client backend[15417] pg_regress/expressions ERROR: operator does not exist: point = box at character 23 2025-07-03 22:05:03.264 UTC client backend[15417] pg_regress/expressions HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:03.264 UTC client backend[15417] pg_regress/expressions STATEMENT: select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0)); 2025-07-03 22:05:03.299 UTC client backend[15404] pg_regress/stats_import WARNING: attribute "id" is not a range type 2025-07-03 22:05:03.299 UTC client backend[15404] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM. 2025-07-03 22:05:03.335 UTC client backend[15404] pg_regress/stats_import WARNING: unable to determine element type of attribute "arange" 2025-07-03 22:05:03.335 UTC client backend[15404] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-07-03 22:05:03.351 UTC client backend[15417] pg_regress/expressions LOG: disconnection: session time: 0:00:00.528 user=postgres database=regression host=[local] 2025-07-03 22:05:03.359 UTC client backend[15404] pg_regress/stats_import WARNING: unable to determine element type of attribute "id" 2025-07-03 22:05:03.359 UTC client backend[15404] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-07-03 22:05:03.363 UTC client backend[15404] pg_regress/stats_import WARNING: "most_common_elem_freqs" must be specified when "most_common_elems" is specified 2025-07-03 22:05:03.380 UTC client backend[15404] pg_regress/stats_import WARNING: "most_common_elems" must be specified when "most_common_elem_freqs" is specified 2025-07-03 22:05:03.408 UTC client backend[15404] pg_regress/stats_import WARNING: unable to determine element type of attribute "id" 2025-07-03 22:05:03.408 UTC client backend[15404] pg_regress/stats_import DETAIL: Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST. 2025-07-03 22:05:03.472 UTC client backend[15412] pg_regress/mvcc LOG: disconnection: session time: 0:00:00.712 user=postgres database=regression host=[local] 2025-07-03 22:05:03.513 UTC checkpointer[14511] LOG: checkpoint complete: wrote 3919 buffers (23.9%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 2 recycled; write=0.157 s, sync=0.001 s, total=0.367 s; sync files=0, longest=0.000 s, average=0.000 s; distance=29222 kB, estimate=29222 kB; lsn=0/355FB10, redo lsn=0/3420698 2025-07-03 22:05:03.563 UTC client backend[15399] pg_regress/regex ERROR: invalid regular expression: regular expression is too complex 2025-07-03 22:05:03.563 UTC client backend[15399] pg_regress/regex STATEMENT: select 'x' ~ repeat('x*y*z*', 1000); 2025-07-03 22:05:03.619 UTC client backend[15399] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-07-03 22:05:03.619 UTC client backend[15399] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=\1)'; 2025-07-03 22:05:03.620 UTC client backend[15399] pg_regress/regex ERROR: invalid regular expression: invalid backreference number 2025-07-03 22:05:03.620 UTC client backend[15399] pg_regress/regex STATEMENT: select 'xyz' ~ 'x(\w)(?=(\1))'; 2025-07-03 22:05:03.621 UTC client backend[15399] pg_regress/regex ERROR: invalid regular expression: invalid escape \ sequence 2025-07-03 22:05:03.621 UTC client backend[15399] pg_regress/regex STATEMENT: select 'a' ~ '\x7fffffff'; 2025-07-03 22:05:03.621 UTC client backend[15399] pg_regress/regex LOG: disconnection: session time: 0:00:00.921 user=postgres database=regression host=[local] 2025-07-03 22:05:03.735 UTC client backend[15404] pg_regress/stats_import LOG: disconnection: session time: 0:00:01.063 user=postgres database=regression host=[local] 2025-07-03 22:05:03.795 UTC client backend[15393] pg_regress/type_sanity LOG: disconnection: session time: 0:00:01.172 user=postgres database=regression host=[local] 2025-07-03 22:05:03.882 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait 2025-07-03 22:05:03.889 UTC checkpointer[14511] LOG: checkpoint complete: wrote 58 buffers (0.4%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.007 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1398 kB, estimate=26440 kB; lsn=0/357E2A8, redo lsn=0/357E250 2025-07-03 22:05:03.965 UTC client backend[15390] pg_regress/horology ERROR: date out of range for timestamp 2025-07-03 22:05:03.965 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamp; 2025-07-03 22:05:03.966 UTC client backend[15390] pg_regress/horology ERROR: date out of range for timestamp 2025-07-03 22:05:03.966 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT '2202020-10-05'::date::timestamptz; 2025-07-03 22:05:03.969 UTC client backend[15390] pg_regress/horology ERROR: date out of range for timestamp 2025-07-03 22:05:03.969 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT '4714-11-24 BC'::date::timestamptz; 2025-07-03 22:05:04.007 UTC client backend[15390] pg_regress/horology ERROR: invalid value "/Feb/16" for "Mon" 2025-07-03 22:05:04.007 UTC client backend[15390] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-07-03 22:05:04.007 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('97/Feb/16', 'YYMonDD'); 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology ERROR: invalid value "JUNK" for "TZ" 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology DETAIL: Time zone abbreviation is not recognized. 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ'); 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology ERROR: invalid value ".." for "TZ" 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.028 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ'); 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology ERROR: invalid value "xy" for "OF" 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.029 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF'); 2025-07-03 22:05:04.038 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2018-11-02 12:34:56.123456789" 2025-07-03 22:05:04.038 UTC client backend[15390] 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-07-03 22:05:04.048 UTC client backend[15390] pg_regress/horology ERROR: invalid value "+" for "MON" 2025-07-03 22:05:04.048 UTC client backend[15390] pg_regress/horology DETAIL: The given value did not match any of the allowed values for this field. 2025-07-03 22:05:04.048 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2000 + + JUN', 'YYYY MON'); 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology ERROR: invalid value "x1" for "MM" 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2011 x12 x18', 'YYYYxMMxDD'); 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology ERROR: invalid combination of date conventions 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology HINT: Do not mix Gregorian and ISO week date conventions in a formatting template. 2025-07-03 22:05:04.057 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2005527', 'YYYYIWID'); 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology ERROR: source string too short for "MM" formatting field 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 remain. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('19971', 'YYYYMMDD'); 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology ERROR: invalid value "1)" for "MM" 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology DETAIL: Field requires 2 characters, but only 1 could be parsed. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology HINT: If your source string is not fixed-width, try using the "FM" modifier. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('19971)24', 'YYYYMMDD'); 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology ERROR: invalid value "da" for "DD" 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY'); 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology ERROR: invalid value "uary" for "YYYY" 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.058 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY'); 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology ERROR: conflicting values for "Mon" field in formatting string 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology DETAIL: This value contradicts a previous setting for the same field type. 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD'); 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology ERROR: invalid value "xy" for "DD" 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology DETAIL: Value must be an integer. 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('199711xy', 'YYYYMMDD'); 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology ERROR: value for "YYYY" in source string is out of range 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology DETAIL: Value must be in the range -2147483648 to 2147483647. 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('10000000000', 'FMYYYY'); 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 25:00:00" 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:60:00" 2025-07-03 22:05:04.059 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.060 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-06-13 15:50:60" 2025-07-03 22:05:04.060 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.064 UTC client backend[15390] pg_regress/horology ERROR: hour "15" is invalid for the 12-hour clock 2025-07-03 22:05:04.064 UTC client backend[15390] pg_regress/horology HINT: Use the 24-hour clock, or give an hour between 1 and 12. 2025-07-03 22:05:04.064 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS'); 2025-07-03 22:05:04.064 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-13-01 15:50:55" 2025-07-03 22:05:04.064 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30 15:50:55" 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29 15:50:55" 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS'); 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-07-03 22:05:04.065 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS'); 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2015-02-11 86400" 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS'); 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology ERROR: value for "Y,YYY" in source string is out of range 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('1000000000,999', 'Y,YYY'); 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "0.-2147483648" 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('0.-2147483648', 'SS.MS'); 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "613566758" 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('613566758', 'W'); 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2024 613566758 1" 2025-07-03 22:05:04.066 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_timestamp('2024 613566758 1', 'YYYY WW D'); 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-13-10" 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2016-13-10', 'YYYY-MM-DD'); 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016-02-30" 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2016-02-30', 'YYYY-MM-DD'); 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2015-02-29" 2025-07-03 22:05:04.067 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2015-02-29', 'YYYY-MM-DD'); 2025-07-03 22:05:04.068 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2015 366" 2025-07-03 22:05:04.068 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2015 366', 'YYYY DDD'); 2025-07-03 22:05:04.068 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2016 367" 2025-07-03 22:05:04.068 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2016 367', 'YYYY DDD'); 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "100000000" 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('100000000', 'CC'); 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "-100000000" 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('-100000000', 'CC'); 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "-2147483648 01" 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('-2147483648 01', 'CC YY'); 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology ERROR: date/time field value out of range: "2147483647 01" 2025-07-03 22:05:04.069 UTC client backend[15390] pg_regress/horology STATEMENT: SELECT to_date('2147483647 01', 'CC YY'); 2025-07-03 22:05:04.080 UTC client backend[15390] pg_regress/horology LOG: disconnection: session time: 0:00:01.473 user=postgres database=regression host=[local] 2025-07-03 22:05:04.364 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait 2025-07-03 22:05:04.434 UTC checkpointer[14511] LOG: checkpoint complete: wrote 31 buffers (0.2%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.070 s; sync files=0, longest=0.000 s, average=0.000 s; distance=133 kB, estimate=23809 kB; lsn=0/35A3B30, redo lsn=0/359F690 2025-07-03 22:05:04.458 UTC client backend[15410] pg_regress/database LOG: disconnection: session time: 0:00:01.680 user=postgres database=regression host=[local] 2025-07-03 22:05:05.278 UTC client backend[15409] pg_regress/opr_sanity LOG: disconnection: session time: 0:00:02.551 user=postgres database=regression host=[local] 2025-07-03 22:05:05.699 UTC not initialized[15724] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.705 UTC client backend[15724] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.705 UTC client backend[15724] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copydml 2025-07-03 22:05:05.708 UTC client backend[15724] pg_regress/copydml LOG: connection ready: setup total=17.244 ms, fork=7.409 ms, authentication=0.412 ms 2025-07-03 22:05:05.708 UTC not initialized[15725] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.710 UTC client backend[15725] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.710 UTC client backend[15725] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copy 2025-07-03 22:05:05.713 UTC client backend[15725] pg_regress/copy LOG: connection ready: setup total=18.062 ms, fork=12.537 ms, authentication=0.413 ms 2025-07-03 22:05:05.717 UTC not initialized[15726] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.729 UTC client backend[15726] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.729 UTC client backend[15726] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyselect 2025-07-03 22:05:05.735 UTC not initialized[15727] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.736 UTC client backend[15726] pg_regress/copyselect LOG: connection ready: setup total=34.107 ms, fork=15.190 ms, authentication=1.121 ms 2025-07-03 22:05:05.737 UTC not initialized[15728] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.738 UTC not initialized[15729] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:05.740 UTC client backend[15727] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.740 UTC client backend[15727] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert_conflict 2025-07-03 22:05:05.740 UTC client backend[15728] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.740 UTC client backend[15728] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/insert 2025-07-03 22:05:05.743 UTC client backend[15728] pg_regress/insert LOG: connection ready: setup total=23.119 ms, fork=14.680 ms, authentication=0.386 ms 2025-07-03 22:05:05.743 UTC client backend[15727] pg_regress/insert_conflict LOG: connection ready: setup total=25.894 ms, fork=16.950 ms, authentication=3.267 ms 2025-07-03 22:05:05.747 UTC client backend[15729] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:05.747 UTC client backend[15729] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/copyencoding 2025-07-03 22:05:05.750 UTC client backend[15729] pg_regress/copyencoding LOG: connection ready: setup total=27.618 ms, fork=14.121 ms, authentication=8.012 ms 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'g') to stdout; 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml ERROR: COPY query must have a RETURNING clause 2025-07-03 22:05:05.762 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-07-03 22:05:05.763 UTC client backend[15724] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-07-03 22:05:05.763 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.766 UTC client backend[15724] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-07-03 22:05:05.766 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.768 UTC client backend[15724] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.768 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.773 UTC client backend[15724] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.773 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.777 UTC client backend[15724] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-07-03 22:05:05.777 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-07-03 22:05:05.780 UTC client backend[15724] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-07-03 22:05:05.780 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-07-03 22:05:05.785 UTC client backend[15728] pg_regress/insert ERROR: null value in column "col2" of relation "inserttest" violates not-null constraint 2025-07-03 22:05:05.785 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (null, null, testing). 2025-07-03 22:05:05.785 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT); 2025-07-03 22:05:05.787 UTC client backend[15724] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.787 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-07-03 22:05:05.792 UTC client backend[15724] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.792 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (update copydml_test set t = 'f') to stdout; 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT); 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert ERROR: INSERT has more target columns than expressions at character 37 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (col1, col2, col3) values (1, 2); 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 42 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (col1) values (1, 2); 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert ERROR: INSERT has more expressions than target columns at character 48 2025-07-03 22:05:05.794 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (col1) values (DEFAULT, DEFAULT); 2025-07-03 22:05:05.796 UTC client backend[15729] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-07-03 22:05:05.796 UTC client backend[15729] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-07-03 22:05:05.796 UTC client backend[15729] 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-07-03 22:05:05.799 UTC client backend[15724] pg_regress/copydml ERROR: DO INSTEAD NOTHING rules are not supported for COPY 2025-07-03 22:05:05.799 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-07-03 22:05:05.802 UTC client backend[15729] pg_regress/copyencoding ERROR: invalid byte sequence for encoding "EUC_JP": 0xe3 0x81 2025-07-03 22:05:05.802 UTC client backend[15729] pg_regress/copyencoding CONTEXT: COPY copy_encoding_tab, line 1 2025-07-03 22:05:05.802 UTC client backend[15729] pg_regress/copyencoding STATEMENT: COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/src/test/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv); 2025-07-03 22:05:05.805 UTC client backend[15725] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-07-03 22:05:05.805 UTC client backend[15725] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-07-03 22:05:05.805 UTC client backend[15725] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-07-03 22:05:05.806 UTC client backend[15725] pg_regress/copy ERROR: end-of-copy marker is not alone on its line 2025-07-03 22:05:05.806 UTC client backend[15725] pg_regress/copy CONTEXT: COPY copytest2, line 3 2025-07-03 22:05:05.806 UTC client backend[15725] pg_regress/copy STATEMENT: copy copytest2(test) from stdin; 2025-07-03 22:05:05.807 UTC client backend[15724] pg_regress/copydml ERROR: DO ALSO rules are not supported for COPY 2025-07-03 22:05:05.807 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-07-03 22:05:05.809 UTC client backend[15726] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-07-03 22:05:05.809 UTC client backend[15726] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-07-03 22:05:05.809 UTC client backend[15726] pg_regress/copyselect STATEMENT: copy v_test1 to stdout; 2025-07-03 22:05:05.811 UTC client backend[15726] pg_regress/copyselect ERROR: COPY (SELECT INTO) is not supported 2025-07-03 22:05:05.811 UTC client backend[15726] pg_regress/copyselect STATEMENT: copy (select t into temp test3 from test1 where id=3) to stdout; 2025-07-03 22:05:05.822 UTC client backend[15726] pg_regress/copyselect ERROR: syntax error at or near "from" at character 28 2025-07-03 22:05:05.822 UTC client backend[15726] pg_regress/copyselect STATEMENT: copy (select * from test1) from stdin; 2025-07-03 22:05:05.822 UTC client backend[15729] pg_regress/copyencoding LOG: disconnection: session time: 0:00:00.085 user=postgres database=regression host=[local] 2025-07-03 22:05:05.822 UTC client backend[15726] pg_regress/copyselect ERROR: syntax error at or near "(" at character 28 2025-07-03 22:05:05.822 UTC client backend[15726] pg_regress/copyselect STATEMENT: copy (select * from test1) (t,id) to stdout; 2025-07-03 22:05:05.823 UTC client backend[15724] pg_regress/copydml ERROR: multi-statement DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.823 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-07-03 22:05:05.832 UTC client backend[15724] pg_regress/copydml ERROR: conditional DO INSTEAD rules are not supported for COPY 2025-07-03 22:05:05.832 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (delete from copydml_test) to stdout; 2025-07-03 22:05:05.836 UTC client backend[15724] pg_regress/copydml ERROR: COPY query must not be a utility command 2025-07-03 22:05:05.836 UTC client backend[15724] pg_regress/copydml STATEMENT: copy (insert into copydml_test default values) to stdout; 2025-07-03 22:05:05.836 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.836 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing; 2025-07-03 22:05:05.837 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.837 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing; 2025-07-03 22:05:05.841 UTC client backend[15726] pg_regress/copyselect ERROR: cannot copy from view "v_test1" 2025-07-03 22:05:05.841 UTC client backend[15726] pg_regress/copyselect HINT: Try the COPY (SELECT ...) TO variant. 2025-07-03 22:05:05.841 UTC client backend[15726] pg_regress/copyselect STATEMENT: COPY v_test1 TO STDOUT 2025-07-03 22:05:05.861 UTC client backend[15728] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 32 2025-07-03 22:05:05.861 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (f2[1], f2[2]) values (1,default); 2025-07-03 22:05:05.862 UTC client backend[15728] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 33 2025-07-03 22:05:05.862 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttest (f3.if1, f3.if2) values (1,default); 2025-07-03 22:05:05.878 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.878 UTC client backend[15727] 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-07-03 22:05:05.885 UTC client backend[15726] pg_regress/copyselect ERROR: division by zero 2025-07-03 22:05:05.885 UTC client backend[15726] pg_regress/copyselect STATEMENT: copy (select 1) to stdout; select 1/0; 2025-07-03 22:05:05.887 UTC client backend[15726] pg_regress/copyselect ERROR: division by zero 2025-07-03 22:05:05.887 UTC client backend[15726] pg_regress/copyselect STATEMENT: select 1/0; copy (select 1) to stdout; 2025-07-03 22:05:05.893 UTC client backend[15724] pg_regress/copydml LOG: disconnection: session time: 0:00:00.194 user=postgres database=regression host=[local] 2025-07-03 22:05:05.897 UTC client backend[15727] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52 2025-07-03 22:05:05.897 UTC client backend[15727] pg_regress/insert_conflict HINT: For example, ON CONFLICT (column_name). 2025-07-03 22:05:05.897 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit; 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "excluded" at character 117 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict DETAIL: There is an entry for table "excluded", but it cannot be referenced from this part of the query. 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit; 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict ERROR: column "keyy" does not exist at character 64 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key". 2025-07-03 22:05:05.899 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict ERROR: column excluded.fruitt does not exist at character 92 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict HINT: Perhaps you meant to reference the column "excluded.fruit". 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt; 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.904 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.905 UTC client backend[15727] pg_regress/insert_conflict ERROR: invalid reference to FROM-clause entry for table "insertconflicttest" at character 106 2025-07-03 22:05:05.905 UTC client backend[15727] pg_regress/insert_conflict HINT: Perhaps you meant to reference the table alias "ict". 2025-07-03 22:05:05.905 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit; 2025-07-03 22:05:05.906 UTC client backend[15727] pg_regress/insert_conflict ERROR: column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90 2025-07-03 22:05:05.906 UTC client backend[15727] pg_regress/insert_conflict HINT: SET target columns cannot be qualified with the relation name. 2025-07-03 22:05:05.906 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango'; 2025-07-03 22:05:05.911 UTC client backend[15726] pg_regress/copyselect LOG: disconnection: session time: 0:00:00.194 user=postgres database=regression host=[local] 2025-07-03 22:05:05.912 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.912 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.913 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.937 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.937 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.938 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.939 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.939 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.948 UTC client backend[15725] pg_regress/copy ERROR: cannot perform COPY FREEZE on a partitioned table 2025-07-03 22:05:05.948 UTC client backend[15725] pg_regress/copy STATEMENT: copy parted_copytest from '/tmp/cirrus-ci-build/src/test/regress/results/parted_copytest.csv' (freeze); 2025-07-03 22:05:05.952 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.952 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.955 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.955 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:05.970 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit; 2025-07-03 22:05:05.993 UTC client backend[15727] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "fruit_index" 2025-07-03 22:05:05.993 UTC client backend[15727] pg_regress/insert_conflict DETAIL: Key (fruit)=(Peach) already exists. 2025-07-03 22:05:05.993 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit; 2025-07-03 22:05:06.004 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:06.004 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit; 2025-07-03 22:05:06.004 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:06.004 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing; 2025-07-03 22:05:06.004 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:06.004 UTC client backend[15727] 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-07-03 22:05:06.046 UTC client backend[15727] pg_regress/insert_conflict ERROR: column excluded.ctid does not exist at character 82 2025-07-03 22:05:06.046 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text; 2025-07-03 22:05:06.084 UTC client backend[15728] pg_regress/insert ERROR: cannot set an array element to DEFAULT at character 33 2025-07-03 22:05:06.084 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (1,default); 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (0,2); 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6); 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_pos_ints violates check constraint "insert_pos_ints_check" 2025-07-03 22:05:06.085 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttesta (f2[1], f2[2]) select 0,8; 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert ERROR: cannot set a subfield to DEFAULT at character 34 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,default); 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,array[null]); 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-07-03 22:05:06.087 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}'); 2025-07-03 22:05:06.088 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-07-03 22:05:06.088 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}'; 2025-07-03 22:05:06.164 UTC client backend[15727] pg_regress/insert_conflict ERROR: table reference "excluded" is ambiguous at character 76 2025-07-03 22:05:06.164 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *; 2025-07-03 22:05:06.198 UTC client backend[15725] pg_regress/copy ERROR: cannot use "match" with HEADER in COPY TO 2025-07-03 22:05:06.198 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest to stdout with (header match); 2025-07-03 22:05:06.198 UTC client backend[15725] pg_regress/copy ERROR: header requires a Boolean value, a non-negative integer, or the string "match" 2025-07-03 22:05:06.198 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header wrong_choice); 2025-07-03 22:05:06.200 UTC client backend[15725] pg_regress/copy ERROR: column name mismatch in header line field 1: got "a", expected "c" 2025-07-03 22:05:06.200 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c" 2025-07-03 22:05:06.200 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest (c, b, a) from stdin with (header match); 2025-07-03 22:05:06.204 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_nnarray violates check constraint "insert_nnarray_check" 2025-07-03 22:05:06.204 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttesta (f1[1]) values (1); 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy ERROR: column name mismatch in header line field 3: got null value ("\N"), expected "c" 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b \N" 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy ERROR: wrong number of fields in header line: got 2, expected 3 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b" 2025-07-03 22:05:06.208 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy ERROR: wrong number of fields in header line: got 4, expected 3 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b c d" 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy ERROR: column name mismatch in header line field 3: got "d", expected "c" 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a b d" 2025-07-03 22:05:06.209 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-07-03 22:05:06.212 UTC client backend[15728] pg_regress/insert ERROR: value for domain insert_test_domain violates check constraint "insert_test_domain_check" 2025-07-03 22:05:06.212 UTC client backend[15728] pg_regress/insert STATEMENT: insert into inserttestb (f1.if1) values (1); 2025-07-03 22:05:06.215 UTC client backend[15725] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-07-03 22:05:06.215 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a ........pg.dropped.2........ c" 2025-07-03 22:05:06.215 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest from stdin with (header match); 2025-07-03 22:05:06.217 UTC client backend[15725] pg_regress/copy ERROR: wrong number of fields in header line: got 3, expected 2 2025-07-03 22:05:06.217 UTC client backend[15725] pg_regress/copy CONTEXT: COPY header_copytest, line 1: "a c b" 2025-07-03 22:05:06.217 UTC client backend[15725] pg_regress/copy STATEMENT: copy header_copytest (a, c) from stdin with (header match); 2025-07-03 22:05:06.238 UTC client backend[15725] pg_regress/copy ERROR: value too long for type character varying(5) 2025-07-03 22:05:06.238 UTC client backend[15725] pg_regress/copy STATEMENT: copy oversized_column_default (col2) from stdin; 2025-07-03 22:05:06.238 UTC client backend[15725] pg_regress/copy ERROR: value too long for type character varying(5) 2025-07-03 22:05:06.238 UTC client backend[15725] pg_regress/copy STATEMENT: copy oversized_column_default from stdin (default ''); 2025-07-03 22:05:06.239 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-07-03 22:05:06.239 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 11). 2025-07-03 22:05:06.239 UTC client backend[15728] pg_regress/insert STATEMENT: insert into range_parted values ('a', 11); 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict ERROR: duplicate key value violates unique constraint "twoconstraints_f1_key" 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict DETAIL: Key (f1)=(1) already exists. 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(1, '((2,2),(3,3))'); 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-07-03 22:05:06.244 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))'); 2025-07-03 22:05:06.245 UTC client backend[15727] pg_regress/insert_conflict ERROR: conflicting key value violates exclusion constraint "twoconstraints_f2_excl" 2025-07-03 22:05:06.245 UTC client backend[15727] pg_regress/insert_conflict DETAIL: Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)). 2025-07-03 22:05:06.245 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into twoconstraints values(2, '((0,0),(1,2))') on conflict on constraint twoconstraints_f1_key do nothing; 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0; 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-07-03 22:05:06.265 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0; 2025-07-03 22:05:06.267 UTC client backend[15727] pg_regress/insert_conflict ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-07-03 22:05:06.267 UTC client backend[15727] pg_regress/insert_conflict HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-07-03 22:05:06.267 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0; 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (a, 11). 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part1 values ('a', 11); 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (b, 1). 2025-07-03 22:05:06.290 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part1 values ('b', 1); 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (b, 21). 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part4 values ('b', 21); 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part4" violates partition constraint 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (a, 10). 2025-07-03 22:05:06.291 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part4 values ('a', 10); 2025-07-03 22:05:06.292 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-07-03 22:05:06.292 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (null, null). 2025-07-03 22:05:06.292 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part1 values (null); 2025-07-03 22:05:06.296 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:06.296 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a; 2025-07-03 22:05:06.299 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part1" violates partition constraint 2025-07-03 22:05:06.299 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (1, null). 2025-07-03 22:05:06.299 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part1 values (1); 2025-07-03 22:05:06.327 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-07-03 22:05:06.327 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2025-07-03 22:05:06.327 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_aa_bb values ('cc', 1); 2025-07-03 22:05:06.328 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-07-03 22:05:06.328 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (AAa, 1). 2025-07-03 22:05:06.328 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_aa_bb values ('AAa', 1); 2025-07-03 22:05:06.329 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_aa_bb" violates partition constraint 2025-07-03 22:05:06.329 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (null, null). 2025-07-03 22:05:06.329 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_aa_bb values (null); 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (aa, 2). 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_default values ('aa', 2); 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_default" violates partition constraint 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (null, 2). 2025-07-03 22:05:06.363 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_default values (null, 2); 2025-07-03 22:05:06.436 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2025-07-03 22:05:06.436 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (EE, 11). 2025-07-03 22:05:06.436 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('EE', 11); 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_default_p2" violates partition constraint 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (gg, 43). 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_default_p2 values ('gg', 43); 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_ee_ff1" violates partition constraint 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (cc, 1). 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_ee_ff1 values ('cc', 1); 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "part_default" found for row 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (43). 2025-07-03 22:05:06.444 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_default values ('gg', 43); 2025-07-03 22:05:06.469 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-07-03 22:05:06.469 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 0). 2025-07-03 22:05:06.469 UTC client backend[15728] pg_regress/insert STATEMENT: insert into range_parted values ('a', 0); 2025-07-03 22:05:06.470 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-07-03 22:05:06.470 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, 20). 2025-07-03 22:05:06.470 UTC client backend[15728] pg_regress/insert STATEMENT: insert into range_parted values ('a', 20); 2025-07-03 22:05:06.475 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "range_parted" found for row 2025-07-03 22:05:06.475 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, (b + 0)) = (a, null). 2025-07-03 22:05:06.475 UTC client backend[15728] pg_regress/insert STATEMENT: insert into range_parted values ('a'); 2025-07-03 22:05:06.489 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "part_def" violates partition constraint 2025-07-03 22:05:06.489 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (b, 10). 2025-07-03 22:05:06.489 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_def values ('b', 10); 2025-07-03 22:05:06.499 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2025-07-03 22:05:06.499 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2025-07-03 22:05:06.499 UTC client backend[15728] pg_regress/insert STATEMENT: insert into list_parted values ('EE', 0); 2025-07-03 22:05:06.500 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "part_ee_ff" found for row 2025-07-03 22:05:06.500 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (0). 2025-07-03 22:05:06.500 UTC client backend[15728] pg_regress/insert STATEMENT: insert into part_ee_ff values ('EE', 0); 2025-07-03 22:05:06.508 UTC client backend[15725] pg_regress/copy ERROR: cannot perform COPY FREEZE on a foreign table 2025-07-03 22:05:06.508 UTC client backend[15725] pg_regress/copy STATEMENT: copy copytest_foreign_table from stdin (freeze); 2025-07-03 22:05:06.519 UTC client backend[15725] pg_regress/copy ERROR: cannot copy from unpopulated materialized view "copytest_mv" 2025-07-03 22:05:06.519 UTC client backend[15725] pg_regress/copy HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-07-03 22:05:06.519 UTC client backend[15725] pg_regress/copy STATEMENT: COPY copytest_mv(id) TO stdout WITH (header); 2025-07-03 22:05:06.532 UTC client backend[15727] pg_regress/insert_conflict ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:05:06.532 UTC client backend[15727] pg_regress/insert_conflict STATEMENT: insert into parted_conflict_1 values (40, 'cuarenta') on conflict (a) do update set b = excluded.b; 2025-07-03 22:05:06.580 UTC client backend[15725] pg_regress/copy LOG: disconnection: session time: 0:00:00.872 user=postgres database=regression host=[local] 2025-07-03 22:05:06.636 UTC client backend[15727] pg_regress/insert_conflict LOG: disconnection: session time: 0:00:00.902 user=postgres database=regression host=[local] 2025-07-03 22:05:06.717 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "hpart0" violates partition constraint 2025-07-03 22:05:06.717 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (11). 2025-07-03 22:05:06.717 UTC client backend[15728] pg_regress/insert STATEMENT: insert into hpart0 values(11); 2025-07-03 22:05:07.022 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted1" found for row 2025-07-03 22:05:07.022 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains ((b + 0)) = (5). 2025-07-03 22:05:07.022 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted (a, b) values (1, 5); 2025-07-03 22:05:07.029 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted11" violates check constraint "check_b" 2025-07-03 22:05:07.029 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (1, 4). 2025-07-03 22:05:07.029 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 2); 2025-07-03 22:05:07.040 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted1" violates partition constraint 2025-07-03 22:05:07.040 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (3, 2). 2025-07-03 22:05:07.040 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted1 (a, b) values (2, 3); 2025-07-03 22:05:07.043 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "lparted_nonullpart" found for row 2025-07-03 22:05:07.043 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (null). 2025-07-03 22:05:07.043 UTC client backend[15728] pg_regress/insert STATEMENT: insert into lparted_nonullpart values (1); 2025-07-03 22:05:07.139 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted5a" violates check constraint "check_b" 2025-07-03 22:05:07.139 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (1, 45, a). 2025-07-03 22:05:07.139 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'a'); 2025-07-03 22:05:07.149 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted5a" violates partition constraint 2025-07-03 22:05:07.149 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (b, 1, 40). 2025-07-03 22:05:07.149 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted5 (a, b, c) values (1, 40, 'a'); 2025-07-03 22:05:07.217 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted_def" found for row 2025-07-03 22:05:07.217 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a) = (70). 2025-07-03 22:05:07.217 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (70, 100); 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted_def1" violates partition constraint 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (52, 50, null). 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted_def1 values (52, 50); 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mlparted_def2" violates partition constraint 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (34, 50, null). 2025-07-03 22:05:07.218 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted_def2 values (34, 50); 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2025-07-03 22:05:07.307 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2025-07-03 22:05:07.378 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted5_cd" found for row 2025-07-03 22:05:07.378 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (c). 2025-07-03 22:05:07.378 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'c', 1); 2025-07-03 22:05:07.379 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mlparted5" found for row 2025-07-03 22:05:07.379 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (c) = (f). 2025-07-03 22:05:07.379 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mlparted values (1, 45, 'f', 1); 2025-07-03 22:05:07.419 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2025-07-03 22:05:07.419 UTC client backend[15728] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2025-07-03 22:05:07.420 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "key_desc_1" found for row 2025-07-03 22:05:07.420 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (b) = (1). 2025-07-03 22:05:07.420 UTC client backend[15728] pg_regress/insert STATEMENT: insert into key_desc values (1, 1); 2025-07-03 22:05:07.420 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "key_desc" found for row 2025-07-03 22:05:07.420 UTC client backend[15728] pg_regress/insert STATEMENT: insert into key_desc values (2, 1); 2025-07-03 22:05:07.429 UTC client backend[15728] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 75 2025-07-03 22:05:07.429 UTC client backend[15728] pg_regress/insert STATEMENT: create table mcrparted0 partition of mcrparted for values from (minvalue, 0, 0) to (1, maxvalue, maxvalue); 2025-07-03 22:05:07.430 UTC client backend[15728] pg_regress/insert ERROR: every bound following MAXVALUE must also be MAXVALUE at character 100 2025-07-03 22:05:07.430 UTC client backend[15728] pg_regress/insert STATEMENT: create table mcrparted2 partition of mcrparted for values from (10, 6, minvalue) to (10, maxvalue, minvalue); 2025-07-03 22:05:07.431 UTC client backend[15728] pg_regress/insert ERROR: every bound following MINVALUE must also be MINVALUE at character 79 2025-07-03 22:05:07.431 UTC client backend[15728] pg_regress/insert STATEMENT: create table mcrparted4 partition of mcrparted for values from (21, minvalue, 0) to (30, 20, minvalue); 2025-07-03 22:05:07.458 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2025-07-03 22:05:07.458 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (null, null, null). 2025-07-03 22:05:07.458 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mcrparted values (null, null, null); 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert ERROR: no partition of relation "mcrparted" found for row 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert DETAIL: Partition key of the failing row contains (a, abs(b), c) = (11, 1, -1). 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mcrparted values (11, 1, -1); 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mcrparted3" violates partition constraint 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (11, 1, -1). 2025-07-03 22:05:07.463 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mcrparted3 values (11, 1, -1); 2025-07-03 22:05:07.464 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "mcrparted4" violates partition constraint 2025-07-03 22:05:07.464 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (30, 21, 20). 2025-07-03 22:05:07.464 UTC client backend[15728] pg_regress/insert STATEMENT: insert into mcrparted4 values (30, 21, 20); 2025-07-03 22:05:07.491 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-07-03 22:05:07.491 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2025-07-03 22:05:07.491 UTC client backend[15728] pg_regress/insert STATEMENT: insert into brtrigpartcon values (1, 'hi there'); 2025-07-03 22:05:07.496 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-07-03 22:05:07.496 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (2, hi there). 2025-07-03 22:05:07.496 UTC client backend[15728] pg_regress/insert STATEMENT: insert into brtrigpartcon1 values (1, 'hi there'); 2025-07-03 22:05:07.505 UTC client backend[15728] pg_regress/insert ERROR: new row for relation "brtrigpartcon1" violates partition constraint 2025-07-03 22:05:07.505 UTC client backend[15728] pg_regress/insert DETAIL: Failing row contains (a, b) = (2, hi there). 2025-07-03 22:05:07.505 UTC client backend[15728] pg_regress/insert STATEMENT: with result as (insert into brtrigpartcon values (1, 'hi there') returning 1) insert into inserttest3 (f3) select * from result; 2025-07-03 22:05:08.021 UTC client backend[15728] pg_regress/insert LOG: disconnection: session time: 0:00:02.286 user=postgres database=regression host=[local] 2025-07-03 22:05:08.226 UTC not initialized[15940] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.235 UTC not initialized[15944] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.235 UTC client backend[15940] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.235 UTC client backend[15940] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_function_c 2025-07-03 22:05:08.237 UTC client backend[15944] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.237 UTC client backend[15944] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_schema 2025-07-03 22:05:08.238 UTC client backend[15940] pg_regress/create_function_c LOG: connection ready: setup total=27.642 ms, fork=13.890 ms, authentication=0.553 ms 2025-07-03 22:05:08.240 UTC client backend[15944] pg_regress/create_schema LOG: connection ready: setup total=16.754 ms, fork=11.314 ms, authentication=0.441 ms 2025-07-03 22:05:08.240 UTC not initialized[15943] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.241 UTC client backend[15943] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.241 UTC not initialized[15942] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.241 UTC client backend[15943] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_misc 2025-07-03 22:05:08.243 UTC client backend[15942] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.243 UTC client backend[15942] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_procedure 2025-07-03 22:05:08.243 UTC not initialized[15945] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.245 UTC client backend[15945] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.245 UTC client backend[15945] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_operator 2025-07-03 22:05:08.246 UTC client backend[15942] pg_regress/create_procedure LOG: connection ready: setup total=25.476 ms, fork=20.619 ms, authentication=0.414 ms 2025-07-03 22:05:08.247 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.247 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE SEQUENCE schema_not_existing.seq; 2025-07-03 22:05:08.248 UTC client backend[15945] pg_regress/create_operator LOG: connection ready: setup total=21.409 ms, fork=12.720 ms, authentication=0.432 ms 2025-07-03 22:05:08.248 UTC not initialized[15946] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.249 UTC client backend[15943] pg_regress/create_misc LOG: connection ready: setup total=27.680 ms, fork=13.217 ms, authentication=0.389 ms 2025-07-03 22:05:08.250 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.250 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE TABLE schema_not_existing.tab (id int); 2025-07-03 22:05:08.252 UTC client backend[15946] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.252 UTC client backend[15946] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_type 2025-07-03 22:05:08.253 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.253 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-07-03 22:05:08.253 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.253 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE INDEX ON schema_not_existing.tab (id); 2025-07-03 22:05:08.254 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.254 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION regress_create_schema_role CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab EXECUTE FUNCTION schema_trig.no_func(); 2025-07-03 22:05:08.255 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.255 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.256 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2025-07-03 22:05:08.257 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role) 2025-07-03 22:05:08.257 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA AUTHORIZATION CURRENT_ROLE CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab EXECUTE FUNCTION schema_trig.no_func(); 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist at character 6 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure HINT: No procedure matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL nonexistent(); 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure ERROR: random() is not a procedure at character 6 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-07-03 22:05:08.258 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL random(); 2025-07-03 22:05:08.258 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-07-03 22:05:08.258 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE SEQUENCE schema_not_existing.seq; 2025-07-03 22:05:08.258 UTC client backend[15940] pg_regress/create_function_c ERROR: could not access file "nosuchfile": No such file or directory 2025-07-03 22:05:08.258 UTC client backend[15940] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C AS 'nosuchfile'; 2025-07-03 22:05:08.259 UTC client backend[15940] pg_regress/create_function_c ERROR: could not find function "nosuchsymbol" in file "/tmp/cirrus-ci-build/src/test/regress/regress.so" 2025-07-03 22:05:08.259 UTC client backend[15940] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C AS '/tmp/cirrus-ci-build/src/test/regress/regress.so', 'nosuchsymbol'; 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE TABLE schema_not_existing.tab (id int); 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE VIEW schema_not_existing.view AS SELECT 1; 2025-07-03 22:05:08.261 UTC client backend[15940] pg_regress/create_function_c ERROR: there is no built-in function named "nosuch" 2025-07-03 22:05:08.261 UTC client backend[15940] pg_regress/create_function_c STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE internal AS 'nosuch'; 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-07-03 22:05:08.261 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE INDEX ON schema_not_existing.tab (id); 2025-07-03 22:05:08.262 UTC client backend[15944] pg_regress/create_schema ERROR: CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1) 2025-07-03 22:05:08.262 UTC client backend[15944] pg_regress/create_schema STATEMENT: CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE CREATE TRIGGER schema_trig BEFORE INSERT ON schema_not_existing.tab EXECUTE FUNCTION schema_trig.no_func(); 2025-07-03 22:05:08.265 UTC client backend[15940] pg_regress/create_function_c LOG: disconnection: session time: 0:00:00.040 user=postgres database=regression host=[local] 2025-07-03 22:05:08.266 UTC not initialized[15947] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:08.268 UTC client backend[15946] pg_regress/create_type LOG: connection ready: setup total=33.915 ms, fork=12.589 ms, authentication=0.420 ms 2025-07-03 22:05:08.274 UTC client backend[15945] pg_regress/create_operator ERROR: operator right argument type must be specified 2025-07-03 22:05:08.274 UTC client backend[15945] pg_regress/create_operator DETAIL: Postfix operators are not supported. 2025-07-03 22:05:08.274 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #%# ( leftarg = int8, -- fail, postfix is no longer supported procedure = factorial ); 2025-07-03 22:05:08.275 UTC client backend[15947] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:08.275 UTC client backend[15947] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_table 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (NONE, int4) IS 'bad prefix'; 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator ERROR: postfix operators are not supported 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, NONE) IS 'bad postfix'; 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2025-07-03 22:05:08.275 UTC client backend[15945] pg_regress/create_operator STATEMENT: COMMENT ON OPERATOR ###### (int4, int8) IS 'bad infix'; 2025-07-03 22:05:08.276 UTC client backend[15945] pg_regress/create_operator ERROR: operator does not exist: ###### integer 2025-07-03 22:05:08.276 UTC client backend[15945] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (NONE, int4); 2025-07-03 22:05:08.278 UTC client backend[15947] pg_regress/create_table LOG: connection ready: setup total=28.690 ms, fork=12.754 ms, authentication=7.954 ms 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator ERROR: postfix operators are not supported 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, NONE); 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator ERROR: operator does not exist: integer ###### bigint 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator STATEMENT: DROP OPERATOR ###### (int4, int8); 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator ERROR: syntax error at or near "=>" at character 17 2025-07-03 22:05:08.278 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR => ( rightarg = int8, procedure = factorial ); 2025-07-03 22:05:08.279 UTC client backend[15945] pg_regress/create_operator ERROR: syntax error at or near ";" at character 14 2025-07-03 22:05:08.279 UTC client backend[15945] pg_regress/create_operator STATEMENT: SELECT 10 !=-; 2025-07-03 22:05:08.288 UTC client backend[15947] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2025-07-03 22:05:08.288 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE unknowntab ( u unknown -- fail ); 2025-07-03 22:05:08.290 UTC client backend[15947] pg_regress/create_table ERROR: column "u" has pseudo-type unknown 2025-07-03 22:05:08.290 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TYPE unknown_comptype AS ( u unknown -- fail ); 2025-07-03 22:05:08.291 UTC client backend[15945] pg_regress/create_operator ERROR: permission denied for schema schema_op1 2025-07-03 22:05:08.291 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR schema_op1.#*# ( rightarg = int8, procedure = factorial ); 2025-07-03 22:05:08.292 UTC client backend[15947] pg_regress/create_table ERROR: unrecognized parameter "Fillfactor" 2025-07-03 22:05:08.292 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE tas_case WITH ("Fillfactor" = 10) AS SELECT 1 a; 2025-07-03 22:05:08.293 UTC client backend[15945] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2025-07-03 22:05:08.293 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = SETOF int8, procedure = factorial ); 2025-07-03 22:05:08.293 UTC client backend[15945] pg_regress/create_operator ERROR: SETOF type not allowed for operator argument 2025-07-03 22:05:08.293 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( rightarg = SETOF int8, procedure = factorial ); 2025-07-03 22:05:08.304 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "invalid_att" not recognized 2025-07-03 22:05:08.304 UTC client backend[15945] pg_regress/create_operator ERROR: operator argument types must be specified 2025-07-03 22:05:08.304 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( procedure = factorial ); 2025-07-03 22:05:08.305 UTC client backend[15945] pg_regress/create_operator ERROR: operator function must be specified 2025-07-03 22:05:08.305 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #@%# ( rightarg = int8 ); 2025-07-03 22:05:08.308 UTC client backend[15945] pg_regress/create_operator ERROR: permission denied for type type_op3 2025-07-03 22:05:08.308 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = type_op3, rightarg = int8, procedure = fn_op3 ); 2025-07-03 22:05:08.311 UTC client backend[15945] pg_regress/create_operator ERROR: permission denied for type type_op4 2025-07-03 22:05:08.311 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = type_op4, procedure = fn_op4 ); 2025-07-03 22:05:08.314 UTC client backend[15946] pg_regress/create_type ERROR: type "shell" already exists 2025-07-03 22:05:08.314 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TYPE shell; 2025-07-03 22:05:08.317 UTC client backend[15946] pg_regress/create_type ERROR: type "shell" does not exist 2025-07-03 22:05:08.317 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP TYPE shell; 2025-07-03 22:05:08.322 UTC client backend[15945] pg_regress/create_operator ERROR: permission denied for function fn_op5 2025-07-03 22:05:08.322 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op5 ); 2025-07-03 22:05:08.330 UTC client backend[15945] pg_regress/create_operator ERROR: permission denied for type type_op6 2025-07-03 22:05:08.330 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR #*# ( leftarg = int8, rightarg = int8, procedure = fn_op6 ); 2025-07-03 22:05:08.331 UTC client backend[15945] pg_regress/create_operator ERROR: operator cannot be its own negator 2025-07-03 22:05:08.331 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = === ); 2025-07-03 22:05:08.334 UTC client backend[15945] pg_regress/create_operator ERROR: operator cannot be its own negator 2025-07-03 22:05:08.334 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR ===!!! ( leftarg = integer, rightarg = integer, procedure = int4ne, negator = ===!!! ); 2025-07-03 22:05:08.335 UTC client backend[15945] pg_regress/create_operator ERROR: commutator operator = is already the commutator of operator = 2025-07-03 22:05:08.335 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, commutator = = ); 2025-07-03 22:05:08.335 UTC client backend[15945] pg_regress/create_operator ERROR: negator operator <> is already the negator of operator = 2025-07-03 22:05:08.335 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( leftarg = integer, rightarg = integer, procedure = int4eq, negator = <> ); 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Leftarg" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Rightarg" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Procedure" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Commutator" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Negator" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Restrict" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Join" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Hashes" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator WARNING: operator attribute "Merges" not recognized 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator ERROR: operator function must be specified 2025-07-03 22:05:08.338 UTC client backend[15945] pg_regress/create_operator STATEMENT: CREATE OPERATOR === ( "Leftarg" = box, "Rightarg" = box, "Procedure" = area_equal_function, "Commutator" = ===, "Negator" = !==, "Restrict" = area_restriction_function, "Join" = area_join_function, "Hashes", "Merges" ); 2025-07-03 22:05:08.341 UTC client backend[15945] pg_regress/create_operator LOG: disconnection: session time: 0:00:00.102 user=postgres database=regression host=[local] 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Internallength" not recognized at character 27 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Input" not recognized at character 50 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Output" not recognized at character 71 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Alignment" not recognized at character 94 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Default" not recognized at character 115 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type WARNING: type attribute "Passedbyvalue" not recognized at character 132 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type ERROR: type input function must be specified 2025-07-03 22:05:08.363 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type ( "Internallength" = 4, "Input" = int42_in, "Output" = int42_out, "Alignment" = int4, "Default" = 42, "Passedbyvalue" ); 2025-07-03 22:05:08.364 UTC client backend[15946] pg_regress/create_type ERROR: type input function array_in must return type bogus_type 2025-07-03 22:05:08.364 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2025-07-03 22:05:08.367 UTC client backend[15946] pg_regress/create_type ERROR: type "bogus_type" does not exist 2025-07-03 22:05:08.367 UTC client backend[15946] pg_regress/create_type HINT: Create the type as a shell type, then create its I/O functions, then do a full CREATE TYPE. 2025-07-03 22:05:08.367 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TYPE bogus_type (INPUT = array_in, OUTPUT = array_out, ELEMENT = int, INTERNALLENGTH = 32); 2025-07-03 22:05:08.373 UTC client backend[15946] pg_regress/create_type ERROR: type "bad" does not exist 2025-07-03 22:05:08.373 UTC client backend[15946] pg_regress/create_type STATEMENT: COMMENT ON TYPE bad IS 'bad comment'; 2025-07-03 22:05:08.375 UTC client backend[15947] pg_regress/create_table ERROR: only temporary relations may be created in temporary schemas at character 23 2025-07-03 22:05:08.375 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE UNLOGGED TABLE pg_temp.unlogged3 (a int primary key); 2025-07-03 22:05:08.375 UTC client backend[15942] pg_regress/create_procedure ERROR: ptest1(unknown) is a procedure at character 8 2025-07-03 22:05:08.375 UTC client backend[15942] pg_regress/create_procedure HINT: To call a procedure, use CALL. 2025-07-03 22:05:08.375 UTC client backend[15942] pg_regress/create_procedure STATEMENT: SELECT ptest1('x'); 2025-07-03 22:05:08.378 UTC client backend[15946] pg_regress/create_type ERROR: column "nope" of relation "default_test_row" does not exist 2025-07-03 22:05:08.378 UTC client backend[15946] pg_regress/create_type STATEMENT: COMMENT ON COLUMN default_test_row.nope IS 'bad comment'; 2025-07-03 22:05:08.378 UTC client backend[15946] pg_regress/create_type ERROR: type "text_w_default" already exists 2025-07-03 22:05:08.378 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TYPE text_w_default; 2025-07-03 22:05:08.397 UTC client backend[15946] pg_regress/create_type ERROR: cannot drop function base_fn_in(cstring) because other objects depend on it 2025-07-03 22:05:08.397 UTC client backend[15946] pg_regress/create_type DETAIL: type base_type depends on function base_fn_in(cstring) function base_fn_out(base_type) depends on type base_type 2025-07-03 22:05:08.397 UTC client backend[15946] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.397 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_in(cstring); 2025-07-03 22:05:08.399 UTC client backend[15946] pg_regress/create_type ERROR: cannot drop function base_fn_out(base_type) because other objects depend on it 2025-07-03 22:05:08.399 UTC client backend[15946] pg_regress/create_type DETAIL: type base_type depends on function base_fn_out(base_type) function base_fn_in(cstring) depends on type base_type 2025-07-03 22:05:08.399 UTC client backend[15946] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.399 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP FUNCTION base_fn_out(base_type); 2025-07-03 22:05:08.401 UTC client backend[15946] pg_regress/create_type ERROR: cannot drop type base_type because other objects depend on it 2025-07-03 22:05:08.401 UTC client backend[15946] pg_regress/create_type DETAIL: function base_fn_in(cstring) depends on type base_type function base_fn_out(base_type) depends on type base_type 2025-07-03 22:05:08.401 UTC client backend[15946] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.401 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP TYPE base_type; 2025-07-03 22:05:08.404 UTC client backend[15947] pg_regress/create_table ERROR: cannot create temporary relation in non-temporary schema at character 19 2025-07-03 22:05:08.404 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TEMP TABLE public.temp_to_perm (a int primary key); 2025-07-03 22:05:08.405 UTC client backend[15942] pg_regress/create_procedure ERROR: CREATE TABLE is not yet supported in unquoted SQL function body 2025-07-03 22:05:08.405 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL BEGIN ATOMIC CREATE TABLE x (a int); END; 2025-07-03 22:05:08.408 UTC client backend[15946] pg_regress/create_type ERROR: invalid NUMERIC type modifier at character 30 2025-07-03 22:05:08.408 UTC client backend[15946] pg_regress/create_type STATEMENT: CREATE TEMP TABLE mytab (foo widget(42,13,7)); 2025-07-03 22:05:08.423 UTC client backend[15947] pg_regress/create_table ERROR: partitioned tables cannot be unlogged 2025-07-03 22:05:08.423 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE UNLOGGED TABLE unlogged1 (a int) PARTITION BY RANGE (a); 2025-07-03 22:05:08.424 UTC client backend[15942] pg_regress/create_procedure ERROR: calling procedures with output arguments is not supported in SQL functions 2025-07-03 22:05:08.424 UTC client backend[15942] pg_regress/create_procedure CONTEXT: SQL function "ptest4b" 2025-07-03 22:05:08.424 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptest4b(INOUT b int, INOUT a int) LANGUAGE SQL AS $$ CALL ptest4a(a, b); -- error, not supported $$; 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table ERROR: ALTER action SET LOGGED cannot be performed on relation "unlogged1" 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table DETAIL: This operation is not supported for partitioned tables. 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table STATEMENT: ALTER TABLE unlogged1 SET LOGGED; 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table ERROR: ALTER action SET UNLOGGED cannot be performed on relation "unlogged1" 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table DETAIL: This operation is not supported for partitioned tables. 2025-07-03 22:05:08.425 UTC client backend[15947] pg_regress/create_table STATEMENT: ALTER TABLE unlogged1 SET UNLOGGED; 2025-07-03 22:05:08.444 UTC client backend[15946] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-07-03 22:05:08.444 UTC client backend[15946] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('(1,2)', 'widget'); 2025-07-03 22:05:08.447 UTC client backend[15946] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-07-03 22:05:08.447 UTC client backend[15946] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('{"(1,2)"}', 'widget[]'); 2025-07-03 22:05:08.447 UTC client backend[15946] pg_regress/create_type ERROR: invalid input syntax for type widget: "(1,2)" 2025-07-03 22:05:08.447 UTC client backend[15946] pg_regress/create_type STATEMENT: SELECT pg_input_is_valid('("(1,2)")', 'mytab'); 2025-07-03 22:05:08.454 UTC client backend[15947] pg_regress/create_table ERROR: relation "as_select1" already exists 2025-07-03 22:05:08.454 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relkind = 'r'; 2025-07-03 22:05:08.467 UTC client backend[15947] pg_regress/create_table ERROR: relation "as_select1" already exists 2025-07-03 22:05:08.467 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE as_select1 AS EXECUTE select1; 2025-07-03 22:05:08.474 UTC client backend[15946] pg_regress/create_type ERROR: type "myvarchar" is only a shell 2025-07-03 22:05:08.474 UTC client backend[15946] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = extended); 2025-07-03 22:05:08.478 UTC client backend[15946] pg_regress/create_type ERROR: cannot change type's storage to PLAIN 2025-07-03 22:05:08.478 UTC client backend[15946] pg_regress/create_type STATEMENT: ALTER TYPE myvarchar SET (storage = plain); 2025-07-03 22:05:08.493 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure ptest9(numeric) does not exist at character 6 2025-07-03 22:05:08.493 UTC client backend[15942] pg_regress/create_procedure HINT: No procedure matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:08.493 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL ptest9(1./0.); 2025-07-03 22:05:08.498 UTC client backend[15946] pg_regress/create_type ERROR: cannot drop function myvarcharsend(myvarchar) because other objects depend on it 2025-07-03 22:05:08.498 UTC client backend[15946] pg_regress/create_type DETAIL: type myvarchar depends on function myvarcharsend(myvarchar) function myvarcharin(cstring,oid,integer) depends on type myvarchar function myvarcharout(myvarchar) depends on type myvarchar function myvarcharrecv(internal,oid,integer) depends on type myvarchar type myvarchardom depends on function myvarcharsend(myvarchar) 2025-07-03 22:05:08.498 UTC client backend[15946] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.498 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP FUNCTION myvarcharsend(myvarchar); 2025-07-03 22:05:08.499 UTC client backend[15946] pg_regress/create_type ERROR: cannot drop type myvarchar because other objects depend on it 2025-07-03 22:05:08.499 UTC client backend[15946] pg_regress/create_type DETAIL: function myvarcharin(cstring,oid,integer) depends on type myvarchar function myvarcharout(myvarchar) depends on type myvarchar function myvarcharsend(myvarchar) depends on type myvarchar function myvarcharrecv(internal,oid,integer) depends on type myvarchar type myvarchardom depends on type myvarchar 2025-07-03 22:05:08.499 UTC client backend[15946] pg_regress/create_type HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.499 UTC client backend[15946] pg_regress/create_type STATEMENT: DROP TYPE myvarchar; 2025-07-03 22:05:08.505 UTC client backend[15944] pg_regress/create_schema LOG: disconnection: session time: 0:00:00.270 user=postgres database=regression host=[local] 2025-07-03 22:05:08.509 UTC client backend[15946] pg_regress/create_type LOG: disconnection: session time: 0:00:00.262 user=postgres database=regression host=[local] 2025-07-03 22:05:08.523 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2025-07-03 22:05:08.523 UTC client backend[15942] pg_regress/create_procedure HINT: Specify the argument list to select the procedure unambiguously. 2025-07-03 22:05:08.523 UTC client backend[15942] pg_regress/create_procedure STATEMENT: drop procedure ptest10; 2025-07-03 22:05:08.531 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure name "ptest10" is not unique 2025-07-03 22:05:08.531 UTC client backend[15942] pg_regress/create_procedure STATEMENT: drop procedure ptest10(int, int, int); 2025-07-03 22:05:08.545 UTC client backend[15943] pg_regress/create_misc LOG: disconnection: session time: 0:00:00.306 user=postgres database=regression host=[local] 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure ERROR: version() is not a procedure at character 6 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL version(); 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure ERROR: sum(integer) is not a procedure at character 6 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure HINT: To call a function, use SELECT. 2025-07-03 22:05:08.559 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL sum(1); 2025-07-03 22:05:08.560 UTC client backend[15942] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2025-07-03 22:05:08.560 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL WINDOW AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 40 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx() LANGUAGE SQL STRICT AS $$ INSERT INTO cp_test VALUES (1, 'a') $$; 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure ERROR: VARIADIC parameter must be the last parameter at character 43 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a VARIADIC int[], b OUT int) LANGUAGE SQL AS $$ SELECT a[1] $$; 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure OUT parameters cannot appear after one with a default value at character 43 2025-07-03 22:05:08.563 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CREATE PROCEDURE ptestx(a int DEFAULT 42, b OUT int) LANGUAGE SQL AS $$ SELECT a $$; 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: invalid attribute in procedure definition at character 30 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE ptest1(text) STRICT; 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: ALTER FUNCTION ptest1(text) VOLATILE; 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE cp_testfunc1(int) VOLATILE; 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: ALTER PROCEDURE nonexistent() VOLATILE; 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: ptest1(text) is not a function 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: DROP FUNCTION ptest1(text); 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure ERROR: cp_testfunc1(integer) is not a procedure 2025-07-03 22:05:08.564 UTC client backend[15942] pg_regress/create_procedure STATEMENT: DROP PROCEDURE cp_testfunc1(int); 2025-07-03 22:05:08.565 UTC client backend[15942] pg_regress/create_procedure ERROR: procedure nonexistent() does not exist 2025-07-03 22:05:08.565 UTC client backend[15942] pg_regress/create_procedure STATEMENT: DROP PROCEDURE nonexistent(); 2025-07-03 22:05:08.566 UTC client backend[15942] pg_regress/create_procedure ERROR: permission denied for procedure ptest1 2025-07-03 22:05:08.566 UTC client backend[15942] pg_regress/create_procedure STATEMENT: CALL ptest1('a'); 2025-07-03 22:05:08.600 UTC client backend[15942] pg_regress/create_procedure LOG: disconnection: session time: 0:00:00.359 user=postgres database=regression host=[local] 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table ERROR: syntax error at or near "OIDS" at character 29 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH OIDS; 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids); 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table ERROR: tables declared WITH OIDS are not supported 2025-07-03 22:05:08.740 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE withoid() WITH (oids = true); 2025-07-03 22:05:08.755 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2025-07-03 22:05:08.755 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (id)); 2025-07-03 22:05:08.756 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 51 2025-07-03 22:05:08.756 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_column (id int DEFAULT (bar.id)); 2025-07-03 22:05:08.757 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 59 2025-07-03 22:05:08.757 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg_column (id int DEFAULT (avg(id))); 2025-07-03 22:05:08.758 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in DEFAULT expression at character 58 2025-07-03 22:05:08.758 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_non_column (a int DEFAULT (avg(non_existent))); 2025-07-03 22:05:08.764 UTC client backend[15947] pg_regress/create_table ERROR: aggregate functions are not allowed in DEFAULT expressions at character 47 2025-07-03 22:05:08.764 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (avg(1))); 2025-07-03 22:05:08.765 UTC client backend[15947] pg_regress/create_table ERROR: cannot use subquery in DEFAULT expression at character 46 2025-07-03 22:05:08.765 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (select 1)); 2025-07-03 22:05:08.767 UTC client backend[15947] pg_regress/create_table ERROR: set-returning functions are not allowed in DEFAULT expressions at character 47 2025-07-03 22:05:08.767 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE default_expr_agg (a int DEFAULT (generate_series(1,3))); 2025-07-03 22:05:08.793 UTC client backend[15947] pg_regress/create_table ERROR: cannot create partitioned table as inheritance child 2025-07-03 22:05:08.793 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) INHERITS (some_table) PARTITION BY LIST (a); 2025-07-03 22:05:08.794 UTC client backend[15947] pg_regress/create_table ERROR: cannot use "list" partition strategy with more than one column 2025-07-03 22:05:08.794 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a1 int, a2 int ) PARTITION BY LIST (a1, a2); 2025-07-03 22:05:08.796 UTC client backend[15947] pg_regress/create_table ERROR: set-returning functions are not allowed in partition key expressions 2025-07-03 22:05:08.796 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (retset(a)); 2025-07-03 22:05:08.797 UTC client backend[15947] pg_regress/create_table ERROR: aggregate functions are not allowed in partition key expressions 2025-07-03 22:05:08.797 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((avg(a))); 2025-07-03 22:05:08.804 UTC client backend[15947] pg_regress/create_table ERROR: window functions are not allowed in partition key expressions 2025-07-03 22:05:08.804 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE ((avg(a) OVER (PARTITION BY b))); 2025-07-03 22:05:08.805 UTC client backend[15947] pg_regress/create_table ERROR: cannot use subquery in partition key expression 2025-07-03 22:05:08.805 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY LIST ((a LIKE (SELECT 1))); 2025-07-03 22:05:08.806 UTC client backend[15947] pg_regress/create_table ERROR: cannot use constant expression as partition key 2025-07-03 22:05:08.806 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE ((42)); 2025-07-03 22:05:08.808 UTC client backend[15947] pg_regress/create_table ERROR: cannot use constant expression as partition key 2025-07-03 22:05:08.808 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (const_func()); 2025-07-03 22:05:08.808 UTC client backend[15947] pg_regress/create_table ERROR: unrecognized partitioning strategy "magic" at character 53 2025-07-03 22:05:08.808 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY MAGIC (a); 2025-07-03 22:05:08.809 UTC client backend[15947] pg_regress/create_table ERROR: column "b" named in partition key does not exist at character 57 2025-07-03 22:05:08.809 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (b); 2025-07-03 22:05:08.810 UTC client backend[15947] pg_regress/create_table ERROR: cannot use system column "xmin" in partition key at character 57 2025-07-03 22:05:08.810 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (xmin); 2025-07-03 22:05:08.816 UTC client backend[15947] pg_regress/create_table ERROR: partition key column 1 has pseudo-type record 2025-07-03 22:05:08.816 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (((a, b))); 2025-07-03 22:05:08.818 UTC client backend[15947] pg_regress/create_table ERROR: partition key column 2 has pseudo-type unknown 2025-07-03 22:05:08.818 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, b int ) PARTITION BY RANGE (a, ('unknown')); 2025-07-03 22:05:08.825 UTC client backend[15947] pg_regress/create_table ERROR: functions in partition key expression must be marked IMMUTABLE 2025-07-03 22:05:08.825 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int ) PARTITION BY RANGE (immut_func(a)); 2025-07-03 22:05:08.830 UTC client backend[15947] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2025-07-03 22:05:08.830 UTC client backend[15947] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2025-07-03 22:05:08.830 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a); 2025-07-03 22:05:08.835 UTC client backend[15947] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2025-07-03 22:05:08.835 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY LIST (a point_ops); 2025-07-03 22:05:08.840 UTC client backend[15947] pg_regress/create_table ERROR: data type point has no default operator class for access method "btree" 2025-07-03 22:05:08.840 UTC client backend[15947] pg_regress/create_table HINT: You must specify a btree operator class or define a default btree operator class for the data type. 2025-07-03 22:05:08.840 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a); 2025-07-03 22:05:08.841 UTC client backend[15947] pg_regress/create_table ERROR: operator class "point_ops" does not exist for access method "btree" 2025-07-03 22:05:08.841 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a point ) PARTITION BY RANGE (a point_ops); 2025-07-03 22:05:08.842 UTC client backend[15947] pg_regress/create_table ERROR: cannot add NO INHERIT constraint to partitioned table "partitioned" 2025-07-03 22:05:08.842 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE partitioned ( a int, CONSTRAINT check_a CHECK (a > 0) NO INHERIT ) PARTITION BY RANGE (a); 2025-07-03 22:05:08.850 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop function plusone(integer) because other objects depend on it 2025-07-03 22:05:08.850 UTC client backend[15947] pg_regress/create_table DETAIL: table partitioned depends on function plusone(integer) 2025-07-03 22:05:08.850 UTC client backend[15947] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:08.850 UTC client backend[15947] pg_regress/create_table STATEMENT: DROP FUNCTION plusone(int); 2025-07-03 22:05:08.852 UTC client backend[15947] pg_regress/create_table ERROR: cannot inherit from partitioned table "partitioned2" 2025-07-03 22:05:08.852 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail () INHERITS (partitioned2); 2025-07-03 22:05:08.936 UTC client backend[15947] pg_regress/create_table ERROR: no partition of relation "partitioned2" found for row 2025-07-03 22:05:08.936 UTC client backend[15947] pg_regress/create_table DETAIL: Partition key of the failing row contains ((a + 1), substr(b, 1, 5)) = (2, hello). 2025-07-03 22:05:08.936 UTC client backend[15947] pg_regress/create_table STATEMENT: INSERT INTO partitioned2 VALUES (1, 'hello'); 2025-07-03 22:05:09.076 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2025-07-03 22:05:09.076 UTC client backend[15947] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2025-07-03 22:05:09.077 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2025-07-03 22:05:09.077 UTC client backend[15947] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2025-07-03 22:05:09.077 UTC client backend[15947] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:09.077 UTC client backend[15947] pg_regress/create_table STATEMENT: drop domain intdom1; 2025-07-03 22:05:09.079 UTC client backend[15947] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2025-07-03 22:05:09.079 UTC client backend[15947] pg_regress/create_table STATEMENT: table partitioned; 2025-07-03 22:05:09.084 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop column "a" because it is part of the partition key of relation "partitioned" 2025-07-03 22:05:09.084 UTC client backend[15947] pg_regress/create_table STATEMENT: alter table partitioned drop column a; 2025-07-03 22:05:09.085 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop type intdom1 because other objects depend on it 2025-07-03 22:05:09.085 UTC client backend[15947] pg_regress/create_table DETAIL: table partitioned depends on type intdom1 2025-07-03 22:05:09.085 UTC client backend[15947] pg_regress/create_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:09.085 UTC client backend[15947] pg_regress/create_table STATEMENT: drop domain intdom1; 2025-07-03 22:05:09.094 UTC client backend[15947] pg_regress/create_table ERROR: relation "partitioned" does not exist at character 7 2025-07-03 22:05:09.094 UTC client backend[15947] pg_regress/create_table STATEMENT: table partitioned; 2025-07-03 22:05:09.147 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-07-03 22:05:09.147 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename); 2025-07-03 22:05:09.149 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-07-03 22:05:09.149 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename.somename); 2025-07-03 22:05:09.155 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 75 2025-07-03 22:05:09.155 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (a); 2025-07-03 22:05:09.156 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2025-07-03 22:05:09.156 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(a)); 2025-07-03 22:05:09.157 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 79 2025-07-03 22:05:09.157 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(somename)); 2025-07-03 22:05:09.158 UTC client backend[15947] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 75 2025-07-03 22:05:09.158 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(1)); 2025-07-03 22:05:09.165 UTC client backend[15947] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 75 2025-07-03 22:05:09.165 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((select 1)); 2025-07-03 22:05:09.166 UTC client backend[15947] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 75 2025-07-03 22:05:09.166 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (generate_series(4, 6)); 2025-07-03 22:05:09.167 UTC client backend[15947] pg_regress/create_table ERROR: collations are not supported by type integer at character 81 2025-07-03 22:05:09.167 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((1+1) collate "POSIX"); 2025-07-03 22:05:09.168 UTC client backend[15947] pg_regress/create_table ERROR: syntax error at or near ")" at character 64 2025-07-03 22:05:09.168 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES IN (); 2025-07-03 22:05:09.169 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2025-07-03 22:05:09.169 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES FROM (1) TO (2); 2025-07-03 22:05:09.170 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a list partition at character 60 2025-07-03 22:05:09.170 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-07-03 22:05:09.178 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "part_default" at character 57 2025-07-03 22:05:09.178 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF list_parted DEFAULT; 2025-07-03 22:05:09.185 UTC client backend[15947] pg_regress/create_table ERROR: specified value cannot be cast to type boolean for column "a" at character 59 2025-07-03 22:05:09.185 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE bools_true PARTITION OF bools FOR VALUES IN (1); 2025-07-03 22:05:09.218 UTC client backend[15947] pg_regress/create_table ERROR: partition "bigintp_10_2" would overlap partition "bigintp_10" at character 63 2025-07-03 22:05:09.218 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE bigintp_10_2 PARTITION OF bigintp FOR VALUES IN ('10'); 2025-07-03 22:05:09.232 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-07-03 22:05:09.232 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (somename) TO ('2019-01-01'); 2025-07-03 22:05:09.234 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-07-03 22:05:09.234 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (somename.somename) TO ('2019-01-01'); 2025-07-03 22:05:09.235 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 80 2025-07-03 22:05:09.235 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (a) TO ('2019-01-01'); 2025-07-03 22:05:09.236 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2025-07-03 22:05:09.236 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (max(a)) TO ('2019-01-01'); 2025-07-03 22:05:09.245 UTC client backend[15947] pg_regress/create_table ERROR: cannot use column reference in partition bound expression at character 84 2025-07-03 22:05:09.245 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (max(somename)) TO ('2019-01-01'); 2025-07-03 22:05:09.247 UTC client backend[15947] pg_regress/create_table ERROR: aggregate functions are not allowed in partition bound at character 80 2025-07-03 22:05:09.247 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (max('2019-02-01'::date)) TO ('2019-01-01'); 2025-07-03 22:05:09.248 UTC client backend[15947] pg_regress/create_table ERROR: cannot use subquery in partition bound at character 80 2025-07-03 22:05:09.248 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM ((select 1)) TO ('2019-01-01'); 2025-07-03 22:05:09.249 UTC client backend[15947] pg_regress/create_table ERROR: set-returning functions are not allowed in partition bound at character 80 2025-07-03 22:05:09.249 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted FOR VALUES FROM (generate_series(1, 3)) TO ('2019-01-01'); 2025-07-03 22:05:09.250 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-07-03 22:05:09.250 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES IN ('a'); 2025-07-03 22:05:09.251 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-07-03 22:05:09.251 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-07-03 22:05:09.252 UTC client backend[15947] pg_regress/create_table ERROR: FROM must specify exactly one value per partitioning column 2025-07-03 22:05:09.252 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a', 1) TO ('z'); 2025-07-03 22:05:09.254 UTC client backend[15947] pg_regress/create_table ERROR: TO must specify exactly one value per partitioning column 2025-07-03 22:05:09.254 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a') TO ('z', 1); 2025-07-03 22:05:09.258 UTC client backend[15947] pg_regress/create_table ERROR: cannot specify NULL in range bound 2025-07-03 22:05:09.258 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM (null) TO (maxvalue); 2025-07-03 22:05:09.259 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a range partition at character 61 2025-07-03 22:05:09.259 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1); 2025-07-03 22:05:09.278 UTC client backend[15947] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2025-07-03 22:05:09.278 UTC client backend[15947] pg_regress/create_table DETAIL: The new modulus 25 is not divisible by 10, the modulus of existing partition "hpart_4". 2025-07-03 22:05:09.278 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 25, REMAINDER 3); 2025-07-03 22:05:09.280 UTC client backend[15947] pg_regress/create_table ERROR: every hash partition modulus must be a factor of the next larger modulus 2025-07-03 22:05:09.280 UTC client backend[15947] pg_regress/create_table DETAIL: The new modulus 150 is not a factor of 200, the modulus of existing partition "hpart_3". 2025-07-03 22:05:09.280 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 150, REMAINDER 3); 2025-07-03 22:05:09.285 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "hpart_4" at character 60 2025-07-03 22:05:09.285 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 100, REMAINDER 3); 2025-07-03 22:05:09.286 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2025-07-03 22:05:09.286 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES FROM ('a', 1) TO ('z'); 2025-07-03 22:05:09.287 UTC client backend[15947] pg_regress/create_table ERROR: invalid bound specification for a hash partition at character 60 2025-07-03 22:05:09.287 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES IN (1000); 2025-07-03 22:05:09.289 UTC client backend[15947] pg_regress/create_table ERROR: a hash-partitioned table may not have a default partition 2025-07-03 22:05:09.289 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF hash_parted DEFAULT; 2025-07-03 22:05:09.296 UTC client backend[15947] pg_regress/create_table ERROR: "unparted" is not partitioned 2025-07-03 22:05:09.296 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES IN ('a'); 2025-07-03 22:05:09.298 UTC client backend[15947] pg_regress/create_table ERROR: "unparted" is not partitioned 2025-07-03 22:05:09.298 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF unparted FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2025-07-03 22:05:09.306 UTC client backend[15947] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-07-03 22:05:09.306 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF temp_parted FOR VALUES IN ('a'); 2025-07-03 22:05:09.332 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_null_z" at character 65 2025-07-03 22:05:09.332 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN (null); 2025-07-03 22:05:09.339 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part_ab" at character 65 2025-07-03 22:05:09.339 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('b', 'c'); 2025-07-03 22:05:09.341 UTC client backend[15947] pg_regress/create_table ERROR: updated partition constraint for default partition "list_parted2_def" would be violated by some row 2025-07-03 22:05:09.341 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('W', 'X', 'Y'); 2025-07-03 22:05:09.345 UTC client backend[15947] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2025-07-03 22:05:09.345 UTC client backend[15947] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (0). 2025-07-03 22:05:09.345 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (0); 2025-07-03 22:05:09.346 UTC client backend[15947] pg_regress/create_table ERROR: empty range bound specified for partition "fail_part" at character 68 2025-07-03 22:05:09.346 UTC client backend[15947] pg_regress/create_table DETAIL: Specified lower bound (1) is greater than or equal to upper bound (1). 2025-07-03 22:05:09.346 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (1); 2025-07-03 22:05:09.354 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2025-07-03 22:05:09.354 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (minvalue) TO (2); 2025-07-03 22:05:09.357 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part0" at character 68 2025-07-03 22:05:09.357 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (-1) TO (1); 2025-07-03 22:05:09.360 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part1" at character 68 2025-07-03 22:05:09.360 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (9) TO (maxvalue); 2025-07-03 22:05:09.377 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2025-07-03 22:05:09.377 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (30); 2025-07-03 22:05:09.384 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part2" at character 76 2025-07-03 22:05:09.384 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (50); 2025-07-03 22:05:09.387 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_default_part" conflicts with existing default partition "range2_default" at character 59 2025-07-03 22:05:09.387 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_default_part PARTITION OF range_parted2 DEFAULT; 2025-07-03 22:05:09.403 UTC client backend[15947] pg_regress/create_table ERROR: updated partition constraint for default partition "range2_default" would be violated by some row 2025-07-03 22:05:09.403 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (80) TO (90); 2025-07-03 22:05:09.415 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part00" at character 68 2025-07-03 22:05:09.415 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (0, minvalue) TO (0, 1); 2025-07-03 22:05:09.436 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part12" at character 71 2025-07-03 22:05:09.436 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, 10) TO (1, 20); 2025-07-03 22:05:09.441 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "part10" at character 68 2025-07-03 22:05:09.441 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, minvalue) TO (1, maxvalue); 2025-07-03 22:05:09.487 UTC client backend[15947] pg_regress/create_table ERROR: partition "fail_part" would overlap partition "h2part_4" at character 61 2025-07-03 22:05:09.487 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 2, REMAINDER 1); 2025-07-03 22:05:09.491 UTC client backend[15947] pg_regress/create_table ERROR: modulus for hash partition must be an integer value greater than zero 2025-07-03 22:05:09.491 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 0, REMAINDER 1); 2025-07-03 22:05:09.492 UTC client backend[15947] pg_regress/create_table ERROR: remainder for hash partition must be less than modulus 2025-07-03 22:05:09.492 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 8, REMAINDER 8); 2025-07-03 22:05:09.513 UTC client backend[15947] pg_regress/create_table ERROR: column "b" specified more than once 2025-07-03 22:05:09.513 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE part_b PARTITION OF parted ( b NOT NULL, b DEFAULT 1, b CHECK (b >= 0), CONSTRAINT check_a CHECK (length(a) > 0) ) FOR VALUES IN ('b'); 2025-07-03 22:05:09.535 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop inherited constraint "check_a" of relation "part_b" 2025-07-03 22:05:09.535 UTC client backend[15947] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_a; 2025-07-03 22:05:09.535 UTC client backend[15947] pg_regress/create_table ERROR: cannot drop inherited constraint "check_b" of relation "part_b" 2025-07-03 22:05:09.535 UTC client backend[15947] pg_regress/create_table STATEMENT: ALTER TABLE part_b DROP CONSTRAINT check_b; 2025-07-03 22:05:09.541 UTC client backend[15947] pg_regress/create_table ERROR: column "c" named in partition key does not exist at character 98 2025-07-03 22:05:09.541 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE fail_part_col_not_found PARTITION OF parted FOR VALUES IN ('c') PARTITION BY RANGE (c); 2025-07-03 22:05:09.568 UTC client backend[15947] pg_regress/create_table ERROR: null value in column "b" of relation "parted_notnull_inh_test1" violates not-null constraint 2025-07-03 22:05:09.568 UTC client backend[15947] pg_regress/create_table DETAIL: Failing row contains (1, null). 2025-07-03 22:05:09.568 UTC client backend[15947] pg_regress/create_table STATEMENT: insert into parted_notnull_inh_test (b) values (null); 2025-07-03 22:05:10.136 UTC client backend[15947] pg_regress/create_table ERROR: cannot specify storage parameters for a partitioned table 2025-07-03 22:05:10.136 UTC client backend[15947] pg_regress/create_table HINT: Specify storage parameters for its leaf partitions instead. 2025-07-03 22:05:10.136 UTC client backend[15947] pg_regress/create_table STATEMENT: CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a) WITH (fillfactor=100); 2025-07-03 22:05:10.243 UTC client backend[15947] pg_regress/create_table ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-07-03 22:05:10.243 UTC client backend[15947] pg_regress/create_table STATEMENT: create table perm_part partition of temp_parted default; 2025-07-03 22:05:10.244 UTC client backend[15947] pg_regress/create_table ERROR: cannot create a temporary relation as partition of permanent relation "perm_parted" 2025-07-03 22:05:10.244 UTC client backend[15947] pg_regress/create_table STATEMENT: create temp table temp_part partition of perm_parted default; 2025-07-03 22:05:10.252 UTC client backend[15947] pg_regress/create_table ERROR: cannot CREATE TABLE .. PARTITION OF "tab_part_create" because it is being used by active queries in this session 2025-07-03 22:05:10.252 UTC client backend[15947] pg_regress/create_table CONTEXT: SQL statement "create table tab_part_create_1 partition of tab_part_create for values in (1)" PL/pgSQL function func_part_create() line 3 at EXECUTE 2025-07-03 22:05:10.252 UTC client backend[15947] pg_regress/create_table STATEMENT: insert into tab_part_create values (1); 2025-07-03 22:05:10.292 UTC client backend[15947] pg_regress/create_table ERROR: updated partition constraint for default partition "defcheck_def" would be violated by some row 2025-07-03 22:05:10.292 UTC client backend[15947] pg_regress/create_table STATEMENT: create table defcheck_0 partition of defcheck for values in (0); 2025-07-03 22:05:10.472 UTC client backend[15947] pg_regress/create_table LOG: disconnection: session time: 0:00:02.209 user=postgres database=regression host=[local] 2025-07-03 22:05:10.670 UTC not initialized[16150] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:10.676 UTC client backend[16150] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:10.676 UTC client backend[16150] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/index_including 2025-07-03 22:05:10.684 UTC not initialized[16153] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:10.685 UTC client backend[16150] pg_regress/index_including LOG: connection ready: setup total=26.623 ms, fork=8.624 ms, authentication=0.401 ms 2025-07-03 22:05:10.689 UTC not initialized[16154] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:10.691 UTC client backend[16153] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:10.691 UTC client backend[16153] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_index_spgist 2025-07-03 22:05:10.691 UTC client backend[16154] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:10.691 UTC client backend[16154] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_view 2025-07-03 22:05:10.692 UTC not initialized[16157] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:10.693 UTC client backend[16157] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:10.693 UTC client backend[16157] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_index 2025-07-03 22:05:10.695 UTC not initialized[16155] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:10.697 UTC client backend[16155] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:10.697 UTC client backend[16155] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/index_including_gist 2025-07-03 22:05:10.701 UTC client backend[16153] pg_regress/create_index_spgist LOG: connection ready: setup total=30.917 ms, fork=8.908 ms, authentication=0.471 ms 2025-07-03 22:05:10.701 UTC client backend[16157] pg_regress/create_index LOG: connection ready: setup total=13.379 ms, fork=3.392 ms, authentication=0.414 ms 2025-07-03 22:05:10.707 UTC client backend[16155] pg_regress/index_including_gist LOG: connection ready: setup total=25.221 ms, fork=12.081 ms, authentication=0.401 ms 2025-07-03 22:05:10.711 UTC client backend[16154] pg_regress/create_view LOG: connection ready: setup total=33.254 ms, fork=10.710 ms, authentication=0.519 ms 2025-07-03 22:05:10.712 UTC client backend[16157] pg_regress/create_index ERROR: syntax error at or near "ON" at character 28 2025-07-03 22:05:10.712 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops); 2025-07-03 22:05:10.851 UTC client backend[16154] pg_regress/create_view ERROR: relation "noview" does not exist 2025-07-03 22:05:10.851 UTC client backend[16154] pg_regress/create_view STATEMENT: COMMENT ON VIEW noview IS 'no view'; 2025-07-03 22:05:10.860 UTC client backend[16150] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_idx_unique" 2025-07-03 22:05:10.860 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-07-03 22:05:10.860 UTC client backend[16150] pg_regress/index_including STATEMENT: CREATE UNIQUE INDEX tbl_include_unique2_idx_unique ON tbl_include_unique2 using btree (c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:10.865 UTC client backend[16150] pg_regress/index_including ERROR: could not create unique index "tbl_include_unique2_c1_c2_c3_c4_key" 2025-07-03 22:05:10.865 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-07-03 22:05:10.865 UTC client backend[16150] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_unique2 add UNIQUE (c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:10.872 UTC client backend[16154] pg_regress/create_view ERROR: cannot drop constraint view_base_table_pkey on table view_base_table because other objects depend on it 2025-07-03 22:05:10.872 UTC client backend[16154] pg_regress/create_view DETAIL: view key_dependent_view depends on constraint view_base_table_pkey on table view_base_table 2025-07-03 22:05:10.872 UTC client backend[16154] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:10.872 UTC client backend[16154] pg_regress/create_view STATEMENT: ALTER TABLE view_base_table DROP CONSTRAINT view_base_table_pkey; 2025-07-03 22:05:10.916 UTC client backend[16154] pg_regress/create_view ERROR: cannot drop columns from view 2025-07-03 22:05:10.916 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a FROM viewtest_tbl WHERE a <> 20; 2025-07-03 22:05:10.916 UTC client backend[16154] pg_regress/create_view ERROR: cannot change name of view column "a" to "?column?" 2025-07-03 22:05:10.916 UTC client backend[16154] pg_regress/create_view HINT: Use ALTER VIEW ... RENAME COLUMN ... to change name of view column instead. 2025-07-03 22:05:10.916 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT 1, * FROM viewtest_tbl; 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view ERROR: cannot change data type of view column "b" from integer to numeric 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b::numeric, c, d FROM viewtest_tbl; 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view ERROR: cannot change data type of view column "c" from numeric(10,1) to numeric(10,2) 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c::numeric(10,2), d FROM viewtest_tbl; 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view ERROR: cannot change collation of view column "d" from "C" to "POSIX" 2025-07-03 22:05:10.917 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE OR REPLACE VIEW viewtest AS SELECT a, b, c, d COLLATE "POSIX" FROM viewtest_tbl; 2025-07-03 22:05:10.944 UTC client backend[16150] pg_regress/index_including ERROR: could not create unique index "tbl_include_box_pk_pkey" 2025-07-03 22:05:10.944 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) is duplicated. 2025-07-03 22:05:10.944 UTC client backend[16150] pg_regress/index_including STATEMENT: ALTER TABLE tbl_include_box_pk add PRIMARY KEY (c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:10.959 UTC client backend[16150] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2025-07-03 22:05:10.959 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-07-03 22:05:10.959 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:10.978 UTC client backend[16154] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2025-07-03 22:05:10.978 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE VIEW temp_view_test.v3_temp AS SELECT * FROM temp_table; 2025-07-03 22:05:10.979 UTC client backend[16154] pg_regress/create_view ERROR: cannot create temporary relation in non-temporary schema 2025-07-03 22:05:10.979 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE SCHEMA test_view_schema CREATE TEMP VIEW testview AS SELECT 1; 2025-07-03 22:05:10.985 UTC client backend[16150] pg_regress/index_including ERROR: duplicate key value violates unique constraint "covering" 2025-07-03 22:05:10.985 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-07-03 22:05:10.985 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:10.987 UTC client backend[16150] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2025-07-03 22:05:10.987 UTC client backend[16150] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2025-07-03 22:05:10.987 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, NULL, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:11.016 UTC client backend[16150] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_c1_c2_c3_c4_key" 2025-07-03 22:05:11.016 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-07-03 22:05:11.016 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:11.035 UTC client backend[16150] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_pkey" 2025-07-03 22:05:11.035 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-07-03 22:05:11.035 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:11.036 UTC client backend[16150] pg_regress/index_including ERROR: null value in column "c2" of relation "tbl" violates not-null constraint 2025-07-03 22:05:11.036 UTC client backend[16150] pg_regress/index_including DETAIL: Failing row contains (1, null, 3, (4,4),(4,4)). 2025-07-03 22:05:11.036 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, NULL, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:11.065 UTC client backend[16150] pg_regress/index_including ERROR: conflicting key value violates exclusion constraint "tbl_c1_c3_c4_excl" 2025-07-03 22:05:11.065 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1)=(1) conflicts with existing key (c1)=(1). 2025-07-03 22:05:11.065 UTC client backend[16150] pg_regress/index_including STATEMENT: INSERT INTO tbl SELECT 1, 2, 3*x, box('4,4,4,4') FROM generate_series(1,10) AS x; 2025-07-03 22:05:11.092 UTC client backend[16157] pg_regress/create_index ERROR: relation "six_wrong" does not exist 2025-07-03 22:05:11.092 UTC client backend[16157] pg_regress/create_index STATEMENT: COMMENT ON INDEX six_wrong IS 'bad index'; 2025-07-03 22:05:11.228 UTC client backend[16154] pg_regress/create_view ERROR: invalid value for boolean option "security_barrier": 100 2025-07-03 22:05:11.228 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE VIEW mysecview5 WITH (security_barrier=100) -- Error AS SELECT * FROM tbl1 WHERE a > 100; 2025-07-03 22:05:11.229 UTC client backend[16154] pg_regress/create_view ERROR: unrecognized parameter "invalid_option" 2025-07-03 22:05:11.229 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE VIEW mysecview6 WITH (invalid_option) -- Error AS SELECT * FROM tbl1 WHERE a < 100; 2025-07-03 22:05:11.238 UTC client backend[16154] pg_regress/create_view ERROR: invalid value for boolean option "security_invoker": 100 2025-07-03 22:05:11.238 UTC client backend[16154] pg_regress/create_view STATEMENT: CREATE VIEW mysecview10 WITH (security_invoker=100) -- Error AS SELECT * FROM tbl1 WHERE a <> 100; 2025-07-03 22:05:11.241 UTC client backend[16150] pg_regress/index_including ERROR: cannot alter statistics on non-expression column "c1" of index "tbl_idx" 2025-07-03 22:05:11.241 UTC client backend[16150] pg_regress/index_including HINT: Alter statistics on table column instead. 2025-07-03 22:05:11.241 UTC client backend[16150] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 1 SET STATISTICS 1000; 2025-07-03 22:05:11.243 UTC client backend[16150] pg_regress/index_including ERROR: cannot alter statistics on included column "c2" of index "tbl_idx" 2025-07-03 22:05:11.243 UTC client backend[16150] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 3 SET STATISTICS 1000; 2025-07-03 22:05:11.243 UTC client backend[16150] pg_regress/index_including ERROR: column number 4 of relation "tbl_idx" does not exist 2025-07-03 22:05:11.243 UTC client backend[16150] pg_regress/index_including STATEMENT: ALTER INDEX tbl_idx ALTER COLUMN 4 SET STATISTICS 1000; 2025-07-03 22:05:11.400 UTC client backend[16150] pg_regress/index_including ERROR: relation "tbl_c1_c2_c3_c4_key" does not exist 2025-07-03 22:05:11.400 UTC client backend[16150] pg_regress/index_including STATEMENT: REINDEX INDEX tbl_c1_c2_c3_c4_key; 2025-07-03 22:05:11.424 UTC client backend[16150] pg_regress/index_including ERROR: access method "brin" does not support included columns 2025-07-03 22:05:11.424 UTC client backend[16150] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING brin(c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:11.439 UTC client backend[16150] pg_regress/index_including ERROR: access method "gin" does not support included columns 2025-07-03 22:05:11.439 UTC client backend[16150] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING gin(c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:11.439 UTC client backend[16150] pg_regress/index_including ERROR: access method "hash" does not support included columns 2025-07-03 22:05:11.439 UTC client backend[16150] pg_regress/index_including STATEMENT: CREATE INDEX on tbl USING hash(c1, c2) INCLUDE (c3, c4); 2025-07-03 22:05:11.512 UTC client backend[16150] pg_regress/index_including ERROR: duplicate key value violates unique constraint "tbl_idx_unique" 2025-07-03 22:05:11.512 UTC client backend[16150] pg_regress/index_including DETAIL: Key (c1, c2)=(1, 2) already exists. 2025-07-03 22:05:11.512 UTC client backend[16150] pg_regress/index_including STATEMENT: UPDATE tbl SET c2 = 2 WHERE c1 = 1; 2025-07-03 22:05:11.734 UTC client backend[16150] pg_regress/index_including LOG: disconnection: session time: 0:00:01.067 user=postgres database=regression host=[local] 2025-07-03 22:05:12.117 UTC client backend[16157] pg_regress/create_index ERROR: duplicate key value violates unique constraint "unique_idx2" 2025-07-03 22:05:12.117 UTC client backend[16157] pg_regress/create_index DETAIL: Key (i)=(null) already exists. 2025-07-03 22:05:12.117 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO unique_tbl (t) VALUES ('seven'); 2025-07-03 22:05:12.122 UTC client backend[16157] pg_regress/create_index ERROR: could not create unique index "unique_idx4" 2025-07-03 22:05:12.122 UTC client backend[16157] pg_regress/create_index DETAIL: Key (i)=(null) is duplicated. 2025-07-03 22:05:12.122 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX unique_idx4 ON unique_tbl (i) NULLS NOT DISTINCT; 2025-07-03 22:05:12.247 UTC client backend[16155] pg_regress/index_including_gist ERROR: conflicting key value violates exclusion constraint "tbl_gist_c4_c1_c2_c3_excl" 2025-07-03 22:05:12.247 UTC client backend[16155] pg_regress/index_including_gist DETAIL: Key (c4)=((4,5),(2,3)) conflicts with existing key (c4)=((2,3),(1,2)). 2025-07-03 22:05:12.247 UTC client backend[16155] pg_regress/index_including_gist STATEMENT: INSERT INTO tbl_gist SELECT x, 2*x, 3*x, box(point(x,x+1),point(2*x,2*x+1)) FROM generate_series(1,10) AS x; 2025-07-03 22:05:12.295 UTC client backend[16157] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2025-07-03 22:05:12.295 UTC client backend[16157] pg_regress/create_index DETAIL: Key (textcat(f1, f2))=(ABCDEF) already exists. 2025-07-03 22:05:12.295 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2025-07-03 22:05:12.355 UTC client backend[16155] pg_regress/index_including_gist LOG: disconnection: session time: 0:00:01.661 user=postgres database=regression host=[local] 2025-07-03 22:05:12.429 UTC client backend[16157] pg_regress/create_index ERROR: duplicate key value violates unique constraint "func_index_index" 2025-07-03 22:05:12.429 UTC client backend[16157] pg_regress/create_index DETAIL: Key ((f1 || f2))=(ABCDEF) already exists. 2025-07-03 22:05:12.429 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO func_index_heap VALUES('ABCD', 'EF'); 2025-07-03 22:05:12.546 UTC client backend[16157] pg_regress/create_index ERROR: column "row" has pseudo-type record 2025-07-03 22:05:12.546 UTC client backend[16157] pg_regress/create_index STATEMENT: create index on func_index_heap ((f1 || f2), (row(f1, f2))); 2025-07-03 22:05:12.564 UTC client backend[16157] pg_regress/create_index ERROR: duplicate key value violates unique constraint "covering_index_index" 2025-07-03 22:05:12.564 UTC client backend[16157] pg_regress/create_index DETAIL: Key (f1, f2)=(1, 2) already exists. 2025-07-03 22:05:12.564 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO covering_index_heap VALUES(1,2,'BBB'); 2025-07-03 22:05:12.605 UTC client backend[16157] pg_regress/create_index ERROR: duplicate key value violates unique constraint "concur_index2" 2025-07-03 22:05:12.605 UTC client backend[16157] pg_regress/create_index DETAIL: Key (f1)=(b) already exists. 2025-07-03 22:05:12.605 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO concur_heap VALUES ('b','x'); 2025-07-03 22:05:12.606 UTC client backend[16157] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2025-07-03 22:05:12.606 UTC client backend[16157] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2025-07-03 22:05:12.606 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2); 2025-07-03 22:05:12.669 UTC client backend[16157] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:12.669 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_index7 ON concur_heap(f1); 2025-07-03 22:05:12.713 UTC client backend[16157] pg_regress/create_index ERROR: could not create unique index "concur_index3" 2025-07-03 22:05:12.713 UTC client backend[16157] pg_regress/create_index DETAIL: Key (f2)=(b) is duplicated. 2025-07-03 22:05:12.713 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE concur_heap; 2025-07-03 22:05:12.854 UTC client backend[16154] pg_regress/create_view ERROR: cannot drop column f3 of table tt14t because other objects depend on it 2025-07-03 22:05:12.854 UTC client backend[16154] pg_regress/create_view DETAIL: view tt14v depends on column f3 of table tt14t 2025-07-03 22:05:12.854 UTC client backend[16154] pg_regress/create_view HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:12.854 UTC client backend[16154] pg_regress/create_view STATEMENT: alter table tt14t drop column f3; 2025-07-03 22:05:12.866 UTC client backend[16154] pg_regress/create_view ERROR: attribute 3 of type record has been dropped 2025-07-03 22:05:12.866 UTC client backend[16154] pg_regress/create_view STATEMENT: select * from tt14v; 2025-07-03 22:05:12.868 UTC client backend[16154] pg_regress/create_view ERROR: cannot alter type of a column used by a view or rule 2025-07-03 22:05:12.868 UTC client backend[16154] pg_regress/create_view DETAIL: rule _RETURN on view tt14v depends on column "f4" 2025-07-03 22:05:12.868 UTC client backend[16154] pg_regress/create_view STATEMENT: alter table tt14t alter column f4 type integer using f4::integer; 2025-07-03 22:05:12.885 UTC client backend[16154] pg_regress/create_view ERROR: attribute 4 of type record has wrong type 2025-07-03 22:05:12.885 UTC client backend[16154] pg_regress/create_view DETAIL: Table has type integer, but query expects text. 2025-07-03 22:05:12.885 UTC client backend[16154] pg_regress/create_view STATEMENT: select * from tt14v; 2025-07-03 22:05:12.920 UTC client backend[16157] pg_regress/create_index ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:12.920 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX CONCURRENTLY concur_temp_ind ON concur_temp(f1); 2025-07-03 22:05:12.941 UTC client backend[16157] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY does not support dropping multiple objects 2025-07-03 22:05:12.941 UTC client backend[16157] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index2", "concur_index3"; 2025-07-03 22:05:12.941 UTC client backend[16157] pg_regress/create_index ERROR: DROP INDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:12.941 UTC client backend[16157] pg_regress/create_index STATEMENT: DROP INDEX CONCURRENTLY "concur_index5"; 2025-07-03 22:05:12.968 UTC client backend[16154] pg_regress/create_view ERROR: operator does not exist: text = text[] at character 20 2025-07-03 22:05:12.968 UTC client backend[16154] pg_regress/create_view HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:12.968 UTC client backend[16154] pg_regress/create_view STATEMENT: select 'foo'::text = any((select array['abc','def','foo']::text[])); 2025-07-03 22:05:13.043 UTC client backend[16154] pg_regress/create_view ERROR: access to non-system view "tt27v" is restricted 2025-07-03 22:05:13.043 UTC client backend[16154] pg_regress/create_view STATEMENT: select a from tt27v where a > 0; 2025-07-03 22:05:13.043 UTC client backend[16154] pg_regress/create_view ERROR: access to non-system view "tt27v" is restricted 2025-07-03 22:05:13.043 UTC client backend[16154] pg_regress/create_view STATEMENT: insert into tt27v values (1); 2025-07-03 22:05:13.177 UTC client backend[16157] pg_regress/create_index ERROR: cannot drop index cwi_replaced_pkey because constraint cwi_replaced_pkey on table cwi_test requires it 2025-07-03 22:05:13.177 UTC client backend[16157] pg_regress/create_index HINT: You can drop constraint cwi_replaced_pkey on table cwi_test instead. 2025-07-03 22:05:13.177 UTC client backend[16157] pg_regress/create_index STATEMENT: DROP INDEX cwi_replaced_pkey; 2025-07-03 22:05:13.178 UTC client backend[16157] pg_regress/create_index ERROR: index "cwi_uniq3_idx" column number 1 does not have default sorting behavior at character 26 2025-07-03 22:05:13.178 UTC client backend[16157] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-07-03 22:05:13.178 UTC client backend[16157] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq3_idx; 2025-07-03 22:05:13.187 UTC client backend[16157] pg_regress/create_index ERROR: index "cwi_uniq4_idx" column number 1 does not have default sorting behavior at character 26 2025-07-03 22:05:13.187 UTC client backend[16157] pg_regress/create_index DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-07-03 22:05:13.187 UTC client backend[16157] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq4_idx; 2025-07-03 22:05:13.192 UTC client backend[16157] pg_regress/create_index ERROR: ALTER TABLE / ADD CONSTRAINT USING INDEX is not supported on partitioned tables 2025-07-03 22:05:13.192 UTC client backend[16157] pg_regress/create_index STATEMENT: alter table cwi_test add primary key using index cwi_test_a_idx ; 2025-07-03 22:05:13.195 UTC client backend[16157] pg_regress/create_index ERROR: primary keys cannot use NULLS NOT DISTINCT indexes 2025-07-03 22:05:13.195 UTC client backend[16157] pg_regress/create_index STATEMENT: ALTER TABLE cwi_test ADD PRIMARY KEY USING INDEX cwi_a_nnd; 2025-07-03 22:05:13.200 UTC client backend[16157] pg_regress/create_index ERROR: relation "syscolcol_table" does not exist 2025-07-03 22:05:13.200 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX ON syscolcol_table (ctid); 2025-07-03 22:05:13.200 UTC client backend[16157] pg_regress/create_index ERROR: index creation on system columns is not supported 2025-07-03 22:05:13.200 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table ((ctid >= '(1000,0)')); 2025-07-03 22:05:13.201 UTC client backend[16157] pg_regress/create_index ERROR: index creation on system columns is not supported 2025-07-03 22:05:13.201 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE INDEX ON syscol_table (a) WHERE ctid >= '(1000,0)'; 2025-07-03 22:05:13.410 UTC client backend[16154] pg_regress/create_view LOG: disconnection: session time: 0:00:02.721 user=postgres database=regression host=[local] 2025-07-03 22:05:13.562 UTC client backend[16153] pg_regress/create_index_spgist LOG: disconnection: session time: 0:00:02.883 user=postgres database=regression host=[local] 2025-07-03 22:05:13.685 UTC client backend[16157] pg_regress/create_index ERROR: concurrent index creation for exclusion constraints is not supported 2025-07-03 22:05:13.685 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_tab3_c2_excl; 2025-07-03 22:05:13.685 UTC client backend[16157] pg_regress/create_index WARNING: cannot reindex exclusion constraint index "public.concur_reindex_tab3_c2_excl" concurrently, skipping 2025-07-03 22:05:13.702 UTC client backend[16157] pg_regress/create_index ERROR: conflicting key value violates exclusion constraint "concur_reindex_tab3_c2_excl" 2025-07-03 22:05:13.702 UTC client backend[16157] pg_regress/create_index DETAIL: Key (c2)=([2,5)) conflicts with existing key (c2)=([1,3)). 2025-07-03 22:05:13.702 UTC client backend[16157] pg_regress/create_index STATEMENT: INSERT INTO concur_reindex_tab3 VALUES (4, '[2,4]'); 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index; 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_index" is not a table or materialized view 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index; 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part_index_10; 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_index_10" is not a table or materialized view 2025-07-03 22:05:13.975 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_part_index_10; 2025-07-03 22:05:13.976 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX INDEX cannot run inside a transaction block 2025-07-03 22:05:13.976 UTC client backend[16157] pg_regress/create_index CONTEXT: while reindexing partitioned index "public.concur_reindex_part_index" 2025-07-03 22:05:13.976 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_index; 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part; 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part" is not an index 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part; 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX concur_reindex_part_10; 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index ERROR: "concur_reindex_part_10" is not an index 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_part_10; 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX TABLE cannot run inside a transaction block 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index CONTEXT: while reindexing partitioned table "public.concur_reindex_part" 2025-07-03 22:05:14.022 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE concur_reindex_part; 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY concur_reindex_tab; 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_class; 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.080 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_class_oid_index; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE CONCURRENTLY pg_toast.pg_toast_1262; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY pg_toast.pg_toast_1262_index; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX SYSTEM CONCURRENTLY postgres; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM postgres; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index ERROR: cannot reindex system catalogs concurrently 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX (CONCURRENTLY) SYSTEM; 2025-07-03 22:05:14.081 UTC client backend[16157] pg_regress/create_index WARNING: cannot reindex system catalogs concurrently, skipping all 2025-07-03 22:05:14.083 UTC client backend[16157] pg_regress/create_index ERROR: can only reindex the currently open database 2025-07-03 22:05:14.083 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX DATABASE not_current_database; 2025-07-03 22:05:14.160 UTC client backend[16157] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5" 2025-07-03 22:05:14.160 UTC client backend[16157] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2025-07-03 22:05:14.160 UTC client backend[16157] pg_regress/create_index STATEMENT: CREATE UNIQUE INDEX CONCURRENTLY concur_reindex_ind5 ON concur_reindex_tab4 (c1); 2025-07-03 22:05:14.162 UTC client backend[16157] pg_regress/create_index ERROR: could not create unique index "concur_reindex_ind5_ccnew" 2025-07-03 22:05:14.162 UTC client backend[16157] pg_regress/create_index DETAIL: Key (c1)=(1) is duplicated. 2025-07-03 22:05:14.162 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_reindex_ind5; 2025-07-03 22:05:14.217 UTC client backend[16157] pg_regress/create_index WARNING: skipping reindex of invalid index "public.concur_reindex_ind5" 2025-07-03 22:05:14.217 UTC client backend[16157] pg_regress/create_index HINT: Use DROP INDEX or REINDEX INDEX. 2025-07-03 22:05:14.422 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:14.422 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_1; 2025-07-03 22:05:14.452 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:05:14.452 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX CONCURRENTLY concur_temp_ind_3; 2025-07-03 22:05:14.593 UTC client backend[16157] pg_regress/create_index ERROR: schema "schema_to_reindex" does not exist 2025-07-03 22:05:14.593 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-07-03 22:05:14.639 UTC client backend[16157] pg_regress/create_index ERROR: REINDEX SCHEMA cannot run inside a transaction block 2025-07-03 22:05:14.639 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-07-03 22:05:14.655 UTC client backend[16157] pg_regress/create_index ERROR: must be owner of schema schema_to_reindex 2025-07-03 22:05:14.655 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX SCHEMA schema_to_reindex; 2025-07-03 22:05:14.656 UTC client backend[16157] pg_regress/create_index ERROR: permission denied for table pg_toast_1262 2025-07-03 22:05:14.656 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX TABLE pg_toast.pg_toast_1262; 2025-07-03 22:05:14.657 UTC client backend[16157] pg_regress/create_index ERROR: permission denied for index pg_toast_1262_index 2025-07-03 22:05:14.657 UTC client backend[16157] pg_regress/create_index STATEMENT: REINDEX INDEX pg_toast.pg_toast_1262_index; 2025-07-03 22:05:14.674 UTC client backend[16157] pg_regress/create_index LOG: disconnection: session time: 0:00:03.982 user=postgres database=regression host=[local] 2025-07-03 22:05:14.894 UTC not initialized[16473] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.896 UTC client backend[16473] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.896 UTC client backend[16473] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/constraints 2025-07-03 22:05:14.918 UTC client backend[16473] pg_regress/constraints LOG: connection ready: setup total=47.387 ms, fork=22.776 ms, authentication=0.418 ms 2025-07-03 22:05:14.923 UTC not initialized[16476] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.927 UTC not initialized[16474] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.927 UTC not initialized[16480] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.929 UTC client backend[16474] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.929 UTC client backend[16474] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/triggers 2025-07-03 22:05:14.929 UTC not initialized[16481] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.929 UTC not initialized[16478] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.931 UTC client backend[16478] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.931 UTC client backend[16481] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.931 UTC client backend[16478] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/typed_table 2025-07-03 22:05:14.931 UTC client backend[16481] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/drop_if_exists 2025-07-03 22:05:14.931 UTC not initialized[16479] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.931 UTC not initialized[16477] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.932 UTC client backend[16480] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.932 UTC client backend[16480] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/errors 2025-07-03 22:05:14.932 UTC client backend[16477] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.933 UTC client backend[16477] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_aggregate 2025-07-03 22:05:14.933 UTC client backend[16479] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.933 UTC client backend[16479] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/inherit 2025-07-03 22:05:14.936 UTC client backend[16476] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.936 UTC client backend[16476] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/hash_func 2025-07-03 22:05:14.937 UTC not initialized[16483] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.939 UTC client backend[16476] pg_regress/hash_func LOG: connection ready: setup total=33.404 ms, fork=16.656 ms, authentication=0.379 ms 2025-07-03 22:05:14.940 UTC client backend[16483] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.940 UTC client backend[16483] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/vacuum 2025-07-03 22:05:14.940 UTC not initialized[16482] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.941 UTC client backend[16482] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.941 UTC client backend[16482] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_function_sql 2025-07-03 22:05:14.942 UTC client backend[16483] pg_regress/vacuum LOG: connection ready: setup total=19.654 ms, fork=11.948 ms, authentication=0.377 ms 2025-07-03 22:05:14.943 UTC client backend[16478] pg_regress/typed_table LOG: connection ready: setup total=34.094 ms, fork=19.788 ms, authentication=0.383 ms 2025-07-03 22:05:14.946 UTC client backend[16482] pg_regress/create_function_sql LOG: connection ready: setup total=24.992 ms, fork=9.313 ms, authentication=0.363 ms 2025-07-03 22:05:14.948 UTC client backend[16480] pg_regress/errors LOG: connection ready: setup total=34.605 ms, fork=13.631 ms, authentication=0.382 ms 2025-07-03 22:05:14.949 UTC client backend[16479] pg_regress/inherit LOG: connection ready: setup total=38.298 ms, fork=14.531 ms, authentication=0.404 ms 2025-07-03 22:05:14.951 UTC client backend[16480] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 15 2025-07-03 22:05:14.951 UTC client backend[16480] pg_regress/errors STATEMENT: select * from nonesuch; 2025-07-03 22:05:14.952 UTC client backend[16481] pg_regress/drop_if_exists LOG: connection ready: setup total=31.922 ms, fork=6.087 ms, authentication=0.423 ms 2025-07-03 22:05:14.952 UTC client backend[16478] pg_regress/typed_table ERROR: type "nothing" does not exist at character 25 2025-07-03 22:05:14.952 UTC client backend[16478] pg_regress/typed_table STATEMENT: CREATE TABLE ttable1 OF nothing; 2025-07-03 22:05:14.953 UTC client backend[16481] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2025-07-03 22:05:14.953 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2025-07-03 22:05:14.953 UTC client backend[16480] pg_regress/errors ERROR: column "nonesuch" does not exist at character 8 2025-07-03 22:05:14.953 UTC client backend[16480] pg_regress/errors STATEMENT: select nonesuch from pg_database; 2025-07-03 22:05:14.953 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "from" at character 17 2025-07-03 22:05:14.953 UTC client backend[16480] pg_regress/errors STATEMENT: select distinct from pg_database; 2025-07-03 22:05:14.953 UTC not initialized[16486] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.954 UTC client backend[16480] pg_regress/errors ERROR: column "nonesuch" does not exist at character 33 2025-07-03 22:05:14.954 UTC client backend[16480] pg_regress/errors STATEMENT: select * from pg_database where nonesuch = pg_database.datname; 2025-07-03 22:05:14.954 UTC not initialized[16484] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.955 UTC client backend[16480] pg_regress/errors ERROR: column "nonesuch" does not exist at character 55 2025-07-03 22:05:14.955 UTC client backend[16480] pg_regress/errors STATEMENT: select * from pg_database where pg_database.datname = nonesuch; 2025-07-03 22:05:14.955 UTC client backend[16480] pg_regress/errors ERROR: column "foobar" does not exist at character 21 2025-07-03 22:05:14.955 UTC client backend[16480] pg_regress/errors STATEMENT: select distinct on (foobar) * from pg_database; 2025-07-03 22:05:14.955 UTC client backend[16474] pg_regress/triggers LOG: connection ready: setup total=63.629 ms, fork=32.726 ms, authentication=0.421 ms 2025-07-03 22:05:14.957 UTC client backend[16484] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.957 UTC client backend[16484] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/roleattributes 2025-07-03 22:05:14.958 UTC not initialized[16485] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.960 UTC client backend[16477] pg_regress/create_aggregate LOG: connection ready: setup total=52.267 ms, fork=21.573 ms, authentication=0.364 ms 2025-07-03 22:05:14.964 UTC client backend[16486] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.964 UTC client backend[16486] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/infinite_recurse 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors STATEMENT: select null from pg_database group by datname for update; 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors ERROR: FOR UPDATE is not allowed with GROUP BY clause 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors STATEMENT: select null from pg_database group by grouping sets (()) for update; 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 12 2025-07-03 22:05:14.967 UTC client backend[16480] pg_regress/errors STATEMENT: delete from; 2025-07-03 22:05:14.968 UTC client backend[16485] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.968 UTC client backend[16485] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_am 2025-07-03 22:05:14.968 UTC client backend[16480] pg_regress/errors ERROR: relation "nonesuch" does not exist at character 13 2025-07-03 22:05:14.968 UTC client backend[16480] pg_regress/errors STATEMENT: delete from nonesuch; 2025-07-03 22:05:14.968 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2025-07-03 22:05:14.968 UTC client backend[16480] pg_regress/errors STATEMENT: drop table; 2025-07-03 22:05:14.969 UTC client backend[16477] pg_regress/create_aggregate ERROR: aggregate newavg_wrong(integer) does not exist 2025-07-03 22:05:14.969 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE newavg_wrong (int4) IS 'an agg comment'; 2025-07-03 22:05:14.972 UTC client backend[16480] pg_regress/errors ERROR: table "nonesuch" does not exist 2025-07-03 22:05:14.972 UTC client backend[16480] pg_regress/errors STATEMENT: drop table nonesuch; 2025-07-03 22:05:14.973 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 19 2025-07-03 22:05:14.973 UTC client backend[16480] pg_regress/errors STATEMENT: alter table rename; 2025-07-03 22:05:14.974 UTC client backend[16480] pg_regress/errors ERROR: relation "nonesuch" does not exist 2025-07-03 22:05:14.974 UTC client backend[16480] pg_regress/errors STATEMENT: alter table nonesuch rename to newnonesuch; 2025-07-03 22:05:14.974 UTC client backend[16480] pg_regress/errors ERROR: relation "nonesuch" does not exist 2025-07-03 22:05:14.974 UTC client backend[16480] pg_regress/errors STATEMENT: alter table nonesuch rename to stud_emp; 2025-07-03 22:05:14.974 UTC client backend[16485] pg_regress/create_am LOG: connection ready: setup total=46.083 ms, fork=28.111 ms, authentication=0.388 ms 2025-07-03 22:05:14.974 UTC not initialized[16488] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors ERROR: relation "student" already exists 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors STATEMENT: alter table stud_emp rename to student; 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors ERROR: relation "stud_emp" already exists 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors STATEMENT: alter table stud_emp rename to stud_emp; 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors ERROR: relation "nonesuchrel" does not exist 2025-07-03 22:05:14.975 UTC client backend[16480] pg_regress/errors STATEMENT: alter table nonesuchrel rename column nonesuchatt to newnonesuchatt; 2025-07-03 22:05:14.975 UTC client backend[16488] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.975 UTC client backend[16488] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_cast 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors ERROR: column "nonesuchatt" does not exist 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors STATEMENT: alter table emp rename column nonesuchatt to newnonesuchatt; 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors ERROR: column "manager" of relation "stud_emp" already exists 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors STATEMENT: alter table emp rename column salary to manager; 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors ERROR: column name "ctid" conflicts with a system column name 2025-07-03 22:05:14.976 UTC client backend[16480] pg_regress/errors STATEMENT: alter table emp rename column salary to ctid; 2025-07-03 22:05:14.977 UTC client backend[16480] pg_regress/errors WARNING: there is no transaction in progress 2025-07-03 22:05:14.977 UTC client backend[16480] pg_regress/errors WARNING: there is no transaction in progress 2025-07-03 22:05:14.977 UTC client backend[16480] pg_regress/errors ERROR: function int2um(integer) does not exist 2025-07-03 22:05:14.977 UTC client backend[16480] pg_regress/errors STATEMENT: create aggregate newavg2 (sfunc = int4pl, basetype = int4, stype = int4, finalfunc = int2um, initcond = '0'); 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: aggregate input type must be specified 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: create aggregate newcnt1 (sfunc = int4inc, stype = int4, initcond = '0'); 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 11 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop index; 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "314159" at character 12 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop index 314159; 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: index "nonesuch" does not exist 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop index nonesuch; 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 15 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate; 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 23 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate newcnt1; 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "314159" at character 16 2025-07-03 22:05:14.978 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate 314159 (int); 2025-07-03 22:05:14.979 UTC client backend[16480] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-07-03 22:05:14.979 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate newcnt (nonesuch); 2025-07-03 22:05:14.979 UTC not initialized[16489] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:14.981 UTC client backend[16486] pg_regress/infinite_recurse LOG: connection ready: setup total=41.561 ms, fork=13.250 ms, authentication=0.432 ms 2025-07-03 22:05:14.982 UTC client backend[16489] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:14.982 UTC client backend[16489] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select 2025-07-03 22:05:14.984 UTC client backend[16484] pg_regress/roleattributes LOG: connection ready: setup total=57.258 ms, fork=27.267 ms, authentication=0.408 ms 2025-07-03 22:05:14.987 UTC client backend[16485] pg_regress/create_am ERROR: function int4in(internal) does not exist 2025-07-03 22:05:14.987 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER int4in; 2025-07-03 22:05:14.988 UTC client backend[16485] pg_regress/create_am ERROR: function heap_tableam_handler must return type index_am_handler 2025-07-03 22:05:14.988 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE INDEX HANDLER heap_tableam_handler; 2025-07-03 22:05:14.994 UTC client backend[16480] pg_regress/errors ERROR: aggregate nonesuch(integer) does not exist 2025-07-03 22:05:14.994 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate nonesuch (int4); 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors ERROR: aggregate newcnt(real) does not exist 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors STATEMENT: drop aggregate newcnt (float4); 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors STATEMENT: drop function (); 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "314159" at character 15 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors STATEMENT: drop function 314159(); 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors ERROR: function nonesuch() does not exist 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors STATEMENT: drop function nonesuch(); 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2025-07-03 22:05:14.995 UTC client backend[16480] pg_regress/errors STATEMENT: drop type; 2025-07-03 22:05:14.996 UTC client backend[16489] pg_regress/select LOG: connection ready: setup total=45.343 ms, fork=22.151 ms, authentication=0.387 ms 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors STATEMENT: drop type 314159; 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors STATEMENT: drop type nonesuch; 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator; 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 21 2025-07-03 22:05:14.997 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator equals; 2025-07-03 22:05:14.999 UTC client backend[16485] pg_regress/create_am ERROR: data type box has no default operator class for access method "gist2" 2025-07-03 22:05:14.999 UTC client backend[16485] pg_regress/create_am HINT: You must specify an operator class for the index or define a default operator class for the data type. 2025-07-03 22:05:14.999 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE INDEX grect2ind2 ON fast_emp4000 USING gist2 (home_base); 2025-07-03 22:05:14.999 UTC client backend[16481] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2025-07-03 22:05:14.999 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2025-07-03 22:05:14.999 UTC client backend[16488] pg_regress/create_cast LOG: connection ready: setup total=50.193 ms, fork=21.976 ms, authentication=0.387 ms 2025-07-03 22:05:15.004 UTC client backend[16477] pg_regress/create_aggregate ERROR: aggregate nosuchagg(*) does not exist 2025-07-03 22:05:15.004 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: COMMENT ON AGGREGATE nosuchagg (*) IS 'should fail'; 2025-07-03 22:05:15.007 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 18 2025-07-03 22:05:15.007 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator ===; 2025-07-03 22:05:15.008 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "," at character 19 2025-07-03 22:05:15.008 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator int4, int4; 2025-07-03 22:05:15.008 UTC not initialized[16491] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:15.010 UTC client backend[16491] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:15.010 UTC client backend[16491] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/updatable_views 2025-07-03 22:05:15.012 UTC client backend[16491] pg_regress/updatable_views LOG: connection ready: setup total=39.038 ms, fork=29.740 ms, authentication=0.409 ms 2025-07-03 22:05:15.019 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "(" at character 15 2025-07-03 22:05:15.019 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator (int4, int4); 2025-07-03 22:05:15.019 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ")" at character 20 2025-07-03 22:05:15.019 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator === (); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: missing argument at character 24 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator === (int4); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: operator does not exist: integer === integer 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator === (int4, int4); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: missing argument at character 26 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors HINT: Use NONE to denote the missing argument of a unary operator. 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator = (nonesuch); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "," at character 19 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator = ( , int4); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator = (nonesuch, int4); 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors ERROR: type "nonesuch" does not exist 2025-07-03 22:05:15.020 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator = (int4, nonesuch); 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ")" at character 24 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop operator = (int4, ); 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 10 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop rule; 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "314159" at character 11 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop rule 314159; 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: relation "noplace" does not exist 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop rule nonesuch on noplace; 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "tuple" at character 6 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop tuple rule nonesuch; 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "instance" at character 6 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop instance rule nonesuch on noplace; 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "rewrite" at character 6 2025-07-03 22:05:15.021 UTC client backend[16480] pg_regress/errors STATEMENT: drop rewrite rule nonesuch; 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0; 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors STATEMENT: select 1::int8/0; 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.022 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0::int8; 2025-07-03 22:05:15.023 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.023 UTC client backend[16480] pg_regress/errors STATEMENT: select 1::int2/0; 2025-07-03 22:05:15.023 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.023 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0::int2; 2025-07-03 22:05:15.024 UTC client backend[16473] pg_regress/constraints ERROR: syntax error at or near ")" at character 45 2025-07-03 22:05:15.024 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (i int DEFAULT (100, )); 2025-07-03 22:05:15.027 UTC client backend[16473] pg_regress/constraints ERROR: syntax error at or near "IN" at character 43 2025-07-03 22:05:15.027 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE error_tbl (b1 bool DEFAULT 1 IN (1, 2)); 2025-07-03 22:05:15.035 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.035 UTC client backend[16480] pg_regress/errors STATEMENT: select 1::numeric/0; 2025-07-03 22:05:15.035 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.035 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0::numeric; 2025-07-03 22:05:15.036 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.036 UTC client backend[16480] pg_regress/errors STATEMENT: select 1::float8/0; 2025-07-03 22:05:15.036 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.036 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0::float8; 2025-07-03 22:05:15.039 UTC client backend[16488] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2025-07-03 22:05:15.039 UTC client backend[16488] pg_regress/create_cast HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:15.039 UTC client backend[16488] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2025-07-03 22:05:15.044 UTC client backend[16481] pg_regress/drop_if_exists ERROR: view "test_view_exists" does not exist 2025-07-03 22:05:15.044 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP VIEW test_view_exists; 2025-07-03 22:05:15.045 UTC client backend[16481] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2025-07-03 22:05:15.045 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2025-07-03 22:05:15.049 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.049 UTC client backend[16480] pg_regress/errors STATEMENT: select 1::float4/0; 2025-07-03 22:05:15.050 UTC client backend[16480] pg_regress/errors ERROR: division by zero 2025-07-03 22:05:15.050 UTC client backend[16480] pg_regress/errors STATEMENT: select 1/0::float4; 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "xxx" at character 1 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors STATEMENT: xxx; 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "foo" at character 8 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE foo; 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near ";" at character 14 2025-07-03 22:05:15.053 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE ; 2025-07-03 22:05:15.054 UTC client backend[16488] pg_regress/create_cast ERROR: function casttestfunc(text) does not exist at character 8 2025-07-03 22:05:15.054 UTC client backend[16488] pg_regress/create_cast HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:15.054 UTC client backend[16488] pg_regress/create_cast STATEMENT: SELECT casttestfunc('foo'::text); 2025-07-03 22:05:15.054 UTC client backend[16480] pg_regress/errors ERROR: syntax error at end of input at character 13 2025-07-03 22:05:15.054 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "foo" at character 29 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) foo; 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "123" at character 13 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: INSERT INTO 123 VALUES(123); 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "123" at character 29 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: INSERT INTO foo VALUES(123) 123 ; 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 94 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE foo (id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL); 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL); 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 35 2025-07-03 22:05:15.055 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE foo( id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY); 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 90 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TABLE foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL); 2025-07-03 22:05:15.057 UTC client backend[16488] pg_regress/create_cast ERROR: cannot cast type integer to casttesttype at character 18 2025-07-03 22:05:15.057 UTC client backend[16488] pg_regress/create_cast STATEMENT: SELECT 1234::int4::casttesttype; 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 100 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TEMPORARY TABLE foo(id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL) ; 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 45 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TEMPORARY TABLE foo( id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, id INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY) ; 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 153 2025-07-03 22:05:15.057 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TEMPORARY TABLE foo (id INT4 UNIQUE NOT NULL, idx INT4 UNIQUE NOT NULL, idy INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, idz INT4 UNIQUE NOT NULL, idv INT4 UNIQUE NOT NULL); 2025-07-03 22:05:15.058 UTC client backend[16480] pg_regress/errors ERROR: syntax error at or near "NUL" at character 180 2025-07-03 22:05:15.058 UTC client backend[16480] pg_regress/errors STATEMENT: CREATE TEMPORARY TABLE foo (id INT4 UNIQUE NOT NULL , idm INT4 UNIQUE NOT NULL, idx INT4 UNIQUE NOT NULL, idy INT4 UNIQUE NOT NULL, id2 TEXT NOT NULL PRIMARY KEY, id3 INTEGER NOT NUL, id4 INT4 UNIQUE NOT NULL, id5 TEXT UNIQUE NOT NULL, idz INT4 UNIQUE NOT NULL, idv INT4 UNIQUE NOT NULL); 2025-07-03 22:05:15.060 UTC client backend[16481] pg_regress/drop_if_exists ERROR: index "test_index_exists" does not exist 2025-07-03 22:05:15.060 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP INDEX test_index_exists; 2025-07-03 22:05:15.061 UTC client backend[16480] pg_regress/errors LOG: disconnection: session time: 0:00:00.134 user=postgres database=regression host=[local] 2025-07-03 22:05:15.068 UTC client backend[16481] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2025-07-03 22:05:15.068 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2025-07-03 22:05:15.070 UTC client backend[16488] pg_regress/create_cast LOG: disconnection: session time: 0:00:00.099 user=postgres database=regression host=[local] 2025-07-03 22:05:15.079 UTC client backend[16481] pg_regress/drop_if_exists ERROR: sequence "test_sequence_exists" does not exist 2025-07-03 22:05:15.079 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP SEQUENCE test_sequence_exists; 2025-07-03 22:05:15.080 UTC client backend[16481] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2025-07-03 22:05:15.080 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2025-07-03 22:05:15.093 UTC client backend[16477] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2025-07-03 22:05:15.093 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2025-07-03 22:05:15.094 UTC client backend[16481] pg_regress/drop_if_exists ERROR: schema "test_schema_exists" does not exist 2025-07-03 22:05:15.094 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP SCHEMA test_schema_exists; 2025-07-03 22:05:15.095 UTC client backend[16481] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2025-07-03 22:05:15.095 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2025-07-03 22:05:15.106 UTC client backend[16476] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2025-07-03 22:05:15.106 UTC client backend[16476] pg_regress/hash_func STATEMENT: SELECT v as value, hash_array(v)::bit(32) as standard FROM (VALUES ('{101}'::varbit[])) x(v); 2025-07-03 22:05:15.106 UTC client backend[16476] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2025-07-03 22:05:15.106 UTC client backend[16476] pg_regress/hash_func STATEMENT: SELECT v as value, hash_array_extended(v, 0)::bit(32) as extended0 FROM (VALUES ('{101}'::varbit[])) x(v); 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (3). 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (3); 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (2). 2025-07-03 22:05:15.128 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (2); 2025-07-03 22:05:15.129 UTC client backend[16477] pg_regress/create_aggregate ERROR: function least_accum(bigint, bigint) requires run-time type coercion 2025-07-03 22:05:15.129 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: create aggregate least_agg(int4) ( stype = int8, sfunc = least_accum ); 2025-07-03 22:05:15.129 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check_tbl" violates check constraint "check_con" 2025-07-03 22:05:15.129 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (1). 2025-07-03 22:05:15.129 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK_TBL VALUES (1); 2025-07-03 22:05:15.129 UTC client backend[16481] pg_regress/drop_if_exists ERROR: type "test_type_exists" does not exist 2025-07-03 22:05:15.129 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TYPE test_type_exists; 2025-07-03 22:05:15.131 UTC client backend[16481] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2025-07-03 22:05:15.131 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2025-07-03 22:05:15.141 UTC client backend[16481] pg_regress/drop_if_exists ERROR: type "test_domain_exists" does not exist 2025-07-03 22:05:15.141 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP DOMAIN test_domain_exists; 2025-07-03 22:05:15.142 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_u2" does not exist 2025-07-03 22:05:15.142 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u2; 2025-07-03 22:05:15.143 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_u1" does not exist 2025-07-03 22:05:15.143 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP USER regress_test_u1; 2025-07-03 22:05:15.143 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_r2" does not exist 2025-07-03 22:05:15.143 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r2; 2025-07-03 22:05:15.144 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_r1" does not exist 2025-07-03 22:05:15.144 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP ROLE regress_test_r1; 2025-07-03 22:05:15.145 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_g2" does not exist 2025-07-03 22:05:15.145 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g2; 2025-07-03 22:05:15.148 UTC client backend[16481] pg_regress/drop_if_exists ERROR: role "regress_test_g1" does not exist 2025-07-03 22:05:15.148 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP GROUP regress_test_g1; 2025-07-03 22:05:15.151 UTC client backend[16481] pg_regress/drop_if_exists ERROR: conversion "test_conversion_exists" does not exist 2025-07-03 22:05:15.151 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP CONVERSION test_conversion_exists; 2025-07-03 22:05:15.159 UTC client backend[16482] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2025-07-03 22:05:15.159 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: ALTER FUNCTION functest_E_2(int) LEAKPROOF; 2025-07-03 22:05:15.159 UTC client backend[16481] pg_regress/drop_if_exists ERROR: text search parser "test_tsparser_exists" does not exist 2025-07-03 22:05:15.159 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH PARSER test_tsparser_exists; 2025-07-03 22:05:15.159 UTC client backend[16482] pg_regress/create_function_sql ERROR: only superuser can define a leakproof function 2025-07-03 22:05:15.159 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_E_3(int) RETURNS bool LANGUAGE 'sql' LEAKPROOF AS 'SELECT $1 < 200'; 2025-07-03 22:05:15.162 UTC client backend[16481] pg_regress/drop_if_exists ERROR: text search dictionary "test_tsdict_exists" does not exist 2025-07-03 22:05:15.162 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH DICTIONARY test_tsdict_exists; 2025-07-03 22:05:15.169 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-07-03 22:05:15.169 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (1, x check failed, -2). 2025-07-03 22:05:15.169 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (1, 'x check failed', -2); 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (5, z check failed, 10). 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (5, 'z check failed', 10); 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (0, check failed, -2). 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (0, 'check failed', -2); 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "check2_tbl" violates check constraint "sequence_con" 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (6, check failed, 11). 2025-07-03 22:05:15.170 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO CHECK2_TBL VALUES (6, 'check failed', 11); 2025-07-03 22:05:15.172 UTC client backend[16481] pg_regress/drop_if_exists ERROR: text search template "test_tstemplate_exists" does not exist 2025-07-03 22:05:15.172 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH TEMPLATE test_tstemplate_exists; 2025-07-03 22:05:15.173 UTC client backend[16481] pg_regress/drop_if_exists ERROR: text search configuration "test_tsconfig_exists" does not exist 2025-07-03 22:05:15.173 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TEXT SEARCH CONFIGURATION test_tsconfig_exists; 2025-07-03 22:05:15.190 UTC client backend[16481] pg_regress/drop_if_exists ERROR: extension "test_extension_exists" does not exist 2025-07-03 22:05:15.190 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP EXTENSION test_extension_exists; 2025-07-03 22:05:15.192 UTC client backend[16481] pg_regress/drop_if_exists ERROR: function test_function_exists() does not exist 2025-07-03 22:05:15.192 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(); 2025-07-03 22:05:15.195 UTC client backend[16481] pg_regress/drop_if_exists ERROR: function test_function_exists(integer, text, integer[]) does not exist 2025-07-03 22:05:15.195 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_function_exists(int, text, int[]); 2025-07-03 22:05:15.197 UTC client backend[16481] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(*) does not exist 2025-07-03 22:05:15.197 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(*); 2025-07-03 22:05:15.204 UTC client backend[16481] pg_regress/drop_if_exists ERROR: aggregate test_aggregate_exists(integer) does not exist 2025-07-03 22:05:15.204 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP AGGREGATE test_aggregate_exists(int); 2025-07-03 22:05:15.211 UTC client backend[16481] pg_regress/drop_if_exists ERROR: operator does not exist: integer @#@ integer 2025-07-03 22:05:15.211 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR @#@ (int, int); 2025-07-03 22:05:15.213 UTC client backend[16485] pg_regress/create_am ERROR: cannot drop access method gist2 because other objects depend on it 2025-07-03 22:05:15.213 UTC client backend[16485] pg_regress/create_am DETAIL: index grect2ind2 depends on operator class box_ops for access method gist2 2025-07-03 22:05:15.213 UTC client backend[16485] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:15.213 UTC client backend[16485] pg_regress/create_am STATEMENT: DROP ACCESS METHOD gist2; 2025-07-03 22:05:15.215 UTC client backend[16481] pg_regress/drop_if_exists ERROR: language "test_language_exists" does not exist 2025-07-03 22:05:15.215 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP LANGUAGE test_language_exists; 2025-07-03 22:05:15.217 UTC client backend[16481] pg_regress/drop_if_exists ERROR: cast from type text to type text does not exist 2025-07-03 22:05:15.217 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP CAST (text AS text); 2025-07-03 22:05:15.218 UTC client backend[16481] pg_regress/drop_if_exists ERROR: trigger "test_trigger_exists" for table "test_exists" does not exist 2025-07-03 22:05:15.218 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON test_exists; 2025-07-03 22:05:15.219 UTC client backend[16481] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2025-07-03 22:05:15.219 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_table; 2025-07-03 22:05:15.221 UTC client backend[16481] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2025-07-03 22:05:15.221 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TRIGGER test_trigger_exists ON no_such_schema.no_such_table; 2025-07-03 22:05:15.225 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.225 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (2, -NULL-, -2). 2025-07-03 22:05:15.225 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (2, -2); 2025-07-03 22:05:15.233 UTC client backend[16481] pg_regress/drop_if_exists ERROR: rule "test_rule_exists" for relation "test_exists" does not exist 2025-07-03 22:05:15.233 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON test_exists; 2025-07-03 22:05:15.236 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.236 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (2, Y, -2). 2025-07-03 22:05:15.236 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2025-07-03 22:05:15.238 UTC client backend[16484] pg_regress/roleattributes LOG: disconnection: session time: 0:00:00.284 user=postgres database=regression host=[local] 2025-07-03 22:05:15.238 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2025-07-03 22:05:15.238 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (1, -NULL-, -2). 2025-07-03 22:05:15.238 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,z) VALUES (1, -2); 2025-07-03 22:05:15.239 UTC client backend[16481] pg_regress/drop_if_exists ERROR: relation "no_such_table" does not exist 2025-07-03 22:05:15.239 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_table; 2025-07-03 22:05:15.239 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.239 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2025-07-03 22:05:15.239 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL VALUES (5, 'check failed', -5); 2025-07-03 22:05:15.241 UTC client backend[16481] pg_regress/drop_if_exists ERROR: schema "no_such_schema" does not exist 2025-07-03 22:05:15.241 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP RULE test_rule_exists ON no_such_schema.no_such_table; 2025-07-03 22:05:15.248 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_check" 2025-07-03 22:05:15.248 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (5, check failed, 4). 2025-07-03 22:05:15.248 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) VALUES ('check failed', 4); 2025-07-03 22:05:15.249 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.249 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (5, check failed, -5). 2025-07-03 22:05:15.249 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(x,y) VALUES (5, 'check failed'); 2025-07-03 22:05:15.250 UTC client backend[16477] pg_regress/create_aggregate ERROR: must specify both or neither of serialization and deserialization functions 2025-07-03 22:05:15.250 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize ); 2025-07-03 22:05:15.254 UTC client backend[16481] pg_regress/drop_if_exists ERROR: foreign-data wrapper "test_fdw_exists" does not exist 2025-07-03 22:05:15.254 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP FOREIGN DATA WRAPPER test_fdw_exists; 2025-07-03 22:05:15.255 UTC client backend[16481] pg_regress/drop_if_exists ERROR: server "test_server_exists" does not exist 2025-07-03 22:05:15.255 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP SERVER test_server_exists; 2025-07-03 22:05:15.255 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.255 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (8, Y, -8). 2025-07-03 22:05:15.255 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y) VALUES ('Y'); 2025-07-03 22:05:15.255 UTC client backend[16477] pg_regress/create_aggregate ERROR: function numeric_avg_deserialize(internal) does not exist 2025-07-03 22:05:15.255 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_deserialize, deserialfunc = numeric_avg_deserialize ); 2025-07-03 22:05:15.257 UTC client backend[16477] pg_regress/create_aggregate ERROR: function numeric_avg_serialize(bytea, internal) does not exist 2025-07-03 22:05:15.257 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize, deserialfunc = numeric_avg_serialize ); 2025-07-03 22:05:15.259 UTC client backend[16481] pg_regress/drop_if_exists ERROR: operator class "test_operator_class" does not exist for access method "btree" 2025-07-03 22:05:15.259 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING btree; 2025-07-03 22:05:15.260 UTC client backend[16477] pg_regress/create_aggregate ERROR: function int4larger(internal, internal) does not exist 2025-07-03 22:05:15.260 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE myavg (numeric) ( stype = internal, sfunc = numeric_avg_accum, serialfunc = numeric_avg_serialize, deserialfunc = numeric_avg_deserialize, combinefunc = int4larger ); 2025-07-03 22:05:15.263 UTC client backend[16481] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-07-03 22:05:15.263 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS test_operator_class USING no_such_am; 2025-07-03 22:05:15.264 UTC client backend[16481] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-07-03 22:05:15.264 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR CLASS IF EXISTS test_operator_class USING no_such_am; 2025-07-03 22:05:15.264 UTC client backend[16482] pg_regress/create_function_sql ERROR: duplicate function body specified 2025-07-03 22:05:15.264 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xxx(x int) RETURNS int LANGUAGE SQL AS $$ SELECT x * 2 $$ RETURN x * 3; 2025-07-03 22:05:15.265 UTC client backend[16481] pg_regress/drop_if_exists ERROR: operator family "test_operator_family" does not exist for access method "btree" 2025-07-03 22:05:15.265 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING btree; 2025-07-03 22:05:15.265 UTC client backend[16482] pg_regress/create_function_sql ERROR: SQL function with unquoted function body cannot have polymorphic arguments 2025-07-03 22:05:15.265 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x anyarray) RETURNS anyelement LANGUAGE SQL RETURN x[1]; 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY test_operator_family USING no_such_am; 2025-07-03 22:05:15.267 UTC client backend[16482] pg_regress/create_function_sql ERROR: operator does not exist: date > integer at character 85 2025-07-03 22:05:15.267 UTC client backend[16482] pg_regress/create_function_sql HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:15.267 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION functest_S_xx(x date) RETURNS boolean LANGUAGE SQL RETURN x > 1; 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "" 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am DETAIL: "default_table_access_method" cannot be empty. 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am STATEMENT: SET default_table_access_method = ''; 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP OPERATOR FAMILY IF EXISTS test_operator_family USING no_such_am; 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am ERROR: invalid value for parameter "default_table_access_method": "I do not exist AM" 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am DETAIL: Table access method "I do not exist AM" does not exist. 2025-07-03 22:05:15.267 UTC client backend[16485] pg_regress/create_am STATEMENT: SET default_table_access_method = 'I do not exist AM'; 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists ERROR: access method "no_such_am" does not exist 2025-07-03 22:05:15.267 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP ACCESS METHOD no_such_am; 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am STATEMENT: SET default_table_access_method = 'btree'; 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am ERROR: function int4in(internal) does not exist 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER int4in; 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am ERROR: function bthandler must return type table_am_handler 2025-07-03 22:05:15.268 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE ACCESS METHOD bogus TYPE TABLE HANDLER bthandler; 2025-07-03 22:05:15.273 UTC client backend[16476] pg_regress/hash_func ERROR: could not identify a hash function for type bit varying 2025-07-03 22:05:15.273 UTC client backend[16476] pg_regress/hash_func STATEMENT: SELECT v as value, hash_record(v)::bit(32) as standard FROM (VALUES (row('10'::varbit, 'aaa')::hash_test_t2)) x(v); 2025-07-03 22:05:15.274 UTC client backend[16476] pg_regress/hash_func ERROR: could not identify an extended hash function for type bit varying 2025-07-03 22:05:15.274 UTC client backend[16476] pg_regress/hash_func STATEMENT: SELECT v as value, hash_record_extended(v, 0)::bit(32) as extended0 FROM (VALUES (row('11'::varbit, 'aaa')::hash_test_t2)) x(v); 2025-07-03 22:05:15.284 UTC client backend[16481] pg_regress/drop_if_exists ERROR: table "test_exists" does not exist 2025-07-03 22:05:15.284 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP TABLE test_exists; 2025-07-03 22:05:15.289 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "sys_col_check_tbl" violates check constraint "sys_col_check_tbl_check" 2025-07-03 22:05:15.289 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (Olympia, Washington, t, 100). 2025-07-03 22:05:15.289 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO SYS_COL_CHECK_TBL VALUES ('Olympia', 'Washington', true, 100); 2025-07-03 22:05:15.291 UTC client backend[16476] pg_regress/hash_func LOG: disconnection: session time: 0:00:00.368 user=postgres database=regression host=[local] 2025-07-03 22:05:15.300 UTC client backend[16478] pg_regress/typed_table ERROR: cannot add column to typed table 2025-07-03 22:05:15.300 UTC client backend[16478] pg_regress/typed_table STATEMENT: ALTER TABLE persons ADD COLUMN comment text; 2025-07-03 22:05:15.300 UTC client backend[16478] pg_regress/typed_table ERROR: cannot drop column from typed table 2025-07-03 22:05:15.300 UTC client backend[16478] pg_regress/typed_table STATEMENT: ALTER TABLE persons DROP COLUMN name; 2025-07-03 22:05:15.303 UTC client backend[16478] pg_regress/typed_table ERROR: cannot rename column of typed table 2025-07-03 22:05:15.303 UTC client backend[16478] pg_regress/typed_table STATEMENT: ALTER TABLE persons RENAME COLUMN id TO num; 2025-07-03 22:05:15.303 UTC client backend[16478] pg_regress/typed_table ERROR: cannot alter column type of typed table at character 34 2025-07-03 22:05:15.303 UTC client backend[16478] pg_regress/typed_table STATEMENT: ALTER TABLE persons ALTER COLUMN name TYPE varchar; 2025-07-03 22:05:15.312 UTC client backend[16478] pg_regress/typed_table ERROR: cannot change inheritance of typed table 2025-07-03 22:05:15.312 UTC client backend[16478] pg_regress/typed_table STATEMENT: ALTER TABLE persons INHERIT stuff; 2025-07-03 22:05:15.312 UTC client backend[16478] pg_regress/typed_table ERROR: column "myname" does not exist 2025-07-03 22:05:15.312 UTC client backend[16478] pg_regress/typed_table STATEMENT: CREATE TABLE personsx OF person_type (myname WITH OPTIONS NOT NULL); 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION test_ambiguous_funcname; 2025-07-03 22:05:15.321 UTC client backend[16477] pg_regress/create_aggregate ERROR: cannot change return type of existing function 2025-07-03 22:05:15.321 UTC client backend[16477] pg_regress/create_aggregate HINT: Use DROP AGGREGATE myavg(numeric) first. 2025-07-03 22:05:15.321 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (numeric) ( stype = numeric, sfunc = numeric_add, finalfunc = numeric_out ); 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists ERROR: function name "test_ambiguous_funcname" is not unique 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists HINT: Specify the argument list to select the function unambiguously. 2025-07-03 22:05:15.321 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP FUNCTION IF EXISTS test_ambiguous_funcname; 2025-07-03 22:05:15.322 UTC client backend[16477] pg_regress/create_aggregate ERROR: cannot change routine kind 2025-07-03 22:05:15.322 UTC client backend[16477] pg_regress/create_aggregate DETAIL: "myavg" is an ordinary aggregate function. 2025-07-03 22:05:15.322 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE myavg (order by numeric) ( stype = numeric, sfunc = numeric_add ); 2025-07-03 22:05:15.324 UTC client backend[16473] pg_regress/constraints ERROR: system column "ctid" reference in check constraint is invalid at character 138 2025-07-03 22:05:15.324 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE SYS_COL_CHECK_TBL (city text, state text, is_capital bool, altitude int, CHECK (NOT (is_capital AND ctid::text = 'sys_col_check_tbl'))); 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am ERROR: syntax error at or near "USING" at character 41 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am STATEMENT: SELECT INTO tableam_tblselectinto_heap2 USING heap2 FROM tableam_tbl_heap2; 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am ERROR: syntax error at or near "USING" at character 32 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE VIEW tableam_view_heap2 USING heap2 AS SELECT * FROM tableam_tbl_heap2; 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am ERROR: syntax error at or near "USING" at character 35 2025-07-03 22:05:15.324 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE SEQUENCE tableam_seq_heap2 USING heap2; 2025-07-03 22:05:15.330 UTC client backend[16477] pg_regress/create_aggregate ERROR: cannot change routine kind 2025-07-03 22:05:15.330 UTC client backend[16477] pg_regress/create_aggregate DETAIL: "sum3" is a function. 2025-07-03 22:05:15.330 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE OR REPLACE AGGREGATE sum3 (int8,int8,int8) ( stype = int8, sfunc = sum4 ); 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE test_ambiguous_procname; 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists ERROR: procedure name "test_ambiguous_procname" is not unique 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists HINT: Specify the argument list to select the procedure unambiguously. 2025-07-03 22:05:15.334 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP PROCEDURE IF EXISTS test_ambiguous_procname; 2025-07-03 22:05:15.335 UTC client backend[16481] pg_regress/drop_if_exists ERROR: routine name "test_ambiguous_procname" is not unique 2025-07-03 22:05:15.335 UTC client backend[16481] pg_regress/drop_if_exists HINT: Specify the argument list to select the routine unambiguously. 2025-07-03 22:05:15.335 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: DROP ROUTINE IF EXISTS test_ambiguous_procname; 2025-07-03 22:05:15.335 UTC client backend[16474] pg_regress/triggers ERROR: trigger "no_such_trigger" for table "main_table" does not exist 2025-07-03 22:05:15.335 UTC client backend[16474] pg_regress/triggers STATEMENT: COMMENT ON TRIGGER no_such_trigger ON main_table IS 'wrong'; 2025-07-03 22:05:15.336 UTC client backend[16477] pg_regress/create_aggregate ERROR: parameter "parallel" must be SAFE, RESTRICTED, or UNSAFE 2025-07-03 22:05:15.336 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE mysum (int) ( stype = int, sfunc = int4pl, parallel = pear ); 2025-07-03 22:05:15.338 UTC client backend[16477] pg_regress/create_aggregate ERROR: strictness of aggregate's forward and inverse transition functions must match 2025-07-03 22:05:15.338 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE invalidsumdouble (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_n ); 2025-07-03 22:05:15.339 UTC client backend[16477] pg_regress/create_aggregate ERROR: return type of inverse transition function float8mi_int is not double precision 2025-07-03 22:05:15.339 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE wrongreturntype (float8) ( stype = float8, sfunc = float8pl, mstype = float8, msfunc = float8pl, minvfunc = float8mi_int ); 2025-07-03 22:05:15.339 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc1" not recognized 2025-07-03 22:05:15.339 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Basetype" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Stype1" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Initcond1" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE case_agg ( -- old syntax "Sfunc1" = int4pl, "Basetype" = int4, "Stype1" = int4, "Initcond1" = '0', "Parallel" = safe ); 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Stype" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Sfunc" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_extra" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Finalfunc_modify" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate WARNING: aggregate attribute "Parallel" not recognized 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate ERROR: aggregate stype must be specified 2025-07-03 22:05:15.340 UTC client backend[16477] pg_regress/create_aggregate STATEMENT: CREATE AGGREGATE case_agg(float8) ( "Stype" = internal, "Sfunc" = ordered_set_transition, "Finalfunc" = percentile_disc_final, "Finalfunc_extra" = true, "Finalfunc_modify" = read_write, "Parallel" = safe ); 2025-07-03 22:05:15.344 UTC client backend[16477] pg_regress/create_aggregate LOG: disconnection: session time: 0:00:00.414 user=postgres database=regression host=[local] 2025-07-03 22:05:15.345 UTC client backend[16481] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2025-07-03 22:05:15.345 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists (force); 2025-07-03 22:05:15.345 UTC client backend[16481] pg_regress/drop_if_exists ERROR: database "test_database_exists" does not exist 2025-07-03 22:05:15.345 UTC client backend[16481] pg_regress/drop_if_exists STATEMENT: drop database test_database_exists with (force); 2025-07-03 22:05:15.354 UTC client backend[16481] pg_regress/drop_if_exists LOG: disconnection: session time: 0:00:00.428 user=postgres database=regression host=[local] 2025-07-03 22:05:15.364 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_child_check" 2025-07-03 22:05:15.364 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (7, -NULL-, -7, 42, 6). 2025-07-03 22:05:15.364 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6); 2025-07-03 22:05:15.365 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_check" 2025-07-03 22:05:15.365 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (6, -NULL-, -7, 42, 7). 2025-07-03 22:05:15.365 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7); 2025-07-03 22:05:15.368 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_child" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.368 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (6, check failed, -6, 42, 7). 2025-07-03 22:05:15.368 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7); 2025-07-03 22:05:15.393 UTC client backend[16479] pg_regress/inherit ERROR: null value in column "aa" of relation "z" violates not-null constraint 2025-07-03 22:05:15.393 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (null, text). 2025-07-03 22:05:15.393 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO z VALUES (NULL, 'text'); 2025-07-03 22:05:15.435 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2025-07-03 22:05:15.435 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (-3). 2025-07-03 22:05:15.435 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2025-07-03 22:05:15.480 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "atacc2" violates check constraint "atacc1_test_check" 2025-07-03 22:05:15.480 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2025-07-03 22:05:15.480 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO ATACC2 (TEST) VALUES (-3); 2025-07-03 22:05:15.484 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test_check" 2025-07-03 22:05:15.484 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (-3, null). 2025-07-03 22:05:15.484 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST) VALUES (-3); 2025-07-03 22:05:15.487 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "atacc1" violates check constraint "atacc1_test2_check" 2025-07-03 22:05:15.487 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (null, 3). 2025-07-03 22:05:15.487 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO ATACC1 (TEST2) VALUES (3); 2025-07-03 22:05:15.515 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view1" 2025-07-03 22:05:15.515 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2025-07-03 22:05:15.515 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.515 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view1; 2025-07-03 22:05:15.516 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view2" 2025-07-03 22:05:15.516 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing GROUP BY are not automatically updatable. 2025-07-03 22:05:15.516 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.516 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view2; 2025-07-03 22:05:15.522 UTC client backend[16483] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2025-07-03 22:05:15.522 UTC client backend[16483] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2025-07-03 22:05:15.522 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE vaccluster; 2025-07-03 22:05:15.524 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view3" 2025-07-03 22:05:15.524 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing HAVING are not automatically updatable. 2025-07-03 22:05:15.524 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.524 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view3; 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view4" 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that return aggregate functions are not automatically updatable. 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view4; 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view5" 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that return window functions are not automatically updatable. 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.525 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view5; 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view6" 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable. 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view6; 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view7" 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing WITH are not automatically updatable. 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.526 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view7 SET a=a+1; 2025-07-03 22:05:15.527 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view8" 2025-07-03 22:05:15.527 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-07-03 22:05:15.527 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.527 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view8 SET a=a+1; 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view9" 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view9 SET a=a+1; 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view10" 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view10 SET a=a+1; 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view11" 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.528 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view11 SET a=a+1; 2025-07-03 22:05:15.529 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view12" 2025-07-03 22:05:15.529 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.529 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.529 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view12 SET a=a+1; 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views HINT: To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view13 VALUES (3, 'Row 3'); 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view13" 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO ro_view13 AS t USING (VALUES (1, 'Row 1')) AS v(a,b) ON t.a = v.a WHEN MATCHED THEN DELETE; 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view13" 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view using MERGE, provide an INSTEAD OF UPDATE trigger. 2025-07-03 22:05:15.530 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO ro_view13 AS t USING (VALUES (2, 'Row 2')) AS v(a,b) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = v.b; 2025-07-03 22:05:15.531 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into view "ro_view13" 2025-07-03 22:05:15.531 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.531 UTC client backend[16491] pg_regress/updatable_views HINT: To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger. 2025-07-03 22:05:15.531 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO ro_view13 AS t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b); 2025-07-03 22:05:15.537 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "ctid" of view "rw_view14" 2025-07-03 22:05:15.537 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-07-03 22:05:15.537 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view14 VALUES (null, 3, 'Row 3'); 2025-07-03 22:05:15.539 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "ctid" of view "rw_view14" 2025-07-03 22:05:15.539 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-07-03 22:05:15.539 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view14 SET ctid=null WHERE a=3; 2025-07-03 22:05:15.543 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.543 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (8, try again, -8). 2025-07-03 22:05:15.543 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO INSERT_TBL(y,z) SELECT yd, -8 FROM tmp WHERE yd = 'try again'; 2025-07-03 22:05:15.546 UTC client backend[16489] pg_regress/select LOG: disconnection: session time: 0:00:00.573 user=postgres database=regression host=[local] 2025-07-03 22:05:15.554 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot merge into column "ctid" of view "rw_view14" 2025-07-03 22:05:15.554 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-07-03 22:05:15.554 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view14 AS t USING (VALUES (2, 'Merged row 2'), (3, 'Merged row 3')) AS v(a,b) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = v.b -- should be OK, except... WHEN NOT MATCHED THEN INSERT VALUES (null, v.a, v.b); 2025-07-03 22:05:15.569 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "insert_tbl" violates check constraint "insert_tbl_con" 2025-07-03 22:05:15.569 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (-4, Y, 4). 2025-07-03 22:05:15.569 UTC client backend[16473] pg_regress/constraints STATEMENT: UPDATE INSERT_TBL SET x = z, z = x; 2025-07-03 22:05:15.574 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-07-03 22:05:15.574 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:15.574 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 VALUES (3, 'ROW 3'); 2025-07-03 22:05:15.580 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-07-03 22:05:15.580 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:15.580 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (3) ON CONFLICT (a) DO UPDATE set upper = 'blarg'; 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "upper" of view "rw_view15" 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view15 (a) VALUES (4); 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper='ROW 3' WHERE a=3; 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "upper" of view "rw_view15" 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:15.586 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view15 SET upper=DEFAULT WHERE a=3; 2025-07-03 22:05:15.593 UTC client backend[16491] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2025-07-03 22:05:15.593 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 VALUES (3, 'Row 3', 3); 2025-07-03 22:05:15.594 UTC client backend[16491] pg_regress/updatable_views ERROR: multiple assignments to same column "a" 2025-07-03 22:05:15.594 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET a=3, aa=-3 WHERE a=3; 2025-07-03 22:05:15.598 UTC client backend[16473] pg_regress/constraints ERROR: new row for relation "copy_tbl" violates check constraint "copy_con" 2025-07-03 22:05:15.598 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (7, check failed, 6). 2025-07-03 22:05:15.598 UTC client backend[16473] pg_regress/constraints CONTEXT: COPY copy_tbl, line 2: "7 check failed 6" 2025-07-03 22:05:15.598 UTC client backend[16473] pg_regress/constraints STATEMENT: COPY COPY_TBL FROM '/tmp/cirrus-ci-build/src/test/regress/data/constrf.data'; 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into view "ro_view1" 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing DISTINCT are not automatically updatable. 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views HINT: To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule. 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO ro_view17 VALUES (3, 'ROW 3'); 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "ro_view18" 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.601 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM ro_view18; 2025-07-03 22:05:15.603 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view19" 2025-07-03 22:05:15.603 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that do not select from a single table or view are not automatically updatable. 2025-07-03 22:05:15.603 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.603 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view19 SET last_value=1000; 2025-07-03 22:05:15.604 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "ro_view20" 2025-07-03 22:05:15.604 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views that return set-returning functions are not automatically updatable. 2025-07-03 22:05:15.604 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.604 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE ro_view20 SET b=upper(b); 2025-07-03 22:05:15.611 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into view "rw_view16" 2025-07-03 22:05:15.611 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-07-03 22:05:15.611 UTC client backend[16491] pg_regress/updatable_views HINT: To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule. 2025-07-03 22:05:15.611 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view16 (a, b) VALUES (3, 'Row 3'); 2025-07-03 22:05:15.612 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update view "rw_view16" 2025-07-03 22:05:15.612 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-07-03 22:05:15.612 UTC client backend[16491] pg_regress/updatable_views HINT: To enable updating the view, provide an INSTEAD OF UPDATE trigger or an unconditional ON UPDATE DO INSTEAD rule. 2025-07-03 22:05:15.612 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view16 SET b='ROW 2' WHERE a=2; 2025-07-03 22:05:15.613 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "rw_view16" 2025-07-03 22:05:15.613 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views with conditional DO INSTEAD rules are not automatically updatable. 2025-07-03 22:05:15.613 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view, provide an INSTEAD OF DELETE trigger or an unconditional ON DELETE DO INSTEAD rule. 2025-07-03 22:05:15.613 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view16 WHERE a=2; 2025-07-03 22:05:15.614 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view16" 2025-07-03 22:05:15.614 UTC client backend[16491] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2025-07-03 22:05:15.614 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view16 AS t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b); 2025-07-03 22:05:15.638 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "primary_tbl_pkey" 2025-07-03 22:05:15.638 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:15.638 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL VALUES (1, 'three'); 2025-07-03 22:05:15.639 UTC client backend[16473] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2025-07-03 22:05:15.639 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (null, six). 2025-07-03 22:05:15.639 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2025-07-03 22:05:15.734 UTC client backend[16474] pg_regress/triggers ERROR: duplicate trigger events specified at or near "ON" at character 63 2025-07-03 22:05:15.734 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_upd_and_col BEFORE UPDATE OR UPDATE OF a ON main_table FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_upd_and_col'); 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers ERROR: column "a" specified more than once 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_upd_a_a BEFORE UPDATE OF a, a ON main_table FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_upd_a_a'); 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers ERROR: syntax error at or near "OF" at character 42 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_ins_a BEFORE INSERT OF a ON main_table FOR EACH ROW EXECUTE PROCEDURE trigger_func('error_ins_a'); 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers ERROR: INSERT trigger's WHEN condition cannot reference OLD values at character 88 2025-07-03 22:05:15.735 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_ins_when BEFORE INSERT OR UPDATE ON main_table FOR EACH ROW WHEN (OLD.a <> NEW.a) EXECUTE PROCEDURE trigger_func('error_ins_old'); 2025-07-03 22:05:15.735 UTC client backend[16478] pg_regress/typed_table ERROR: column "name" specified more than once 2025-07-03 22:05:15.735 UTC client backend[16478] pg_regress/typed_table STATEMENT: CREATE TABLE persons4 OF person_type ( name WITH OPTIONS NOT NULL, name WITH OPTIONS DEFAULT '' -- error, specified more than once ); 2025-07-03 22:05:15.739 UTC client backend[16474] pg_regress/triggers ERROR: DELETE trigger's WHEN condition cannot reference NEW values at character 97 2025-07-03 22:05:15.739 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_del_when BEFORE DELETE OR UPDATE ON main_table FOR EACH ROW WHEN (OLD.a <> NEW.a) EXECUTE PROCEDURE trigger_func('error_del_new'); 2025-07-03 22:05:15.739 UTC client backend[16474] pg_regress/triggers ERROR: BEFORE trigger's WHEN condition cannot reference NEW system columns at character 88 2025-07-03 22:05:15.739 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_del_when BEFORE INSERT OR UPDATE ON main_table FOR EACH ROW WHEN (NEW.tableoid <> 0) EXECUTE PROCEDURE trigger_func('error_when_sys_column'); 2025-07-03 22:05:15.741 UTC client backend[16478] pg_regress/typed_table ERROR: cannot drop type person_type because other objects depend on it 2025-07-03 22:05:15.741 UTC client backend[16478] pg_regress/typed_table DETAIL: table persons depends on type person_type function get_all_persons() depends on type person_type table persons2 depends on type person_type table persons3 depends on type person_type 2025-07-03 22:05:15.741 UTC client backend[16478] pg_regress/typed_table HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:15.741 UTC client backend[16478] pg_regress/typed_table STATEMENT: DROP TYPE person_type RESTRICT; 2025-07-03 22:05:15.744 UTC client backend[16474] pg_regress/triggers ERROR: statement trigger's WHEN condition cannot reference column values at character 90 2025-07-03 22:05:15.744 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER error_stmt_when BEFORE UPDATE OF a ON main_table FOR EACH STATEMENT WHEN (OLD.* IS DISTINCT FROM NEW.*) EXECUTE PROCEDURE trigger_func('error_stmt_when'); 2025-07-03 22:05:15.745 UTC client backend[16474] pg_regress/triggers ERROR: cannot drop column b of table main_table because other objects depend on it 2025-07-03 22:05:15.745 UTC client backend[16474] pg_regress/triggers DETAIL: trigger after_upd_b_row_trig on table main_table depends on column b of table main_table trigger after_upd_a_b_row_trig on table main_table depends on column b of table main_table trigger after_upd_b_stmt_trig on table main_table depends on column b of table main_table 2025-07-03 22:05:15.745 UTC client backend[16474] pg_regress/triggers HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:15.745 UTC client backend[16474] pg_regress/triggers STATEMENT: ALTER TABLE main_table DROP COLUMN b; 2025-07-03 22:05:15.758 UTC client backend[16473] pg_regress/constraints ERROR: null value in column "i" of relation "primary_tbl" violates not-null constraint 2025-07-03 22:05:15.758 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (null, six). 2025-07-03 22:05:15.758 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO PRIMARY_TBL (t) VALUES ('six'); 2025-07-03 22:05:15.768 UTC client backend[16482] pg_regress/create_function_sql ERROR: could not find a function named "functest_b_1" 2025-07-03 22:05:15.768 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_1; 2025-07-03 22:05:15.769 UTC client backend[16482] pg_regress/create_function_sql ERROR: function name "functest_b_2" is not unique 2025-07-03 22:05:15.769 UTC client backend[16482] pg_regress/create_function_sql HINT: Specify the argument list to select the function unambiguously. 2025-07-03 22:05:15.769 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: DROP FUNCTION functest_b_2; 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql ERROR: cannot change routine kind 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE FUNCTION functest1(a int) RETURNS int LANGUAGE SQL WINDOW AS 'SELECT $1'; 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql ERROR: cannot change routine kind 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql DETAIL: "functest1" is a function. 2025-07-03 22:05:15.775 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE OR REPLACE PROCEDURE functest1(a int) LANGUAGE SQL AS 'SELECT $1'; 2025-07-03 22:05:15.800 UTC client backend[16478] pg_regress/typed_table ERROR: type stuff is the row type of another table 2025-07-03 22:05:15.800 UTC client backend[16478] pg_regress/typed_table DETAIL: A typed table must use a stand-alone composite type created with CREATE TYPE. 2025-07-03 22:05:15.800 UTC client backend[16478] pg_regress/typed_table STATEMENT: CREATE TABLE persons5 OF stuff; 2025-07-03 22:05:15.807 UTC client backend[16483] pg_regress/vacuum ERROR: ANALYZE cannot be executed from VACUUM or ANALYZE 2025-07-03 22:05:15.807 UTC client backend[16483] pg_regress/vacuum CONTEXT: SQL function "do_analyze" statement 1 SQL function "wrap_do_analyze" statement 1 2025-07-03 22:05:15.807 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM FULL vaccluster; 2025-07-03 22:05:15.809 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:15.809 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:15.809 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2025-07-03 22:05:15.809 UTC client backend[16478] pg_regress/typed_table ERROR: type tt_enum_type is not a composite type 2025-07-03 22:05:15.809 UTC client backend[16478] pg_regress/typed_table STATEMENT: CREATE TABLE of_tt_enum_type OF tt_enum_type; 2025-07-03 22:05:15.816 UTC client backend[16485] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-07-03 22:05:15.816 UTC client backend[16485] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2025-07-03 22:05:15.817 UTC client backend[16485] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-07-03 22:05:15.817 UTC client backend[16485] pg_regress/create_am STATEMENT: ALTER TABLE heaptable SET ACCESS METHOD DEFAULT, SET ACCESS METHOD heap2; 2025-07-03 22:05:15.817 UTC client backend[16473] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time 2025-07-03 22:05:15.817 UTC client backend[16473] pg_regress/constraints HINT: Ensure that no rows proposed for insertion within the same command have duplicate constrained values. 2025-07-03 22:05:15.817 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'a'), (2, 'b'), (2, 'b') ON CONFLICT (i) DO UPDATE SET t = 'fails'; 2025-07-03 22:05:15.817 UTC client backend[16485] pg_regress/create_am ERROR: cannot have multiple SET ACCESS METHOD subcommands 2025-07-03 22:05:15.817 UTC client backend[16485] pg_regress/create_am STATEMENT: ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap, SET ACCESS METHOD heap2; 2025-07-03 22:05:15.864 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:15.864 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:15.864 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'three'); 2025-07-03 22:05:15.867 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:15.867 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(null) already exists. 2025-07-03 22:05:15.867 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL (t) VALUES ('seven'); 2025-07-03 22:05:15.930 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_t_key" 2025-07-03 22:05:15.930 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i, t)=(1, one) already exists. 2025-07-03 22:05:15.930 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO UNIQUE_TBL VALUES (1, 'one'); 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql DETAIL: Actual return type is text. 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT ''not an integer'';'; 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql ERROR: syntax error at or near "not" at character 62 2025-07-03 22:05:15.944 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'not even SQL'; 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql DETAIL: Final statement must return exactly one column. 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT 1, 2, 3;'; 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql ERROR: there is no parameter $2 at character 69 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'SELECT $2;'; 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql ERROR: only one AS item needed for language "sql" 2025-07-03 22:05:15.945 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS 'a', 'b'; 2025-07-03 22:05:15.946 UTC client backend[16482] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer 2025-07-03 22:05:15.946 UTC client backend[16482] pg_regress/create_function_sql DETAIL: Function's final statement must be SELECT or INSERT/UPDATE/DELETE/MERGE RETURNING. 2025-07-03 22:05:15.946 UTC client backend[16482] pg_regress/create_function_sql CONTEXT: SQL function "test1" 2025-07-03 22:05:15.946 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL AS ''; 2025-07-03 22:05:15.947 UTC client backend[16482] pg_regress/create_function_sql ERROR: return type mismatch in function declared to return integer[] 2025-07-03 22:05:15.947 UTC client backend[16482] pg_regress/create_function_sql DETAIL: Function's final statement must be SELECT or INSERT/UPDATE/DELETE/MERGE RETURNING. 2025-07-03 22:05:15.947 UTC client backend[16482] pg_regress/create_function_sql CONTEXT: SQL function "test1" during startup 2025-07-03 22:05:15.947 UTC client backend[16482] pg_regress/create_function_sql STATEMENT: SELECT test1(0); 2025-07-03 22:05:15.985 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:15.985 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:15.985 UTC client backend[16473] pg_regress/constraints STATEMENT: UPDATE unique_tbl SET i = 1 WHERE i = 0; 2025-07-03 22:05:15.986 UTC client backend[16479] pg_regress/inherit ERROR: column "tomorrow" inherits conflicting default values 2025-07-03 22:05:15.986 UTC client backend[16479] pg_regress/inherit HINT: To resolve the conflict, specify a default explicitly. 2025-07-03 22:05:15.986 UTC client backend[16479] pg_regress/inherit STATEMENT: CREATE TABLE otherchild () INHERITS (firstparent, thirdparent); 2025-07-03 22:05:16.018 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:16.018 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-07-03 22:05:16.018 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMIT; 2025-07-03 22:05:16.022 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:16.022 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-07-03 22:05:16.022 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO unique_tbl VALUES (3, 'Three'); 2025-07-03 22:05:16.025 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:16.025 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-07-03 22:05:16.025 UTC client backend[16473] pg_regress/constraints STATEMENT: SET CONSTRAINTS ALL IMMEDIATE; 2025-07-03 22:05:16.025 UTC client backend[16482] pg_regress/create_function_sql LOG: disconnection: session time: 0:00:01.094 user=postgres database=regression host=[local] 2025-07-03 22:05:16.124 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2025-07-03 22:05:16.124 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:16.124 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO parted_uniq_tbl VALUES (1); 2025-07-03 22:05:16.131 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key" 2025-07-03 22:05:16.131 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(1) already exists. 2025-07-03 22:05:16.131 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMIT; 2025-07-03 22:05:16.164 UTC client backend[16478] pg_regress/typed_table LOG: disconnection: session time: 0:00:01.235 user=postgres database=regression host=[local] 2025-07-03 22:05:16.174 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.174 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.174 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.175 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2025-07-03 22:05:16.177 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.177 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.177 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER INSERT ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row'); 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER UPDATE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row'); 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have row-level BEFORE or AFTER triggers. 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER DELETE ON main_view FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row'); 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2025-07-03 22:05:16.178 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig BEFORE TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2025-07-03 22:05:16.183 UTC client backend[16474] pg_regress/triggers ERROR: "main_view" is a view 2025-07-03 22:05:16.183 UTC client backend[16474] pg_regress/triggers DETAIL: Views cannot have TRUNCATE triggers. 2025-07-03 22:05:16.183 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig AFTER TRUNCATE ON main_view EXECUTE PROCEDURE trigger_func('before_tru_row'); 2025-07-03 22:05:16.184 UTC client backend[16474] pg_regress/triggers ERROR: "main_table" is a table 2025-07-03 22:05:16.184 UTC client backend[16474] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-07-03 22:05:16.184 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF INSERT ON main_table FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_ins'); 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers ERROR: "main_table" is a table 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_table FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers ERROR: "main_table" is a table 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF DELETE ON main_table FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_del'); 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have WHEN conditions 2025-07-03 22:05:16.185 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view FOR EACH ROW WHEN (OLD.a <> NEW.a) EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2025-07-03 22:05:16.186 UTC client backend[16474] pg_regress/triggers ERROR: INSTEAD OF triggers cannot have column lists 2025-07-03 22:05:16.186 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE OF a ON main_view FOR EACH ROW EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2025-07-03 22:05:16.187 UTC client backend[16474] pg_regress/triggers ERROR: INSTEAD OF triggers must be FOR EACH ROW 2025-07-03 22:05:16.187 UTC client backend[16474] pg_regress/triggers STATEMENT: CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view EXECUTE PROCEDURE view_trigger('instead_of_upd'); 2025-07-03 22:05:16.194 UTC client backend[16485] pg_regress/create_am ERROR: zero-length delimited identifier at or near """" at character 37 2025-07-03 22:05:16.194 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING ""; 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am ERROR: access method "i_do_not_exist_am" does not exist 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING i_do_not_exist_am; 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am ERROR: access method "I do not exist AM" does not exist 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "I do not exist AM"; 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am ERROR: access method "btree" is not of type TABLE 2025-07-03 22:05:16.195 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE TABLE i_am_a_failure() USING "btree"; 2025-07-03 22:05:16.203 UTC client backend[16485] pg_regress/create_am ERROR: "tableam_parted_a_heap2" is not partitioned 2025-07-03 22:05:16.203 UTC client backend[16485] pg_regress/create_am STATEMENT: CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x; 2025-07-03 22:05:16.208 UTC client backend[16485] pg_regress/create_am ERROR: cannot drop access method heap2 because other objects depend on it 2025-07-03 22:05:16.208 UTC client backend[16485] pg_regress/create_am DETAIL: table tableam_tbl_heap2 depends on access method heap2 table tableam_tblas_heap2 depends on access method heap2 materialized view tableam_tblmv_heap2 depends on access method heap2 table tableam_parted_b_heap2 depends on access method heap2 table tableam_parted_d_heap2 depends on access method heap2 2025-07-03 22:05:16.208 UTC client backend[16485] pg_regress/create_am HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:16.208 UTC client backend[16485] pg_regress/create_am STATEMENT: DROP ACCESS METHOD heap2; 2025-07-03 22:05:16.217 UTC client backend[16485] pg_regress/create_am LOG: disconnection: session time: 0:00:01.260 user=postgres database=regression host=[local] 2025-07-03 22:05:16.304 UTC client backend[16479] pg_regress/inherit ERROR: cannot alter inherited column "f1" of relation "childtab" 2025-07-03 22:05:16.304 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table parent1 alter column f1 type bigint; 2025-07-03 22:05:16.488 UTC client backend[16479] pg_regress/inherit ERROR: constraint "p2chk" conflicts with inherited constraint on relation "c2" 2025-07-03 22:05:16.488 UTC client backend[16479] pg_regress/inherit STATEMENT: create table c2 (constraint p2chk check (ff1 > 10) no inherit) inherits (p1); 2025-07-03 22:05:16.525 UTC client backend[16473] pg_regress/constraints ERROR: duplicate key value violates unique constraint "unique_tbl_i_key" 2025-07-03 22:05:16.525 UTC client backend[16473] pg_regress/constraints DETAIL: Key (i)=(3) already exists. 2025-07-03 22:05:16.525 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMIT; 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints ERROR: misplaced ENFORCED clause at character 41 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE UNIQUE_EN_TBL(i int UNIQUE ENFORCED); 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints ERROR: misplaced NOT ENFORCED clause at character 44 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE UNIQUE_NOTEN_TBL(i int UNIQUE NOT ENFORCED); 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints ERROR: cannot alter enforceability of constraint "unique_tbl_i_key" of relation "unique_tbl" 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key ENFORCED; 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints ERROR: cannot alter enforceability of constraint "unique_tbl_i_key" of relation "unique_tbl" 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key NOT ENFORCED; 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints ERROR: constraints cannot be altered to be NOT VALID at character 58 2025-07-03 22:05:16.536 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key NOT VALID; 2025-07-03 22:05:16.575 UTC client backend[16473] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "circles_c1_c2_excl" 2025-07-03 22:05:16.575 UTC client backend[16473] pg_regress/constraints DETAIL: Key (c1, (c2::circle))=(<(20,20),10>, <(0,0),4>) conflicts with existing key (c1, (c2::circle))=(<(10,10),10>, <(0,0),5>). 2025-07-03 22:05:16.575 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>'); 2025-07-03 22:05:16.579 UTC client backend[16473] pg_regress/constraints ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:05:16.579 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>') ON CONFLICT ON CONSTRAINT circles_c1_c2_excl DO UPDATE SET c2 = EXCLUDED.c2; 2025-07-03 22:05:16.582 UTC client backend[16473] pg_regress/constraints ERROR: could not create exclusion constraint "circles_c1_c2_excl1" 2025-07-03 22:05:16.582 UTC client backend[16473] pg_regress/constraints DETAIL: Key (c1, (c2::circle))=(<(0,0),5>, <(0,0),5>) conflicts with key (c1, (c2::circle))=(<(0,0),5>, <(0,0),4>). 2025-07-03 22:05:16.582 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE circles ADD EXCLUDE USING gist (c1 WITH &&, (c2::circle) WITH &&); 2025-07-03 22:05:16.614 UTC client backend[16483] pg_regress/vacuum ERROR: parallel workers for vacuum must be between 0 and 1024 at character 9 2025-07-03 22:05:16.614 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL -1) pvactst; 2025-07-03 22:05:16.619 UTC client backend[16473] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-07-03 22:05:16.619 UTC client backend[16473] pg_regress/constraints DETAIL: Key (f1)=(1) conflicts with existing key (f1)=(1). 2025-07-03 22:05:16.619 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1); 2025-07-03 22:05:16.619 UTC client backend[16483] pg_regress/vacuum ERROR: VACUUM FULL cannot be performed in parallel 2025-07-03 22:05:16.619 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL 2, FULL TRUE) pvactst; 2025-07-03 22:05:16.620 UTC client backend[16473] pg_regress/constraints ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters 2025-07-03 22:05:16.620 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO deferred_excl VALUES(1) ON CONFLICT ON CONSTRAINT deferred_excl_con DO NOTHING; 2025-07-03 22:05:16.620 UTC client backend[16483] pg_regress/vacuum ERROR: parallel option requires a value between 0 and 1024 at character 9 2025-07-03 22:05:16.620 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (PARALLEL) pvactst; 2025-07-03 22:05:16.620 UTC client backend[16473] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-07-03 22:05:16.620 UTC client backend[16473] pg_regress/constraints DETAIL: Key (f1)=(2) conflicts with existing key (f1)=(2). 2025-07-03 22:05:16.620 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMIT; 2025-07-03 22:05:16.624 UTC client backend[16473] pg_regress/constraints ERROR: conflicting key value violates exclusion constraint "deferred_excl_con" 2025-07-03 22:05:16.624 UTC client backend[16473] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with existing key (f1)=(3). 2025-07-03 22:05:16.624 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMIT; 2025-07-03 22:05:16.636 UTC client backend[16473] pg_regress/constraints ERROR: could not create exclusion constraint "deferred_excl_f1_excl" 2025-07-03 22:05:16.636 UTC client backend[16473] pg_regress/constraints DETAIL: Key (f1)=(3) conflicts with key (f1)=(3). 2025-07-03 22:05:16.636 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE deferred_excl ADD EXCLUDE (f1 WITH =); 2025-07-03 22:05:16.643 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot execute MERGE on relation "rw_view1" 2025-07-03 22:05:16.643 UTC client backend[16491] pg_regress/updatable_views DETAIL: MERGE is not supported for relations with rules. 2025-07-03 22:05:16.643 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (3, 'Row 3')) AS v(a,b) ON t.a = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.b); 2025-07-03 22:05:16.657 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_check" 2025-07-03 22:05:16.657 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (null). 2025-07-03 22:05:16.657 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2025-07-03 22:05:16.658 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_check" 2025-07-03 22:05:16.658 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (null, null). 2025-07-03 22:05:16.658 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2025-07-03 22:05:16.658 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_check" of relation "bc" 2025-07-03 22:05:16.658 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_check; 2025-07-03 22:05:16.670 UTC client backend[16474] pg_regress/triggers ERROR: No such country: "Japon" 2025-07-03 22:05:16.670 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function city_update() line 9 at RAISE 2025-07-03 22:05:16.670 UTC client backend[16474] pg_regress/triggers STATEMENT: UPDATE city_view SET country_name = 'Japon' WHERE city_name = 'Tokyo'; 2025-07-03 22:05:16.684 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "ac" violates check constraint "ac_aa_check" 2025-07-03 22:05:16.684 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (null). 2025-07-03 22:05:16.684 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into ac (aa) values (NULL); 2025-07-03 22:05:16.686 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "bc" violates check constraint "ac_aa_check" 2025-07-03 22:05:16.686 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (null, null). 2025-07-03 22:05:16.686 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into bc (aa) values (NULL); 2025-07-03 22:05:16.687 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "ac_aa_check" of relation "bc" 2025-07-03 22:05:16.687 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table bc drop constraint ac_aa_check; 2025-07-03 22:05:16.759 UTC client backend[16483] pg_regress/vacuum WARNING: disabling parallel option of vacuum on "tmp" --- cannot vacuum temporary tables in parallel 2025-07-03 22:05:16.847 UTC client backend[16479] pg_regress/inherit ERROR: check constraint "cc" of relation "c1" is violated by some row 2025-07-03 22:05:16.847 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p2 add constraint cc check (f2>0); 2025-07-03 22:05:16.857 UTC client backend[16479] pg_regress/inherit ERROR: check constraint "p2_f2_check" of relation "c1" is violated by some row 2025-07-03 22:05:16.857 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p2 add check (f2>0); 2025-07-03 22:05:16.860 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "c1" violates check constraint "p2_f2_check" 2025-07-03 22:05:16.860 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (1, -1, 2). 2025-07-03 22:05:16.860 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into c1 values(1,-1,2); 2025-07-03 22:05:16.908 UTC client backend[16486] pg_regress/infinite_recurse ERROR: stack depth limit exceeded 2025-07-03 22:05:16.908 UTC client backend[16486] pg_regress/infinite_recurse HINT: Increase the configuration parameter "max_stack_depth" (currently 2048kB), after ensuring the platform's stack depth limit is adequate. 2025-07-03 22:05:16.908 UTC client backend[16486] pg_regress/infinite_recurse CONTEXT: SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 SQL function "infinite_recurse" statement 1 2025-07-03 22:05:16.908 UTC client backend[16486] pg_regress/infinite_recurse STATEMENT: select infinite_recurse(); 2025-07-03 22:05:16.915 UTC client backend[16473] pg_regress/constraints ERROR: constraint "notnull_tbl1_a_not_null" for relation "notnull_tbl1" already exists 2025-07-03 22:05:16.915 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD COLUMN b INT CONSTRAINT notnull_tbl1_a_not_null NOT NULL; 2025-07-03 22:05:16.978 UTC client backend[16486] pg_regress/infinite_recurse LOG: disconnection: session time: 0:00:02.025 user=postgres database=regression host=[local] 2025-07-03 22:05:16.980 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot delete from view "rw_view1" 2025-07-03 22:05:16.980 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-07-03 22:05:16.980 UTC client backend[16491] pg_regress/updatable_views HINT: To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger. 2025-07-03 22:05:16.980 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (SELECT x, 'R'||x FROM generate_series(0,3) x) AS s(a,b) ON t.a = s.a WHEN MATCHED AND t.a <= 1 THEN DELETE WHEN MATCHED THEN UPDATE SET b = s.b WHEN NOT MATCHED AND s.a > 0 THEN INSERT VALUES (s.a, s.b); 2025-07-03 22:05:16.993 UTC client backend[16474] pg_regress/triggers ERROR: U9999 2025-07-03 22:05:16.993 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function depth_c_tf() line 5 at RAISE SQL statement "insert into depth_c values (1)" PL/pgSQL function depth_b_tf() line 12 at EXECUTE SQL statement "insert into depth_b values (new.id)" PL/pgSQL function depth_a_tf() line 4 at SQL statement 2025-07-03 22:05:16.993 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into depth_a values (1); 2025-07-03 22:05:16.994 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into view "rw_view1" 2025-07-03 22:05:16.994 UTC client backend[16491] pg_regress/updatable_views DETAIL: Views containing LIMIT or OFFSET are not automatically updatable. 2025-07-03 22:05:16.994 UTC client backend[16491] pg_regress/updatable_views HINT: To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger. 2025-07-03 22:05:16.994 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (SELECT x, 'R'||x FROM generate_series(0,3) x) AS s(a,b) ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = s.b WHEN NOT MATCHED AND s.a > 0 THEN INSERT VALUES (s.a, s.b); 2025-07-03 22:05:17.004 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot merge into view "rw_view2" 2025-07-03 22:05:17.004 UTC client backend[16491] pg_regress/updatable_views DETAIL: MERGE is not supported for views with INSTEAD OF triggers for some actions but not all. 2025-07-03 22:05:17.004 UTC client backend[16491] pg_regress/updatable_views HINT: To enable merging into the view, either provide a full set of INSTEAD OF triggers or drop the existing INSTEAD OF triggers. 2025-07-03 22:05:17.004 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (SELECT x, 'R'||x FROM generate_series(0,3) x) AS s(a,b) ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = s.b WHEN NOT MATCHED AND s.a > 0 THEN INSERT VALUES (s.a, s.b); 2025-07-03 22:05:17.123 UTC client backend[16474] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2025-07-03 22:05:17.123 UTC client backend[16474] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-07-03 22:05:17.123 UTC client backend[16474] pg_regress/triggers STATEMENT: update parent set val1 = 'b' where aid = 1; 2025-07-03 22:05:17.124 UTC client backend[16474] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2025-07-03 22:05:17.124 UTC client backend[16474] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-07-03 22:05:17.124 UTC client backend[16474] pg_regress/triggers STATEMENT: merge into parent p using (values (1)) as v(id) on p.aid = v.id when matched then update set val1 = 'b'; 2025-07-03 22:05:17.125 UTC client backend[16483] pg_regress/vacuum ERROR: null value in column "i" of relation "vac_truncate_test" violates not-null constraint 2025-07-03 22:05:17.125 UTC client backend[16483] pg_regress/vacuum DETAIL: Failing row contains (null, null). 2025-07-03 22:05:17.125 UTC client backend[16483] pg_regress/vacuum STATEMENT: INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL); 2025-07-03 22:05:17.132 UTC client backend[16474] pg_regress/triggers ERROR: tuple to be deleted was already modified by an operation triggered by the current command 2025-07-03 22:05:17.132 UTC client backend[16474] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-07-03 22:05:17.132 UTC client backend[16474] pg_regress/triggers STATEMENT: delete from parent where aid = 1; 2025-07-03 22:05:17.135 UTC client backend[16474] pg_regress/triggers ERROR: tuple to be updated or deleted was already modified by an operation triggered by the current command 2025-07-03 22:05:17.135 UTC client backend[16474] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-07-03 22:05:17.135 UTC client backend[16474] pg_regress/triggers STATEMENT: merge into parent p using (values (1)) as v(id) on p.aid = v.id when matched then delete; 2025-07-03 22:05:17.184 UTC client backend[16483] pg_regress/vacuum ERROR: null value in column "i" of relation "vac_truncate_test" violates not-null constraint 2025-07-03 22:05:17.184 UTC client backend[16483] pg_regress/vacuum DETAIL: Failing row contains (null, null). 2025-07-03 22:05:17.184 UTC client backend[16483] pg_regress/vacuum STATEMENT: INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL); 2025-07-03 22:05:17.190 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.190 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0); 2025-07-03 22:05:17.193 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.193 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3); 2025-07-03 22:05:17.193 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.193 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES ('Row 3', 3.0, 3); 2025-07-03 22:05:17.194 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.194 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES ('Row 3', 3.0, 3)) AS v(b,c,a) ON t.aa = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.b, v.c, v.a); 2025-07-03 22:05:17.194 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.194 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES ('Row 3', 3.0, 3)) AS v(b,c,a) ON t.aa = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.b, v.c, v.a); 2025-07-03 22:05:17.195 UTC client backend[16479] pg_regress/inherit ERROR: cannot rename inherited column "b" 2025-07-03 22:05:17.195 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; 2025-07-03 22:05:17.196 UTC client backend[16479] pg_regress/inherit ERROR: cannot rename inherited column "aa" 2025-07-03 22:05:17.196 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inhts RENAME aa TO aaa; 2025-07-03 22:05:17.202 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.202 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET b=b; 2025-07-03 22:05:17.202 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.202 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-07-03 22:05:17.204 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.204 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bb=bb; 2025-07-03 22:05:17.207 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.207 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET aa = aa; 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET bb = bb; 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl; 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1; 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.211 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view2; 2025-07-03 22:05:17.220 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.220 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-07-03 22:05:17.221 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.221 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-07-03 22:05:17.223 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.223 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED AND bb = 'xxx' THEN DELETE; 2025-07-03 22:05:17.228 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.228 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (5, 'Row 5', 5.0); 2025-07-03 22:05:17.232 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.232 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES ('Row 6', 6.0, 6); 2025-07-03 22:05:17.232 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.232 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl WHERE a=3; 2025-07-03 22:05:17.233 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.233 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view2 WHERE aa=4; 2025-07-03 22:05:17.235 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.235 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED AND bb = 'xxx' THEN DELETE; 2025-07-03 22:05:17.237 UTC client backend[16474] pg_regress/triggers ERROR: tuple to be updated was already modified by an operation triggered by the current command 2025-07-03 22:05:17.237 UTC client backend[16474] pg_regress/triggers HINT: Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows. 2025-07-03 22:05:17.237 UTC client backend[16474] pg_regress/triggers STATEMENT: delete from self_ref_trigger; 2025-07-03 22:05:17.258 UTC client backend[16483] pg_regress/vacuum ERROR: column "a" of relation "vacparted" appears more than once 2025-07-03 22:05:17.258 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vacparted(a,b,a); 2025-07-03 22:05:17.259 UTC client backend[16483] pg_regress/vacuum ERROR: column "b" of relation "vacparted" appears more than once 2025-07-03 22:05:17.259 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE vacparted(a,b,b); 2025-07-03 22:05:17.281 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.281 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-07-03 22:05:17.283 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.283 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-07-03 22:05:17.284 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.284 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-07-03 22:05:17.284 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.284 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.288 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.288 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.289 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.289 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-07-03 22:05:17.289 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.289 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-07-03 22:05:17.290 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.290 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.294 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.295 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.295 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.296 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.296 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-07-03 22:05:17.298 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.298 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-07-03 22:05:17.298 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.298 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.300 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.300 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-07-03 22:05:17.301 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.301 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-07-03 22:05:17.301 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.301 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.310 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.310 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-07-03 22:05:17.310 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.310 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-07-03 22:05:17.311 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.311 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'bar'; 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1 FOR UPDATE; 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = 'foo' WHERE a = 1; 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.324 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.326 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.326 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2 FOR UPDATE; 2025-07-03 22:05:17.327 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.327 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET b = 'bar' WHERE a = 1; 2025-07-03 22:05:17.328 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.328 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET b = 'foo'; 2025-07-03 22:05:17.357 UTC client backend[16474] pg_regress/triggers ERROR: cannot ALTER TABLE "trigger_ddl_table" because it is being used by active queries in this session 2025-07-03 22:05:17.357 UTC client backend[16474] pg_regress/triggers CONTEXT: SQL statement "alter table trigger_ddl_table add primary key (col1)" PL/pgSQL function trigger_ddl_func() line 3 at SQL statement 2025-07-03 22:05:17.357 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2025-07-03 22:05:17.363 UTC client backend[16474] pg_regress/triggers ERROR: cannot CREATE INDEX "trigger_ddl_table" because it is being used by active queries in this session 2025-07-03 22:05:17.363 UTC client backend[16474] pg_regress/triggers CONTEXT: SQL statement "create index on trigger_ddl_table (col2)" PL/pgSQL function trigger_ddl_func() line 3 at SQL statement 2025-07-03 22:05:17.363 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into trigger_ddl_table values (1, 42); 2025-07-03 22:05:17.365 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.365 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM base_tbl; 2025-07-03 22:05:17.367 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.367 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-07-03 22:05:17.367 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.367 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0); 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3); 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET a=a; 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET bb=bb, cc=cc; 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.368 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET bb = bb; 2025-07-03 22:05:17.369 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.369 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM base_tbl; 2025-07-03 22:05:17.370 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.370 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1; 2025-07-03 22:05:17.370 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.370 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN DELETE; 2025-07-03 22:05:17.377 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.377 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE base_tbl SET b=b; 2025-07-03 22:05:17.382 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.382 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-07-03 22:05:17.382 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.382 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET bb=bb; 2025-07-03 22:05:17.383 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.383 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET aa = aa; 2025-07-03 22:05:17.383 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.383 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET bb = bb; 2025-07-03 22:05:17.386 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.386 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-07-03 22:05:17.389 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.389 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-07-03 22:05:17.389 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.389 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN DELETE; 2025-07-03 22:05:17.393 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.393 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4); 2025-07-03 22:05:17.394 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.394 UTC client backend[16491] pg_regress/updatable_views STATEMENT: DELETE FROM rw_view1 WHERE aa=2; 2025-07-03 22:05:17.394 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.394 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN DELETE; 2025-07-03 22:05:17.395 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.395 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM vacparted, does_not_exist; 2025-07-03 22:05:17.407 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.407 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (FREEZE) does_not_exist, vaccluster; 2025-07-03 22:05:17.415 UTC client backend[16483] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vactst" does not exist 2025-07-03 22:05:17.415 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM ANALYZE vactst (does_not_exist), vacparted (b); 2025-07-03 22:05:17.416 UTC client backend[16479] pg_regress/inherit ERROR: cannot rename inherited column "b" 2025-07-03 22:05:17.416 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inht1 RENAME b TO bb; 2025-07-03 22:05:17.428 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (1,black) 2025-07-03 22:05:17.428 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.431 UTC client backend[16474] pg_regress/triggers WARNING: after insert (new): (1,black) 2025-07-03 22:05:17.431 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-07-03 22:05:17.434 UTC client backend[16483] pg_regress/vacuum ERROR: ANALYZE option must be specified when a column list is provided 2025-07-03 22:05:17.434 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM FULL vactst, vacparted (a, b), vaccluster (i); 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (2,red) 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new, modified): (3,"red trig modified") 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers WARNING: after insert (new): (3,"red trig modified") 2025-07-03 22:05:17.435 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-07-03 22:05:17.436 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.436 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-07-03 22:05:17.438 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.438 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-07-03 22:05:17.439 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.439 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (2, 'Row 2', 2.0)) AS v(a,b,c) ON t.aa = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.b, v.c, v.a); 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (3,orange) 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers WARNING: before update (old): (3,"red trig modified") 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers WARNING: before update (new): (3,"updated red trig modified") 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers WARNING: after update (old): (3,"red trig modified") 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers WARNING: after update (new): (3,"updated red trig modified") 2025-07-03 22:05:17.441 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (4,green) 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new, modified): (5,"green trig modified") 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers WARNING: after insert (new): (5,"green trig modified") 2025-07-03 22:05:17.447 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-07-03 22:05:17.449 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.449 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE vactst, does_not_exist, vacparted; 2025-07-03 22:05:17.449 UTC client backend[16483] pg_regress/vacuum ERROR: column "does_not_exist" of relation "vacparted" does not exist 2025-07-03 22:05:17.449 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE vactst (i), vacparted (does_not_exist); 2025-07-03 22:05:17.450 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.450 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.451 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.451 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (5,purple) 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers WARNING: before update (old): (5,"green trig modified") 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers WARNING: before update (new): (5,"updated green trig modified") 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers WARNING: after update (old): (5,"green trig modified") 2025-07-03 22:05:17.451 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-07-03 22:05:17.452 UTC client backend[16474] pg_regress/triggers WARNING: after update (new): (5,"updated green trig modified") 2025-07-03 22:05:17.452 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-07-03 22:05:17.451 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.451 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (2, 'Row 2', 2.0)) AS v(a,b,c) ON t.aaa = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.c, v.a, v.b); 2025-07-03 22:05:17.457 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (6,white) 2025-07-03 22:05:17.457 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.457 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new, modified): (7,"white trig modified") 2025-07-03 22:05:17.457 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-07-03 22:05:17.458 UTC client backend[16474] pg_regress/triggers WARNING: after insert (new): (7,"white trig modified") 2025-07-03 22:05:17.458 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-07-03 22:05:17.461 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.461 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET cc=cc; 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (7,pink) 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers WARNING: before update (old): (7,"white trig modified") 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 4 at RAISE 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers WARNING: before update (new): (7,"updated white trig modified") 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 5 at RAISE 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers WARNING: after update (old): (7,"white trig modified") 2025-07-03 22:05:17.461 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 4 at RAISE 2025-07-03 22:05:17.462 UTC client backend[16474] pg_regress/triggers WARNING: after update (new): (7,"updated white trig modified") 2025-07-03 22:05:17.462 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 5 at RAISE 2025-07-03 22:05:17.462 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.462 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET cc = cc; 2025-07-03 22:05:17.465 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.465 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.465 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.465 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new): (8,yellow) 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 7 at RAISE 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers WARNING: before insert (new, modified): (9,"yellow trig modified") 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_before_func() line 11 at RAISE 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers WARNING: after insert (new): (9,"yellow trig modified") 2025-07-03 22:05:17.465 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function upsert_after_func() line 7 at RAISE 2025-07-03 22:05:17.466 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.466 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.471 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.471 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.474 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.474 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.474 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.474 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.477 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.483 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.483 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.484 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.484 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.484 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.484 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.491 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.491 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.492 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.492 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.492 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.492 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.493 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.493 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.495 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.495 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.496 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.496 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.496 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.496 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.497 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.497 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET ccc=ccc; 2025-07-03 22:05:17.499 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.499 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.503 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.503 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.504 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.504 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET ccc = ccc; 2025-07-03 22:05:17.510 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.510 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.510 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.510 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.511 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.511 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.511 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.511 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.516 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.516 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view1; 2025-07-03 22:05:17.519 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.519 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET aa=aa; 2025-07-03 22:05:17.523 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.523 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (1)) AS v(a) ON t.aa = v.a WHEN MATCHED THEN UPDATE SET aa = aa; 2025-07-03 22:05:17.524 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.524 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.525 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.525 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.526 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.526 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.526 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.526 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.529 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.529 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.529 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.529 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.531 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.531 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.532 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.532 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.533 UTC client backend[16474] pg_regress/triggers ERROR: "my_view" is a view 2025-07-03 22:05:17.533 UTC client backend[16474] pg_regress/triggers DETAIL: Triggers on views cannot have transition tables. 2025-07-03 22:05:17.533 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger my_trigger after update on my_view referencing old table as old_table for each statement execute procedure my_trigger_function(); 2025-07-03 22:05:17.538 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.538 UTC client backend[16491] pg_regress/updatable_views STATEMENT: SELECT * FROM rw_view2; 2025-07-03 22:05:17.539 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.539 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.539 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.539 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.540 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.540 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET ccc=ccc; 2025-07-03 22:05:17.540 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.540 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.544 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.544 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.544 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.544 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET ccc = ccc; 2025-07-03 22:05:17.546 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.546 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET aaa=aaa; 2025-07-03 22:05:17.547 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.547 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET bbb=bbb; 2025-07-03 22:05:17.548 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:17.548 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET aaa = aaa; 2025-07-03 22:05:17.548 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:17.548 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (1)) AS v(a) ON t.aaa = v.a WHEN MATCHED THEN UPDATE SET bbb = bbb; 2025-07-03 22:05:17.549 UTC client backend[16483] pg_regress/vacuum WARNING: VACUUM ONLY of partitioned table "vacparted" has no effect 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers ERROR: "parted_trig" is a table 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers DETAIL: Tables cannot have INSTEAD OF triggers. 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger failed instead of update on parted_trig for each row execute procedure trigger_nothing(); 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers ERROR: "parted_trig" is a partitioned table 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported on partitioned tables. 2025-07-03 22:05:17.584 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger failed after update on parted_trig referencing old table as old_table for each row execute procedure trigger_nothing(); 2025-07-03 22:05:17.714 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.714 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE) does_not_exist; 2025-07-03 22:05:17.715 UTC client backend[16483] pg_regress/vacuum ERROR: syntax error at or near "arg" at character 22 2025-07-03 22:05:17.715 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE (nonexistent-arg) does_not_exist; 2025-07-03 22:05:17.715 UTC client backend[16483] pg_regress/vacuum ERROR: unrecognized ANALYZE option "nonexistentarg" at character 10 2025-07-03 22:05:17.715 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE (nonexistentarg) does_not_exit; 2025-07-03 22:05:17.717 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.717 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE (SKIP_LOCKED, VERBOSE) does_not_exist; 2025-07-03 22:05:17.717 UTC client backend[16483] pg_regress/vacuum ERROR: relation "does_not_exist" does not exist 2025-07-03 22:05:17.717 UTC client backend[16483] pg_regress/vacuum STATEMENT: ANALYZE (VERBOSE, SKIP_LOCKED) does_not_exist; 2025-07-03 22:05:17.746 UTC client backend[16474] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart1 because trigger trg1 on table trigpart requires it 2025-07-03 22:05:17.746 UTC client backend[16474] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-07-03 22:05:17.746 UTC client backend[16474] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart1; 2025-07-03 22:05:17.747 UTC client backend[16473] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-07-03 22:05:17.747 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null constraint bar not null); 2025-07-03 22:05:17.747 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-07-03 22:05:17.747 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null no inherit constraint foo not null); 2025-07-03 22:05:17.748 UTC client backend[16474] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart2 because trigger trg1 on table trigpart requires it 2025-07-03 22:05:17.748 UTC client backend[16474] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-07-03 22:05:17.748 UTC client backend[16474] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart2; 2025-07-03 22:05:17.748 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:17.748 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int constraint foo not null, constraint foo not null a no inherit); 2025-07-03 22:05:17.749 UTC client backend[16474] pg_regress/triggers ERROR: cannot drop trigger trg1 on table trigpart3 because trigger trg1 on table trigpart requires it 2025-07-03 22:05:17.749 UTC client backend[16474] pg_regress/triggers HINT: You can drop trigger trg1 on table trigpart instead. 2025-07-03 22:05:17.749 UTC client backend[16474] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2025-07-03 22:05:17.753 UTC client backend[16473] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-07-03 22:05:17.753 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial constraint foo not null, constraint bar not null a); 2025-07-03 22:05:17.754 UTC client backend[16473] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "bar" 2025-07-03 22:05:17.754 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial, constraint foo not null a, constraint bar not null a); 2025-07-03 22:05:17.764 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:17.764 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial, constraint foo not null a no inherit); 2025-07-03 22:05:17.772 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "ctid" of view "rw_view1" 2025-07-03 22:05:17.772 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that refer to system columns are not updatable. 2025-07-03 22:05:17.772 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (null, null, 1.1, null); 2025-07-03 22:05:17.773 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-07-03 22:05:17.773 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a serial not null no inherit); 2025-07-03 22:05:17.774 UTC client backend[16473] pg_regress/constraints ERROR: conflicting not-null constraint names "foo" and "foo2" 2025-07-03 22:05:17.774 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (like notnull_tbl1, constraint foo2 not null a); 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (s, c, a) VALUES (null, null, 1.1); 2025-07-03 22:05:17.774 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-07-03 22:05:17.774 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int primary key constraint foo not null no inherit); 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.774 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (s, c, a) VALUES (default, default, 1.1); 2025-07-03 22:05:17.775 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-07-03 22:05:17.775 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int not null no inherit primary key); 2025-07-03 22:05:17.775 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:17.775 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int primary key, not null a no inherit); 2025-07-03 22:05:17.776 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-07-03 22:05:17.776 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.776 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET s = s WHERE a = 1.1; 2025-07-03 22:05:17.779 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:17.779 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int, primary key(a), not null a no inherit); 2025-07-03 22:05:17.780 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:17.780 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int generated by default as identity, constraint foo not null a no inherit); 2025-07-03 22:05:17.783 UTC client backend[16473] pg_regress/constraints ERROR: conflicting NO INHERIT declarations for not-null constraints on column "a" 2025-07-03 22:05:17.783 UTC client backend[16473] pg_regress/constraints STATEMENT: create table notnull_tbl_fail (a int generated by default as identity not null no inherit); 2025-07-03 22:05:17.785 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "t" of view "rw_view2" 2025-07-03 22:05:17.785 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.785 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (null, null, null, 1.1, null); 2025-07-03 22:05:17.791 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-07-03 22:05:17.791 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.791 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2(s, c, base_a) VALUES (null, null, 1.1); 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET s = s WHERE base_a = 1.1; 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "t" of view "rw_view2" 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.794 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET t = t WHERE base_a = 1.1; 2025-07-03 22:05:17.798 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "t" of view "rw_view3" 2025-07-03 22:05:17.798 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.798 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3 VALUES (null, null, null, null); 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "s" of view "rw_view1" 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3(s) VALUES (null); 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot update column "s" of view "rw_view1" 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:17.800 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view3 SET s = s; 2025-07-03 22:05:17.832 UTC client backend[16483] pg_regress/vacuum ERROR: PROCESS_TOAST required with VACUUM FULL 2025-07-03 22:05:17.832 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (PROCESS_TOAST FALSE, FULL) vac_option_tab; 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert a non-DEFAULT value into column "idplus1" 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views DETAIL: Column "idplus1" is a generated column. 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO base_tbl (id, idplus1) VALUES (5, 6); 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert a non-DEFAULT value into column "idplus1" 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views DETAIL: Column "idplus1" is a generated column. 2025-07-03 22:05:17.880 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 (id, idplus1) VALUES (6, 7); 2025-07-03 22:05:17.945 UTC client backend[16473] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2025-07-03 22:05:17.945 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int NOT NULL NO INHERIT) PARTITION BY LIST (a); 2025-07-03 22:05:17.945 UTC client backend[16473] pg_regress/constraints ERROR: not-null constraints on partitioned tables cannot be NO INHERIT 2025-07-03 22:05:17.945 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE ATACC1 (a int, NOT NULL a NO INHERIT) PARTITION BY LIST (a); 2025-07-03 22:05:17.954 UTC client backend[16483] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-07-03 22:05:17.954 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 16777220) vac_option_tab; 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 120) vac_option_tab; 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum HINT: Value exceeds integer range. 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT 10000000000) vac_option_tab; 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum ERROR: BUFFER_USAGE_LIMIT cannot be specified for VACUUM FULL 2025-07-03 22:05:17.955 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (BUFFER_USAGE_LIMIT '512 kB', FULL) vac_option_tab; 2025-07-03 22:05:17.958 UTC client backend[16483] pg_regress/vacuum ERROR: ONLY_DATABASE_STATS cannot be specified with a list of tables 2025-07-03 22:05:17.958 UTC client backend[16483] pg_regress/vacuum STATEMENT: VACUUM (ONLY_DATABASE_STATS) vactst; 2025-07-03 22:05:17.964 UTC client backend[16473] pg_regress/constraints ERROR: cannot change NO INHERIT status of NOT NULL constraint "a_is_not_null" on relation "atacc2" 2025-07-03 22:05:17.964 UTC client backend[16473] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:17.964 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE ATACC1 ADD CONSTRAINT ditto NOT NULL a; 2025-07-03 22:05:17.991 UTC client backend[16474] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart3" does not exist 2025-07-03 22:05:17.991 UTC client backend[16474] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart3; 2025-07-03 22:05:18.002 UTC client backend[16473] pg_regress/constraints ERROR: constraint "blah" for relation "notnull_tbl2" already exists 2025-07-03 22:05:18.002 UTC client backend[16473] pg_regress/constraints STATEMENT: CREATE TABLE notnull_tbl2 (a INTEGER CONSTRAINT blah NOT NULL, b INTEGER CONSTRAINT blah NOT NULL); 2025-07-03 22:05:18.005 UTC client backend[16474] pg_regress/triggers ERROR: trigger "trg1" for table "trigpart41" does not exist 2025-07-03 22:05:18.005 UTC client backend[16474] pg_regress/triggers STATEMENT: drop trigger trg1 on trigpart41; 2025-07-03 22:05:18.005 UTC client backend[16473] pg_regress/constraints ERROR: column "a" is in a primary key 2025-07-03 22:05:18.005 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl2 ALTER a DROP NOT NULL; 2025-07-03 22:05:18.048 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2025-07-03 22:05:18.054 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned", skipping it 2025-07-03 22:05:18.056 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned", skipping it 2025-07-03 22:05:18.056 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2025-07-03 22:05:18.057 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "pg_class", skipping it 2025-07-03 22:05:18.057 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "pg_class", skipping it 2025-07-03 22:05:18.059 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2025-07-03 22:05:18.061 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "pg_authid", skipping it 2025-07-03 22:05:18.061 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "pg_authid", skipping it 2025-07-03 22:05:18.063 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-07-03 22:05:18.064 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.065 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.065 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.067 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.067 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2025-07-03 22:05:18.068 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-07-03 22:05:18.068 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.068 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-07-03 22:05:18.069 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.069 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-07-03 22:05:18.069 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.071 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.074 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (4, 3). 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES(4,3); 2025-07-03 22:05:18.074 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (5, null). 2025-07-03 22:05:18.074 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES(5,null); 2025-07-03 22:05:18.075 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.075 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (3, -5). 2025-07-03 22:05:18.075 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b = -5 WHERE a = 3; 2025-07-03 22:05:18.077 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.077 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (10, 10). 2025-07-03 22:05:18.077 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1(a) VALUES (10); 2025-07-03 22:05:18.080 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.085 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.085 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (11, 10). 2025-07-03 22:05:18.085 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (11)) AS v(a) ON t.a = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.a, v.a - 1); 2025-07-03 22:05:18.087 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.089 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.095 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.095 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.095 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (3, 3). 2025-07-03 22:05:18.095 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view1 t USING (VALUES (2)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET a = t.a + 1; 2025-07-03 22:05:18.096 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.099 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.104 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-07-03 22:05:18.105 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.108 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.108 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_parted", skipping it 2025-07-03 22:05:18.108 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.111 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.112 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_parted", skipping it 2025-07-03 22:05:18.112 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.116 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.124 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.124 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.125 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.126 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.129 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-07-03 22:05:18.129 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.129 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part1", skipping it 2025-07-03 22:05:18.129 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to analyze "vacowned_part2", skipping it 2025-07-03 22:05:18.132 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.133 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.134 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part1", skipping it 2025-07-03 22:05:18.134 UTC client backend[16483] pg_regress/vacuum WARNING: permission denied to vacuum "vacowned_part2", skipping it 2025-07-03 22:05:18.169 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.169 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-07-03 22:05:18.169 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-5); 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (15); 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-07-03 22:05:18.170 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a - 10; 2025-07-03 22:05:18.171 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.171 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-07-03 22:05:18.171 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a + 10; 2025-07-03 22:05:18.171 UTC client backend[16483] pg_regress/vacuum LOG: disconnection: session time: 0:00:03.236 user=postgres database=regression host=[local] 2025-07-03 22:05:18.179 UTC client backend[16474] pg_regress/triggers ERROR: trigger "trg1" for relation "trigpart3" already exists 2025-07-03 22:05:18.179 UTC client backend[16474] pg_regress/triggers STATEMENT: alter table trigpart attach partition trigpart3 FOR VALUES FROM (2000) to (3000); 2025-07-03 22:05:18.226 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.226 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (20). 2025-07-03 22:05:18.226 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (20); 2025-07-03 22:05:18.228 UTC client backend[16491] pg_regress/updatable_views ERROR: invalid value for enum option "check_option": here 2025-07-03 22:05:18.228 UTC client backend[16491] pg_regress/updatable_views DETAIL: Valid values are "local" and "cascaded". 2025-07-03 22:05:18.228 UTC client backend[16491] pg_regress/updatable_views STATEMENT: ALTER VIEW rw_view1 SET (check_option=here); 2025-07-03 22:05:18.231 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.231 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-20). 2025-07-03 22:05:18.231 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-20); 2025-07-03 22:05:18.232 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.232 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (30). 2025-07-03 22:05:18.232 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (30); 2025-07-03 22:05:18.344 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.344 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-3). 2025-07-03 22:05:18.344 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view3 VALUES (-3); 2025-07-03 22:05:18.371 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.371 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (10, {4,5}). 2025-07-03 22:05:18.371 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (10, ARRAY[4,5]); 2025-07-03 22:05:18.374 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.374 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (1, {-1,-2,3}). 2025-07-03 22:05:18.374 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET b[1] = -b[1] WHERE a = 1; 2025-07-03 22:05:18.384 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.384 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (10, {4,5}). 2025-07-03 22:05:18.384 UTC client backend[16491] pg_regress/updatable_views STATEMENT: EXECUTE ins(10, ARRAY[4,5]); 2025-07-03 22:05:18.408 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.408 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-07-03 22:05:18.408 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (15); 2025-07-03 22:05:18.415 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.415 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (15). 2025-07-03 22:05:18.415 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET a = a + 5; 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (15, 10). 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view1 VALUES (15, 20); 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view1" 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (20, 10). 2025-07-03 22:05:18.434 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view1 SET a = 20, b = 30; 2025-07-03 22:05:18.458 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.458 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-07-03 22:05:18.458 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO rw_view2 VALUES (-5); 2025-07-03 22:05:18.459 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.459 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-07-03 22:05:18.459 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (-5)) AS v(a) ON t.a = v.a WHEN NOT MATCHED THEN INSERT VALUES (v.a); 2025-07-03 22:05:18.464 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.464 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-5). 2025-07-03 22:05:18.464 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE rw_view2 SET a = a - 10; 2025-07-03 22:05:18.466 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "rw_view2" 2025-07-03 22:05:18.466 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-4). 2025-07-03 22:05:18.466 UTC client backend[16491] pg_regress/updatable_views STATEMENT: MERGE INTO rw_view2 t USING (VALUES (6)) AS v(a) ON t.a = v.a WHEN MATCHED THEN UPDATE SET a = t.a - 10; 2025-07-03 22:05:18.612 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_check_constraint7" conflicts with NOT ENFORCED constraint on relation "p1_c1" 2025-07-03 22:05:18.612 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1 add constraint inh_check_constraint7 check (f1 < 10) enforced; 2025-07-03 22:05:18.621 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_check_constraint8" conflicts with NOT ENFORCED constraint on relation "p1_c1" 2025-07-03 22:05:18.621 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1_c1 add constraint inh_check_constraint8 check (f1 < 10) not enforced; 2025-07-03 22:05:18.624 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_check_constraint2" conflicts with NOT ENFORCED constraint on relation "p1_fail" 2025-07-03 22:05:18.624 UTC client backend[16479] pg_regress/inherit STATEMENT: create table p1_fail(f1 int constraint inh_check_constraint2 check (f1 < 10) not enforced) inherits(p1); 2025-07-03 22:05:18.637 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_check_constraint6" conflicts with NOT ENFORCED constraint on relation "p1_fail" 2025-07-03 22:05:18.637 UTC client backend[16479] pg_regress/inherit STATEMENT: create table p1_fail(f1 int constraint inh_check_constraint6 check (f1 < 10) not enforced) inherits(p1, p1_c1); 2025-07-03 22:05:18.656 UTC client backend[16473] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-07-03 22:05:18.656 UTC client backend[16473] pg_regress/constraints DETAIL: The constraint "cnn_pk_a_not_null" on column "a" of table "cnn_pk", marked NO INHERIT, is incompatible with a primary key. 2025-07-03 22:05:18.656 UTC client backend[16473] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:18.656 UTC client backend[16473] pg_regress/constraints STATEMENT: alter table cnn_pk add primary key (a); 2025-07-03 22:05:18.670 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "cnn_part1" contains null values 2025-07-03 22:05:18.670 UTC client backend[16473] pg_regress/constraints STATEMENT: alter table cnn2_parted add primary key (a); 2025-07-03 22:05:18.688 UTC client backend[16479] pg_regress/inherit ERROR: constraint "p1_a_check" conflicts with NOT ENFORCED constraint on child table "p1_c1" 2025-07-03 22:05:18.688 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1_c1 inherit p1; 2025-07-03 22:05:18.701 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1" 2025-07-03 22:05:18.701 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1_c1 drop constraint f1_pos; 2025-07-03 22:05:18.767 UTC client backend[16474] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-07-03 22:05:18.767 UTC client backend[16474] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1_1". 2025-07-03 22:05:18.767 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'uno uno v2'); 2025-07-03 22:05:18.768 UTC client backend[16474] pg_regress/triggers ERROR: no partition of relation "parted" found for row 2025-07-03 22:05:18.768 UTC client backend[16474] pg_regress/triggers DETAIL: Partition key of the failing row contains (a) = (2). 2025-07-03 22:05:18.768 UTC client backend[16474] pg_regress/triggers STATEMENT: update parted set c = c || 'v3'; 2025-07-03 22:05:18.770 UTC client backend[16474] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-07-03 22:05:18.770 UTC client backend[16474] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1_1". 2025-07-03 22:05:18.770 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'uno uno v4'); 2025-07-03 22:05:18.771 UTC client backend[16474] pg_regress/triggers ERROR: no partition of relation "parted_1" found for row 2025-07-03 22:05:18.771 UTC client backend[16474] pg_regress/triggers DETAIL: Partition key of the failing row contains (b) = (2). 2025-07-03 22:05:18.771 UTC client backend[16474] pg_regress/triggers STATEMENT: update parted set c = c || 'v5'; 2025-07-03 22:05:18.898 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c2" 2025-07-03 22:05:18.898 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1_c2 drop constraint f1_pos; 2025-07-03 22:05:18.904 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "f1_pos" of relation "p1_c1c2" 2025-07-03 22:05:18.904 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table p1_c1c2 drop constraint f1_pos; 2025-07-03 22:05:18.937 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_check_constraint" conflicts with NOT VALID constraint on relation "invalid_check_con_child" 2025-07-03 22:05:18.937 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table invalid_check_con add constraint inh_check_constraint check(f1 > 0); 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "invalid_check_con" violates check constraint "inh_check_constraint" 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0). 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into invalid_check_con values(0); 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "invalid_check_con_child" violates check constraint "inh_check_constraint" 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0). 2025-07-03 22:05:18.948 UTC client backend[16479] pg_regress/inherit STATEMENT: insert into invalid_check_con_child values(0); 2025-07-03 22:05:18.979 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-07-03 22:05:18.979 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-2, minus two, 20). 2025-07-03 22:05:18.979 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO v2 VALUES (-2, 'minus two', 20); 2025-07-03 22:05:18.981 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "v2" 2025-07-03 22:05:18.981 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (3, three, 30). 2025-07-03 22:05:18.981 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO v2 VALUES (3, 'three', 30); 2025-07-03 22:05:18.982 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-07-03 22:05:18.982 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-1, ONE, 10). 2025-07-03 22:05:18.982 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE v2 SET a = -1 WHERE a = 1; 2025-07-03 22:05:18.984 UTC client backend[16474] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-07-03 22:05:18.984 UTC client backend[16474] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_1". 2025-07-03 22:05:18.984 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into parted values (1, 1, 'one fail'); 2025-07-03 22:05:18.984 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "v2" 2025-07-03 22:05:18.984 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (1, ONE, 30). 2025-07-03 22:05:18.984 UTC client backend[16491] pg_regress/updatable_views STATEMENT: UPDATE v2 SET c = 30 WHERE a = 1; 2025-07-03 22:05:18.985 UTC client backend[16474] pg_regress/triggers ERROR: moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported 2025-07-03 22:05:18.985 UTC client backend[16474] pg_regress/triggers DETAIL: Before executing trigger "t", the row was to be in partition "public.parted_2". 2025-07-03 22:05:18.985 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into parted values (1, 2, 'two fail'); 2025-07-03 22:05:19.017 UTC client backend[16474] pg_regress/triggers ERROR: constraint triggers cannot be marked NOT VALID at character 54 2025-07-03 22:05:19.017 UTC client backend[16474] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo not valid for each row execute procedure foo (); 2025-07-03 22:05:19.018 UTC client backend[16474] pg_regress/triggers ERROR: constraint triggers cannot be marked NO INHERIT at character 54 2025-07-03 22:05:19.018 UTC client backend[16474] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo no inherit for each row execute procedure foo (); 2025-07-03 22:05:19.025 UTC client backend[16474] pg_regress/triggers ERROR: constraint triggers cannot be marked NOT ENFORCED at character 54 2025-07-03 22:05:19.025 UTC client backend[16474] pg_regress/triggers STATEMENT: create constraint trigger crtr after insert on foo not enforced for each row execute procedure foo (); 2025-07-03 22:05:19.044 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "v1" 2025-07-03 22:05:19.044 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (-1, invalid). 2025-07-03 22:05:19.044 UTC client backend[16491] pg_regress/updatable_views STATEMENT: INSERT INTO v1 VALUES (-1, 'invalid'); 2025-07-03 22:05:19.116 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "uv_ptv_wco" 2025-07-03 22:05:19.116 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (1, 2, null). 2025-07-03 22:05:19.116 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into uv_ptv_wco values (1, 2); 2025-07-03 22:05:19.117 UTC client backend[16491] pg_regress/updatable_views ERROR: MERGE command cannot affect row a second time 2025-07-03 22:05:19.117 UTC client backend[16491] pg_regress/updatable_views HINT: Ensure that not more than one source row matches any one target row. 2025-07-03 22:05:19.117 UTC client backend[16491] pg_regress/updatable_views STATEMENT: merge into uv_ptv t using (values (1,2), (1,4)) as v(a,b) on t.a = v.a -- fail: matches 2 src rows when matched then update set b = t.b + 1 when not matched then insert values (v.a, v.b + 1); 2025-07-03 22:05:19.123 UTC client backend[16491] pg_regress/updatable_views ERROR: no partition of relation "uv_pt1" found for row 2025-07-03 22:05:19.123 UTC client backend[16491] pg_regress/updatable_views DETAIL: Partition key of the failing row contains (b) = (5). 2025-07-03 22:05:19.123 UTC client backend[16491] pg_regress/updatable_views STATEMENT: merge into uv_ptv t using (values (1,2), (1,4)) as v(a,b) on t.a = v.a and t.b = v.b when matched then update set b = t.b + 1 when not matched then insert values (v.a, v.b + 1); 2025-07-03 22:05:19.165 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "wcowrtest_v" 2025-07-03 22:05:19.165 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (1). 2025-07-03 22:05:19.165 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into wcowrtest_v values (1); 2025-07-03 22:05:19.199 UTC client backend[16491] pg_regress/updatable_views ERROR: new row violates check option for view "wcowrtest_v2" 2025-07-03 22:05:19.199 UTC client backend[16491] pg_regress/updatable_views DETAIL: Failing row contains (2, no such row in sometable). 2025-07-03 22:05:19.199 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into wcowrtest_v2 values (2, 'no such row in sometable'); 2025-07-03 22:05:19.275 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-07-03 22:05:19.275 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn NOT NULL a; 2025-07-03 22:05:19.276 UTC client backend[16473] pg_regress/constraints ERROR: null value in column "a" of relation "notnull_tbl1" violates not-null constraint 2025-07-03 22:05:19.276 UTC client backend[16473] pg_regress/constraints DETAIL: Failing row contains (null, 4). 2025-07-03 22:05:19.276 UTC client backend[16473] pg_regress/constraints STATEMENT: INSERT INTO notnull_tbl1 VALUES (NULL, 4); 2025-07-03 22:05:19.288 UTC client backend[16491] pg_regress/updatable_views ERROR: cannot insert into column "cc" of view "uv_iocu_view" 2025-07-03 22:05:19.288 UTC client backend[16491] pg_regress/updatable_views DETAIL: View columns that are not columns of their base relation are not updatable. 2025-07-03 22:05:19.288 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into uv_iocu_view (aa) values (1) on conflict (aa) do update set cc = 'XXX'; 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn" on relation "notnull_tbl1" 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn1 NOT NULL a NOT VALID NO INHERIT; 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints ERROR: incompatible NOT VALID constraint "nn" on relation "notnull_tbl1" 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-07-03 22:05:19.311 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD CONSTRAINT nn NOT NULL a; 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "notnull_tbl1", marked NOT VALID, is incompatible with a primary key. 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ADD PRIMARY KEY (a); 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-07-03 22:05:19.312 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER a SET NOT NULL; 2025-07-03 22:05:19.324 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:19.324 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into rw_view1 values ('yyy',2.0,1) on conflict (aa) do update set bb = excluded.cc; 2025-07-03 22:05:19.325 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:19.325 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into rw_view1 values ('yyy',2.0,1) on conflict (aa) do update set bb = rw_view1.cc; 2025-07-03 22:05:19.332 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:19.332 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into rw_view1 values ('zzz',2.0,1) on conflict (aa) do update set cc = 3.0; 2025-07-03 22:05:19.340 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for table base_tbl 2025-07-03 22:05:19.340 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into rw_view2 (aa,bb) values (1,'xxx') on conflict (aa) do update set bb = excluded.bb; 2025-07-03 22:05:19.354 UTC client backend[16491] pg_regress/updatable_views ERROR: permission denied for view rw_view1 2025-07-03 22:05:19.354 UTC client backend[16491] pg_regress/updatable_views STATEMENT: insert into rw_view4 (aa,bb) values (1,'yyy') on conflict (aa) do update set bb = excluded.bb; 2025-07-03 22:05:19.384 UTC client backend[16473] pg_regress/constraints ERROR: column "a" in child table "notnull_tbl1_child2" must be marked NOT NULL 2025-07-03 22:05:19.384 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1_child2 INHERIT notnull_tbl1; 2025-07-03 22:05:19.401 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1" contains null values 2025-07-03 22:05:19.401 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 VALIDATE CONSTRAINT nn; 2025-07-03 22:05:19.475 UTC client backend[16473] pg_regress/constraints ERROR: constraint "nn_parent" conflicts with NOT VALID constraint on child table "notnull_tbl1" 2025-07-03 22:05:19.475 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 INHERIT notnull_chld0; 2025-07-03 22:05:19.499 UTC client backend[16491] pg_regress/updatable_views LOG: disconnection: session time: 0:00:04.495 user=postgres database=regression host=[local] 2025-07-03 22:05:19.500 UTC client backend[16473] pg_regress/constraints ERROR: incompatible NOT VALID constraint "nn" on relation "notnull_inhchild" 2025-07-03 22:05:19.500 UTC client backend[16473] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-07-03 22:05:19.500 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_inhchild ADD CONSTRAINT nn1 NOT NULL i; 2025-07-03 22:05:19.506 UTC client backend[16479] pg_regress/inherit ERROR: cannot define not-null constraint with NO INHERIT on column "a2" 2025-07-03 22:05:19.506 UTC client backend[16479] pg_regress/inherit DETAIL: The column has an inherited not-null constraint. 2025-07-03 22:05:19.506 UTC client backend[16479] pg_regress/inherit STATEMENT: create table cc3 (a2 int not null no inherit) inherits (cc1); 2025-07-03 22:05:19.507 UTC client backend[16479] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn" on relation "cc2" 2025-07-03 22:05:19.507 UTC client backend[16479] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:19.507 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table cc2 add not null a2 no inherit; 2025-07-03 22:05:19.507 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "nn" of relation "cc2" 2025-07-03 22:05:19.507 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table cc2 alter column a2 drop not null; 2025-07-03 22:05:19.512 UTC client backend[16473] pg_regress/constraints ERROR: table "notnull_tbl1" does not exist 2025-07-03 22:05:19.512 UTC client backend[16473] pg_regress/constraints STATEMENT: DROP TABLE notnull_tbl1; 2025-07-03 22:05:19.542 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "pp1_f1_not_null" of relation "cc2" 2025-07-03 22:05:19.542 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table cc2 alter column f1 drop not null; 2025-07-03 22:05:19.554 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1_3" contains null values 2025-07-03 22:05:19.554 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1 ALTER COLUMN a SET NOT NULL; 2025-07-03 22:05:19.554 UTC client backend[16473] pg_regress/constraints ERROR: column "a" of relation "notnull_tbl1_3" contains null values 2025-07-03 22:05:19.554 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE notnull_tbl1_3 VALIDATE CONSTRAINT nn3; 2025-07-03 22:05:19.580 UTC client backend[16473] pg_regress/constraints ERROR: constraint "nn1" conflicts with NOT VALID constraint on child table "pp_nn_1" 2025-07-03 22:05:19.580 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE pp_nn ATTACH PARTITION pp_nn_1 FOR VALUES IN (NULL,5); 2025-07-03 22:05:19.581 UTC client backend[16479] pg_regress/inherit ERROR: cannot drop inherited constraint "pp1_f1_not_null" of relation "cc1" 2025-07-03 22:05:19.581 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table cc1 alter column f1 drop not null; 2025-07-03 22:05:19.604 UTC client backend[16473] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-07-03 22:05:19.604 UTC client backend[16473] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "pp_nn_1", marked NOT VALID, is incompatible with a primary key. 2025-07-03 22:05:19.604 UTC client backend[16473] pg_regress/constraints HINT: You might need to validate it using ALTER TABLE ... VALIDATE CONSTRAINT. 2025-07-03 22:05:19.604 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE ONLY pp_nn ADD PRIMARY KEY (a); 2025-07-03 22:05:19.611 UTC client backend[16473] pg_regress/constraints ERROR: cannot create primary key on column "a" 2025-07-03 22:05:19.611 UTC client backend[16473] pg_regress/constraints DETAIL: The constraint "nn" on column "a" of table "pp_nn_1", marked NO INHERIT, is incompatible with a primary key. 2025-07-03 22:05:19.611 UTC client backend[16473] pg_regress/constraints HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:19.611 UTC client backend[16473] pg_regress/constraints STATEMENT: ALTER TABLE ONLY pp_nn ADD PRIMARY KEY (a); 2025-07-03 22:05:19.712 UTC client backend[16473] pg_regress/constraints ERROR: constraint "no_constraint" for table "constraint_comments_tbl" does not exist 2025-07-03 22:05:19.712 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON constraint_comments_tbl IS 'yes, the comment'; 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints ERROR: constraint "no_constraint" for domain constraint_comments_dom does not exist 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT no_constraint ON DOMAIN constraint_comments_dom IS 'yes, another comment'; 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints ERROR: relation "no_comments_tbl" does not exist 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON no_comments_tbl IS 'bad comment'; 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints ERROR: type "no_comments_dom" does not exist 2025-07-03 22:05:19.716 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN no_comments_dom IS 'another bad comment'; 2025-07-03 22:05:19.718 UTC client backend[16473] pg_regress/constraints ERROR: must be owner of relation constraint_comments_tbl 2025-07-03 22:05:19.718 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON constraint_comments_tbl IS 'no, the comment'; 2025-07-03 22:05:19.718 UTC client backend[16473] pg_regress/constraints ERROR: must be owner of type constraint_comments_dom 2025-07-03 22:05:19.718 UTC client backend[16473] pg_regress/constraints STATEMENT: COMMENT ON CONSTRAINT the_constraint ON DOMAIN constraint_comments_dom IS 'no, another comment'; 2025-07-03 22:05:19.726 UTC client backend[16473] pg_regress/constraints LOG: disconnection: session time: 0:00:04.833 user=postgres database=regression host=[local] 2025-07-03 22:05:20.080 UTC client backend[16479] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "inh_nn_parent_a_not_null" on relation "inh_nn_parent" 2025-07-03 22:05:20.080 UTC client backend[16479] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:20.080 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_parent ADD CONSTRAINT nna NOT NULL a; 2025-07-03 22:05:20.087 UTC client backend[16479] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "inh_nn_parent_a_not_null" on relation "inh_nn_parent" 2025-07-03 22:05:20.087 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_parent ALTER a SET NOT NULL; 2025-07-03 22:05:20.094 UTC client backend[16479] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "foo" on relation "inh_nn_lvl3" 2025-07-03 22:05:20.094 UTC client backend[16479] pg_regress/inherit HINT: You might need to make the existing constraint inheritable using ALTER TABLE ... ALTER CONSTRAINT ... INHERIT. 2025-07-03 22:05:20.094 UTC client backend[16479] pg_regress/inherit STATEMENT: ALTER TABLE inh_nn_lvl1 ADD PRIMARY KEY (a); 2025-07-03 22:05:20.096 UTC client backend[16479] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:20.096 UTC client backend[16479] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn1 (a int primary key, b int, not null a no inherit); 2025-07-03 22:05:20.102 UTC client backend[16479] pg_regress/inherit ERROR: cannot define not-null constraint with NO INHERIT on column "a" 2025-07-03 22:05:20.102 UTC client backend[16479] pg_regress/inherit DETAIL: The column has an inherited not-null constraint. 2025-07-03 22:05:20.102 UTC client backend[16479] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn2 (a int not null no inherit) INHERITS (inh_nn1); 2025-07-03 22:05:20.103 UTC client backend[16479] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:20.103 UTC client backend[16479] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn3 (a int not null, b int, not null a no inherit); 2025-07-03 22:05:20.104 UTC client backend[16479] pg_regress/inherit ERROR: conflicting NO INHERIT declaration for not-null constraint on column "a" 2025-07-03 22:05:20.104 UTC client backend[16479] pg_regress/inherit STATEMENT: CREATE TABLE inh_nn4 (a int not null no inherit, b int, not null a); 2025-07-03 22:05:20.116 UTC client backend[16479] pg_regress/inherit ERROR: column "f1" in child table "inh_child2" must be marked NOT NULL 2025-07-03 22:05:20.116 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_child2 inherit inh_child1; 2025-07-03 22:05:20.129 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.129 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.129 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (1); 2025-07-03 22:05:20.239 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.239 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.239 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (1); 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (11); 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.243 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (21); 2025-07-03 22:05:20.245 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.245 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.245 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (30); 2025-07-03 22:05:20.246 UTC client backend[16474] pg_regress/triggers ERROR: except 2025-07-03 22:05:20.246 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function tgf() line 1 at RAISE 2025-07-03 22:05:20.246 UTC client backend[16474] pg_regress/triggers STATEMENT: INSERT INTO trgfire VALUES (40); 2025-07-03 22:05:20.319 UTC client backend[16479] pg_regress/inherit ERROR: column "a" in child table "inh_child" must be marked NOT NULL 2025-07-03 22:05:20.319 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_child inherit inh_parent; 2025-07-03 22:05:20.325 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_child_a_not_null" conflicts with non-inherited constraint on child table "inh_child" 2025-07-03 22:05:20.325 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_child inherit inh_parent; 2025-07-03 22:05:20.505 UTC client backend[16479] pg_regress/inherit ERROR: column "f1" of relation "inh_nn2" contains null values 2025-07-03 22:05:20.505 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_not_null inherit; 2025-07-03 22:05:20.546 UTC client backend[16479] pg_regress/inherit ERROR: cannot change NO INHERIT status of NOT NULL constraint "nn3_f1" on relation "inh_nn3" 2025-07-03 22:05:20.546 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_not_null inherit; 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_nn1_f1_check" of relation "inh_nn1" is not a not-null constraint 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_check inherit; 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_nn1_pkey" of relation "inh_nn1" is not a not-null constraint 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_pkey inherit; 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit ERROR: constraint "inh_nn1_f1_fkey" of relation "inh_nn1" is not a not-null constraint 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint inh_nn1_f1_fkey inherit; 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit ERROR: constraint "foo" of relation "inh_nn1" does not exist 2025-07-03 22:05:20.579 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn1 alter constraint foo inherit; 2025-07-03 22:05:20.581 UTC client backend[16479] pg_regress/inherit ERROR: cannot alter inherited constraint "inh_nn1_f2_not_null" on relation "inh_nn2" 2025-07-03 22:05:20.581 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_nn2 alter constraint inh_nn1_f2_not_null no inherit; 2025-07-03 22:05:20.589 UTC client backend[16474] pg_regress/triggers ERROR: ROW triggers with transition tables are not supported on partitions 2025-07-03 22:05:20.589 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger child_row_trig after insert on child referencing new table as new_table for each row execute procedure dump_insert(); 2025-07-03 22:05:20.599 UTC client backend[16474] pg_regress/triggers ERROR: trigger "child_row_trig" prevents table "child" from becoming a partition 2025-07-03 22:05:20.599 UTC client backend[16474] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported on partitions. 2025-07-03 22:05:20.599 UTC client backend[16474] pg_regress/triggers STATEMENT: alter table parent attach partition child for values in ('AAA'); 2025-07-03 22:05:20.602 UTC client backend[16479] pg_regress/inherit ERROR: must be owner of table inh_child 2025-07-03 22:05:20.602 UTC client backend[16479] pg_regress/inherit STATEMENT: alter table inh_parent alter a drop not null; 2025-07-03 22:05:20.618 UTC client backend[16479] pg_regress/inherit ERROR: cannot inherit from temporary relation "inh_temp_parent" 2025-07-03 22:05:20.618 UTC client backend[16479] pg_regress/inherit STATEMENT: create table inh_perm_child () inherits (inh_temp_parent); 2025-07-03 22:05:21.129 UTC client backend[16474] pg_regress/triggers ERROR: ROW triggers with transition tables are not supported on inheritance children 2025-07-03 22:05:21.129 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger child_row_trig after insert on child referencing new table as new_table for each row execute procedure dump_insert(); 2025-07-03 22:05:21.147 UTC client backend[16474] pg_regress/triggers ERROR: trigger "child_row_trig" prevents table "child" from becoming an inheritance child 2025-07-03 22:05:21.147 UTC client backend[16474] pg_regress/triggers DETAIL: ROW triggers with transition tables are not supported in inheritance hierarchies. 2025-07-03 22:05:21.147 UTC client backend[16474] pg_regress/triggers STATEMENT: alter table child inherit parent; 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0, 1, 10). 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', '10'); 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 1, 10). 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', '10'); 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 1, 10). 2025-07-03 22:05:21.227 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', '10'); 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_fastdef" violates not-null constraint 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0, 1, null). 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', NULL); 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_plaindef" violates not-null constraint 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 1, null). 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', NULL); 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit ERROR: null value in column "data" of relation "errtst_child_reorder" violates not-null constraint 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 1, null). 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', NULL); 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "shdata_small" 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0, 5, 5). 2025-07-03 22:05:21.228 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '5', '5'); 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "shdata_small" 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 5, 5). 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '5', '5'); 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "shdata_small" 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 5, 5). 2025-07-03 22:05:21.229 UTC client backend[16479] pg_regress/inherit STATEMENT: INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '5', '5'); 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0, 1, 15). 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 0; 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 1, 15). 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 10; 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 1, 15). 2025-07-03 22:05:21.232 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET data = data + 10 WHERE partid = 20; 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates partition constraint 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 1, 5). 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_child_fastdef SET partid = partid + 10 WHERE partid = 0; 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates partition constraint 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 1, 5). 2025-07-03 22:05:21.239 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_child_plaindef SET partid = partid + 10 WHERE partid = 10; 2025-07-03 22:05:21.240 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates partition constraint 2025-07-03 22:05:21.240 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (5, 1, 30). 2025-07-03 22:05:21.240 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_child_reorder SET partid = partid + 10 WHERE partid = 20; 2025-07-03 22:05:21.241 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check" 2025-07-03 22:05:21.241 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (10, 1, 15). 2025-07-03 22:05:21.241 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 10, data = data + 10 WHERE partid = 0; 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check" 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (20, 1, 15). 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 20, data = data + 10 WHERE partid = 10; 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit ERROR: new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check" 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit DETAIL: Failing row contains (0, 1, 15). 2025-07-03 22:05:21.242 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 0, data = data + 10 WHERE partid = 20; 2025-07-03 22:05:21.243 UTC client backend[16479] pg_regress/inherit ERROR: no partition of relation "errtst_parent" found for row 2025-07-03 22:05:21.243 UTC client backend[16479] pg_regress/inherit DETAIL: Partition key of the failing row contains (partid) = (30). 2025-07-03 22:05:21.243 UTC client backend[16479] pg_regress/inherit STATEMENT: UPDATE errtst_parent SET partid = 30, data = data + 10 WHERE partid = 20; 2025-07-03 22:05:21.313 UTC client backend[16479] pg_regress/inherit LOG: disconnection: session time: 0:00:06.387 user=postgres database=regression host=[local] 2025-07-03 22:05:21.485 UTC client backend[16474] pg_regress/triggers ERROR: transition tables cannot be specified for triggers with more than one event 2025-07-03 22:05:21.485 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger my_table_multievent_trig after insert or update on my_table referencing new table as new_table for each statement execute procedure dump_insert(); 2025-07-03 22:05:21.487 UTC client backend[16474] pg_regress/triggers ERROR: transition tables cannot be specified for triggers with column lists 2025-07-03 22:05:21.487 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger my_table_col_update_trig after update of b on my_table referencing new table as new_table for each statement execute procedure dump_insert(); 2025-07-03 22:05:21.530 UTC client backend[16474] pg_regress/triggers ERROR: transition table "new_table" cannot be referenced in a persistent object 2025-07-03 22:05:21.530 UTC client backend[16474] pg_regress/triggers CONTEXT: SQL statement "create materialized view transition_test_mv as select * from new_table" PL/pgSQL function make_bogus_matview() line 2 at SQL statement 2025-07-03 22:05:21.530 UTC client backend[16474] pg_regress/triggers STATEMENT: insert into my_table values (42); 2025-07-03 22:05:21.919 UTC client backend[16474] pg_regress/triggers ERROR: trigger "my_trig" for relation "my_table" already exists 2025-07-03 22:05:21.919 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger my_trig before insert on my_table for each row execute procedure funcB(); 2025-07-03 22:05:22.050 UTC client backend[16474] pg_regress/triggers ERROR: trigger "my_trig" for relation "parted_trig_1" is an internal or a child trigger 2025-07-03 22:05:22.050 UTC client backend[16474] pg_regress/triggers STATEMENT: create or replace trigger my_trig after insert on parted_trig_1 for each row execute procedure funcB(); 2025-07-03 22:05:22.079 UTC client backend[16474] pg_regress/triggers ERROR: trigger "my_trig" for relation "parted_trig_1" already exists 2025-07-03 22:05:22.079 UTC client backend[16474] pg_regress/triggers STATEMENT: create trigger my_trig after insert on parted_trig for each row execute procedure funcB(); 2025-07-03 22:05:22.410 UTC client backend[16474] pg_regress/triggers ERROR: BOOM! 2025-07-03 22:05:22.410 UTC client backend[16474] pg_regress/triggers CONTEXT: PL/pgSQL function convslot_trig4() line 1 at RAISE 2025-07-03 22:05:22.410 UTC client backend[16474] pg_regress/triggers STATEMENT: update convslot_test_parent set val = 3; 2025-07-03 22:05:22.482 UTC client backend[16474] pg_regress/triggers ERROR: syntax error at or near "only" at character 20 2025-07-03 22:05:22.482 UTC client backend[16474] pg_regress/triggers STATEMENT: alter trigger a on only grandparent rename to b; 2025-07-03 22:05:22.482 UTC client backend[16474] pg_regress/triggers ERROR: cannot rename trigger "b" on table "middle" 2025-07-03 22:05:22.482 UTC client backend[16474] pg_regress/triggers HINT: Rename the trigger on the partitioned table "grandparent" instead. 2025-07-03 22:05:22.482 UTC client backend[16474] pg_regress/triggers STATEMENT: alter trigger b on middle rename to c; 2025-07-03 22:05:22.485 UTC client backend[16474] pg_regress/triggers ERROR: trigger "c" for relation "middle" already exists 2025-07-03 22:05:22.485 UTC client backend[16474] pg_regress/triggers STATEMENT: alter trigger b on grandparent rename to c; 2025-07-03 22:05:22.788 UTC client backend[16474] pg_regress/triggers ERROR: division by zero 2025-07-03 22:05:22.788 UTC client backend[16474] pg_regress/triggers CONTEXT: SQL statement "SELECT 1 / 0" PL/pgSQL function whoami() line 4 at PERFORM 2025-07-03 22:05:22.788 UTC client backend[16474] pg_regress/triggers STATEMENT: commit; 2025-07-03 22:05:22.829 UTC client backend[16474] pg_regress/triggers LOG: disconnection: session time: 0:00:07.904 user=postgres database=regression host=[local] 2025-07-03 22:05:23.322 UTC not initialized[17097] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:23.324 UTC client backend[17097] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:23.324 UTC client backend[17097] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sanity_check 2025-07-03 22:05:23.327 UTC client backend[17097] pg_regress/sanity_check LOG: connection ready: setup total=16.279 ms, fork=8.590 ms, authentication=0.413 ms 2025-07-03 22:05:23.929 UTC client backend[17097] pg_regress/sanity_check LOG: disconnection: session time: 0:00:00.610 user=postgres database=regression host=[local] 2025-07-03 22:05:24.064 UTC not initialized[17194] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.067 UTC not initialized[17195] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.069 UTC client backend[17195] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.069 UTC client backend[17195] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/union 2025-07-03 22:05:24.071 UTC not initialized[17198] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.071 UTC not initialized[17196] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.072 UTC client backend[17198] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.072 UTC client backend[17198] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/subselect 2025-07-03 22:05:24.072 UTC client backend[17196] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.072 UTC client backend[17196] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/join 2025-07-03 22:05:24.074 UTC not initialized[17197] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.078 UTC client backend[17197] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.078 UTC client backend[17197] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_distinct_on 2025-07-03 22:05:24.085 UTC client backend[17194] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.085 UTC client backend[17194] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_implicit 2025-07-03 22:05:24.085 UTC not initialized[17199] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.086 UTC not initialized[17200] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.086 UTC client backend[17199] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.086 UTC client backend[17199] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/case 2025-07-03 22:05:24.087 UTC client backend[17200] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.087 UTC client backend[17200] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/random 2025-07-03 22:05:24.095 UTC not initialized[17201] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.096 UTC client backend[17201] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.096 UTC client backend[17201] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/portals 2025-07-03 22:05:24.099 UTC not initialized[17204] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.099 UTC not initialized[17202] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.100 UTC client backend[17202] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.100 UTC client backend[17202] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_distinct 2025-07-03 22:05:24.105 UTC not initialized[17207] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.106 UTC client backend[17207] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.106 UTC client backend[17207] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_having 2025-07-03 22:05:24.107 UTC client backend[17204] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.107 UTC client backend[17204] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/aggregates 2025-07-03 22:05:24.111 UTC not initialized[17205] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.112 UTC client backend[17205] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.112 UTC client backend[17205] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_into 2025-07-03 22:05:24.127 UTC not initialized[17208] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.134 UTC client backend[17208] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.134 UTC client backend[17208] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/transactions 2025-07-03 22:05:24.134 UTC not initialized[17210] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.135 UTC not initialized[17209] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.136 UTC client backend[17210] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.136 UTC client backend[17210] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/arrays 2025-07-03 22:05:24.140 UTC client backend[17209] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.140 UTC client backend[17209] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/btree_index 2025-07-03 22:05:24.143 UTC not initialized[17211] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.144 UTC client backend[17211] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.144 UTC client backend[17211] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/update 2025-07-03 22:05:24.155 UTC not initialized[17212] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.156 UTC client backend[17212] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.156 UTC client backend[17212] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/hash_index 2025-07-03 22:05:24.175 UTC not initialized[17215] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.176 UTC client backend[17215] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.177 UTC client backend[17215] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/namespace 2025-07-03 22:05:24.183 UTC not initialized[17214] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.183 UTC not initialized[17216] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.186 UTC client backend[17214] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.186 UTC client backend[17214] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/delete 2025-07-03 22:05:24.188 UTC client backend[17216] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.188 UTC client backend[17216] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/prepared_xacts 2025-07-03 22:05:24.191 UTC client backend[17216] pg_regress/prepared_xacts LOG: connection ready: setup total=33.918 ms, fork=22.597 ms, authentication=0.398 ms 2025-07-03 22:05:24.193 UTC client backend[17197] pg_regress/select_distinct_on LOG: connection ready: setup total=142.691 ms, fork=17.346 ms, authentication=0.403 ms 2025-07-03 22:05:24.212 UTC client backend[17204] pg_regress/aggregates LOG: connection ready: setup total=138.937 ms, fork=25.109 ms, authentication=3.568 ms 2025-07-03 22:05:24.213 UTC client backend[17195] pg_regress/union LOG: connection ready: setup total=172.300 ms, fork=18.798 ms, authentication=0.890 ms 2025-07-03 22:05:24.222 UTC client backend[17199] pg_regress/case LOG: connection ready: setup total=159.889 ms, fork=20.884 ms, authentication=0.366 ms 2025-07-03 22:05:24.226 UTC client backend[17196] pg_regress/join LOG: connection ready: setup total=180.116 ms, fork=22.556 ms, authentication=0.380 ms 2025-07-03 22:05:24.230 UTC client backend[17207] pg_regress/select_having LOG: connection ready: setup total=137.445 ms, fork=11.569 ms, authentication=0.372 ms 2025-07-03 22:05:24.243 UTC client backend[17197] pg_regress/select_distinct_on ERROR: SELECT DISTINCT ON expressions must match initial ORDER BY expressions at character 30 2025-07-03 22:05:24.243 UTC client backend[17197] pg_regress/select_distinct_on STATEMENT: SELECT DISTINCT ON (string4, ten) string4, two, ten FROM onek ORDER BY string4 using <, two using <, ten using <; 2025-07-03 22:05:24.248 UTC client backend[17200] pg_regress/random LOG: connection ready: setup total=182.038 ms, fork=16.793 ms, authentication=0.349 ms 2025-07-03 22:05:24.254 UTC client backend[17194] pg_regress/select_implicit LOG: connection ready: setup total=215.737 ms, fork=20.045 ms, authentication=0.401 ms 2025-07-03 22:05:24.260 UTC client backend[17198] pg_regress/subselect LOG: connection ready: setup total=206.214 ms, fork=15.054 ms, authentication=0.414 ms 2025-07-03 22:05:24.266 UTC client backend[17201] pg_regress/portals LOG: connection ready: setup total=195.739 ms, fork=23.987 ms, authentication=0.384 ms 2025-07-03 22:05:24.268 UTC client backend[17208] pg_regress/transactions LOG: connection ready: setup total=173.813 ms, fork=30.924 ms, authentication=5.997 ms 2025-07-03 22:05:24.277 UTC client backend[17202] pg_regress/select_distinct LOG: connection ready: setup total=205.342 ms, fork=22.986 ms, authentication=0.372 ms 2025-07-03 22:05:24.280 UTC client backend[17205] pg_regress/select_into LOG: connection ready: setup total=189.120 ms, fork=16.902 ms, authentication=0.353 ms 2025-07-03 22:05:24.291 UTC client backend[17209] pg_regress/btree_index LOG: connection ready: setup total=187.616 ms, fork=30.360 ms, authentication=0.349 ms 2025-07-03 22:05:24.304 UTC client backend[17210] pg_regress/arrays LOG: connection ready: setup total=197.374 ms, fork=27.440 ms, authentication=0.414 ms 2025-07-03 22:05:24.305 UTC client backend[17211] pg_regress/update LOG: connection ready: setup total=197.419 ms, fork=30.632 ms, authentication=0.365 ms 2025-07-03 22:05:24.326 UTC client backend[17194] pg_regress/select_implicit ERROR: column "test_missing_target.b" must appear in the GROUP BY clause or be used in an aggregate function at character 62 2025-07-03 22:05:24.326 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT count(*) FROM test_missing_target GROUP BY a ORDER BY b; 2025-07-03 22:05:24.329 UTC client backend[17215] pg_regress/namespace LOG: connection ready: setup total=173.989 ms, fork=9.549 ms, authentication=0.386 ms 2025-07-03 22:05:24.331 UTC client backend[17212] pg_regress/hash_index LOG: connection ready: setup total=222.552 ms, fork=40.338 ms, authentication=0.403 ms 2025-07-03 22:05:24.336 UTC client backend[17199] pg_regress/case ERROR: division by zero 2025-07-03 22:05:24.336 UTC client backend[17199] pg_regress/case STATEMENT: SELECT CASE WHEN i > 100 THEN 1/0 ELSE 0 END FROM case_tbl; 2025-07-03 22:05:24.341 UTC client backend[17214] pg_regress/delete LOG: connection ready: setup total=230.385 ms, fork=64.217 ms, authentication=0.410 ms 2025-07-03 22:05:24.351 UTC client backend[17207] pg_regress/select_having ERROR: column "test_having.a" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:05:24.351 UTC client backend[17207] pg_regress/select_having STATEMENT: SELECT a FROM test_having HAVING min(a) < max(a); 2025-07-03 22:05:24.354 UTC client backend[17207] pg_regress/select_having ERROR: column "test_having.a" must appear in the GROUP BY clause or be used in an aggregate function at character 41 2025-07-03 22:05:24.354 UTC client backend[17207] pg_regress/select_having STATEMENT: SELECT 1 AS one FROM test_having HAVING a > 1; 2025-07-03 22:05:24.355 UTC client backend[17216] pg_regress/prepared_xacts ERROR: transaction identifier "regress_foo3" is already in use 2025-07-03 22:05:24.355 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: PREPARE TRANSACTION 'regress_foo3'; 2025-07-03 22:05:24.358 UTC client backend[17194] pg_regress/select_implicit ERROR: GROUP BY position 3 is not in select list at character 54 2025-07-03 22:05:24.358 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT c, count(*) FROM test_missing_target GROUP BY 3; 2025-07-03 22:05:24.359 UTC client backend[17194] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 105 2025-07-03 22:05:24.359 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT count(*) FROM test_missing_target x, test_missing_target y WHERE x.a = y.a GROUP BY b ORDER BY b; 2025-07-03 22:05:24.360 UTC client backend[17196] pg_regress/join ERROR: column reference "i" is ambiguous at character 8 2025-07-03 22:05:24.360 UTC client backend[17196] pg_regress/join STATEMENT: SELECT i, k, t FROM J1_TBL CROSS JOIN J2_TBL; 2025-07-03 22:05:24.367 UTC client backend[17208] pg_regress/transactions ERROR: parameter "transaction_isolation" cannot be reset 2025-07-03 22:05:24.367 UTC client backend[17208] pg_regress/transactions STATEMENT: RESET transaction_isolation; 2025-07-03 22:05:24.368 UTC client backend[17208] pg_regress/transactions ERROR: parameter "transaction_read_only" cannot be reset 2025-07-03 22:05:24.368 UTC client backend[17208] pg_regress/transactions STATEMENT: RESET transaction_read_only; 2025-07-03 22:05:24.368 UTC client backend[17208] pg_regress/transactions ERROR: parameter "transaction_deferrable" cannot be reset 2025-07-03 22:05:24.368 UTC client backend[17208] pg_regress/transactions STATEMENT: RESET transaction_deferrable; 2025-07-03 22:05:24.369 UTC client backend[17208] pg_regress/transactions ERROR: parameter "transaction_read_only" cannot be set locally in functions 2025-07-03 22:05:24.369 UTC client backend[17208] pg_regress/transactions STATEMENT: CREATE FUNCTION errfunc() RETURNS int LANGUAGE SQL AS 'SELECT 1' SET transaction_read_only = on; 2025-07-03 22:05:24.382 UTC client backend[17216] pg_regress/prepared_xacts ERROR: could not serialize access due to read/write dependencies among transactions 2025-07-03 22:05:24.382 UTC client backend[17216] pg_regress/prepared_xacts DETAIL: Reason code: Canceled on identification as a pivot, during write. 2025-07-03 22:05:24.382 UTC client backend[17216] pg_regress/prepared_xacts HINT: The transaction might succeed if retried. 2025-07-03 22:05:24.382 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: INSERT INTO pxtest1 VALUES ('fff'); 2025-07-03 22:05:24.395 UTC client backend[17208] pg_regress/transactions ERROR: transaction read-write mode must be set before any query 2025-07-03 22:05:24.395 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-07-03 22:05:24.397 UTC client backend[17208] pg_regress/transactions ERROR: cannot set transaction read-write mode inside a read-only transaction 2025-07-03 22:05:24.397 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-07-03 22:05:24.407 UTC client backend[17207] pg_regress/select_having LOG: disconnection: session time: 0:00:00.302 user=postgres database=regression host=[local] 2025-07-03 22:05:24.415 UTC client backend[17208] pg_regress/transactions ERROR: cannot set transaction read-write mode inside a read-only transaction 2025-07-03 22:05:24.415 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION READ WRITE; 2025-07-03 22:05:24.419 UTC client backend[17208] pg_regress/transactions ERROR: cannot execute DROP TABLE in a read-only transaction 2025-07-03 22:05:24.419 UTC client backend[17208] pg_regress/transactions STATEMENT: DROP TABLE writetest; 2025-07-03 22:05:24.419 UTC client backend[17208] pg_regress/transactions ERROR: cannot execute INSERT in a read-only transaction 2025-07-03 22:05:24.419 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO writetest VALUES (1); 2025-07-03 22:05:24.430 UTC client backend[17205] pg_regress/select_into ERROR: permission denied for table tbl_withdata1 2025-07-03 22:05:24.430 UTC client backend[17205] pg_regress/select_into STATEMENT: INSERT INTO selinto_schema.tbl_withdata1 VALUES (4); 2025-07-03 22:05:24.431 UTC client backend[17198] pg_regress/subselect ERROR: more than one row returned by a subquery used as an expression 2025-07-03 22:05:24.431 UTC client backend[17198] pg_regress/subselect STATEMENT: SELECT ROW(1, 2) = (SELECT f1, f2 FROM SUBSELECT_TBL); 2025-07-03 22:05:24.431 UTC client backend[17208] pg_regress/transactions ERROR: cannot execute UPDATE in a read-only transaction 2025-07-03 22:05:24.431 UTC client backend[17208] pg_regress/transactions STATEMENT: EXECUTE test; 2025-07-03 22:05:24.433 UTC client backend[17211] pg_regress/update ERROR: column "t" of relation "update_test" does not exist at character 26 2025-07-03 22:05:24.433 UTC client backend[17211] pg_regress/update HINT: SET target columns cannot be qualified with the relation name. 2025-07-03 22:05:24.433 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test t SET t.b = t.b + 10 WHERE t.a = 10; 2025-07-03 22:05:24.434 UTC client backend[17208] pg_regress/transactions ERROR: cannot execute CREATE TABLE AS in a read-only transaction 2025-07-03 22:05:24.434 UTC client backend[17208] pg_regress/transactions STATEMENT: CREATE TABLE test AS SELECT * FROM writetest; 2025-07-03 22:05:24.434 UTC client backend[17211] pg_regress/update ERROR: column "a" is of type integer but expression is of type record at character 28 2025-07-03 22:05:24.434 UTC client backend[17211] pg_regress/update HINT: You will need to rewrite or cast the expression. 2025-07-03 22:05:24.434 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test SET a = v.* FROM (VALUES(100, 20)) AS v(i, j) WHERE update_test.b = v.j; 2025-07-03 22:05:24.437 UTC client backend[17195] pg_regress/union ERROR: FOR NO KEY UPDATE is not allowed with UNION/INTERSECT/EXCEPT 2025-07-03 22:05:24.437 UTC client backend[17195] pg_regress/union STATEMENT: SELECT q1 FROM int8_tbl EXCEPT ALL SELECT q1 FROM int8_tbl FOR NO KEY UPDATE; 2025-07-03 22:05:24.438 UTC client backend[17194] pg_regress/select_implicit ERROR: column "test_missing_target.b" must appear in the GROUP BY clause or be used in an aggregate function at character 62 2025-07-03 22:05:24.438 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT count(a) FROM test_missing_target GROUP BY a ORDER BY b; 2025-07-03 22:05:24.446 UTC client backend[17216] pg_regress/prepared_xacts ERROR: cannot PREPARE while holding both session-level and transaction-level locks on the same object 2025-07-03 22:05:24.446 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: PREPARE TRANSACTION 'regress_foo6'; 2025-07-03 22:05:24.453 UTC client backend[17214] pg_regress/delete ERROR: invalid reference to FROM-clause entry for table "delete_test" at character 34 2025-07-03 22:05:24.453 UTC client backend[17214] pg_regress/delete HINT: Perhaps you meant to reference the table alias "dt". 2025-07-03 22:05:24.453 UTC client backend[17214] pg_regress/delete STATEMENT: DELETE FROM delete_test dt WHERE delete_test.a > 25; 2025-07-03 22:05:24.457 UTC client backend[17211] pg_regress/update ERROR: multiple assignments to same column "b" 2025-07-03 22:05:24.457 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test SET (c,b) = ('car', a+b), b = a + 1 WHERE a = 10; 2025-07-03 22:05:24.459 UTC client backend[17194] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 109 2025-07-03 22:05:24.459 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT count(x.a) FROM test_missing_target x, test_missing_target y WHERE x.a = y.a GROUP BY b/2 ORDER BY b/2; 2025-07-03 22:05:24.460 UTC client backend[17194] pg_regress/select_implicit ERROR: column reference "b" is ambiguous at character 14 2025-07-03 22:05:24.460 UTC client backend[17194] pg_regress/select_implicit STATEMENT: SELECT count(b) FROM test_missing_target x, test_missing_target y WHERE x.a = y.a GROUP BY x.b/2; 2025-07-03 22:05:24.461 UTC client backend[17215] pg_regress/namespace ERROR: column "c" does not exist at character 70 2025-07-03 22:05:24.461 UTC client backend[17215] pg_regress/namespace STATEMENT: CREATE SCHEMA test_ns_schema_2 CREATE VIEW abc_view AS SELECT c FROM abc; 2025-07-03 22:05:24.473 UTC client backend[17200] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-07-03 22:05:24.473 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random(1, 0); 2025-07-03 22:05:24.473 UTC client backend[17216] pg_regress/prepared_xacts ERROR: cursor "foo" does not exist 2025-07-03 22:05:24.473 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: FETCH 1 FROM foo; 2025-07-03 22:05:24.473 UTC client backend[17216] pg_regress/prepared_xacts ERROR: relation "pxtest2" does not exist at character 15 2025-07-03 22:05:24.473 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: SELECT * FROM pxtest2; 2025-07-03 22:05:24.473 UTC client backend[17200] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-07-03 22:05:24.473 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random(1000000000001, 1000000000000); 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random ERROR: lower bound must be less than or equal to upper bound 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random(-2.0, -3.0); 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random ERROR: lower bound cannot be NaN 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random('NaN'::numeric, 10); 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random ERROR: lower bound cannot be infinity 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random('-Inf'::numeric, 0); 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random ERROR: upper bound cannot be NaN 2025-07-03 22:05:24.474 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random(0, 'NaN'::numeric); 2025-07-03 22:05:24.475 UTC client backend[17200] pg_regress/random ERROR: upper bound cannot be infinity 2025-07-03 22:05:24.475 UTC client backend[17200] pg_regress/random STATEMENT: SELECT random(0, 'Inf'::numeric); 2025-07-03 22:05:24.477 UTC client backend[17210] pg_regress/arrays ERROR: value too long for type character(5) 2025-07-03 22:05:24.477 UTC client backend[17210] pg_regress/arrays STATEMENT: INSERT INTO arrtest (f) VALUES ('{"too long"}'); 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays ERROR: subscripted assignment to "b" requires type integer but expression is of type timestamp with time zone at character 22 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays HINT: You will need to rewrite or cast the expression. 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays STATEMENT: INSERT INTO arrtest (b[2]) VALUES(now()); 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays ERROR: subscripted assignment to "b" requires type integer[] but expression is of type timestamp with time zone at character 22 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays HINT: You will need to rewrite or cast the expression. 2025-07-03 22:05:24.478 UTC client backend[17210] pg_regress/arrays STATEMENT: INSERT INTO arrtest (b[1:2]) VALUES(now()); 2025-07-03 22:05:24.480 UTC client backend[17211] pg_regress/update ERROR: more than one row returned by a subquery used as an expression 2025-07-03 22:05:24.480 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test SET (b,a) = (select a+1,b from update_test); 2025-07-03 22:05:24.481 UTC client backend[17211] pg_regress/update ERROR: source for a multiple-column UPDATE item must be a sub-SELECT or ROW() expression at character 33 2025-07-03 22:05:24.481 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test SET (a,b) = (v.*) FROM (VALUES(21, 101)) AS v(i, j) WHERE update_test.a = v.i; 2025-07-03 22:05:24.481 UTC client backend[17211] pg_regress/update ERROR: invalid reference to FROM-clause entry for table "update_test" at character 33 2025-07-03 22:05:24.481 UTC client backend[17211] pg_regress/update HINT: Perhaps you meant to reference the table alias "t". 2025-07-03 22:05:24.481 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE update_test AS t SET b = update_test.b + 10 WHERE t.a = 10; 2025-07-03 22:05:24.491 UTC client backend[17216] pg_regress/prepared_xacts ERROR: could not obtain lock on relation "pxtest3" 2025-07-03 22:05:24.491 UTC client backend[17216] pg_regress/prepared_xacts STATEMENT: lock table pxtest3 in access share mode nowait; 2025-07-03 22:05:24.510 UTC client backend[17201] pg_regress/portals ERROR: cursor can only scan forward 2025-07-03 22:05:24.510 UTC client backend[17201] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-07-03 22:05:24.510 UTC client backend[17201] pg_regress/portals STATEMENT: FETCH BACKWARD 1 FROM foo24; 2025-07-03 22:05:24.519 UTC client backend[17214] pg_regress/delete LOG: disconnection: session time: 0:00:00.344 user=postgres database=regression host=[local] 2025-07-03 22:05:24.520 UTC client backend[17197] pg_regress/select_distinct_on LOG: disconnection: session time: 0:00:00.452 user=postgres database=regression host=[local] 2025-07-03 22:05:24.524 UTC not initialized[17237] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:24.528 UTC client backend[17201] pg_regress/portals ERROR: cursor can only scan forward 2025-07-03 22:05:24.528 UTC client backend[17201] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-07-03 22:05:24.528 UTC client backend[17201] pg_regress/portals STATEMENT: FETCH ABSOLUTE 1 FROM foo24; 2025-07-03 22:05:24.529 UTC client backend[17194] pg_regress/select_implicit LOG: disconnection: session time: 0:00:00.470 user=postgres database=regression host=[local] 2025-07-03 22:05:24.534 UTC client backend[17237] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:24.536 UTC client backend[17208] pg_regress/transactions ERROR: relation "trans_bar" does not exist at character 15 2025-07-03 22:05:24.536 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT * FROM trans_bar; 2025-07-03 22:05:24.534 UTC client backend[17237] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/prepared_xacts 2025-07-03 22:05:24.540 UTC client backend[17215] pg_regress/namespace ERROR: schema "test_ns_schema_renamed" already exists 2025-07-03 22:05:24.540 UTC client backend[17215] pg_regress/namespace STATEMENT: CREATE SCHEMA test_ns_schema_renamed; 2025-07-03 22:05:24.544 UTC client backend[17215] pg_regress/namespace ERROR: CREATE SCHEMA IF NOT EXISTS cannot include schema elements at character 79 2025-07-03 22:05:24.544 UTC client backend[17215] pg_regress/namespace STATEMENT: CREATE SCHEMA IF NOT EXISTS test_ns_schema_renamed -- fail, disallowed CREATE TABLE abc ( a serial, b int UNIQUE ); 2025-07-03 22:05:24.549 UTC client backend[17208] pg_regress/transactions ERROR: relation "trans_bar" does not exist at character 13 2025-07-03 22:05:24.549 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT into trans_bar VALUES (1); 2025-07-03 22:05:24.552 UTC client backend[17237] pg_regress/prepared_xacts LOG: connection ready: setup total=60.295 ms, fork=22.749 ms, authentication=0.415 ms 2025-07-03 22:05:24.552 UTC client backend[17216] pg_regress/prepared_xacts LOG: disconnection: session time: 0:00:00.373 user=postgres database=regression host=[local] 2025-07-03 22:05:24.564 UTC client backend[17208] pg_regress/transactions ERROR: column "trans_foo" does not exist at character 8 2025-07-03 22:05:24.564 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT trans_foo; 2025-07-03 22:05:24.571 UTC client backend[17199] pg_regress/case LOG: disconnection: session time: 0:00:00.488 user=postgres database=regression host=[local] 2025-07-03 22:05:24.573 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:24.581 UTC client backend[17205] pg_regress/select_into ERROR: too many column names were specified 2025-07-03 22:05:24.581 UTC client backend[17205] pg_regress/select_into STATEMENT: CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base; 2025-07-03 22:05:24.582 UTC client backend[17205] pg_regress/select_into ERROR: too many column names were specified 2025-07-03 22:05:24.582 UTC client backend[17205] pg_regress/select_into STATEMENT: CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base WITH NO DATA; 2025-07-03 22:05:24.582 UTC client backend[17210] pg_regress/arrays ERROR: number of array dimensions (7) exceeds the maximum allowed (6) 2025-07-03 22:05:24.582 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT ('{}'::int[])[1][2][3][4][5][6][7]; 2025-07-03 22:05:24.589 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:24.590 UTC client backend[17208] pg_regress/transactions ERROR: column "trans_foo" does not exist at character 8 2025-07-03 22:05:24.590 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT trans_foo; 2025-07-03 22:05:24.594 UTC client backend[17210] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-07-03 22:05:24.594 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[NULL] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[NULL:1] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays ERROR: array subscript in assignment must not be null 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE arrtest SET c[1:NULL] = '{"can''t assign"}' WHERE array_dims(c) is not null; 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays ERROR: cannot subscript type timestamp with time zone because it does not support subscripting at character 9 2025-07-03 22:05:24.599 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT (now())[1]; 2025-07-03 22:05:24.619 UTC client backend[17237] pg_regress/prepared_xacts ERROR: could not obtain lock on relation "pxtest3" 2025-07-03 22:05:24.619 UTC client backend[17237] pg_regress/prepared_xacts STATEMENT: lock table pxtest3 in access share mode nowait; 2025-07-03 22:05:24.656 UTC client backend[17201] pg_regress/portals ERROR: cursor can only scan forward 2025-07-03 22:05:24.656 UTC client backend[17201] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-07-03 22:05:24.656 UTC client backend[17201] pg_regress/portals STATEMENT: FETCH ABSOLUTE 4 FROM foo25ns; 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions STATEMENT: SAVEPOINT one; 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK TO SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions STATEMENT: ROLLBACK TO SAVEPOINT one; 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions ERROR: RELEASE SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:24.663 UTC client backend[17208] pg_regress/transactions STATEMENT: RELEASE SAVEPOINT one; 2025-07-03 22:05:24.664 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:24.664 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 0/0; 2025-07-03 22:05:24.665 UTC client backend[17210] pg_regress/arrays ERROR: source array too small 2025-07-03 22:05:24.665 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE arrtest_s SET a[:] = '{23, 24, 25}'; 2025-07-03 22:05:24.666 UTC client backend[17210] pg_regress/arrays ERROR: array slice subscript must provide both boundaries 2025-07-03 22:05:24.666 UTC client backend[17210] pg_regress/arrays DETAIL: When assigning to a slice of an empty array value, slice boundaries must be fully specified. 2025-07-03 22:05:24.666 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE arrtest_s SET a[:] = '{11, 12, 13, 14, 15}'; 2025-07-03 22:05:24.667 UTC client backend[17208] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:05:24.667 UTC client backend[17208] pg_regress/transactions STATEMENT: SAVEPOINT two; 2025-07-03 22:05:24.667 UTC client backend[17208] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:05:24.667 UTC client backend[17208] pg_regress/transactions STATEMENT: RELEASE SAVEPOINT one; 2025-07-03 22:05:24.676 UTC client backend[17201] pg_regress/portals ERROR: cursor "foo26" does not exist 2025-07-03 22:05:24.676 UTC client backend[17201] pg_regress/portals STATEMENT: FETCH FROM foo26; 2025-07-03 22:05:24.691 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:24.691 UTC client backend[17208] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-07-03 22:05:24.691 UTC client backend[17210] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-07-03 22:05:24.691 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT f1[0:1] FROM POINT_TBL; 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT f1[0:] FROM POINT_TBL; 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT f1[:1] FROM POINT_TBL; 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays ERROR: slices of fixed-length arrays not implemented 2025-07-03 22:05:24.692 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT f1[:] FROM POINT_TBL; 2025-07-03 22:05:24.693 UTC client backend[17208] pg_regress/transactions ERROR: portal "c" cannot be run 2025-07-03 22:05:24.693 UTC client backend[17208] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-07-03 22:05:24.694 UTC client backend[17208] pg_regress/transactions ERROR: portal "c" cannot be run 2025-07-03 22:05:24.694 UTC client backend[17208] pg_regress/transactions STATEMENT: FETCH 10 FROM c; 2025-07-03 22:05:24.714 UTC client backend[17210] pg_regress/arrays ERROR: array subscript out of range 2025-07-03 22:05:24.714 UTC client backend[17210] pg_regress/arrays STATEMENT: UPDATE point_tbl SET f1[3] = 10 WHERE f1::text = '(-10,-10)'::point::text RETURNING *; 2025-07-03 22:05:24.729 UTC client backend[17205] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 38 2025-07-03 22:05:24.729 UTC client backend[17205] pg_regress/select_into STATEMENT: DECLARE foo CURSOR FOR SELECT 1 INTO int4_tbl; 2025-07-03 22:05:24.732 UTC client backend[17205] pg_regress/select_into ERROR: COPY (SELECT INTO) is not supported 2025-07-03 22:05:24.732 UTC client backend[17205] pg_regress/select_into STATEMENT: COPY (SELECT 1 INTO frak UNION SELECT 2) TO 'blob'; 2025-07-03 22:05:24.738 UTC client backend[17205] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 30 2025-07-03 22:05:24.738 UTC client backend[17205] pg_regress/select_into STATEMENT: SELECT * FROM (SELECT 1 INTO f) bar; 2025-07-03 22:05:24.738 UTC client backend[17205] pg_regress/select_into ERROR: views must not contain SELECT INTO 2025-07-03 22:05:24.738 UTC client backend[17205] pg_regress/select_into STATEMENT: CREATE VIEW foo AS SELECT 1 INTO int4_tbl; 2025-07-03 22:05:24.739 UTC client backend[17205] pg_regress/select_into ERROR: SELECT ... INTO is not allowed here at character 36 2025-07-03 22:05:24.739 UTC client backend[17205] pg_regress/select_into STATEMENT: INSERT INTO int4_tbl SELECT 1 INTO f; 2025-07-03 22:05:24.747 UTC client backend[17202] pg_regress/select_distinct LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17202.1", size 147456 2025-07-03 22:05:24.747 UTC client backend[17202] pg_regress/select_distinct STATEMENT: CREATE TABLE distinct_group_1 AS SELECT DISTINCT g%1000 FROM generate_series(0,9999) g; 2025-07-03 22:05:24.747 UTC client backend[17202] pg_regress/select_distinct LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17202.0", size 140000 2025-07-03 22:05:24.747 UTC client backend[17202] pg_regress/select_distinct STATEMENT: CREATE TABLE distinct_group_1 AS SELECT DISTINCT g%1000 FROM generate_series(0,9999) g; 2025-07-03 22:05:24.753 UTC client backend[17205] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-07-03 22:05:24.753 UTC client backend[17205] pg_regress/select_into STATEMENT: CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0; 2025-07-03 22:05:24.753 UTC client backend[17205] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-07-03 22:05:24.753 UTC client backend[17205] pg_regress/select_into STATEMENT: CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0 WITH NO DATA; 2025-07-03 22:05:24.755 UTC client backend[17205] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-07-03 22:05:24.755 UTC client backend[17205] pg_regress/select_into STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF) CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0; 2025-07-03 22:05:24.756 UTC client backend[17205] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-07-03 22:05:24.756 UTC client backend[17205] pg_regress/select_into STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF) CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0 WITH NO DATA; 2025-07-03 22:05:24.756 UTC client backend[17205] pg_regress/select_into ERROR: relation "ctas_ine_tbl" already exists 2025-07-03 22:05:24.756 UTC client backend[17205] pg_regress/select_into STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF) CREATE TABLE ctas_ine_tbl AS EXECUTE ctas_ine_query; 2025-07-03 22:05:24.762 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate functions are not allowed in WHERE at character 114 2025-07-03 22:05:24.762 UTC client backend[17204] pg_regress/aggregates STATEMENT: select ten, sum(distinct four) from onek a group by ten having exists (select 1 from onek b where sum(distinct a.four + b.four) = b.four); 2025-07-03 22:05:24.778 UTC client backend[17205] pg_regress/select_into LOG: disconnection: session time: 0:00:00.669 user=postgres database=regression host=[local] 2025-07-03 22:05:24.793 UTC client backend[17208] pg_regress/transactions ERROR: duplicate key value violates unique constraint "koju_a_key" 2025-07-03 22:05:24.793 UTC client backend[17208] pg_regress/transactions DETAIL: Key (a)=(1) already exists. 2025-07-03 22:05:24.793 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO koju VALUES (1); 2025-07-03 22:05:24.810 UTC client backend[17215] pg_regress/namespace LOG: disconnection: session time: 0:00:00.645 user=postgres database=regression host=[local] 2025-07-03 22:05:24.814 UTC client backend[17208] pg_regress/transactions ERROR: duplicate key value violates unique constraint "koju_a_key" 2025-07-03 22:05:24.814 UTC client backend[17208] pg_regress/transactions DETAIL: Key (a)=(1) already exists. 2025-07-03 22:05:24.814 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO koju VALUES (1); 2025-07-03 22:05:24.817 UTC client backend[17200] pg_regress/random LOG: disconnection: session time: 0:00:00.733 user=postgres database=regression host=[local] 2025-07-03 22:05:24.863 UTC client backend[17237] pg_regress/prepared_xacts ERROR: relation "pxtest3" does not exist at character 15 2025-07-03 22:05:24.863 UTC client backend[17237] pg_regress/prepared_xacts STATEMENT: SELECT * FROM pxtest3; 2025-07-03 22:05:24.872 UTC client backend[17210] pg_regress/arrays ERROR: searching for elements in multidimensional arrays is not supported 2025-07-03 22:05:24.872 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_position(ARRAY[[1,2],[3,4]], 3); 2025-07-03 22:05:24.886 UTC client backend[17210] pg_regress/arrays ERROR: searching for elements in multidimensional arrays is not supported 2025-07-03 22:05:24.886 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_positions(ARRAY[[1,2],[3,4]], 4); 2025-07-03 22:05:24.891 UTC client backend[17201] pg_regress/portals ERROR: cursor can only scan forward 2025-07-03 22:05:24.891 UTC client backend[17201] pg_regress/portals HINT: Declare it with SCROLL option to enable backward scan. 2025-07-03 22:05:24.891 UTC client backend[17201] pg_regress/portals STATEMENT: FETCH RELATIVE 0 FROM c1; 2025-07-03 22:05:24.894 UTC client backend[17237] pg_regress/prepared_xacts ERROR: table "pxtest3" does not exist 2025-07-03 22:05:24.894 UTC client backend[17237] pg_regress/prepared_xacts STATEMENT: DROP TABLE pxtest3; 2025-07-03 22:05:24.907 UTC client backend[17237] pg_regress/prepared_xacts LOG: disconnection: session time: 0:00:00.392 user=postgres database=regression host=[local] 2025-07-03 22:05:24.935 UTC client backend[17201] pg_regress/portals ERROR: cursor "c1" is not a simply updatable scan of table "uctest" 2025-07-03 22:05:24.935 UTC client backend[17201] pg_regress/portals STATEMENT: UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1; 2025-07-03 22:05:24.940 UTC client backend[17201] pg_regress/portals ERROR: cursor "c1" has multiple FOR UPDATE/SHARE references to table "uctest" 2025-07-03 22:05:24.940 UTC client backend[17201] pg_regress/portals STATEMENT: UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1; 2025-07-03 22:05:24.943 UTC client backend[17208] pg_regress/transactions ERROR: cursor "foo" does not exist 2025-07-03 22:05:24.943 UTC client backend[17208] pg_regress/transactions STATEMENT: fetch from foo; 2025-07-03 22:05:24.947 UTC client backend[17202] pg_regress/select_distinct LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17202.2", size 140000 2025-07-03 22:05:24.947 UTC client backend[17202] pg_regress/select_distinct STATEMENT: CREATE TABLE distinct_group_2 AS SELECT DISTINCT (g%1000)::text FROM generate_series(0,9999) g; 2025-07-03 22:05:24.953 UTC client backend[17201] pg_regress/portals ERROR: cursor "c1" does not exist 2025-07-03 22:05:24.953 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c1; 2025-07-03 22:05:24.955 UTC client backend[17201] pg_regress/portals ERROR: cursor "cx" is held from a previous transaction 2025-07-03 22:05:24.955 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF cx; 2025-07-03 22:05:24.960 UTC client backend[17201] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "uctest" 2025-07-03 22:05:24.960 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-07-03 22:05:24.961 UTC client backend[17201] pg_regress/portals ERROR: cursor "c" does not have a FOR UPDATE/SHARE reference to table "uctest" 2025-07-03 22:05:24.961 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-07-03 22:05:24.967 UTC client backend[17201] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "tenk1" 2025-07-03 22:05:24.967 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM tenk1 WHERE CURRENT OF c; 2025-07-03 22:05:24.975 UTC client backend[17201] pg_regress/portals ERROR: cursor "c" is not a simply updatable scan of table "uctest" 2025-07-03 22:05:24.975 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c; 2025-07-03 22:05:24.977 UTC client backend[17201] pg_regress/portals ERROR: cursor "c1" is not positioned on a row 2025-07-03 22:05:24.977 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM uctest WHERE CURRENT OF c1; 2025-07-03 22:05:24.980 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:24.980 UTC client backend[17208] pg_regress/transactions CONTEXT: PL/pgSQL function invert(double precision) line 1 at RETURN SQL statement "INSERT INTO new_table SELECT invert(0.0)" PL/pgSQL function create_temp_tab() line 6 at SQL statement 2025-07-03 22:05:24.980 UTC client backend[17208] pg_regress/transactions STATEMENT: FETCH ctt; 2025-07-03 22:05:24.985 UTC client backend[17201] pg_regress/portals ERROR: FOR UPDATE is not allowed with aggregate functions 2025-07-03 22:05:24.985 UTC client backend[17201] pg_regress/portals STATEMENT: DECLARE c1 CURSOR FOR SELECT MIN(f1) FROM uctest FOR UPDATE; 2025-07-03 22:05:24.987 UTC client backend[17208] pg_regress/transactions ERROR: portal "ctt" cannot be run 2025-07-03 22:05:24.987 UTC client backend[17208] pg_regress/transactions STATEMENT: FETCH ctt; 2025-07-03 22:05:25.005 UTC client backend[17201] pg_regress/portals ERROR: WHERE CURRENT OF on a view is not implemented 2025-07-03 22:05:25.005 UTC client backend[17201] pg_regress/portals STATEMENT: DELETE FROM ucview WHERE CURRENT OF c1; 2025-07-03 22:05:25.008 UTC client backend[17208] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-07-03 22:05:25.008 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-07-03 22:05:25.008 UTC client backend[17208] pg_regress/transactions ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:05:25.008 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (3); 2025-07-03 22:05:25.015 UTC client backend[17208] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-07-03 22:05:25.015 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-07-03 22:05:25.035 UTC client backend[17210] pg_regress/arrays ERROR: op ANY/ALL (array) requires operator to yield boolean at character 11 2025-07-03 22:05:25.035 UTC client backend[17210] pg_regress/arrays STATEMENT: select 33 * any ('{1,2,3}'); 2025-07-03 22:05:25.035 UTC client backend[17210] pg_regress/arrays ERROR: op ANY/ALL (array) requires array on right side at character 11 2025-07-03 22:05:25.035 UTC client backend[17210] pg_regress/arrays STATEMENT: select 33 * any (44); 2025-07-03 22:05:25.046 UTC client backend[17202] pg_regress/select_distinct LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17202.4", size 140000 2025-07-03 22:05:25.046 UTC client backend[17202] pg_regress/select_distinct STATEMENT: CREATE TABLE distinct_hash_1 AS SELECT DISTINCT g%1000 FROM generate_series(0,9999) g; 2025-07-03 22:05:25.053 UTC client backend[17208] pg_regress/transactions ERROR: invalid input syntax for type integer: "error" at character 31 2025-07-03 22:05:25.053 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES ('error'); 2025-07-03 22:05:25.055 UTC client backend[17208] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.055 UTC client backend[17208] pg_regress/transactions STATEMENT: COMMIT AND CHAIN; 2025-07-03 22:05:25.055 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.055 UTC client backend[17208] pg_regress/transactions STATEMENT: ROLLBACK AND CHAIN; 2025-07-03 22:05:25.084 UTC client backend[17210] pg_regress/arrays ERROR: duplicate key value violates unique constraint "arr_tbl_f1_key" 2025-07-03 22:05:25.084 UTC client backend[17210] pg_regress/arrays DETAIL: Key (f1)=({1,2,3}) already exists. 2025-07-03 22:05:25.084 UTC client backend[17210] pg_regress/arrays STATEMENT: insert into arr_tbl values ('{1,2,3}'); 2025-07-03 22:05:25.085 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:25.085 UTC client backend[17208] pg_regress/transactions STATEMENT: insert into i_table values(2); select * from i_table; select 1/0; 2025-07-03 22:05:25.088 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.093 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.094 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.096 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.096 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:25.096 UTC client backend[17208] pg_regress/transactions STATEMENT: insert into i_table values(7); commit; insert into i_table values(8); select 1/0; 2025-07-03 22:05:25.097 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.097 UTC client backend[17211] pg_regress/update ERROR: new row for relation "part_c_100_200" violates partition constraint 2025-07-03 22:05:25.097 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (105, 85, null, b, 15). 2025-07-03 22:05:25.097 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE part_c_100_200 set c = c - 20, d = c WHERE c = 105; 2025-07-03 22:05:25.099 UTC client backend[17211] pg_regress/update ERROR: new row for relation "part_b_10_b_20" violates partition constraint 2025-07-03 22:05:25.099 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (null, 96, a, 12, 1). 2025-07-03 22:05:25.099 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE part_b_10_b_20 set a = 'a'; 2025-07-03 22:05:25.099 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.103 UTC client backend[17208] pg_regress/transactions ERROR: VACUUM cannot run inside a transaction block 2025-07-03 22:05:25.103 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 1; VACUUM; 2025-07-03 22:05:25.107 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions ERROR: VACUUM cannot run inside a transaction block 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 1; COMMIT; VACUUM; 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 1; SAVEPOINT sp; 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions ERROR: SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 1; COMMIT; SAVEPOINT sp; 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK TO SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:25.108 UTC client backend[17208] pg_regress/transactions STATEMENT: ROLLBACK TO SAVEPOINT sp; SELECT 2; 2025-07-03 22:05:25.109 UTC client backend[17208] pg_regress/transactions ERROR: RELEASE SAVEPOINT can only be used in transaction blocks 2025-07-03 22:05:25.109 UTC client backend[17208] pg_regress/transactions STATEMENT: SELECT 2; RELEASE SAVEPOINT sp; SELECT 3; 2025-07-03 22:05:25.112 UTC client backend[17211] pg_regress/update ERROR: new row for relation "part_b_10_b_20" violates partition constraint 2025-07-03 22:05:25.112 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (2, 117, b, 7, 2). 2025-07-03 22:05:25.112 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE part_b_10_b_20 set b = b - 6 WHERE c > 116 returning *; 2025-07-03 22:05:25.114 UTC client backend[17208] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.114 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION READ ONLY; COMMIT AND CHAIN; 2025-07-03 22:05:25.115 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.115 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION READ ONLY; ROLLBACK AND CHAIN; 2025-07-03 22:05:25.123 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.125 UTC client backend[17208] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.125 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (7); COMMIT; INSERT INTO trans_abc VALUES (8); COMMIT AND CHAIN; 2025-07-03 22:05:25.127 UTC client backend[17208] pg_regress/transactions WARNING: there is no transaction in progress 2025-07-03 22:05:25.127 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.127 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (9); ROLLBACK; INSERT INTO trans_abc VALUES (10); ROLLBACK AND CHAIN; 2025-07-03 22:05:25.128 UTC client backend[17208] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.128 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (11); COMMIT AND CHAIN; INSERT INTO trans_abc VALUES (12); COMMIT; 2025-07-03 22:05:25.128 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.128 UTC client backend[17208] pg_regress/transactions STATEMENT: INSERT INTO trans_abc VALUES (13); ROLLBACK AND CHAIN; INSERT INTO trans_abc VALUES (14); ROLLBACK; 2025-07-03 22:05:25.138 UTC client backend[17208] pg_regress/transactions ERROR: COMMIT AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.138 UTC client backend[17208] pg_regress/transactions STATEMENT: START TRANSACTION ISOLATION LEVEL REPEATABLE READ; INSERT INTO trans_abc VALUES (17); COMMIT; INSERT INTO trans_abc VALUES (18); COMMIT AND CHAIN; 2025-07-03 22:05:25.139 UTC client backend[17208] pg_regress/transactions ERROR: ROLLBACK AND CHAIN can only be used in transaction blocks 2025-07-03 22:05:25.139 UTC client backend[17208] pg_regress/transactions STATEMENT: START TRANSACTION ISOLATION LEVEL REPEATABLE READ; INSERT INTO trans_abc VALUES (19); ROLLBACK; INSERT INTO trans_abc VALUES (20); ROLLBACK AND CHAIN; 2025-07-03 22:05:25.143 UTC client backend[17210] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-07-03 22:05:25.143 UTC client backend[17210] pg_regress/arrays STATEMENT: update arr_pk_tbl set f1[2147483647] = 42 where pk = 10; 2025-07-03 22:05:25.146 UTC client backend[17202] pg_regress/select_distinct LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17202.5", size 140000 2025-07-03 22:05:25.146 UTC client backend[17202] pg_regress/select_distinct STATEMENT: CREATE TABLE distinct_hash_2 AS SELECT DISTINCT (g%1000)::text FROM generate_series(0,9999) g; 2025-07-03 22:05:25.146 UTC client backend[17210] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-07-03 22:05:25.146 UTC client backend[17210] pg_regress/arrays STATEMENT: update arr_pk_tbl set f1[2147483646:2147483647] = array[4,2] where pk = 10; 2025-07-03 22:05:25.146 UTC client backend[17210] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-07-03 22:05:25.146 UTC client backend[17210] pg_regress/arrays STATEMENT: insert into arr_pk_tbl(pk, f1[0:2147483647]) values (2, '{}'); 2025-07-03 22:05:25.147 UTC client backend[17210] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-07-03 22:05:25.147 UTC client backend[17210] pg_regress/arrays STATEMENT: insert into arr_pk_tbl(pk, f1[-2147483648:2147483647]) values (2, '{}'); 2025-07-03 22:05:25.147 UTC client backend[17210] pg_regress/arrays ERROR: array size exceeds the maximum allowed (134217727) 2025-07-03 22:05:25.147 UTC client backend[17210] pg_regress/arrays CONTEXT: PL/pgSQL function inline_code_block line 4 at assignment 2025-07-03 22:05:25.147 UTC client backend[17210] pg_regress/arrays STATEMENT: do $$ declare a int[]; begin a := '[-2147483648:-2147483647]={1,2}'::int[]; a[2147483647] := 42; end $$; 2025-07-03 22:05:25.154 UTC client backend[17208] pg_regress/transactions ERROR: invalid snapshot identifier: "Incorrect Identifier" 2025-07-03 22:05:25.154 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION SNAPSHOT 'Incorrect Identifier'; 2025-07-03 22:05:25.154 UTC client backend[17208] pg_regress/transactions ERROR: snapshot "FFF-FFF-F" does not exist 2025-07-03 22:05:25.154 UTC client backend[17208] pg_regress/transactions STATEMENT: SET TRANSACTION SNAPSHOT 'FFF-FFF-F'; 2025-07-03 22:05:25.155 UTC client backend[17208] pg_regress/transactions ERROR: division by zero 2025-07-03 22:05:25.155 UTC client backend[17208] pg_regress/transactions STATEMENT: select 1/0; 2025-07-03 22:05:25.155 UTC client backend[17208] pg_regress/transactions ERROR: savepoint "x" does not exist 2025-07-03 22:05:25.155 UTC client backend[17208] pg_regress/transactions STATEMENT: rollback to X; 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1,{2}},{2,3}}" at character 8 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1,{2}},{2,3}}'::text[]; 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1,2},\{2,3}}" at character 8 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays STATEMENT: select E'{{1,2},\\{2,3}}'::text[]; 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{"a"b}" at character 8 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{"a"b}'::text[]; 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{a"b"}" at character 8 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-07-03 22:05:25.160 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{a"b"}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{"a""b"}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{"a""b"}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{"1 2" x},{3}}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Incorrectly quoted array element. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{"1 2" x},{3}}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{"1 2"} x,{3}}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected array element. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{"1 2"} x,{3}}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{}}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Junk after closing right brace. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{}}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17208] pg_regress/transactions LOG: disconnection: session time: 0:00:01.036 user=postgres database=regression host=[local] 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{ }}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Junk after closing right brace. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{ }}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "}{" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Array value must start with "{" or dimension information. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '}{'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{foo{}}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "{" character. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{foo{}}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{"foo"{}}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "{" character. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{"foo"{}}'::text[]; 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{foo,,bar}" at character 8 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "," character. 2025-07-03 22:05:25.161 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{foo,,bar}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1},{{2}}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1},{{2}}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{{1}},{2}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{{1}},{2}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{},{{}}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{},{{}}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{{}},{}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{{}},{}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1},{}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1},{}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{},{1}}" at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{},{1}}'::text[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: upper bound cannot be less than lower bound at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[1:0]={}'::int[]; 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays ERROR: array upper bound is too large: 2147483647 at character 8 2025-07-03 22:05:25.162 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[2147483646:2147483647]={1,2}'::int[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: upper bound cannot be less than lower bound at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[1:-1]={}'::int[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "[2]={1}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: Specified array dimensions do not match array contents. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[2]={1}'::int[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "[1:]={1}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: Missing array dimension value. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[1:]={1}'::int[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "[:1]={1}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: "[" must introduce explicitly-specified array dimensions. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[:1]={1}'::int[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: cannot determine type of empty array at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays HINT: Explicitly cast to the desired type, for example ARRAY[]::integer[]. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select array[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1,},{1},}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1,},{1},}'::text[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1,},{1}}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1,},{1}}'::text[]; 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{{1,}}" at character 8 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-07-03 22:05:25.163 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{{1,}}'::text[]; 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays ERROR: malformed array literal: "{1,}" at character 8 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays DETAIL: Unexpected "}" character. 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays STATEMENT: select '{1,}'::text[]; 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays ERROR: array bound is out of integer range at character 8 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[21474836488:21474836489]={1,2}'::int[]; 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays ERROR: array bound is out of integer range at character 8 2025-07-03 22:05:25.164 UTC client backend[17210] pg_regress/arrays STATEMENT: select '[-2147483649:-2147483648]={1,2}'::int[]; 2025-07-03 22:05:25.168 UTC client backend[17195] pg_regress/union ERROR: column "q2" does not exist at character 65 2025-07-03 22:05:25.168 UTC client backend[17195] pg_regress/union DETAIL: There is a column named "q2" in table "*SELECT* 2", but it cannot be referenced from this part of the query. 2025-07-03 22:05:25.168 UTC client backend[17195] pg_regress/union STATEMENT: SELECT q1 FROM int8_tbl EXCEPT SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1; 2025-07-03 22:05:25.197 UTC client backend[17195] pg_regress/union ERROR: invalid input syntax for type numeric: "foo" at character 36 2025-07-03 22:05:25.197 UTC client backend[17195] pg_regress/union STATEMENT: SELECT '3.4'::numeric UNION SELECT 'foo'; 2025-07-03 22:05:25.284 UTC client backend[17201] pg_regress/portals LOG: disconnection: session time: 0:00:01.190 user=postgres database=regression host=[local] 2025-07-03 22:05:25.345 UTC client backend[17198] pg_regress/subselect ERROR: operator does not exist: bigint = text at character 33 2025-07-03 22:05:25.345 UTC client backend[17198] pg_regress/subselect HINT: No operator matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:25.345 UTC client backend[17198] pg_regress/subselect STATEMENT: select * from int8_tbl where q1 in (select c1 from inner_text); 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays ERROR: dimension array or low bound array cannot be null 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, null, array[2,2]); 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays ERROR: dimension array or low bound array cannot be null 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, array[2,2], null); 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays ERROR: wrong number of array subscripts 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays DETAIL: Low bound array has different size than dimensions array. 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, array[2,2], '{}'); 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays ERROR: wrong number of array subscripts 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays DETAIL: Low bound array has different size than dimensions array. 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, array[3,3], array[1,1,1]); 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays ERROR: dimension values cannot be null 2025-07-03 22:05:25.358 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, array[1,2,null]); 2025-07-03 22:05:25.361 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 12 2025-07-03 22:05:25.361 UTC client backend[17204] pg_regress/aggregates STATEMENT: select max(min(unique1)) from tenk1; 2025-07-03 22:05:25.362 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 20 2025-07-03 22:05:25.362 UTC client backend[17204] pg_regress/aggregates STATEMENT: select (select max(min(unique1)) from int8_tbl) from tenk1; 2025-07-03 22:05:25.363 UTC client backend[17210] pg_regress/arrays ERROR: wrong number of array subscripts 2025-07-03 22:05:25.363 UTC client backend[17210] pg_regress/arrays DETAIL: Dimension array must be one dimensional. 2025-07-03 22:05:25.363 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_fill(1, array[[1,2],[3,4]]); 2025-07-03 22:05:25.364 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 49 2025-07-03 22:05:25.364 UTC client backend[17204] pg_regress/aggregates STATEMENT: select avg((select avg(a1.col1 order by (select avg(a2.col2) from tenk1 a3)) from tenk1 a1(col1))) from tenk1 a2(col2); 2025-07-03 22:05:25.448 UTC client backend[17210] pg_regress/arrays ERROR: cannot accumulate empty arrays 2025-07-03 22:05:25.448 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_agg('{}'::int[]) from generate_series(1,2); 2025-07-03 22:05:25.449 UTC client backend[17210] pg_regress/arrays ERROR: cannot accumulate null arrays 2025-07-03 22:05:25.449 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_agg(null::int[]) from generate_series(1,2); 2025-07-03 22:05:25.449 UTC client backend[17210] pg_regress/arrays ERROR: cannot accumulate arrays of different dimensionality 2025-07-03 22:05:25.449 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_agg(ar) from (values ('{1,2}'::int[]), ('{3}'::int[])) v(ar); 2025-07-03 22:05:25.457 UTC client backend[17210] pg_regress/arrays ERROR: removing elements from multidimensional arrays is not supported 2025-07-03 22:05:25.457 UTC client backend[17210] pg_regress/arrays STATEMENT: select array_remove('{{1,2,2},{1,4,3}}', 2); 2025-07-03 22:05:25.575 UTC client backend[17211] pg_regress/update ERROR: new row violates check option for view "upview" 2025-07-03 22:05:25.575 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (a, 4, 120, 1, 1). 2025-07-03 22:05:25.575 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE upview set c = 120 WHERE b = 4; 2025-07-03 22:05:25.625 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "j1_tbl" at character 57 2025-07-03 22:05:25.625 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "j1_tbl", but it cannot be referenced from this part of the query. 2025-07-03 22:05:25.625 UTC client backend[17196] pg_regress/join STATEMENT: SELECT * FROM (J1_TBL JOIN J2_TBL USING (i)) AS x WHERE J1_TBL.t = 'one'; 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join ERROR: column x.t does not exist at character 55 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join STATEMENT: SELECT * FROM J1_TBL JOIN J2_TBL USING (i) AS x WHERE x.t = 'one'; 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join ERROR: missing FROM-clause entry for table "x" at character 63 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join STATEMENT: SELECT * FROM (J1_TBL JOIN J2_TBL USING (i) AS x) AS xx WHERE x.i = 1; 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join ERROR: table name "a1" specified more than once 2025-07-03 22:05:25.628 UTC client backend[17196] pg_regress/join STATEMENT: SELECT * FROM J1_TBL a1 JOIN J2_TBL a2 USING (i) AS a1; 2025-07-03 22:05:25.678 UTC client backend[17195] pg_regress/union LOG: disconnection: session time: 0:00:01.618 user=postgres database=regression host=[local] 2025-07-03 22:05:25.694 UTC client backend[17204] pg_regress/aggregates ERROR: column "t1.f1" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:05:25.694 UTC client backend[17204] pg_regress/aggregates STATEMENT: select t1.f1 from t1 left join t2 using (f1) group by f1; 2025-07-03 22:05:25.739 UTC client backend[17202] pg_regress/select_distinct LOG: disconnection: session time: 0:00:01.644 user=postgres database=regression host=[local] 2025-07-03 22:05:25.748 UTC client backend[17211] pg_regress/update ERROR: new row violates check option for view "upview" 2025-07-03 22:05:25.748 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (b, 15, 120, 1, 1). 2025-07-03 22:05:25.748 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE upview set a = 'b', b = 15, c = 120 WHERE b = 4; 2025-07-03 22:05:25.884 UTC client backend[17210] pg_regress/arrays ERROR: function width_bucket(text, integer[]) does not exist at character 8 2025-07-03 22:05:25.884 UTC client backend[17210] pg_regress/arrays HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:05:25.884 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT width_bucket('5'::text, ARRAY[3, 4]::integer[]); 2025-07-03 22:05:25.885 UTC client backend[17210] pg_regress/arrays ERROR: thresholds array must not contain NULLs 2025-07-03 22:05:25.885 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT width_bucket(5, ARRAY[3, 4, NULL]); 2025-07-03 22:05:25.885 UTC client backend[17210] pg_regress/arrays ERROR: thresholds must be one-dimensional array 2025-07-03 22:05:25.885 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT width_bucket(5, ARRAY[ARRAY[1, 2], ARRAY[3, 4]]); 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 3 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[1, 2, 3], -1); 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 3 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[1, 2, 3], 10); 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays ERROR: number of elements to trim must be between 0 and 0 2025-07-03 22:05:25.888 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT trim_array(ARRAY[]::int[], 1); 2025-07-03 22:05:25.891 UTC client backend[17210] pg_regress/arrays ERROR: sample size must be between 0 and 6 2025-07-03 22:05:25.891 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_sample('{1,2,3,4,5,6}'::int[], -1); 2025-07-03 22:05:25.891 UTC client backend[17210] pg_regress/arrays ERROR: sample size must be between 0 and 6 2025-07-03 22:05:25.891 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_sample('{1,2,3,4,5,6}'::int[], 7); 2025-07-03 22:05:25.923 UTC client backend[17210] pg_regress/arrays ERROR: could not identify a comparison function for type xid 2025-07-03 22:05:25.923 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_sort('{1,2,3}'::xid[]); 2025-07-03 22:05:25.924 UTC client backend[17210] pg_regress/arrays ERROR: could not identify a comparison function for type xid 2025-07-03 22:05:25.924 UTC client backend[17210] pg_regress/arrays STATEMENT: SELECT array_sort('{{1,2,3},{2,3,4}}'::xid[]); 2025-07-03 22:05:25.949 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 39 2025-07-03 22:05:25.949 UTC client backend[17204] pg_regress/aggregates STATEMENT: select aggfns(distinct a,b,c order by i) from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i; 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates STATEMENT: select aggfns(distinct a,b,c order by a,b+1) from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i; 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 43 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates STATEMENT: select aggfns(distinct a,b,c order by a,b,i,c) from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i; 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41 2025-07-03 22:05:25.950 UTC client backend[17204] pg_regress/aggregates STATEMENT: select aggfns(distinct a,a,c order by a,b) from (values (1,1,'foo')) v(a,b,c), generate_series(1,2) i; 2025-07-03 22:05:25.968 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 51 2025-07-03 22:05:25.968 UTC client backend[17204] pg_regress/aggregates STATEMENT: select string_agg(distinct f1::text, ',' order by f1) from varchar_tbl; 2025-07-03 22:05:25.968 UTC client backend[17204] pg_regress/aggregates ERROR: in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 45 2025-07-03 22:05:25.968 UTC client backend[17204] pg_regress/aggregates STATEMENT: select string_agg(distinct f1, ',' order by f1::text) from varchar_tbl; 2025-07-03 22:05:26.032 UTC client backend[17210] pg_regress/arrays LOG: disconnection: session time: 0:00:01.898 user=postgres database=regression host=[local] 2025-07-03 22:05:26.432 UTC client backend[17211] pg_regress/update ERROR: new row violates row-level security policy for table "range_parted" 2025-07-03 22:05:26.432 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 151 WHERE a = 'a' and c = 200; 2025-07-03 22:05:26.451 UTC client backend[17198] pg_regress/subselect LOG: disconnection: session time: 0:00:02.382 user=postgres database=regression host=[local] 2025-07-03 22:05:26.567 UTC client backend[17211] pg_regress/update ERROR: new row violates row-level security policy for table "range_parted" 2025-07-03 22:05:26.567 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 150 WHERE a = 'a' and c = 200; 2025-07-03 22:05:26.643 UTC client backend[17211] pg_regress/update ERROR: new row violates row-level security policy "policy_range_parted_subplan" for table "range_parted" 2025-07-03 22:05:26.643 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 122 WHERE a = 'a' and c = 200; 2025-07-03 22:05:26.750 UTC client backend[17211] pg_regress/update ERROR: new row violates row-level security policy "policy_range_parted_wholerow" for table "range_parted" 2025-07-03 22:05:26.750 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE range_parted set a = 'b', c = 116 WHERE a = 'a' and c = 200; 2025-07-03 22:05:26.765 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate functions are not allowed in FILTER at character 35 2025-07-03 22:05:26.765 UTC client backend[17204] pg_regress/aggregates STATEMENT: select max(unique1) filter (where sum(ten) > 0) from tenk1; 2025-07-03 22:05:26.765 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 43 2025-07-03 22:05:26.765 UTC client backend[17204] pg_regress/aggregates STATEMENT: select (select max(unique1) filter (where sum(ten) > 0) from int8_tbl) from tenk1; 2025-07-03 22:05:26.766 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate functions are not allowed in FILTER at character 35 2025-07-03 22:05:26.766 UTC client backend[17204] pg_regress/aggregates STATEMENT: select max(unique1) filter (where bool_or(ten > 0)) from tenk1; 2025-07-03 22:05:26.766 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 43 2025-07-03 22:05:26.766 UTC client backend[17204] pg_regress/aggregates STATEMENT: select (select max(unique1) filter (where bool_or(ten > 0)) from int8_tbl) from tenk1; 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates ERROR: cannot use multiple ORDER BY clauses with WITHIN GROUP at character 41 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates STATEMENT: select p, percentile_cont(p order by p) within group (order by x) -- error from generate_series(1,5) x, (values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p) group by p order by p; 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates ERROR: sum is not an ordered-set aggregate, so it cannot have WITHIN GROUP at character 11 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates STATEMENT: select p, sum() within group (order by x::float8) -- error from generate_series(1,5) x, (values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p) group by p order by p; 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates ERROR: WITHIN GROUP is required for ordered-set aggregate percentile_cont at character 11 2025-07-03 22:05:26.768 UTC client backend[17204] pg_regress/aggregates STATEMENT: select p, percentile_cont(p,p) -- error from generate_series(1,5) x, (values (0::float8),(0.1),(0.25),(0.4),(0.5),(0.6),(0.75),(0.9),(1)) v(p) group by p order by p; 2025-07-03 22:05:27.006 UTC client backend[17204] pg_regress/aggregates ERROR: column "x.x" must appear in the GROUP BY clause or be used in an aggregate function at character 13 2025-07-03 22:05:27.006 UTC client backend[17204] pg_regress/aggregates DETAIL: Direct arguments of an ordered-set aggregate must use only grouped columns. 2025-07-03 22:05:27.006 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank(x) within group (order by x) from generate_series(1,5) x; 2025-07-03 22:05:27.011 UTC client backend[17204] pg_regress/aggregates ERROR: outer-level aggregate cannot contain a lower-level variable in its direct arguments at character 37 2025-07-03 22:05:27.011 UTC client backend[17204] pg_regress/aggregates STATEMENT: select array(select percentile_disc(a) within group (order by x) from (values (0.3),(0.7)) v(a) group by a) from generate_series(1,5) g(x); 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates ERROR: aggregate function calls cannot be nested at character 13 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank(sum(x)) within group (order by x) from generate_series(1,5) x; 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates ERROR: WITHIN GROUP types text and integer cannot be matched at character 13 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank(3) within group (order by x) from (values ('fred'),('jim')) v(x); 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates ERROR: function rank(integer, name, name) does not exist at character 8 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates HINT: To use the hypothetical-set aggregate rank, the number of hypothetical direct arguments (here 1) must match the number of ordering columns (here 2). 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank(3) within group (order by stringu1,stringu2) from tenk1; 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates ERROR: invalid input syntax for type integer: "fred" at character 13 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank('fred') within group (order by x) from generate_series(1,5) x; 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 64 2025-07-03 22:05:27.014 UTC client backend[17204] pg_regress/aggregates STATEMENT: select rank('adam'::text collate "C") within group (order by x collate "POSIX") from (values ('fred'),('jim')) v(x); 2025-07-03 22:05:27.089 UTC client backend[17211] pg_regress/update ERROR: new row for relation "part_def" violates partition constraint 2025-07-03 22:05:27.089 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (a, 9, null, null, null). 2025-07-03 22:05:27.089 UTC client backend[17211] pg_regress/update STATEMENT: update part_def set a = 'a' where a = 'd'; 2025-07-03 22:05:27.099 UTC client backend[17211] pg_regress/update ERROR: new row for relation "part_a_10_a_20" violates partition constraint 2025-07-03 22:05:27.099 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (ad, 10, 200, 1, null). 2025-07-03 22:05:27.099 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE part_a_10_a_20 set a = 'ad' WHERE a = 'a'; 2025-07-03 22:05:27.157 UTC client backend[17196] pg_regress/join ERROR: column t1.x does not exist at character 8 2025-07-03 22:05:27.157 UTC client backend[17196] pg_regress/join HINT: Perhaps you meant to reference the column "t3.x". 2025-07-03 22:05:27.157 UTC client backend[17196] pg_regress/join STATEMENT: select t1.x from t1 join t3 on (t1.a = t3.x); 2025-07-03 22:05:27.168 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait 2025-07-03 22:05:27.213 UTC client backend[17211] pg_regress/update ERROR: new row for relation "list_default" violates partition constraint 2025-07-03 22:05:27.213 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (a, 10). 2025-07-03 22:05:27.213 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE list_default set a = 'a' WHERE a = 'd'; 2025-07-03 22:05:27.262 UTC client backend[17211] pg_regress/update ERROR: cannot retrieve a system column in this context 2025-07-03 22:05:27.262 UTC client backend[17211] pg_regress/update STATEMENT: insert into utrtest values (2, 'bar') returning *, tableoid::regclass, xmin = pg_current_xact_id()::xid as xmin_ok; 2025-07-03 22:05:27.276 UTC client backend[17211] pg_regress/update ERROR: cannot retrieve a system column in this context 2025-07-03 22:05:27.276 UTC client backend[17211] pg_regress/update STATEMENT: update utrtest set a = 3 - a from (values (1), (2)) s(x) where a = s.x returning *, tableoid::regclass, xmin = pg_current_xact_id()::xid as xmin_ok; 2025-07-03 22:05:27.333 UTC client backend[17211] pg_regress/update ERROR: new row for relation "sub_parted" violates partition constraint 2025-07-03 22:05:27.333 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (2, 2, 10). 2025-07-03 22:05:27.333 UTC client backend[17211] pg_regress/update STATEMENT: UPDATE sub_parted set a = 2 WHERE c = 10; 2025-07-03 22:05:27.437 UTC client backend[17211] pg_regress/update ERROR: new row for relation "hpart1" violates partition constraint 2025-07-03 22:05:27.437 UTC client backend[17211] pg_regress/update DETAIL: Failing row contains (3, 4). 2025-07-03 22:05:27.437 UTC client backend[17211] pg_regress/update STATEMENT: update hpart1 set a = 3, b=4 where a = 1; 2025-07-03 22:05:27.456 UTC client backend[17211] pg_regress/update LOG: disconnection: session time: 0:00:03.317 user=postgres database=regression host=[local] 2025-07-03 22:05:27.489 UTC checkpointer[14511] LOG: checkpoint complete: wrote 3655 buffers (22.3%), wrote 4 SLRU buffers; 0 WAL file(s) added, 0 removed, 4 recycled; write=0.140 s, sync=0.001 s, total=0.321 s; sync files=0, longest=0.000 s, average=0.000 s; distance=67477 kB, estimate=67477 kB; lsn=0/77F56C8, redo lsn=0/7784DD0 2025-07-03 22:05:27.522 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait 2025-07-03 22:05:27.527 UTC checkpointer[14511] LOG: checkpoint complete: wrote 159 buffers (1.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.001 s, total=0.005 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1256 kB, estimate=60855 kB; lsn=0/78BF1B8, redo lsn=0/78BF158 2025-07-03 22:05:27.608 UTC checkpointer[14511] LOG: checkpoint starting: immediate force wait 2025-07-03 22:05:27.610 UTC checkpointer[14511] LOG: checkpoint complete: wrote 32 buffers (0.2%), 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=457 kB, estimate=54815 kB; lsn=0/7933438, redo lsn=0/7931680 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index ERROR: value 9 out of bounds for option "fillfactor" 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index STATEMENT: CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops) WITH (fillfactor=9); 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index ERROR: value 101 out of bounds for option "fillfactor" 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:27.668 UTC client backend[17212] pg_regress/hash_index STATEMENT: CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops) WITH (fillfactor=101); 2025-07-03 22:05:27.678 UTC client backend[17212] pg_regress/hash_index LOG: disconnection: session time: 0:00:03.529 user=postgres database=regression host=[local] 2025-07-03 22:05:28.328 UTC client backend[17196] pg_regress/join ERROR: FOR UPDATE cannot be applied to a join at character 101 2025-07-03 22:05:28.328 UTC client backend[17196] pg_regress/join STATEMENT: select foo.*, unnamed_join.* from t1 join t2 using (a) as foo, t3 as unnamed_join for update of foo; 2025-07-03 22:05:28.328 UTC client backend[17196] pg_regress/join ERROR: relation "foo" in FOR UPDATE clause not found in FROM clause at character 110 2025-07-03 22:05:28.328 UTC client backend[17196] pg_regress/join STATEMENT: select bar.*, unnamed_join.* from (t1 join t2 using (a) as foo) as bar, t3 as unnamed_join for update of foo; 2025-07-03 22:05:28.330 UTC client backend[17196] pg_regress/join ERROR: FOR UPDATE cannot be applied to a join at character 110 2025-07-03 22:05:28.330 UTC client backend[17196] pg_regress/join STATEMENT: select bar.*, unnamed_join.* from (t1 join t2 using (a) as foo) as bar, t3 as unnamed_join for update of bar; 2025-07-03 22:05:28.335 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.1", size 280000 2025-07-03 22:05:28.335 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_data_20k as select g from generate_series(0, 19999) g; 2025-07-03 22:05:28.580 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.2", size 401408 2025-07-03 22:05:28.580 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_group_1 as select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3 from agg_data_20k group by g%10000; 2025-07-03 22:05:29.025 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.5", size 794624 2025-07-03 22:05:29.025 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_1 as select g%10000 as c1, sum(g::numeric) as c2, count(*) as c3 from agg_data_20k group by g%10000; 2025-07-03 22:05:29.087 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.6", size 204800 2025-07-03 22:05:29.087 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_2 as select * from (values (100), (300), (500)) as r(a), lateral ( select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3 from agg_data_2k where g < r.a group by g/2) as s; 2025-07-03 22:05:29.092 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.7", size 204800 2025-07-03 22:05:29.092 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_2 as select * from (values (100), (300), (500)) as r(a), lateral ( select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3 from agg_data_2k where g < r.a group by g/2) as s; 2025-07-03 22:05:29.104 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.8", size 204800 2025-07-03 22:05:29.104 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_2 as select * from (values (100), (300), (500)) as r(a), lateral ( select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3 from agg_data_2k where g < r.a group by g/2) as s; 2025-07-03 22:05:29.134 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.9", size 204800 2025-07-03 22:05:29.134 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_3 as select (g/2)::numeric as c1, sum(7::int4) as c2, count(*) as c3 from agg_data_2k group by g/2; 2025-07-03 22:05:29.175 UTC client backend[17204] pg_regress/aggregates LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17204.10", size 212992 2025-07-03 22:05:29.175 UTC client backend[17204] pg_regress/aggregates STATEMENT: create table agg_hash_4 as select (g/2)::numeric as c1, array_agg(g::numeric) as c2, count(*) as c3 from agg_data_2k group by g/2; 2025-07-03 22:05:29.438 UTC client backend[17204] pg_regress/aggregates LOG: disconnection: session time: 0:00:05.339 user=postgres database=regression host=[local] 2025-07-03 22:05:29.751 UTC client backend[17196] pg_regress/join ERROR: column reference "f1" is ambiguous at character 78 2025-07-03 22:05:29.751 UTC client backend[17196] pg_regress/join STATEMENT: select * from int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = f1; 2025-07-03 22:05:29.751 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "y" at character 78 2025-07-03 22:05:29.751 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "y", but it cannot be referenced from this part of the query. 2025-07-03 22:05:29.751 UTC client backend[17196] pg_regress/join STATEMENT: select * from int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = y.f1; 2025-07-03 22:05:30.127 UTC client backend[17196] pg_regress/join ERROR: column t1.uunique1 does not exist at character 8 2025-07-03 22:05:30.127 UTC client backend[17196] pg_regress/join HINT: Perhaps you meant to reference the column "t1.unique1". 2025-07-03 22:05:30.127 UTC client backend[17196] pg_regress/join STATEMENT: select t1.uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join ERROR: column t2.uunique1 does not exist at character 8 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join HINT: Perhaps you meant to reference the column "t2.unique1". 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join STATEMENT: select t2.uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join ERROR: column "uunique1" does not exist at character 8 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join HINT: Perhaps you meant to reference the column "t1.unique1" or the column "t2.unique1". 2025-07-03 22:05:30.128 UTC client backend[17196] pg_regress/join STATEMENT: select uunique1 from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-07-03 22:05:30.129 UTC client backend[17196] pg_regress/join ERROR: column "ctid" does not exist at character 8 2025-07-03 22:05:30.129 UTC client backend[17196] pg_regress/join DETAIL: There are columns named "ctid", but they are in tables that cannot be referenced from this part of the query. 2025-07-03 22:05:30.129 UTC client backend[17196] pg_regress/join HINT: Try using a table-qualified name. 2025-07-03 22:05:30.129 UTC client backend[17196] pg_regress/join STATEMENT: select ctid from tenk1 t1 join tenk2 t2 on t1.two = t2.two; 2025-07-03 22:05:30.133 UTC client backend[17196] pg_regress/join ERROR: column atts.relid does not exist at character 8 2025-07-03 22:05:30.133 UTC client backend[17196] pg_regress/join STATEMENT: select atts.relid::regclass, s.* from pg_stats s join pg_attribute a on s.attname = a.attname and s.tablename = a.attrelid::regclass::text join (select unnest(indkey) attnum, indexrelid from pg_index i) atts on atts.attnum = a.attnum where schemaname != 'pg_catalog'; 2025-07-03 22:05:30.579 UTC client backend[17196] pg_regress/join ERROR: join expression "ss" has 3 columns available but 4 columns specified 2025-07-03 22:05:30.579 UTC client backend[17196] pg_regress/join STATEMENT: SELECT * FROM (int8_tbl i cross join int4_tbl j) ss(a,b,c,d); 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join ERROR: column "f1" does not exist at character 38 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join DETAIL: There is a column named "f1" in table "a", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join HINT: To reference that column, you must mark this subquery with LATERAL. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a, (select f1 as g) ss; 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 38 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "a", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join HINT: To reference that table, you must mark this subquery with LATERAL. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a, (select a.f1 as g) ss; 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join ERROR: column "f1" does not exist at character 48 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join DETAIL: There is a column named "f1" in table "a", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join HINT: To reference that column, you must mark this subquery with LATERAL. 2025-07-03 22:05:30.597 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a cross join (select f1 as g) ss; 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 48 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "a", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join HINT: To reference that table, you must mark this subquery with LATERAL. 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a cross join (select a.f1 as g) ss; 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 67 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join DETAIL: The combining JOIN type must be INNER or LEFT for a LATERAL reference. 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a right join lateral generate_series(0, a.f1) g on true; 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "a" at character 66 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join DETAIL: The combining JOIN type must be INNER or LEFT for a LATERAL reference. 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join STATEMENT: select f1,g from int4_tbl a full join lateral generate_series(0, a.f1) g on true; 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join ERROR: table reference "x" is ambiguous at character 78 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join STATEMENT: select * from int8_tbl x cross join (int4_tbl x cross join lateral (select x.f1) ss); 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 40 2025-07-03 22:05:30.598 UTC client backend[17196] pg_regress/join STATEMENT: select 1 from tenk1 a, lateral (select max(a.unique1) from int4_tbl b) ss; 2025-07-03 22:05:30.605 UTC client backend[17196] pg_regress/join ERROR: column "x1" does not exist at character 64 2025-07-03 22:05:30.605 UTC client backend[17196] pg_regress/join DETAIL: There is a column named "x1" in table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.605 UTC client backend[17196] pg_regress/join STATEMENT: update xx1 set x2 = f1 from (select * from int4_tbl where f1 = x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 64 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: update xx1 set x2 = f1 from (select * from int4_tbl where f1 = xx1.x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 72 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join HINT: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: update xx1 set x2 = f1 from lateral (select * from int4_tbl where f1 = x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: table name "xx1" specified more than once 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: update xx1 set x2 = f1 from xx1, lateral (select * from int4_tbl where f1 = x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: column "x1" does not exist at character 58 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join DETAIL: There is a column named "x1" in table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: delete from xx1 using (select * from int4_tbl where f1 = x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 58 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join DETAIL: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: delete from xx1 using (select * from int4_tbl where f1 = xx1.x1) ss; 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join ERROR: invalid reference to FROM-clause entry for table "xx1" at character 66 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join HINT: There is an entry for table "xx1", but it cannot be referenced from this part of the query. 2025-07-03 22:05:30.606 UTC client backend[17196] pg_regress/join STATEMENT: delete from xx1 using lateral (select * from int4_tbl where f1 = x1) ss; 2025-07-03 22:05:31.281 UTC client backend[17196] pg_regress/join LOG: disconnection: session time: 0:00:07.212 user=postgres database=regression host=[local] 2025-07-03 22:05:32.091 UTC client backend[17209] pg_regress/btree_index ERROR: operator class int4_ops has no options 2025-07-03 22:05:32.091 UTC client backend[17209] pg_regress/btree_index STATEMENT: create index on btree_tall_tbl (id int4_ops(foo=1)); 2025-07-03 22:05:32.148 UTC client backend[17209] pg_regress/btree_index ERROR: ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_tall_idx2" 2025-07-03 22:05:32.148 UTC client backend[17209] pg_regress/btree_index DETAIL: This operation is not supported for indexes. 2025-07-03 22:05:32.148 UTC client backend[17209] pg_regress/btree_index STATEMENT: ALTER INDEX btree_tall_idx2 ALTER COLUMN id SET (n_distinct=100); 2025-07-03 22:05:32.154 UTC client backend[17209] pg_regress/btree_index ERROR: ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_part_idx" 2025-07-03 22:05:32.154 UTC client backend[17209] pg_regress/btree_index DETAIL: This operation is not supported for partitioned indexes. 2025-07-03 22:05:32.154 UTC client backend[17209] pg_regress/btree_index STATEMENT: ALTER INDEX btree_part_idx ALTER COLUMN id SET (n_distinct=100); 2025-07-03 22:05:32.167 UTC client backend[17209] pg_regress/btree_index LOG: disconnection: session time: 0:00:08.032 user=postgres database=regression host=[local] 2025-07-03 22:05:32.439 UTC not initialized[17961] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.444 UTC client backend[17961] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.444 UTC client backend[17961] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rowsecurity 2025-07-03 22:05:32.446 UTC not initialized[17964] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.448 UTC not initialized[17966] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.449 UTC client backend[17966] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.449 UTC client backend[17966] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/security_label 2025-07-03 22:05:32.451 UTC not initialized[17963] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.451 UTC not initialized[17960] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.453 UTC client backend[17963] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.453 UTC client backend[17963] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/spgist 2025-07-03 22:05:32.453 UTC client backend[17960] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.453 UTC client backend[17960] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/gist 2025-07-03 22:05:32.455 UTC client backend[17964] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.455 UTC client backend[17964] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate 2025-07-03 22:05:32.455 UTC not initialized[17965] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.455 UTC not initialized[17962] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.456 UTC client backend[17963] pg_regress/spgist LOG: connection ready: setup total=27.550 ms, fork=19.230 ms, authentication=0.389 ms 2025-07-03 22:05:32.457 UTC client backend[17965] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.457 UTC client backend[17965] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin 2025-07-03 22:05:32.459 UTC not initialized[17967] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.459 UTC client backend[17962] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.459 UTC client backend[17962] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/matview 2025-07-03 22:05:32.460 UTC client backend[17964] pg_regress/collate LOG: connection ready: setup total=30.797 ms, fork=15.037 ms, authentication=8.040 ms 2025-07-03 22:05:32.461 UTC client backend[17967] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.461 UTC client backend[17967] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/gin 2025-07-03 22:05:32.462 UTC client backend[17962] pg_regress/matview LOG: connection ready: setup total=35.826 ms, fork=18.966 ms, authentication=3.346 ms 2025-07-03 22:05:32.467 UTC client backend[17961] pg_regress/rowsecurity LOG: connection ready: setup total=44.663 ms, fork=13.055 ms, authentication=0.430 ms 2025-07-03 22:05:32.473 UTC client backend[17966] pg_regress/security_label LOG: connection ready: setup total=40.235 ms, fork=12.780 ms, authentication=0.400 ms 2025-07-03 22:05:32.476 UTC client backend[17960] pg_regress/gist LOG: connection ready: setup total=54.478 ms, fork=24.015 ms, authentication=0.373 ms 2025-07-03 22:05:32.479 UTC not initialized[17970] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.481 UTC client backend[17970] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.481 UTC client backend[17970] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/object_address 2025-07-03 22:05:32.485 UTC client backend[17965] pg_regress/brin LOG: connection ready: setup total=54.448 ms, fork=16.299 ms, authentication=0.475 ms 2025-07-03 22:05:32.486 UTC client backend[17970] pg_regress/object_address LOG: connection ready: setup total=39.231 ms, fork=24.530 ms, authentication=0.412 ms 2025-07-03 22:05:32.492 UTC not initialized[17971] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.493 UTC client backend[17971] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.493 UTC client backend[17971] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/lock 2025-07-03 22:05:32.495 UTC not initialized[17974] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.495 UTC not initialized[17972] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.495 UTC not initialized[17973] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.497 UTC client backend[17972] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.497 UTC client backend[17972] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/init_privs 2025-07-03 22:05:32.497 UTC client backend[17973] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.497 UTC client backend[17973] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:32.499 UTC client backend[17967] pg_regress/gin LOG: connection ready: setup total=65.551 ms, fork=20.788 ms, authentication=0.404 ms 2025-07-03 22:05:32.505 UTC client backend[17974] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.505 UTC client backend[17974] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/replica_identity 2025-07-03 22:05:32.509 UTC not initialized[17976] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.511 UTC client backend[17973] pg_regress/privileges LOG: connection ready: setup total=48.305 ms, fork=30.825 ms, authentication=0.399 ms 2025-07-03 22:05:32.515 UTC not initialized[17977] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.516 UTC client backend[17974] pg_regress/replica_identity LOG: connection ready: setup total=38.633 ms, fork=15.858 ms, authentication=0.403 ms 2025-07-03 22:05:32.517 UTC client backend[17977] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.517 UTC client backend[17977] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/drop_operator 2025-07-03 22:05:32.519 UTC client backend[17976] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.519 UTC client backend[17976] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tablesample 2025-07-03 22:05:32.520 UTC client backend[17971] pg_regress/lock LOG: connection ready: setup total=62.103 ms, fork=33.758 ms, authentication=0.390 ms 2025-07-03 22:05:32.520 UTC not initialized[17982] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.522 UTC client backend[17982] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.522 UTC client backend[17982] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/join_hash 2025-07-03 22:05:32.522 UTC client backend[17972] pg_regress/init_privs LOG: connection ready: setup total=60.417 ms, fork=29.993 ms, authentication=0.388 ms 2025-07-03 22:05:32.523 UTC client backend[17976] pg_regress/tablesample LOG: connection ready: setup total=38.844 ms, fork=23.351 ms, authentication=0.393 ms 2025-07-03 22:05:32.525 UTC not initialized[17980] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.526 UTC client backend[17980] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.526 UTC client backend[17980] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/identity 2025-07-03 22:05:32.527 UTC not initialized[17978] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.529 UTC client backend[17980] pg_regress/identity LOG: connection ready: setup total=18.177 ms, fork=12.713 ms, authentication=0.410 ms 2025-07-03 22:05:32.534 UTC not initialized[17979] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.537 UTC client backend[17982] pg_regress/join_hash LOG: connection ready: setup total=24.389 ms, fork=7.158 ms, authentication=0.416 ms 2025-07-03 22:05:32.537 UTC client backend[17977] pg_regress/drop_operator LOG: connection ready: setup total=46.816 ms, fork=18.211 ms, authentication=0.395 ms 2025-07-03 22:05:32.538 UTC not initialized[17984] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:32.539 UTC client backend[17984] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.539 UTC client backend[17984] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/generated_stored 2025-07-03 22:05:32.539 UTC client backend[17978] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.539 UTC client backend[17978] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/password 2025-07-03 22:05:32.541 UTC client backend[17979] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:32.541 UTC client backend[17979] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/groupingsets 2025-07-03 22:05:32.589 UTC client backend[17972] pg_regress/init_privs LOG: disconnection: session time: 0:00:00.097 user=postgres database=regression host=[local] 2025-07-03 22:05:32.590 UTC client backend[17973] pg_regress/privileges ERROR: role "regress_priv_user5" already exists 2025-07-03 22:05:32.590 UTC client backend[17973] pg_regress/privileges STATEMENT: CREATE USER regress_priv_user5; 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges ERROR: ADMIN option cannot be granted back to your own grantor 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges STATEMENT: GRANT regress_priv_user1 TO regress_priv_user2 WITH ADMIN OPTION GRANTED BY regress_priv_user3; 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges ERROR: dependent privileges exist 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges STATEMENT: REVOKE ADMIN OPTION FOR regress_priv_user1 FROM regress_priv_user2; 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges ERROR: dependent privileges exist 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-07-03 22:05:32.604 UTC client backend[17973] pg_regress/privileges STATEMENT: REVOKE regress_priv_user1 FROM regress_priv_user2; 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist ERROR: invalid value for enum option "buffering": invalid_value 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist DETAIL: Valid values are "on", "off", and "auto". 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (buffering = invalid_value); 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist ERROR: value 9 out of bounds for option "fillfactor" 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=9); 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist ERROR: value 101 out of bounds for option "fillfactor" 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:32.609 UTC client backend[17960] pg_regress/gist STATEMENT: create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=101); 2025-07-03 22:05:32.634 UTC client backend[17973] pg_regress/privileges ERROR: role "regress_priv_user2" cannot be dropped because some objects depend on it 2025-07-03 22:05:32.634 UTC client backend[17973] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user3 in role regress_priv_user1 2025-07-03 22:05:32.634 UTC client backend[17973] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user2; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl1 IS 'classified'; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: security label provider "dummy" is not loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL FOR 'dummy' ON TABLE seclabel_tbl1 IS 'classified'; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl1 IS '...invalid label...'; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON TABLE seclabel_tbl3 IS 'unclassified'; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user1 IS 'classified'; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: security label provider "dummy" is not loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL FOR 'dummy' ON ROLE regress_seclabel_user1 IS 'classified'; 2025-07-03 22:05:32.635 UTC client backend[17973] pg_regress/privileges ERROR: role "regress_priv_user2" cannot be dropped because some objects depend on it 2025-07-03 22:05:32.635 UTC client backend[17973] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user3 in role regress_priv_user1 2025-07-03 22:05:32.635 UTC client backend[17973] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user2; 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.635 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user1 IS '...invalid label...'; 2025-07-03 22:05:32.636 UTC client backend[17966] pg_regress/security_label ERROR: no security label providers have been loaded 2025-07-03 22:05:32.636 UTC client backend[17966] pg_regress/security_label STATEMENT: SECURITY LABEL ON ROLE regress_seclabel_user3 IS 'unclassified'; 2025-07-03 22:05:32.650 UTC client backend[17979] pg_regress/groupingsets LOG: connection ready: setup total=157.310 ms, fork=38.243 ms, authentication=0.396 ms 2025-07-03 22:05:32.658 UTC client backend[17973] pg_regress/privileges ERROR: role "regress_priv_user3" cannot be dropped because some objects depend on it 2025-07-03 22:05:32.658 UTC client backend[17973] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user4 in role regress_priv_user1 2025-07-03 22:05:32.658 UTC client backend[17973] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user3; 2025-07-03 22:05:32.664 UTC client backend[17984] pg_regress/generated_stored LOG: connection ready: setup total=150.994 ms, fork=20.997 ms, authentication=0.393 ms 2025-07-03 22:05:32.681 UTC client backend[17973] pg_regress/privileges ERROR: role "regress_priv_user5" cannot be dropped because some objects depend on it 2025-07-03 22:05:32.681 UTC client backend[17973] pg_regress/privileges DETAIL: privileges for membership of role regress_priv_user6 in role regress_priv_user1 2025-07-03 22:05:32.681 UTC client backend[17973] pg_regress/privileges STATEMENT: DROP ROLE regress_priv_user5; 2025-07-03 22:05:32.686 UTC client backend[17977] pg_regress/drop_operator LOG: disconnection: session time: 0:00:00.178 user=postgres database=regression host=[local] 2025-07-03 22:05:32.716 UTC client backend[17962] pg_regress/matview ERROR: materialized view "mvtest_tm" has not been populated 2025-07-03 22:05:32.716 UTC client backend[17962] pg_regress/matview HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-07-03 22:05:32.716 UTC client backend[17962] pg_regress/matview STATEMENT: SELECT * FROM mvtest_tm ORDER BY type; 2025-07-03 22:05:32.733 UTC client backend[17978] pg_regress/password LOG: connection ready: setup total=241.616 ms, fork=32.945 ms, authentication=0.373 ms 2025-07-03 22:05:32.758 UTC client backend[17966] pg_regress/security_label LOG: disconnection: session time: 0:00:00.312 user=postgres database=regression host=[local] 2025-07-03 22:05:32.767 UTC client backend[17978] pg_regress/password ERROR: invalid value for parameter "password_encryption": "novalue" 2025-07-03 22:05:32.767 UTC client backend[17978] pg_regress/password HINT: Available values: md5, scram-sha-256. 2025-07-03 22:05:32.767 UTC client backend[17978] pg_regress/password STATEMENT: SET password_encryption = 'novalue'; 2025-07-03 22:05:32.768 UTC client backend[17978] pg_regress/password ERROR: invalid value for parameter "password_encryption": "true" 2025-07-03 22:05:32.768 UTC client backend[17978] pg_regress/password HINT: Available values: md5, scram-sha-256. 2025-07-03 22:05:32.768 UTC client backend[17978] pg_regress/password STATEMENT: SET password_encryption = true; 2025-07-03 22:05:32.773 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to set role "pg_read_all_settings" 2025-07-03 22:05:32.773 UTC client backend[17973] pg_regress/privileges STATEMENT: SET ROLE pg_read_all_settings; 2025-07-03 22:05:32.773 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to set role "pg_read_all_stats" 2025-07-03 22:05:32.773 UTC client backend[17973] pg_regress/privileges STATEMENT: SET ROLE pg_read_all_stats; 2025-07-03 22:05:32.776 UTC client backend[17978] pg_regress/password WARNING: setting an MD5-encrypted password 2025-07-03 22:05:32.776 UTC client backend[17978] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-07-03 22:05:32.776 UTC client backend[17978] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-07-03 22:05:32.777 UTC client backend[17978] pg_regress/password WARNING: setting an MD5-encrypted password 2025-07-03 22:05:32.777 UTC client backend[17978] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-07-03 22:05:32.777 UTC client backend[17978] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-07-03 22:05:32.795 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest3" is already an identity column 2025-07-03 22:05:32.795 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest3 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:32.800 UTC client backend[17961] pg_regress/rowsecurity ERROR: unrecognized row security option "ugly" at character 33 2025-07-03 22:05:32.800 UTC client backend[17961] pg_regress/rowsecurity HINT: Only PERMISSIVE or RESTRICTIVE policies are supported currently. 2025-07-03 22:05:32.800 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: CREATE POLICY p1 ON document AS UGLY USING (dlevel <= (SELECT seclv FROM uaccount WHERE pguser = current_user)); 2025-07-03 22:05:32.820 UTC client backend[17970] pg_regress/object_address WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:05:32.820 UTC client backend[17970] pg_regress/object_address HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:05:32.826 UTC client backend[17970] pg_regress/object_address WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:05:32.826 UTC client backend[17970] pg_regress/object_address HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:05:32.830 UTC client backend[17964] pg_regress/collate ERROR: collations are not supported by type integer at character 44 2025-07-03 22:05:32.830 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE TABLE collate_test_fail ( a int COLLATE "C", b text ); 2025-07-03 22:05:32.841 UTC client backend[17970] pg_regress/object_address WARNING: subscription was created, but is not connected 2025-07-03 22:05:32.841 UTC client backend[17970] pg_regress/object_address HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:05:32.844 UTC client backend[17970] pg_regress/object_address ERROR: unrecognized object type "stone" 2025-07-03 22:05:32.844 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('stone', '{}', '{}'); 2025-07-03 22:05:32.845 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be at least 1 2025-07-03 22:05:32.845 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('table', '{}', '{}'); 2025-07-03 22:05:32.851 UTC client backend[17970] pg_regress/object_address ERROR: name or argument lists may not contain nulls 2025-07-03 22:05:32.851 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('table', '{NULL}', '{}'); 2025-07-03 22:05:32.854 UTC client backend[17970] pg_regress/object_address WARNING: error for toast table: unsupported object type "toast table" 2025-07-03 22:05:32.854 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.855 UTC client backend[17971] pg_regress/lock ERROR: permission denied for table lock_tbl2 2025-07-03 22:05:32.855 UTC client backend[17971] pg_regress/lock STATEMENT: LOCK TABLE lock_tbl2; 2025-07-03 22:05:32.863 UTC client backend[17970] pg_regress/object_address WARNING: error for index column: unsupported object type "index column" 2025-07-03 22:05:32.863 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.863 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence column: unsupported object type "sequence column" 2025-07-03 22:05:32.863 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.865 UTC client backend[17971] pg_regress/lock ERROR: permission denied for view lock_view1 2025-07-03 22:05:32.865 UTC client backend[17971] pg_regress/lock STATEMENT: LOCK TABLE lock_view1; 2025-07-03 22:05:32.874 UTC client backend[17970] pg_regress/object_address WARNING: error for toast table column: unsupported object type "toast table column" 2025-07-03 22:05:32.874 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address WARNING: error for view column: unsupported object type "view column" 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view column: unsupported object type "materialized view column" 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 11 at RAISE 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address ERROR: operator 1 (int4, bool) of operator family integer_ops for access method btree does not exist 2025-07-03 22:05:32.875 UTC client backend[17970] pg_regress/object_address STATEMENT: select * from pg_get_object_address('operator of access method', '{btree,integer_ops,1}', '{int4,bool}'); 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address ERROR: operator 99 (int4, int4) of operator family integer_ops for access method btree does not exist 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address STATEMENT: select * from pg_get_object_address('operator of access method', '{btree,integer_ops,99}', '{int4,int4}'); 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address ERROR: function 1 (int4, bool) of operator family integer_ops for access method btree does not exist 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address STATEMENT: select * from pg_get_object_address('function of access method', '{btree,integer_ops,1}', '{int4,bool}'); 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address ERROR: function 99 (int4, int4) of operator family integer_ops for access method btree does not exist 2025-07-03 22:05:32.876 UTC client backend[17970] pg_regress/object_address STATEMENT: select * from pg_get_object_address('function of access method', '{btree,integer_ops,99}', '{int4,int4}'); 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.878 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.883 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.883 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.894 UTC client backend[17978] pg_regress/password WARNING: setting an MD5-encrypted password 2025-07-03 22:05:32.894 UTC client backend[17978] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-07-03 22:05:32.894 UTC client backend[17978] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-07-03 22:05:32.895 UTC client backend[17978] pg_regress/password WARNING: setting an MD5-encrypted password 2025-07-03 22:05:32.895 UTC client backend[17978] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-07-03 22:05:32.895 UTC client backend[17978] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-07-03 22:05:32.898 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.898 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.899 UTC client backend[17970] pg_regress/object_address WARNING: error for table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.899 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.899 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.899 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.903 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for index,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address WARNING: error for sequence,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.904 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.905 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.906 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.906 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.906 UTC client backend[17970] pg_regress/object_address WARNING: error for view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.906 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.909 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.909 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.909 UTC client backend[17971] pg_regress/lock ERROR: permission denied for view lock_view8 2025-07-03 22:05:32.909 UTC client backend[17971] pg_regress/lock STATEMENT: LOCK TABLE lock_view8; 2025-07-03 22:05:32.912 UTC client backend[17971] pg_regress/lock ERROR: permission denied for table lock_tbl1 2025-07-03 22:05:32.912 UTC client backend[17971] pg_regress/lock STATEMENT: LOCK TABLE lock_view8; 2025-07-03 22:05:32.914 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.914 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.914 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.914 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.915 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.915 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.919 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.919 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for materialized view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{eins},{}: relation "eins" does not exist 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.923 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{eins},{}: column name must be qualified 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{eins},{integer}: column name must be qualified 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for table column,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{eins},{}: column name must be qualified 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{eins},{integer}: column name must be qualified 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.924 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for foreign table column,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{eins},{}: aggregate eins(*) does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{eins},{integer}: aggregate eins(integer) does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{addr_nsp,zwei},{}: aggregate addr_nsp.zwei(*) does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{addr_nsp,zwei},{integer}: aggregate addr_nsp.zwei(integer) does not exist 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.925 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address WARNING: error for aggregate,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{eins},{}: function eins() does not exist 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{eins},{integer}: function eins(integer) does not exist 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{addr_nsp,zwei},{}: function addr_nsp.zwei() does not exist 2025-07-03 22:05:32.927 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{addr_nsp,zwei},{integer}: function addr_nsp.zwei(integer) does not exist 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for function,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{eins},{}: procedure eins() does not exist 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{eins},{integer}: procedure eins(integer) does not exist 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{addr_nsp,zwei},{}: procedure addr_nsp.zwei() does not exist 2025-07-03 22:05:32.928 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{addr_nsp,zwei},{integer}: procedure addr_nsp.zwei(integer) does not exist 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address WARNING: error for procedure,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.929 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{eins},{}: type "eins" does not exist 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{eins},{integer}: type "eins" does not exist 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.930 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.931 UTC client backend[17970] pg_regress/object_address WARNING: error for type,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.931 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.934 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use non-unique index "test_replica_identity_keyab" as replica identity 2025-07-03 22:05:32.934 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_keyab; 2025-07-03 22:05:32.934 UTC client backend[17974] pg_regress/replica_identity ERROR: index "test_replica_identity_nonkey" cannot be used as replica identity because column "nonkey" is nullable 2025-07-03 22:05:32.934 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_nonkey; 2025-07-03 22:05:32.935 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.935 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.935 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use non-unique index "test_replica_identity_hash" as replica identity 2025-07-03 22:05:32.935 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_hash; 2025-07-03 22:05:32.935 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use expression index "test_replica_identity_expr" as replica identity 2025-07-03 22:05:32.935 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_expr; 2025-07-03 22:05:32.936 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use partial index "test_replica_identity_partial" as replica identity 2025-07-03 22:05:32.936 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_partial; 2025-07-03 22:05:32.936 UTC client backend[17974] pg_regress/replica_identity ERROR: "test_replica_identity_othertable_pkey" is not an index for table "test_replica_identity" 2025-07-03 22:05:32.936 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_othertable_pkey; 2025-07-03 22:05:32.937 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use non-immediate index "test_replica_identity_unique_defer" as replica identity 2025-07-03 22:05:32.937 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_unique_defer; 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{eins},{integer}: type "eins" does not exist 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.941 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for cast,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{eins},{}: must specify relation and object name 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{eins},{integer}: must specify relation and object name 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for table constraint,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{eins},{integer}: type "eins" does not exist 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.942 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for domain constraint,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{eins},{}: conversion "eins" does not exist 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{eins},{integer}: conversion "eins" does not exist 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{addr_nsp,zwei},{}: conversion "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{addr_nsp,zwei},{integer}: conversion "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address WARNING: error for conversion,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.943 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.944 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{eins},{}: column name must be qualified 2025-07-03 22:05:32.944 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.944 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{eins},{integer}: column name must be qualified 2025-07-03 22:05:32.944 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.948 UTC client backend[17974] pg_regress/replica_identity ERROR: cannot use non-immediate index "pk" as replica identity 2025-07-03 22:05:32.948 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity_t3 REPLICA IDENTITY USING INDEX pk; 2025-07-03 22:05:32.955 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.955 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.959 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.959 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.959 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.959 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for default value,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{eins},{}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{eins},{integer}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{addr_nsp,zwei},{}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{addr_nsp,zwei},{integer}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address WARNING: error for operator,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-07-03 22:05:32.960 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{eins},{}: name list length must be at least 2 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{eins},{integer}: name list length must be at least 2 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist 2025-07-03 22:05:32.964 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{eins,zwei,drei},{}: access method "eins" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator class,{eins,zwei,drei},{integer}: access method "eins" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{eins},{}: name list length must be at least 2 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{eins},{integer}: name list length must be at least 2 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{eins,zwei,drei},{}: access method "eins" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for operator family,{eins,zwei,drei},{integer}: access method "eins" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{eins},{}: must specify relation and object name 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{eins},{integer}: must specify relation and object name 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.965 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.966 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.966 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address WARNING: error for rule,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{eins},{}: must specify relation and object name 2025-07-03 22:05:32.968 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{eins},{integer}: must specify relation and object name 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for trigger,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{eins},{}: text search parser "eins" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{eins},{integer}: text search parser "eins" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{addr_nsp,zwei},{}: text search parser "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.969 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{addr_nsp,zwei},{integer}: text search parser "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search parser,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{eins},{}: text search dictionary "eins" does not exist 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{eins},{integer}: text search dictionary "eins" does not exist 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{addr_nsp,zwei},{}: text search dictionary "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{addr_nsp,zwei},{integer}: text search dictionary "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address WARNING: error for text search dictionary,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.970 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{eins},{}: text search template "eins" does not exist 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{eins},{integer}: text search template "eins" does not exist 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{addr_nsp,zwei},{}: text search template "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{addr_nsp,zwei},{integer}: text search template "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search template,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{eins},{}: text search configuration "eins" does not exist 2025-07-03 22:05:32.971 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.974 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{eins},{integer}: text search configuration "eins" does not exist 2025-07-03 22:05:32.974 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.974 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{addr_nsp,zwei},{}: text search configuration "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.974 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.976 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{addr_nsp,zwei},{integer}: text search configuration "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.976 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address WARNING: error for text search configuration,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{eins},{}: must specify relation and object name 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{eins},{integer}: must specify relation and object name 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.977 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{eins,zwei,drei},{}: schema "eins" does not exist 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address WARNING: error for policy,{eins,zwei,drei},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.978 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.983 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.983 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.985 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{eins},{integer}: user mapping for user "eins" on server "integer" does not exist 2025-07-03 22:05:32.985 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.991 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.991 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.991 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.991 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for user mapping,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{eins},{integer}: unrecognized default ACL object type "i" 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{addr_nsp,zwei},{}: argument list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{addr_nsp,zwei},{integer}: unrecognized default ACL object type "i" 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{eins,zwei,drei},{}: argument list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for default acl,{eins,zwei,drei},{integer}: unrecognized default ACL object type "i" 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{eins},{integer}: type "eins" does not exist 2025-07-03 22:05:32.994 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for transform,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{eins},{}: name list length must be at least 3 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{eins},{integer}: name list length must be at least 3 2025-07-03 22:05:32.995 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{addr_nsp,zwei},{}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for operator of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{eins},{}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{eins},{integer}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{addr_nsp,zwei},{}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{eins,zwei,drei},{}: argument list length must be exactly 2 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for function of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{eins},{integer}: schema "eins" does not exist 2025-07-03 22:05:32.998 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{addr_nsp,zwei},{}: name list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{addr_nsp,zwei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{eins,zwei,drei},{}: name list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication namespace,{eins,zwei,drei},{integer}: name list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{eins},{}: argument list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{eins},{integer}: relation "eins" does not exist 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{addr_nsp,zwei},{}: argument list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{eins,zwei,drei},{}: argument list length must be exactly 1 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address WARNING: error for publication relation,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei" 2025-07-03 22:05:32.999 UTC client backend[17970] pg_regress/object_address CONTEXT: PL/pgSQL function inline_code_block line 27 at RAISE 2025-07-03 22:05:33.000 UTC client backend[17970] pg_regress/object_address ERROR: language "one" does not exist 2025-07-03 22:05:33.000 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('language', '{one}', '{}'); 2025-07-03 22:05:33.000 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.000 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('language', '{one,two}', '{}'); 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address ERROR: large object 123 does not exist 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{123}', '{}'); 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{123,456}', '{}'); 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address ERROR: invalid input syntax for type oid: "blargh" 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('large object', '{blargh}', '{}'); 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address ERROR: schema "one" does not exist 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('schema', '{one}', '{}'); 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.001 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('schema', '{one,two}', '{}'); 2025-07-03 22:05:33.002 UTC client backend[17970] pg_regress/object_address ERROR: role "one" does not exist 2025-07-03 22:05:33.002 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('role', '{one}', '{}'); 2025-07-03 22:05:33.002 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.002 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('role', '{one,two}', '{}'); 2025-07-03 22:05:33.015 UTC client backend[17970] pg_regress/object_address ERROR: database "one" does not exist 2025-07-03 22:05:33.015 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('database', '{one}', '{}'); 2025-07-03 22:05:33.015 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.015 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('database', '{one,two}', '{}'); 2025-07-03 22:05:33.016 UTC client backend[17970] pg_regress/object_address ERROR: tablespace "one" does not exist 2025-07-03 22:05:33.016 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('tablespace', '{one}', '{}'); 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('tablespace', '{one,two}', '{}'); 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address ERROR: foreign-data wrapper "one" does not exist 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('foreign-data wrapper', '{one}', '{}'); 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.020 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('foreign-data wrapper', '{one,two}', '{}'); 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address ERROR: server "one" does not exist 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('server', '{one}', '{}'); 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('server', '{one,two}', '{}'); 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address ERROR: extension "one" does not exist 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('extension', '{one}', '{}'); 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('extension', '{one,two}', '{}'); 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address ERROR: event trigger "one" does not exist 2025-07-03 22:05:33.021 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('event trigger', '{one}', '{}'); 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('event trigger', '{one,two}', '{}'); 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address ERROR: access method "one" does not exist 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('access method', '{one}', '{}'); 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.024 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('access method', '{one,two}', '{}'); 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address ERROR: publication "one" does not exist 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('publication', '{one}', '{}'); 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('publication', '{one,two}', '{}'); 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address ERROR: subscription "one" does not exist 2025-07-03 22:05:33.025 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('subscription', '{one}', '{}'); 2025-07-03 22:05:33.026 UTC client backend[17970] pg_regress/object_address ERROR: name list length must be exactly 1 2025-07-03 22:05:33.026 UTC client backend[17970] pg_regress/object_address STATEMENT: SELECT pg_get_object_address('subscription', '{one,two}', '{}'); 2025-07-03 22:05:33.065 UTC client backend[17978] pg_regress/password WARNING: setting an MD5-encrypted password 2025-07-03 22:05:33.065 UTC client backend[17978] pg_regress/password DETAIL: MD5 password support is deprecated and will be removed in a future release of PostgreSQL. 2025-07-03 22:05:33.065 UTC client backend[17978] pg_regress/password HINT: Refer to the PostgreSQL documentation for details about migrating to another password type. 2025-07-03 22:05:33.115 UTC client backend[17971] pg_regress/lock LOG: disconnection: session time: 0:00:00.623 user=postgres database=regression host=[local] 2025-07-03 22:05:33.128 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 58 2025-07-03 22:05:33.128 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "POSIX"; 2025-07-03 22:05:33.138 UTC client backend[17964] pg_regress/collate ERROR: collations are not supported by type integer at character 31 2025-07-03 22:05:33.138 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE DOMAIN testdomain_i AS int COLLATE "POSIX"; 2025-07-03 22:05:33.160 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest4" must be declared NOT NULL before identity can be added 2025-07-03 22:05:33.160 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:33.185 UTC client backend[17980] pg_regress/identity ERROR: column "c" of relation "itest4" does not exist 2025-07-03 22:05:33.185 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN c ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:33.187 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest4" is an identity column 2025-07-03 22:05:33.187 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a DROP NOT NULL; 2025-07-03 22:05:33.189 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest4" is already an identity column 2025-07-03 22:05:33.189 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:33.198 UTC client backend[17980] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-07-03 22:05:33.198 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN b ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:33.199 UTC client backend[17980] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-07-03 22:05:33.199 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest_err_1 (a text generated by default as identity); 2025-07-03 22:05:33.199 UTC client backend[17980] pg_regress/identity ERROR: multiple identity specifications for column "a" of table "itest_err_2" at character 62 2025-07-03 22:05:33.199 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest_err_2 (a int generated always as identity generated by default as identity); 2025-07-03 22:05:33.200 UTC client backend[17980] pg_regress/identity ERROR: both default and identity specified for column "a" of table "itest_err_3" at character 43 2025-07-03 22:05:33.200 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest_err_3 (a int default 5 generated by default as identity); 2025-07-03 22:05:33.200 UTC client backend[17980] pg_regress/identity ERROR: both default and identity specified for column "a" of table "itest_err_4" 2025-07-03 22:05:33.200 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest_err_4 (a serial generated by default as identity); 2025-07-03 22:05:33.235 UTC client backend[17984] pg_regress/generated_stored ERROR: multiple generation clauses specified for column "b" of table "gtest_err_1" at character 87 2025-07-03 22:05:33.235 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_1 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) STORED GENERATED ALWAYS AS (a * 3) STORED); 2025-07-03 22:05:33.241 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression at character 74 2025-07-03 22:05:33.241 UTC client backend[17984] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:05:33.241 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_2a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (b * 2) STORED); 2025-07-03 22:05:33.246 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression at character 116 2025-07-03 22:05:33.246 UTC client backend[17984] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:05:33.246 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_2b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) STORED, c int GENERATED ALWAYS AS (b * 3) STORED); 2025-07-03 22:05:33.251 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use whole-row variable in column generation expression at character 88 2025-07-03 22:05:33.251 UTC client backend[17984] pg_regress/generated_stored DETAIL: This would cause the generated column to depend on its own value. 2025-07-03 22:05:33.251 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_2c (a int PRIMARY KEY, b int GENERATED ALWAYS AS (num_nulls(gtest_err_2c)) STORED); 2025-07-03 22:05:33.256 UTC client backend[17984] pg_regress/generated_stored ERROR: column "c" does not exist at character 73 2025-07-03 22:05:33.256 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_3 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (c * 2) STORED); 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to alter role 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members. 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges STATEMENT: ALTER GROUP regress_priv_group2 ADD USER regress_priv_user2; 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to alter role 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members. 2025-07-03 22:05:33.266 UTC client backend[17973] pg_regress/privileges STATEMENT: ALTER GROUP regress_priv_group2 DROP USER regress_priv_user2; 2025-07-03 22:05:33.267 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to alter role 2025-07-03 22:05:33.267 UTC client backend[17973] pg_regress/privileges DETAIL: To change another role's password, the current user must have the CREATEROLE attribute and the ADMIN option on the role. 2025-07-03 22:05:33.267 UTC client backend[17973] pg_regress/privileges STATEMENT: ALTER USER regress_priv_user2 PASSWORD 'verysecret'; 2025-07-03 22:05:33.270 UTC client backend[17973] pg_regress/privileges ERROR: permission denied to grant privileges as role "regress_priv_role" 2025-07-03 22:05:33.270 UTC client backend[17973] pg_regress/privileges DETAIL: The grantor must have the ADMIN option on role "regress_priv_role". 2025-07-03 22:05:33.270 UTC client backend[17973] pg_regress/privileges STATEMENT: GRANT regress_priv_role TO regress_priv_user1 WITH ADMIN OPTION GRANTED BY regress_priv_role; 2025-07-03 22:05:33.271 UTC client backend[17973] pg_regress/privileges ERROR: role "foo" does not exist 2025-07-03 22:05:33.271 UTC client backend[17973] pg_regress/privileges STATEMENT: REVOKE ADMIN OPTION FOR regress_priv_role FROM regress_priv_user1 GRANTED BY foo; 2025-07-03 22:05:33.271 UTC client backend[17973] pg_regress/privileges WARNING: role "regress_priv_user1" has not been granted membership in role "regress_priv_role" by role "regress_priv_user2" 2025-07-03 22:05:33.274 UTC client backend[17984] pg_regress/generated_stored ERROR: generation expression is not immutable 2025-07-03 22:05:33.274 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) STORED); 2025-07-03 22:05:33.296 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.296 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.296 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.296 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (1, 'a'); 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (2, 'b'), (3, 'c'); 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.313 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (DEFAULT, 'b'), (3, 'c'); 2025-07-03 22:05:33.314 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.314 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.314 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.314 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest5 VALUES (2, 'b'), (DEFAULT, 'c'); 2025-07-03 22:05:33.334 UTC client backend[17984] pg_regress/generated_stored ERROR: both default and generation expression specified for column "b" of table "gtest_err_5a" at character 63 2025-07-03 22:05:33.334 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_5a (a int PRIMARY KEY, b int DEFAULT 5 GENERATED ALWAYS AS (a * 2) STORED); 2025-07-03 22:05:33.334 UTC client backend[17984] pg_regress/generated_stored ERROR: both identity and generation expression specified for column "b" of table "gtest_err_5b" at character 82 2025-07-03 22:05:33.334 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_5b (a int PRIMARY KEY, b int GENERATED ALWAYS AS identity GENERATED ALWAYS AS (a * 2) STORED); 2025-07-03 22:05:33.337 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use system column "xmin" in column generation expression at character 75 2025-07-03 22:05:33.337 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_6a (a int PRIMARY KEY, b bool GENERATED ALWAYS AS (xmin <> 37) STORED); 2025-07-03 22:05:33.341 UTC client backend[17984] pg_regress/generated_stored ERROR: aggregate functions are not allowed in column generation expressions at character 74 2025-07-03 22:05:33.341 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (avg(a)) STORED); 2025-07-03 22:05:33.346 UTC client backend[17984] pg_regress/generated_stored ERROR: window functions are not allowed in column generation expressions at character 74 2025-07-03 22:05:33.346 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (row_number() OVER (ORDER BY a)) STORED); 2025-07-03 22:05:33.360 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use subquery in column generation expression at character 74 2025-07-03 22:05:33.360 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7c (a int PRIMARY KEY, b int GENERATED ALWAYS AS ((SELECT a)) STORED); 2025-07-03 22:05:33.371 UTC client backend[17984] pg_regress/generated_stored ERROR: set-returning functions are not allowed in column generation expressions at character 74 2025-07-03 22:05:33.371 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_7d (a int PRIMARY KEY, b int GENERATED ALWAYS AS (generate_series(1, a)) STORED); 2025-07-03 22:05:33.372 UTC client backend[17984] pg_regress/generated_stored ERROR: for a generated column, GENERATED ALWAYS must be specified at character 62 2025-07-03 22:05:33.372 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_err_8 (a int PRIMARY KEY, b int GENERATED BY DEFAULT AS (a * 2) STORED); 2025-07-03 22:05:33.379 UTC client backend[17973] pg_regress/privileges ERROR: grantor must be current user 2025-07-03 22:05:33.379 UTC client backend[17973] pg_regress/privileges STATEMENT: GRANT TRUNCATE ON atest2 TO regress_priv_user4 GRANTED BY regress_priv_user5; 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33); 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.383 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, 44); 2025-07-03 22:05:33.384 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.384 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.384 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, DEFAULT), (4, 44); 2025-07-03 22:05:33.385 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.385 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.385 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, DEFAULT); 2025-07-03 22:05:33.395 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between explicit collations "C" and "POSIX" at character 36 2025-07-03 22:05:33.395 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT string_agg(x COLLATE "C", y COLLATE "POSIX") FROM collate_test10; 2025-07-03 22:05:33.405 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" can only be updated to DEFAULT 2025-07-03 22:05:33.405 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.405 UTC client backend[17984] pg_regress/generated_stored STATEMENT: UPDATE gtest1 SET b = 11 WHERE a = 1; 2025-07-03 22:05:33.406 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.406 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.406 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.406 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest2 VALUES (10, 'xyz'); 2025-07-03 22:05:33.412 UTC client backend[17970] pg_regress/object_address LOG: disconnection: session time: 0:00:00.940 user=postgres database=regression host=[local] 2025-07-03 22:05:33.414 UTC client backend[17984] pg_regress/generated_stored ERROR: integer out of range 2025-07-03 22:05:33.414 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1 VALUES (2000000000); 2025-07-03 22:05:33.423 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.423 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-07-03 22:05:33.428 UTC client backend[17980] pg_regress/identity ERROR: column "a" can only be updated to DEFAULT 2025-07-03 22:05:33.428 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.428 UTC client backend[17980] pg_regress/identity STATEMENT: UPDATE itest2 SET a = 101 WHERE a = 1; 2025-07-03 22:05:33.428 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.428 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest2 SET col2 = NOT col2; 2025-07-03 22:05:33.429 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 32 2025-07-03 22:05:33.429 UTC client backend[17964] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:05:33.429 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT array_agg(a ORDER BY x||y) FROM collate_test10; 2025-07-03 22:05:33.429 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.429 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest2 FOR UPDATE; 2025-07-03 22:05:33.429 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.429 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atest2; 2025-07-03 22:05:33.430 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.430 UTC client backend[17973] pg_regress/privileges STATEMENT: TRUNCATE atest2; 2025-07-03 22:05:33.435 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.435 UTC client backend[17973] pg_regress/privileges STATEMENT: LOCK atest2 IN ACCESS EXCLUSIVE MODE; 2025-07-03 22:05:33.438 UTC client backend[17976] pg_regress/tablesample ERROR: tablesample method foobar does not exist at character 45 2025-07-03 22:05:33.438 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE FOOBAR (1); 2025-07-03 22:05:33.440 UTC client backend[17976] pg_regress/tablesample ERROR: TABLESAMPLE parameter cannot be null 2025-07-03 22:05:33.440 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (NULL); 2025-07-03 22:05:33.441 UTC client backend[17964] pg_regress/collate ERROR: could not determine which collation to use for string comparison 2025-07-03 22:05:33.441 UTC client backend[17964] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:05:33.441 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2 ORDER BY 2; 2025-07-03 22:05:33.441 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.441 UTC client backend[17973] pg_regress/privileges STATEMENT: COPY atest2 FROM stdin; 2025-07-03 22:05:33.441 UTC client backend[17973] pg_regress/privileges WARNING: no privileges were granted for "atest1" 2025-07-03 22:05:33.447 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p1r" for table "document" 2025-07-03 22:05:33.447 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (100, 44, 1, 'regress_rls_dave', 'testing sorting of policies'); 2025-07-03 22:05:33.447 UTC client backend[17976] pg_regress/tablesample ERROR: TABLESAMPLE REPEATABLE parameter cannot be null 2025-07-03 22:05:33.447 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (50) REPEATABLE (NULL); 2025-07-03 22:05:33.448 UTC client backend[17976] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-07-03 22:05:33.448 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (-1); 2025-07-03 22:05:33.450 UTC client backend[17976] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-07-03 22:05:33.450 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (200); 2025-07-03 22:05:33.452 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p2r" for table "document" 2025-07-03 22:05:33.452 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (100, 55, 1, 'regress_rls_dave', 'testing sorting of policies'); 2025-07-03 22:05:33.455 UTC client backend[17976] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-07-03 22:05:33.455 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (-1); 2025-07-03 22:05:33.458 UTC client backend[17976] pg_regress/tablesample ERROR: sample percentage must be between 0 and 100 2025-07-03 22:05:33.458 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (200); 2025-07-03 22:05:33.459 UTC client backend[17976] pg_regress/tablesample ERROR: TABLESAMPLE clause can only be applied to tables and materialized views at character 16 2025-07-03 22:05:33.459 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT id FROM test_tablesample_v1 TABLESAMPLE BERNOULLI (1); 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample ERROR: cannot insert into view "test_tablesample_v1" 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample DETAIL: Views containing TABLESAMPLE are not automatically updatable. 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample HINT: To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule. 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample STATEMENT: INSERT INTO test_tablesample_v1 VALUES(1); 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample ERROR: TABLESAMPLE clause can only be applied to tables and materialized views at character 69 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample STATEMENT: WITH query_select AS (SELECT * FROM test_tablesample) SELECT * FROM query_select TABLESAMPLE BERNOULLI (5.5) REPEATABLE (1); 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample ERROR: syntax error at or near "TABLESAMPLE" at character 55 2025-07-03 22:05:33.463 UTC client backend[17976] pg_regress/tablesample STATEMENT: SELECT q.* FROM (SELECT * FROM test_tablesample) as q TABLESAMPLE BERNOULLI (5); 2025-07-03 22:05:33.464 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 48 2025-07-03 22:05:33.464 UTC client backend[17964] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:05:33.464 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test2 ORDER BY 2; 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 52 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test2 ORDER BY 2; 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 49 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:05:33.465 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test2 ORDER BY 2; 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate ERROR: no collation was derived for column "b" with collatable type text 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2; 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate ERROR: could not determine which collation to use for string comparison 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate STATEMENT: select x < y from collate_test10; 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate ERROR: collation mismatch between implicit collations "C" and "POSIX" at character 47 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:05:33.466 UTC client backend[17964] pg_regress/collate STATEMENT: select x, y from collate_test10 order by x || y; 2025-07-03 22:05:33.467 UTC client backend[17964] pg_regress/collate ERROR: recursive query "foo" column 1 has collation "C" in non-recursive term but collation "POSIX" overall at character 37 2025-07-03 22:05:33.467 UTC client backend[17964] pg_regress/collate HINT: Use the COLLATE clause to set the collation of the non-recursive term. 2025-07-03 22:05:33.467 UTC client backend[17964] pg_regress/collate STATEMENT: WITH RECURSIVE foo(x) AS (SELECT x FROM (VALUES('a' COLLATE "C"),('b')) t(x) UNION ALL SELECT (x || 'c') COLLATE "POSIX" FROM foo WHERE length(x) < 10) SELECT * FROM foo; 2025-07-03 22:05:33.468 UTC client backend[17964] pg_regress/collate ERROR: could not determine which collation to use for string hashing 2025-07-03 22:05:33.468 UTC client backend[17964] pg_regress/collate HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:05:33.468 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT * FROM collate_test10 WHERE (x, y) NOT IN (SELECT y, x FROM collate_test10); 2025-07-03 22:05:33.470 UTC client backend[17961] pg_regress/rowsecurity ERROR: must be owner of table document 2025-07-03 22:05:33.470 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: ALTER POLICY p1 ON document USING (true); 2025-07-03 22:05:33.470 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.470 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-07-03 22:05:33.474 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest1 2025-07-03 22:05:33.474 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest1; 2025-07-03 22:05:33.474 UTC client backend[17961] pg_regress/rowsecurity ERROR: must be owner of relation document 2025-07-03 22:05:33.474 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON document; 2025-07-03 22:05:33.475 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.475 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest2; 2025-07-03 22:05:33.481 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table pg_class 2025-07-03 22:05:33.481 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE pg_catalog.pg_class SET relname = '123'; 2025-07-03 22:05:33.483 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table pg_class 2025-07-03 22:05:33.483 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM pg_catalog.pg_class; 2025-07-03 22:05:33.484 UTC client backend[17964] pg_regress/collate ERROR: syntax error at or near "COLLATE" at character 26 2025-07-03 22:05:33.484 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT CAST('42' AS text COLLATE "C"); 2025-07-03 22:05:33.485 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table pg_toast_1213 2025-07-03 22:05:33.485 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE pg_toast.pg_toast_1213 SET chunk_id = 1; 2025-07-03 22:05:33.488 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.488 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest2; 2025-07-03 22:05:33.488 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest1 2025-07-03 22:05:33.488 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest1 VALUES (2, 'two'); 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest2 VALUES ('foo', true); 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest1 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest1 SELECT 1, b FROM atest1; 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest1 2025-07-03 22:05:33.489 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest1 SET a = 1 WHERE a = 2; 2025-07-03 22:05:33.495 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest4" is not an identity column 2025-07-03 22:05:33.495 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest4 ALTER COLUMN a DROP IDENTITY; 2025-07-03 22:05:33.496 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.496 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest2 SET col2 = NOT col2; 2025-07-03 22:05:33.498 UTC client backend[17980] pg_regress/identity ERROR: null value in column "a" of relation "itest4" violates not-null constraint 2025-07-03 22:05:33.498 UTC client backend[17980] pg_regress/identity DETAIL: Failing row contains (null, ). 2025-07-03 22:05:33.498 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itest4 DEFAULT VALUES; 2025-07-03 22:05:33.506 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest1 2025-07-03 22:05:33.506 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest1 FOR UPDATE; 2025-07-03 22:05:33.507 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.507 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest2 FOR UPDATE; 2025-07-03 22:05:33.508 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.508 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atest2; 2025-07-03 22:05:33.509 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.509 UTC client backend[17973] pg_regress/privileges STATEMENT: TRUNCATE atest2; 2025-07-03 22:05:33.512 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.512 UTC client backend[17973] pg_regress/privileges STATEMENT: COPY atest2 FROM stdin; 2025-07-03 22:05:33.515 UTC client backend[17980] pg_regress/identity ERROR: relation "itest4_a_seq" does not exist at character 27 2025-07-03 22:05:33.515 UTC client backend[17980] pg_regress/identity STATEMENT: SELECT sequence_name FROM itest4_a_seq; 2025-07-03 22:05:33.515 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.515 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest1 WHERE ( b IN ( SELECT col1 FROM atest2 ) ); 2025-07-03 22:05:33.516 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:33.516 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest2 WHERE ( col1 IN ( SELECT b FROM atest1 ) ); 2025-07-03 22:05:33.518 UTC client backend[17961] pg_regress/rowsecurity ERROR: update or delete on table "category" violates foreign key constraint "document_cid_fkey" on table "document" 2025-07-03 22:05:33.518 UTC client backend[17961] pg_regress/rowsecurity DETAIL: Key is still referenced from table "document". 2025-07-03 22:05:33.518 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DELETE FROM category WHERE cid = 33; 2025-07-03 22:05:33.528 UTC client backend[17976] pg_regress/tablesample LOG: disconnection: session time: 0:00:01.020 user=postgres database=regression host=[local] 2025-07-03 22:05:33.541 UTC client backend[17961] pg_regress/rowsecurity ERROR: duplicate key value violates unique constraint "document_pkey" 2025-07-03 22:05:33.541 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (8, 44, 1, 'regress_rls_bob', 'my third manga'); 2025-07-03 22:05:33.542 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:33.542 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (8, 44, 1, 'regress_rls_carol', 'my third manga'); 2025-07-03 22:05:33.544 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:33.544 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: UPDATE document SET did = 8, dauthor = 'regress_rls_carol' WHERE did = 5; 2025-07-03 22:05:33.575 UTC client backend[17964] pg_regress/collate ERROR: collations are not supported by type integer 2025-07-03 22:05:33.575 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "POSIX"); 2025-07-03 22:05:33.583 UTC client backend[17964] pg_regress/collate ERROR: collations are not supported by type integer at character 54 2025-07-03 22:05:33.583 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "POSIX")); 2025-07-03 22:05:33.616 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.616 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.616 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (4, 8); 2025-07-03 22:05:33.619 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.619 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.619 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, 77); 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, DEFAULT), (7, 77); 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.623 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, DEFAULT); 2025-07-03 22:05:33.637 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.637 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.637 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT); 2025-07-03 22:05:33.638 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:05:33.638 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:33.638 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT), (9, DEFAULT); 2025-07-03 22:05:33.640 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:33.640 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:33.640 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:33.640 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT INTO itestv11 VALUES (10, 'xyz'); 2025-07-03 22:05:33.668 UTC client backend[17964] pg_regress/collate ERROR: insert or update on table "collate_test21" violates foreign key constraint "collate_test21_f2_fkey" 2025-07-03 22:05:33.668 UTC client backend[17964] pg_regress/collate DETAIL: Key (f2)=(baz) is not present in table "collate_test20". 2025-07-03 22:05:33.668 UTC client backend[17964] pg_regress/collate STATEMENT: INSERT INTO collate_test21 VALUES ('baz'); 2025-07-03 22:05:33.673 UTC client backend[17978] pg_regress/password ERROR: encrypted password is too long 2025-07-03 22:05:33.673 UTC client backend[17978] pg_regress/password DETAIL: Encrypted passwords must be no longer than 512 bytes. 2025-07-03 22:05:33.673 UTC client backend[17978] pg_regress/password STATEMENT: CREATE ROLE regress_passwd10 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU='; 2025-07-03 22:05:33.708 UTC client backend[17964] pg_regress/collate ERROR: insert or update on table "collate_test22" violates foreign key constraint "collate_test22_f2_fkey" 2025-07-03 22:05:33.708 UTC client backend[17964] pg_regress/collate DETAIL: Key (f2)=(baz) is not present in table "collate_test20". 2025-07-03 22:05:33.708 UTC client backend[17964] pg_regress/collate STATEMENT: ALTER TABLE collate_test22 ADD FOREIGN KEY (f2) REFERENCES collate_test20; 2025-07-03 22:05:33.741 UTC client backend[17978] pg_regress/password ERROR: encrypted password is too long 2025-07-03 22:05:33.741 UTC client backend[17978] pg_regress/password DETAIL: Encrypted passwords must be no longer than 512 bytes. 2025-07-03 22:05:33.741 UTC client backend[17978] pg_regress/password STATEMENT: ALTER ROLE regress_passwd9 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU='; 2025-07-03 22:05:33.752 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest1" is an identity column 2025-07-03 22:05:33.752 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest1 ALTER COLUMN a SET DEFAULT 1; 2025-07-03 22:05:33.758 UTC client backend[17964] pg_regress/collate ERROR: parameter "locale" must be specified 2025-07-03 22:05:33.758 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin ); 2025-07-03 22:05:33.760 UTC client backend[17964] pg_regress/collate ERROR: invalid locale name "en_US" for builtin provider 2025-07-03 22:05:33.760 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin, LOCALE = "en_US" ); 2025-07-03 22:05:33.762 UTC client backend[17964] pg_regress/collate ERROR: parameter "locale" must be specified 2025-07-03 22:05:33.762 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION builtin2 ( PROVIDER = builtin, LC_CTYPE = "C", LC_COLLATE = "C" ); 2025-07-03 22:05:33.767 UTC client backend[17964] pg_regress/collate ERROR: collation "default" cannot be copied 2025-07-03 22:05:33.767 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION mycoll3 FROM "default"; 2025-07-03 22:05:33.788 UTC client backend[17980] pg_regress/identity ERROR: column "a" of relation "itest5" already has a default value 2025-07-03 22:05:33.788 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest5 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:33.801 UTC client backend[17978] pg_regress/password LOG: disconnection: session time: 0:00:01.276 user=postgres database=regression host=[local] 2025-07-03 22:05:33.804 UTC client backend[17964] pg_regress/collate ERROR: cannot drop collation mycoll2 because other objects depend on it 2025-07-03 22:05:33.804 UTC client backend[17964] pg_regress/collate DETAIL: column f1 of table collate_test23 depends on collation mycoll2 2025-07-03 22:05:33.804 UTC client backend[17964] pg_regress/collate HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:33.804 UTC client backend[17964] pg_regress/collate STATEMENT: DROP COLLATION mycoll2; 2025-07-03 22:05:33.805 UTC client backend[17964] pg_regress/collate ERROR: collation attribute "Lc_Collate" not recognized at character 29 2025-07-03 22:05:33.805 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION case_coll ("Lc_Collate" = "POSIX", "Lc_Ctype" = "POSIX"); 2025-07-03 22:05:33.829 UTC client backend[17984] pg_regress/generated_stored ERROR: child column "b" specifies generation expression 2025-07-03 22:05:33.829 UTC client backend[17984] pg_regress/generated_stored HINT: A child table column cannot be generated unless its parent column is. 2025-07-03 22:05:33.829 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_normal_child (a int, b int GENERATED ALWAYS AS (a * 2) STORED) INHERITS (gtest_normal); 2025-07-03 22:05:33.829 UTC client backend[17964] pg_regress/collate ERROR: collations are not supported by type integer 2025-07-03 22:05:33.829 UTC client backend[17964] pg_regress/collate STATEMENT: SELECT collation for ((SELECT a FROM collate_test1 LIMIT 1)); 2025-07-03 22:05:33.855 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" in child table must not be a generated column 2025-07-03 22:05:33.855 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_normal_child INHERIT gtest_normal; 2025-07-03 22:05:33.861 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" inherits from generated column but specifies default 2025-07-03 22:05:33.861 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int DEFAULT 10) INHERITS (gtest1); 2025-07-03 22:05:33.865 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" inherits from generated column but specifies identity 2025-07-03 22:05:33.865 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS IDENTITY) INHERITS (gtest1); 2025-07-03 22:05:33.869 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" inherits from generated column of different kind 2025-07-03 22:05:33.869 UTC client backend[17984] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-07-03 22:05:33.869 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS (a * 22) VIRTUAL) INHERITS (gtest1); 2025-07-03 22:05:33.879 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "part_document" 2025-07-03 22:05:33.879 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_dave', 'testing pp1'); 2025-07-03 22:05:33.883 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp1r" for table "part_document" 2025-07-03 22:05:33.883 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 99, 1, 'regress_rls_dave', 'testing pp1r'); 2025-07-03 22:05:33.885 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp1r" for table "part_document" 2025-07-03 22:05:33.885 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 55, 1, 'regress_rls_dave', 'testing RLS with partitions'); 2025-07-03 22:05:33.911 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "part_document_satire" 2025-07-03 22:05:33.911 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document_satire VALUES (101, 55, 1, 'regress_rls_dave', 'testing RLS with partitions'); 2025-07-03 22:05:33.918 UTC client backend[17961] pg_regress/rowsecurity ERROR: must be owner of table part_document 2025-07-03 22:05:33.918 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: ALTER POLICY pp1 ON part_document USING (true); 2025-07-03 22:05:33.923 UTC client backend[17961] pg_regress/rowsecurity ERROR: must be owner of relation part_document 2025-07-03 22:05:33.923 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP POLICY pp1 ON part_document; 2025-07-03 22:05:33.968 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "part_document" 2025-07-03 22:05:33.968 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM part_document ORDER by did; 2025-07-03 22:05:33.969 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "part_document_satire" 2025-07-03 22:05:33.969 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM part_document_satire ORDER by did; 2025-07-03 22:05:33.973 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "pp3" for table "part_document" 2025-07-03 22:05:33.973 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_carol', 'testing pp3'); 2025-07-03 22:05:34.001 UTC client backend[17980] pg_regress/identity ERROR: identity column type must be smallint, integer, or bigint 2025-07-03 22:05:34.001 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest3 ALTER COLUMN a TYPE text; 2025-07-03 22:05:34.007 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" in child table must be a generated column 2025-07-03 22:05:34.007 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtestxx_1 INHERIT gtest1; 2025-07-03 22:05:34.011 UTC client backend[17961] pg_regress/rowsecurity ERROR: cannot drop table dependee because other objects depend on it 2025-07-03 22:05:34.011 UTC client backend[17961] pg_regress/rowsecurity DETAIL: policy d1 on table dependent depends on table dependee 2025-07-03 22:05:34.011 UTC client backend[17961] pg_regress/rowsecurity HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:34.011 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP TABLE dependee; 2025-07-03 22:05:34.040 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-07-03 22:05:34.040 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-07-03 22:05:34.045 UTC client backend[17984] pg_regress/generated_stored ERROR: inherited column "b" has a generation conflict 2025-07-03 22:05:34.045 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest0, gtesty); 2025-07-03 22:05:34.054 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 54 2025-07-03 22:05:34.054 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_COLLATE = "NONSENSE", LC_CTYPE = "POSIX"); 2025-07-03 22:05:34.055 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 52 2025-07-03 22:05:34.055 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LC_CTYPE = "NONSENSE", LC_COLLATE = "POSIX"); 2025-07-03 22:05:34.063 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 48 2025-07-03 22:05:34.063 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (PROVIDER = icu, PROVIDER = NONSENSE, LC_COLLATE = "POSIX", LC_CTYPE = "POSIX"); 2025-07-03 22:05:34.063 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-07-03 22:05:34.063 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-07-03 22:05:34.064 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 47 2025-07-03 22:05:34.064 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION case_sensitive (LOCALE = '', LOCALE = "NONSENSE"); 2025-07-03 22:05:34.064 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 54 2025-07-03 22:05:34.064 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (DETERMINISTIC = TRUE, DETERMINISTIC = NONSENSE, LOCALE = ''); 2025-07-03 22:05:34.065 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options at character 47 2025-07-03 22:05:34.065 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (VERSION = '1', VERSION = "NONSENSE", LOCALE = ''); 2025-07-03 22:05:34.065 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options 2025-07-03 22:05:34.065 UTC client backend[17964] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-07-03 22:05:34.065 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_CTYPE = "POSIX", LOCALE = ''); 2025-07-03 22:05:34.066 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options 2025-07-03 22:05:34.066 UTC client backend[17964] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-07-03 22:05:34.066 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LOCALE = ''); 2025-07-03 22:05:34.067 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options 2025-07-03 22:05:34.067 UTC client backend[17964] pg_regress/collate DETAIL: LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE. 2025-07-03 22:05:34.067 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LOCALE = ''); 2025-07-03 22:05:34.068 UTC client backend[17984] pg_regress/generated_stored ERROR: inherited column "b" has a generation conflict 2025-07-03 22:05:34.068 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-07-03 22:05:34.068 UTC client backend[17964] pg_regress/collate ERROR: conflicting or redundant options 2025-07-03 22:05:34.068 UTC client backend[17964] pg_regress/collate DETAIL: FROM cannot be specified together with any other options. 2025-07-03 22:05:34.068 UTC client backend[17964] pg_regress/collate STATEMENT: CREATE COLLATION coll_dup_chk (FROM = "C", VERSION = "1"); 2025-07-03 22:05:34.088 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" inherits conflicting generation expressions 2025-07-03 22:05:34.088 UTC client backend[17984] pg_regress/generated_stored HINT: To resolve the conflict, specify a generation expression explicitly. 2025-07-03 22:05:34.088 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-07-03 22:05:34.092 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-07-03 22:05:34.092 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-07-03 22:05:34.101 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest12 2025-07-03 22:05:34.101 UTC client backend[17973] pg_regress/privileges STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM atest12 WHERE a >>> 0; 2025-07-03 22:05:34.169 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "rec1" 2025-07-03 22:05:34.169 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rec1; 2025-07-03 22:05:34.204 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest3 2025-07-03 22:05:34.204 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest3; 2025-07-03 22:05:34.218 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest3 2025-07-03 22:05:34.218 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atest3; 2025-07-03 22:05:34.219 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest3 2025-07-03 22:05:34.219 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atest3; 2025-07-03 22:05:34.247 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:34.247 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-07-03 22:05:34.262 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for view atestv2 2025-07-03 22:05:34.262 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-07-03 22:05:34.264 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for view atestv0 2025-07-03 22:05:34.264 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atestv0; 2025-07-03 22:05:34.268 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table int8_tbl 2025-07-03 22:05:34.268 UTC client backend[17973] pg_regress/privileges STATEMENT: select * from ((select a.q1 as x from int8_tbl a offset 0) union all (select b.q2 as x from int8_tbl b offset 0)) ss where false; 2025-07-03 22:05:34.268 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-07-03 22:05:34.268 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM s1 WHERE f_leak(b); 2025-07-03 22:05:34.269 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-07-03 22:05:34.269 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO s1 VALUES (1, 'foo'); 2025-07-03 22:05:34.278 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table int8_tbl 2025-07-03 22:05:34.278 UTC client backend[17973] pg_regress/privileges STATEMENT: select * from ((select a.q1 as x, random() from int8_tbl a where q1 > 0) union all (select b.q2 as x, random() from int8_tbl b where q2 > 0)) ss where x < 0; 2025-07-03 22:05:34.292 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for view atestv3 2025-07-03 22:05:34.292 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atestv3; 2025-07-03 22:05:34.295 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:34.295 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atestv2; 2025-07-03 22:05:34.299 UTC client backend[17961] pg_regress/rowsecurity ERROR: infinite recursion detected in policy for relation "s1" 2025-07-03 22:05:34.299 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM s1 WHERE f_leak(b); 2025-07-03 22:05:34.320 UTC client backend[17964] pg_regress/collate LOG: disconnection: session time: 0:00:01.875 user=postgres database=regression host=[local] 2025-07-03 22:05:34.348 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.348 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest5; 2025-07-03 22:05:34.357 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.357 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT two FROM atest5; 2025-07-03 22:05:34.358 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.358 UTC client backend[17973] pg_regress/privileges STATEMENT: COPY atest5 (two) TO stdout; 2025-07-03 22:05:34.358 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.358 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT atest5 FROM atest5; 2025-07-03 22:05:34.359 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.359 UTC client backend[17973] pg_regress/privileges STATEMENT: COPY atest5 (one,two) TO stdout; 2025-07-03 22:05:34.366 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.366 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 a JOIN atest5 b USING (two); 2025-07-03 22:05:34.367 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.367 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 a NATURAL JOIN atest5 b; 2025-07-03 22:05:34.368 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.368 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-07-03 22:05:34.370 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.370 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT j.* FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-07-03 22:05:34.374 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.374 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT (j.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one)) j; 2025-07-03 22:05:34.378 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.378 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-07-03 22:05:34.379 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.379 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT j.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-07-03 22:05:34.380 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.380 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-07-03 22:05:34.383 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.383 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT j.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j; 2025-07-03 22:05:34.384 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.384 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM (atest5 a JOIN atest5 b USING (one)); 2025-07-03 22:05:34.385 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.385 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT a.* FROM (atest5 a JOIN atest5 b USING (one)); 2025-07-03 22:05:34.386 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.386 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT (a.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one)); 2025-07-03 22:05:34.386 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-07-03 22:05:34.386 UTC client backend[17984] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:05:34.386 UTC client backend[17984] pg_regress/generated_stored STATEMENT: COPY gtest1 (a, b) TO stdout; 2025-07-03 22:05:34.386 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.386 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.388 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.388 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT a.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.388 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-07-03 22:05:34.388 UTC client backend[17984] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:05:34.388 UTC client backend[17984] pg_regress/generated_stored STATEMENT: COPY gtest1 (a, b) FROM stdin; 2025-07-03 22:05:34.390 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.390 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.394 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.394 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.395 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.395 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.396 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.396 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.398 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.398 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.398 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.398 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT b.y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one)); 2025-07-03 22:05:34.403 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.403 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT 1 FROM atest5 WHERE two = 2; 2025-07-03 22:05:34.404 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.404 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest1, atest5; 2025-07-03 22:05:34.411 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.411 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT atest1.*,atest5.one FROM atest1 JOIN atest5 ON (atest1.a = atest5.two); 2025-07-03 22:05:34.413 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-07-03 22:05:34.413 UTC client backend[17984] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:05:34.413 UTC client backend[17984] pg_regress/generated_stored STATEMENT: COPY gtest3 (a, b) TO stdout; 2025-07-03 22:05:34.413 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.413 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT one, two FROM atest5; 2025-07-03 22:05:34.415 UTC client backend[17984] pg_regress/generated_stored ERROR: column "b" is a generated column 2025-07-03 22:05:34.415 UTC client backend[17984] pg_regress/generated_stored DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:05:34.415 UTC client backend[17984] pg_regress/generated_stored STATEMENT: COPY gtest3 (a, b) FROM stdin; 2025-07-03 22:05:34.418 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.418 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT one, two FROM atest5 NATURAL JOIN atest6; 2025-07-03 22:05:34.435 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.435 UTC client backend[17973] pg_regress/privileges STATEMENT: COPY atest5 FROM stdin; 2025-07-03 22:05:34.437 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.437 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5 (three) VALUES (4); 2025-07-03 22:05:34.438 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.438 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5 VALUES (5,5,5); 2025-07-03 22:05:34.441 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.441 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest5 SET one = 8; 2025-07-03 22:05:34.444 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.444 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest5 SET three = 5, one = 2; 2025-07-03 22:05:34.448 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.448 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = 10 RETURNING atest5.three; 2025-07-03 22:05:34.450 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.450 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = EXCLUDED.three; 2025-07-03 22:05:34.451 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.451 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set one = 8; 2025-07-03 22:05:34.451 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.451 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(three) VALUES (4) ON CONFLICT (two) DO UPDATE set three = 10; 2025-07-03 22:05:34.458 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.458 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4); 2025-07-03 22:05:34.469 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.469 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4) ON CONFLICT (four) DO UPDATE set three = 3; 2025-07-03 22:05:34.471 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.471 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO atest5(four) VALUES (4) ON CONFLICT ON CONSTRAINT atest5_four_key DO UPDATE set three = 3; 2025-07-03 22:05:34.481 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.481 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT one FROM atest5; 2025-07-03 22:05:34.481 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "b1" 2025-07-03 22:05:34.481 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO bv1 VALUES (-1, 'xxx'); 2025-07-03 22:05:34.481 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.481 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atest5 SET one = 1; 2025-07-03 22:05:34.482 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "b1" 2025-07-03 22:05:34.482 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO bv1 VALUES (11, 'xxx'); 2025-07-03 22:05:34.514 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.514 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (2, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_carol', 'my first novel') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle, dauthor = EXCLUDED.dauthor; 2025-07-03 22:05:34.520 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table msource 2025-07-03 22:05:34.520 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = s.b WHEN NOT MATCHED THEN INSERT VALUES (a, NULL); 2025-07-03 22:05:34.521 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.521 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (33, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_bob', 'Some novel, replaces sci-fi') -- takes UPDATE path ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle; 2025-07-03 22:05:34.521 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table msource 2025-07-03 22:05:34.521 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = 'x' WHEN NOT MATCHED THEN INSERT VALUES (a, b); 2025-07-03 22:05:34.528 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table msource 2025-07-03 22:05:34.528 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED AND s.b = 'x' THEN UPDATE SET b = 'x' WHEN NOT MATCHED THEN INSERT VALUES (a, NULL); 2025-07-03 22:05:34.539 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.539 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (78, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_bob', 'some technology novel') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle, cid = 33 RETURNING *; 2025-07-03 22:05:34.545 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table mtarget 2025-07-03 22:05:34.545 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = t.b WHEN NOT MATCHED THEN INSERT VALUES (a, NULL); 2025-07-03 22:05:34.547 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table mtarget 2025-07-03 22:05:34.547 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED THEN UPDATE SET b = s.b, a = t.a + 1 WHEN NOT MATCHED THEN INSERT VALUES (a, b); 2025-07-03 22:05:34.548 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.548 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (79, (SELECT cid from category WHERE cname = 'technology'), 1, 'regress_rls_bob', 'technology book, can only insert') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle RETURNING *; 2025-07-03 22:05:34.548 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table mtarget 2025-07-03 22:05:34.548 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED AND t.b IS NOT NULL THEN UPDATE SET b = s.b WHEN NOT MATCHED THEN INSERT VALUES (a, b); 2025-07-03 22:05:34.551 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table mtarget 2025-07-03 22:05:34.551 UTC client backend[17973] pg_regress/privileges STATEMENT: MERGE INTO mtarget t USING msource s ON t.a = s.a WHEN MATCHED AND t.b IS NOT NULL THEN DELETE; 2025-07-03 22:05:34.569 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.569 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (79, (SELECT cid from category WHERE cname = 'technology'), 1, 'regress_rls_bob', 'technology book, can only insert') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle RETURNING *; 2025-07-03 22:05:34.574 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.574 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (2, (SELECT cid from category WHERE cname = 'technology'), 1, 'regress_rls_bob', 'my first novel') ON CONFLICT (did) DO UPDATE SET cid = EXCLUDED.cid, dtitle = EXCLUDED.dtitle RETURNING *; 2025-07-03 22:05:34.580 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.580 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (80, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_carol', 'my first novel') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle, cid = 33; 2025-07-03 22:05:34.583 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.583 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (4, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_bob', 'my first novel') ON CONFLICT (did) DO UPDATE SET dtitle = EXCLUDED.dtitle; 2025-07-03 22:05:34.586 UTC client backend[17973] pg_regress/privileges ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-07-03 22:05:34.586 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1, c2) VALUES (1, 1); 2025-07-03 22:05:34.588 UTC client backend[17973] pg_regress/privileges ERROR: duplicate key value violates unique constraint "t1_pkey" 2025-07-03 22:05:34.588 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE t1 SET c2 = 1; 2025-07-03 22:05:34.588 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "c1" of relation "t1" violates not-null constraint 2025-07-03 22:05:34.588 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (c1, c2) = (null, null). 2025-07-03 22:05:34.588 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1, c2) VALUES (null, null); 2025-07-03 22:05:34.589 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "c1" of relation "t1" violates not-null constraint 2025-07-03 22:05:34.589 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (c1, c3) = (null, null). 2025-07-03 22:05:34.589 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO t1 (c3) VALUES (null); 2025-07-03 22:05:34.591 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "c2" of relation "t1" violates not-null constraint 2025-07-03 22:05:34.591 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (c1) = (5). 2025-07-03 22:05:34.591 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO t1 (c1) VALUES (5); 2025-07-03 22:05:34.591 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.591 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO document VALUES (1, (SELECT cid from category WHERE cname = 'novel'), 1, 'regress_rls_bob', 'my first novel') ON CONFLICT (did) DO UPDATE SET dauthor = 'regress_rls_carol'; 2025-07-03 22:05:34.592 UTC client backend[17973] pg_regress/privileges ERROR: new row for relation "t1" violates check constraint "t1_c3_check" 2025-07-03 22:05:34.592 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (c1, c3) = (1, 10). 2025-07-03 22:05:34.592 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE t1 SET c3 = 10; 2025-07-03 22:05:34.630 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.630 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 1 as sdid) s ON did = s.sdid WHEN MATCHED THEN UPDATE SET dnotes = dnotes || ' notes added by merge1 ', dlevel = 0; 2025-07-03 22:05:34.636 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot drop column b of table gtest10 because other objects depend on it 2025-07-03 22:05:34.636 UTC client backend[17984] pg_regress/generated_stored DETAIL: column c of table gtest10 depends on column b of table gtest10 2025-07-03 22:05:34.636 UTC client backend[17984] pg_regress/generated_stored HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:34.636 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest10 DROP COLUMN b; 2025-07-03 22:05:34.637 UTC client backend[17961] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.637 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 3 as sdid) s ON did = s.sdid WHEN MATCHED THEN UPDATE SET dnotes = dnotes || ' notes added by merge '; 2025-07-03 22:05:34.638 UTC client backend[17961] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.638 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 3 as sdid) s ON did = s.sdid WHEN MATCHED THEN DELETE; 2025-07-03 22:05:34.640 UTC client backend[17961] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.640 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 4 as sdid) s ON did = s.sdid WHEN MATCHED AND dnotes = '' THEN UPDATE SET dnotes = dnotes || ' notes added by merge ' WHEN MATCHED THEN DELETE; 2025-07-03 22:05:34.644 UTC client backend[17961] pg_regress/rowsecurity ERROR: target row violates row-level security policy (USING expression) for table "document" 2025-07-03 22:05:34.644 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 4 as sdid) s ON did = s.sdid WHEN MATCHED AND dnotes <> '' THEN UPDATE SET dnotes = dnotes || ' notes added by merge ' WHEN MATCHED THEN DELETE; 2025-07-03 22:05:34.655 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.655 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 12 as sdid) s ON did = s.sdid WHEN MATCHED THEN DELETE WHEN NOT MATCHED THEN INSERT VALUES (12, 11, 1, 'regress_rls_dave', 'another novel'); 2025-07-03 22:05:34.683 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-07-03 22:05:34.683 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, null). 2025-07-03 22:05:34.683 UTC client backend[17973] pg_regress/privileges STATEMENT: INSERT INTO errtst (a, b) VALUES ('aaa', NULL); 2025-07-03 22:05:34.686 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-07-03 22:05:34.686 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, ccc). 2025-07-03 22:05:34.686 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE errtst SET b = NULL; 2025-07-03 22:05:34.688 UTC client backend[17961] pg_regress/rowsecurity ERROR: duplicate key value violates unique constraint "document_pkey" 2025-07-03 22:05:34.688 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 7 as sdid) s ON did = s.sdid WHEN MATCHED THEN UPDATE SET dnotes = dnotes || ' notes added by merge5 ' WHEN NOT MATCHED THEN INSERT VALUES (12, 11, 1, 'regress_rls_bob', 'another novel'); 2025-07-03 22:05:34.696 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.696 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 1 as sdid) s ON did = s.sdid WHEN MATCHED THEN UPDATE SET dnotes = dnotes || ' notes added by merge6 ', cid = (SELECT cid from category WHERE cname = 'technology'); 2025-07-03 22:05:34.696 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_1" violates not-null constraint 2025-07-03 22:05:34.696 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaa, null, ccc). 2025-07-03 22:05:34.696 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaa', b = NULL; 2025-07-03 22:05:34.704 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_2" violates not-null constraint 2025-07-03 22:05:34.704 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaaa, null, ccc). 2025-07-03 22:05:34.704 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaaa', b = NULL; 2025-07-03 22:05:34.706 UTC client backend[17973] pg_regress/privileges ERROR: null value in column "b" of relation "errtst_part_2" violates not-null constraint 2025-07-03 22:05:34.706 UTC client backend[17973] pg_regress/privileges DETAIL: Failing row contains (a, b, c) = (aaaa, null, ccc). 2025-07-03 22:05:34.706 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE errtst SET a = 'aaaa', b = NULL WHERE a = 'aaa'; 2025-07-03 22:05:34.740 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "document" 2025-07-03 22:05:34.740 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: MERGE INTO document d USING (SELECT 14 as sdid) s ON did = s.sdid WHEN MATCHED THEN UPDATE SET dnotes = dnotes || ' notes added by merge9 ' WHEN NOT MATCHED THEN INSERT VALUES (14, 44, 1, 'regress_rls_bob', 'new manga') RETURNING *; 2025-07-03 22:05:34.785 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest6 2025-07-03 22:05:34.785 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT atest6 FROM atest6; 2025-07-03 22:05:34.787 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.787 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT one FROM atest5 NATURAL JOIN atest6; 2025-07-03 22:05:34.811 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest6 2025-07-03 22:05:34.811 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT * FROM atest6; 2025-07-03 22:05:34.812 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest6 2025-07-03 22:05:34.812 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT 1 FROM atest6; 2025-07-03 22:05:34.814 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atest5 2025-07-03 22:05:34.814 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atest5 WHERE one = 1; 2025-07-03 22:05:34.821 UTC client backend[17962] pg_regress/matview ERROR: cannot refresh materialized view "public.mvtest_tvmm" concurrently 2025-07-03 22:05:34.821 UTC client backend[17962] pg_regress/matview HINT: Create a unique index with no WHERE clause on one or more columns of the materialized view. 2025-07-03 22:05:34.821 UTC client backend[17962] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm; 2025-07-03 22:05:34.821 UTC client backend[17984] pg_regress/generated_stored ERROR: permission denied for table gtest11 2025-07-03 22:05:34.821 UTC client backend[17984] pg_regress/generated_stored STATEMENT: SELECT a, b FROM gtest11; 2025-07-03 22:05:34.834 UTC client backend[17984] pg_regress/generated_stored ERROR: permission denied for function gf1 2025-07-03 22:05:34.834 UTC client backend[17984] pg_regress/generated_stored STATEMENT: SELECT gf1(10); 2025-07-03 22:05:34.845 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.845 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT fy FROM atestc; 2025-07-03 22:05:34.862 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.862 UTC client backend[17973] pg_regress/privileges STATEMENT: SELECT f2 FROM atestc; 2025-07-03 22:05:34.863 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.863 UTC client backend[17973] pg_regress/privileges STATEMENT: DELETE FROM atestc; 2025-07-03 22:05:34.865 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.865 UTC client backend[17973] pg_regress/privileges STATEMENT: UPDATE atestc SET f1 = 1; 2025-07-03 22:05:34.867 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.867 UTC client backend[17973] pg_regress/privileges STATEMENT: TRUNCATE atestc; 2025-07-03 22:05:34.873 UTC client backend[17984] pg_regress/generated_stored ERROR: permission denied for function gf1 2025-07-03 22:05:34.873 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest12 VALUES (3, 30), (4, 40); 2025-07-03 22:05:34.878 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot drop function gf1(integer) because other objects depend on it 2025-07-03 22:05:34.878 UTC client backend[17984] pg_regress/generated_stored DETAIL: column c of table gtest12 depends on function gf1(integer) 2025-07-03 22:05:34.878 UTC client backend[17984] pg_regress/generated_stored HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:34.878 UTC client backend[17984] pg_regress/generated_stored STATEMENT: DROP FUNCTION gf1(int); 2025-07-03 22:05:34.893 UTC client backend[17973] pg_regress/privileges ERROR: permission denied for table atestc 2025-07-03 22:05:34.893 UTC client backend[17973] pg_regress/privileges STATEMENT: LOCK atestc; 2025-07-03 22:05:34.914 UTC not initialized[18138] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:34.917 UTC client backend[18138] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:34.917 UTC client backend[18138] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:34.927 UTC client backend[18138] pg_regress/privileges LOG: connection ready: setup total=32.547 ms, fork=13.977 ms, authentication=0.416 ms 2025-07-03 22:05:34.927 UTC client backend[17973] pg_regress/privileges LOG: disconnection: session time: 0:00:02.433 user=postgres database=regression host=[local] 2025-07-03 22:05:34.950 UTC client backend[18138] pg_regress/privileges ERROR: language "c" is not trusted 2025-07-03 22:05:34.950 UTC client backend[18138] pg_regress/privileges DETAIL: GRANT and REVOKE are not allowed on untrusted languages, because only superusers can use untrusted languages. 2025-07-03 22:05:34.950 UTC client backend[18138] pg_regress/privileges STATEMENT: GRANT USAGE ON LANGUAGE c TO PUBLIC; 2025-07-03 22:05:34.950 UTC client backend[18138] pg_regress/privileges WARNING: no privileges were granted for "sql" 2025-07-03 22:05:34.954 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for view rls_view 2025-07-03 22:05:34.954 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:34.955 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for view rls_view 2025-07-03 22:05:34.955 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:34.956 UTC client backend[17984] pg_regress/generated_stored ERROR: new row for relation "gtest20" violates check constraint "gtest20_b_check" 2025-07-03 22:05:34.956 UTC client backend[17984] pg_regress/generated_stored DETAIL: Failing row contains (30, 60). 2025-07-03 22:05:34.956 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest20 (a) VALUES (30); 2025-07-03 22:05:34.961 UTC client backend[17984] pg_regress/generated_stored ERROR: check constraint "gtest20_b_check" of relation "gtest20" is violated by some row 2025-07-03 22:05:34.961 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 100); 2025-07-03 22:05:34.984 UTC client backend[17962] pg_regress/matview ERROR: CONCURRENTLY and WITH NO DATA options cannot be used together 2025-07-03 22:05:34.984 UTC client backend[17962] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm WITH NO DATA; 2025-07-03 22:05:34.984 UTC client backend[17962] pg_regress/matview ERROR: cannot lock rows in materialized view "mvtest_tvvm" 2025-07-03 22:05:34.984 UTC client backend[17962] pg_regress/matview STATEMENT: SELECT * FROM mvtest_tvvm FOR SHARE; 2025-07-03 22:05:34.988 UTC client backend[18138] pg_regress/privileges ERROR: priv_testproc1(integer) is not a function 2025-07-03 22:05:34.988 UTC client backend[18138] pg_regress/privileges STATEMENT: REVOKE ALL ON FUNCTION priv_testproc1(int) FROM PUBLIC; 2025-07-03 22:05:34.989 UTC client backend[18138] pg_regress/privileges ERROR: invalid privilege type USAGE for function 2025-07-03 22:05:34.989 UTC client backend[18138] pg_regress/privileges STATEMENT: GRANT USAGE ON FUNCTION priv_testfunc1(int) TO regress_priv_user3; 2025-07-03 22:05:34.995 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:34.995 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:35.001 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.001 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:35.004 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.004 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:35.004 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.004 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:35.012 UTC client backend[18138] pg_regress/privileges ERROR: invalid privilege type USAGE for function 2025-07-03 22:05:35.012 UTC client backend[18138] pg_regress/privileges STATEMENT: GRANT USAGE ON FUNCTION priv_testagg1(int) TO regress_priv_user3; 2025-07-03 22:05:35.013 UTC client backend[18138] pg_regress/privileges ERROR: invalid privilege type USAGE for procedure 2025-07-03 22:05:35.013 UTC client backend[18138] pg_regress/privileges STATEMENT: GRANT USAGE ON PROCEDURE priv_testproc1(int) TO regress_priv_user3; 2025-07-03 22:05:35.014 UTC client backend[18138] pg_regress/privileges ERROR: function priv_testfunc_nosuch(integer) does not exist 2025-07-03 22:05:35.014 UTC client backend[18138] pg_regress/privileges STATEMENT: GRANT ALL PRIVILEGES ON FUNCTION priv_testfunc_nosuch(int) TO regress_priv_user4; 2025-07-03 22:05:35.032 UTC client backend[17962] pg_regress/matview ERROR: cannot drop table mvtest_t because other objects depend on it 2025-07-03 22:05:35.032 UTC client backend[17962] pg_regress/matview DETAIL: view mvtest_tv depends on table mvtest_t materialized view mvtest_mvschema.mvtest_tvm depends on view mvtest_tv materialized view mvtest_tvmm depends on materialized view mvtest_mvschema.mvtest_tvm view mvtest_tvv depends on view mvtest_tv materialized view mvtest_tvvm depends on view mvtest_tvv view mvtest_tvvmv depends on materialized view mvtest_tvvm materialized view mvtest_bb depends on view mvtest_tvvmv materialized view mvtest_tm depends on table mvtest_t materialized view mvtest_tmm depends on materialized view mvtest_tm 2025-07-03 22:05:35.032 UTC client backend[17962] pg_regress/matview HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:05:35.032 UTC client backend[17962] pg_regress/matview STATEMENT: DROP TABLE mvtest_t; 2025-07-03 22:05:35.043 UTC client backend[18138] pg_regress/privileges ERROR: permission denied for language sql 2025-07-03 22:05:35.043 UTC client backend[18138] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE sql; 2025-07-03 22:05:35.048 UTC client backend[17984] pg_regress/generated_stored ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-07-03 22:05:35.048 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20a ADD CHECK (b < 50); 2025-07-03 22:05:35.049 UTC client backend[18138] pg_regress/privileges ERROR: permission denied for function priv_testfunc1 2025-07-03 22:05:35.049 UTC client backend[18138] pg_regress/privileges STATEMENT: SELECT priv_testfunc1(5); 2025-07-03 22:05:35.051 UTC client backend[17984] pg_regress/generated_stored ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-07-03 22:05:35.051 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20a ADD COLUMN c float8 DEFAULT random() CHECK (b < 50); 2025-07-03 22:05:35.052 UTC client backend[18138] pg_regress/privileges ERROR: permission denied for aggregate priv_testagg1 2025-07-03 22:05:35.052 UTC client backend[18138] pg_regress/privileges STATEMENT: SELECT priv_testagg1(x) FROM (VALUES (1), (2), (3)) _(x); 2025-07-03 22:05:35.052 UTC client backend[18138] pg_regress/privileges ERROR: permission denied for procedure priv_testproc1 2025-07-03 22:05:35.052 UTC client backend[18138] pg_regress/privileges STATEMENT: CALL priv_testproc1(6); 2025-07-03 22:05:35.054 UTC client backend[18138] pg_regress/privileges ERROR: permission denied for table atest2 2025-07-03 22:05:35.054 UTC client backend[18138] pg_regress/privileges STATEMENT: SELECT col1 FROM atest2 WHERE col2 = true; 2025-07-03 22:05:35.069 UTC client backend[18138] pg_regress/privileges ERROR: must be owner of function priv_testfunc1 2025-07-03 22:05:35.069 UTC client backend[18138] pg_regress/privileges STATEMENT: DROP FUNCTION priv_testfunc1(int); 2025-07-03 22:05:35.071 UTC client backend[18138] pg_regress/privileges ERROR: must be owner of aggregate priv_testagg1 2025-07-03 22:05:35.071 UTC client backend[18138] pg_regress/privileges STATEMENT: DROP AGGREGATE priv_testagg1(int); 2025-07-03 22:05:35.071 UTC client backend[18138] pg_regress/privileges ERROR: must be owner of procedure priv_testproc1 2025-07-03 22:05:35.071 UTC client backend[18138] pg_regress/privileges STATEMENT: DROP PROCEDURE priv_testproc1(int); 2025-07-03 22:05:35.073 UTC client backend[17974] pg_regress/replica_identity ERROR: column "id" is in index used as replica identity 2025-07-03 22:05:35.073 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity3 ALTER COLUMN id DROP NOT NULL; 2025-07-03 22:05:35.088 UTC not initialized[18154] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:35.105 UTC client backend[18154] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:35.105 UTC client backend[18154] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:35.109 UTC client backend[18154] pg_regress/privileges LOG: connection ready: setup total=37.886 ms, fork=11.592 ms, authentication=15.588 ms 2025-07-03 22:05:35.110 UTC client backend[18138] pg_regress/privileges LOG: disconnection: session time: 0:00:00.201 user=postgres database=regression host=[local] 2025-07-03 22:05:35.149 UTC client backend[17984] pg_regress/generated_stored ERROR: check constraint "chk" of relation "gtest20b" is violated by some row 2025-07-03 22:05:35.149 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest20b VALIDATE CONSTRAINT chk; 2025-07-03 22:05:35.172 UTC client backend[18154] pg_regress/privileges ERROR: permission denied for function int8 2025-07-03 22:05:35.172 UTC client backend[18154] pg_regress/privileges STATEMENT: SELECT '{1}'::int4[]::int8[]; 2025-07-03 22:05:35.183 UTC client backend[17984] pg_regress/generated_stored ERROR: new row for relation "gtest20c" violates check constraint "whole_row_check" 2025-07-03 22:05:35.183 UTC client backend[17984] pg_regress/generated_stored DETAIL: Failing row contains (null, null). 2025-07-03 22:05:35.183 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest20c VALUES (NULL); 2025-07-03 22:05:35.188 UTC client backend[17979] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 69 2025-07-03 22:05:35.188 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select * from (values (1),(2)) v(x), lateral (select a, b, sum(v.x) from gstest_data(v.x) group by rollup (a,b)) s; 2025-07-03 22:05:35.193 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.193 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:35.195 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.195 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:35.202 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.202 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:35.203 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.203 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:35.204 UTC not initialized[18162] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:35.207 UTC client backend[17984] pg_regress/generated_stored ERROR: null value in column "b" of relation "gtest21a" violates not-null constraint 2025-07-03 22:05:35.207 UTC client backend[17984] pg_regress/generated_stored DETAIL: Failing row contains (0, null). 2025-07-03 22:05:35.207 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest21a (a) VALUES (0); 2025-07-03 22:05:35.212 UTC client backend[18162] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:35.212 UTC client backend[18162] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:35.215 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.215 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_view; 2025-07-03 22:05:35.215 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table z1_blacklist 2025-07-03 22:05:35.215 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: EXPLAIN (COSTS OFF) SELECT * FROM rls_view; 2025-07-03 22:05:35.230 UTC client backend[18162] pg_regress/privileges LOG: connection ready: setup total=54.861 ms, fork=13.760 ms, authentication=4.486 ms 2025-07-03 22:05:35.230 UTC client backend[18154] pg_regress/privileges LOG: disconnection: session time: 0:00:00.146 user=postgres database=regression host=[local] 2025-07-03 22:05:35.275 UTC client backend[17984] pg_regress/generated_stored ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-07-03 22:05:35.275 UTC client backend[17984] pg_regress/generated_stored DETAIL: Failing row contains (0, null). 2025-07-03 22:05:35.275 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest21b (a) VALUES (0); 2025-07-03 22:05:35.278 UTC client backend[18162] pg_regress/privileges ERROR: cannot set privileges of array types 2025-07-03 22:05:35.278 UTC client backend[18162] pg_regress/privileges HINT: Set the privileges of the element type instead. 2025-07-03 22:05:35.278 UTC client backend[18162] pg_regress/privileges STATEMENT: GRANT USAGE ON TYPE _priv_testtype1 TO regress_priv_user2; 2025-07-03 22:05:35.279 UTC client backend[18162] pg_regress/privileges ERROR: "priv_testtype1" is not a domain 2025-07-03 22:05:35.279 UTC client backend[18162] pg_regress/privileges STATEMENT: GRANT USAGE ON DOMAIN priv_testtype1 TO regress_priv_user2; 2025-07-03 22:05:35.281 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.281 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE AGGREGATE priv_testagg1a(priv_testdomain1) (sfunc = int4_sum, stype = bigint); 2025-07-03 22:05:35.281 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.281 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE DOMAIN priv_testdomain2a AS priv_testdomain1; 2025-07-03 22:05:35.289 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.289 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE CAST (priv_testdomain1 AS priv_testdomain3a) WITH FUNCTION castfunc(int); 2025-07-03 22:05:35.290 UTC client backend[17980] pg_regress/identity ERROR: column "b" of relation "itest6" is not an identity column 2025-07-03 22:05:35.290 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest6 ALTER COLUMN b SET INCREMENT BY 2; 2025-07-03 22:05:35.292 UTC client backend[17980] pg_regress/identity ERROR: cannot change ownership of identity sequence 2025-07-03 22:05:35.292 UTC client backend[17980] pg_regress/identity DETAIL: Sequence "itest6_a_seq" is linked to table "itest6". 2025-07-03 22:05:35.292 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER SEQUENCE itest6_a_seq OWNED BY NONE; 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc5a(a priv_testdomain1) RETURNS int LANGUAGE SQL AS $$ SELECT $1 $$; 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE FUNCTION priv_testfunc6a(b int) RETURNS priv_testdomain1 LANGUAGE SQL AS $$ SELECT $1::priv_testdomain1 $$; 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.315 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE OPERATOR !+! (PROCEDURE = int4pl, LEFTARG = priv_testdomain1, RIGHTARG = priv_testdomain1); 2025-07-03 22:05:35.316 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.316 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE TABLE test5a (a int, b priv_testdomain1); 2025-07-03 22:05:35.317 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-07-03 22:05:35.317 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE TABLE test6a OF priv_testtype1; 2025-07-03 22:05:35.319 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-07-03 22:05:35.319 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE TABLE test10a (a int[], b priv_testtype1[]); 2025-07-03 22:05:35.324 UTC client backend[17979] pg_regress/groupingsets ERROR: arguments to GROUPING must be grouping expressions of the associated query level at character 25 2025-07-03 22:05:35.324 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select (select grouping(a,b) from gstest2) from gstest2 group by a,b; 2025-07-03 22:05:35.326 UTC client backend[17984] pg_regress/generated_stored ERROR: duplicate key value violates unique constraint "gtest22a_b_key" 2025-07-03 22:05:35.326 UTC client backend[17984] pg_regress/generated_stored DETAIL: Key (b)=(1) already exists. 2025-07-03 22:05:35.326 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest22a VALUES (3); 2025-07-03 22:05:35.336 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.336 UTC client backend[18162] pg_regress/privileges STATEMENT: ALTER TABLE test9a ADD COLUMN c priv_testdomain1; 2025-07-03 22:05:35.337 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.337 UTC client backend[18162] pg_regress/privileges STATEMENT: ALTER TABLE test9a ALTER COLUMN b TYPE priv_testdomain1; 2025-07-03 22:05:35.340 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.340 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE TYPE test7a AS (a int, b priv_testdomain1); 2025-07-03 22:05:35.343 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.343 UTC client backend[18162] pg_regress/privileges STATEMENT: ALTER TYPE test8a ADD ATTRIBUTE c priv_testdomain1; 2025-07-03 22:05:35.347 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.347 UTC client backend[18162] pg_regress/privileges STATEMENT: ALTER TYPE test8a ALTER ATTRIBUTE b TYPE priv_testdomain1; 2025-07-03 22:05:35.348 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testdomain1 2025-07-03 22:05:35.348 UTC client backend[18162] pg_regress/privileges STATEMENT: CREATE TABLE test11a AS (SELECT 1::priv_testdomain1 AS a); 2025-07-03 22:05:35.350 UTC client backend[18162] pg_regress/privileges ERROR: permission denied for type priv_testtype1 2025-07-03 22:05:35.350 UTC client backend[18162] pg_regress/privileges STATEMENT: REVOKE ALL ON TYPE priv_testtype1 FROM PUBLIC; 2025-07-03 22:05:35.364 UTC client backend[18162] pg_regress/privileges WARNING: cast will be ignored because the source data type is a domain 2025-07-03 22:05:35.365 UTC client backend[17984] pg_regress/generated_stored ERROR: duplicate key value violates unique constraint "gtest22b_pkey" 2025-07-03 22:05:35.365 UTC client backend[17984] pg_regress/generated_stored DETAIL: Key (a, b)=(2, 1) already exists. 2025-07-03 22:05:35.365 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest22b VALUES (2); 2025-07-03 22:05:35.394 UTC client backend[17961] pg_regress/rowsecurity ERROR: policy "p1" for table "y1" already exists 2025-07-03 22:05:35.394 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: CREATE POLICY p1 ON y1 FOR SELECT USING (a % 2 = 1); 2025-07-03 22:05:35.414 UTC client backend[17980] pg_regress/identity ERROR: cannot recursively add identity column to table that has child tables 2025-07-03 22:05:35.414 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest7d ADD COLUMN b int GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:35.471 UTC client backend[18162] pg_regress/privileges WARNING: no privileges could be revoked for "priv_testtype1" 2025-07-03 22:05:35.487 UTC not initialized[18182] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:35.496 UTC client backend[18182] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:35.496 UTC client backend[18182] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:35.510 UTC client backend[18182] pg_regress/privileges LOG: connection ready: setup total=37.066 ms, fork=13.258 ms, authentication=0.414 ms 2025-07-03 22:05:35.510 UTC client backend[18162] pg_regress/privileges LOG: disconnection: session time: 0:00:00.321 user=postgres database=regression host=[local] 2025-07-03 22:05:35.560 UTC client backend[17979] pg_regress/groupingsets ERROR: could not implement GROUP BY 2025-07-03 22:05:35.560 UTC client backend[17979] pg_regress/groupingsets DETAIL: Some of the datatypes only support hashing, while others only support sorting. 2025-07-03 22:05:35.560 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select count(*) from gstest4 group by rollup(unhashable_col,unsortable_col); 2025-07-03 22:05:35.564 UTC client backend[17979] pg_regress/groupingsets ERROR: could not implement GROUP BY 2025-07-03 22:05:35.564 UTC client backend[17979] pg_regress/groupingsets DETAIL: Some of the datatypes only support hashing, while others only support sorting. 2025-07-03 22:05:35.564 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select array_agg(v order by v) from gstest4 group by grouping sets ((id,unsortable_col),(id)); 2025-07-03 22:05:35.623 UTC client backend[17979] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 69 2025-07-03 22:05:35.623 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select * from (values (1),(2)) v(x), lateral (select a, b, sum(v.x) from gstest_data(v.x) group by grouping sets (a,b)) s; 2025-07-03 22:05:35.624 UTC client backend[17979] pg_regress/groupingsets ERROR: aggregate functions are not allowed in FROM clause of their own query level at character 95 2025-07-03 22:05:35.624 UTC client backend[17979] pg_regress/groupingsets STATEMENT: explain (costs off) select * from (values (1),(2)) v(x), lateral (select a, b, sum(v.x) from gstest_data(v.x) group by grouping sets (a,b)) s; 2025-07-03 22:05:35.642 UTC client backend[17974] pg_regress/replica_identity ERROR: constraint "test_replica_identity5_pkey" of relation "test_replica_identity5" does not exist 2025-07-03 22:05:35.642 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity5 DROP CONSTRAINT test_replica_identity5_pkey; 2025-07-03 22:05:35.642 UTC client backend[17974] pg_regress/replica_identity ERROR: column "b" is in index used as replica identity 2025-07-03 22:05:35.642 UTC client backend[17974] pg_regress/replica_identity STATEMENT: ALTER TABLE test_replica_identity5 ALTER b DROP NOT NULL; 2025-07-03 22:05:35.681 UTC client backend[17962] pg_regress/matview ERROR: could not create unique index "mvtest_mv_a_idx" 2025-07-03 22:05:35.681 UTC client backend[17962] pg_regress/matview DETAIL: Key (a)=(1) is duplicated. 2025-07-03 22:05:35.681 UTC client backend[17962] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW mvtest_mv; 2025-07-03 22:05:35.690 UTC client backend[17962] pg_regress/matview ERROR: new data for materialized view "mvtest_mv" contains duplicate rows without any null columns 2025-07-03 22:05:35.690 UTC client backend[17962] pg_regress/matview DETAIL: Row: (1,10) 2025-07-03 22:05:35.690 UTC client backend[17962] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_mv; 2025-07-03 22:05:35.700 UTC client backend[18182] pg_regress/privileges ERROR: permission denied for table atest3 2025-07-03 22:05:35.700 UTC client backend[18182] pg_regress/privileges STATEMENT: TRUNCATE atest3; 2025-07-03 22:05:35.705 UTC client backend[18182] pg_regress/privileges ERROR: relation "pg_shad" does not exist 2025-07-03 22:05:35.705 UTC client backend[18182] pg_regress/privileges STATEMENT: select has_table_privilege('pg_shad','select'); 2025-07-03 22:05:35.709 UTC client backend[18182] pg_regress/privileges ERROR: role "nosuchuser" does not exist 2025-07-03 22:05:35.709 UTC client backend[18182] pg_regress/privileges STATEMENT: select has_table_privilege('nosuchuser','pg_authid','select'); 2025-07-03 22:05:35.709 UTC client backend[18182] pg_regress/privileges ERROR: unrecognized privilege type: "sel" 2025-07-03 22:05:35.709 UTC client backend[18182] pg_regress/privileges STATEMENT: select has_table_privilege('pg_authid','sel'); 2025-07-03 22:05:35.712 UTC client backend[17980] pg_regress/identity ERROR: column "f22" of relation "itest8" contains null values 2025-07-03 22:05:35.712 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE itest8 ADD COLUMN f22 int NOT NULL, ALTER COLUMN f22 ADD GENERATED ALWAYS AS IDENTITY; 2025-07-03 22:05:35.721 UTC client backend[17974] pg_regress/replica_identity LOG: disconnection: session time: 0:00:03.227 user=postgres database=regression host=[local] 2025-07-03 22:05:35.731 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "t1" 2025-07-03 22:05:35.731 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: WITH cte1 AS (UPDATE t1 SET a = a + 1 RETURNING *) SELECT * FROM cte1; 2025-07-03 22:05:35.731 UTC not initialized[18192] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:35.733 UTC client backend[18192] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:35.733 UTC client backend[18192] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:35.744 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "t1" 2025-07-03 22:05:35.744 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: WITH cte1 AS (INSERT INTO t1 VALUES (21, 'Fail') RETURNING *) SELECT * FROM cte1; 2025-07-03 22:05:35.748 UTC client backend[17961] pg_regress/rowsecurity ERROR: policy "p1" for table "t1" already exists 2025-07-03 22:05:35.748 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: ALTER POLICY p1 ON t1 RENAME TO p1; 2025-07-03 22:05:35.750 UTC client backend[18192] pg_regress/privileges LOG: connection ready: setup total=37.710 ms, fork=14.695 ms, authentication=0.431 ms 2025-07-03 22:05:35.751 UTC client backend[18182] pg_regress/privileges LOG: disconnection: session time: 0:00:00.264 user=postgres database=regression host=[local] 2025-07-03 22:05:35.768 UTC client backend[17984] pg_regress/generated_stored ERROR: invalid ON UPDATE action for foreign key constraint containing generated column 2025-07-03 22:05:35.768 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) STORED REFERENCES gtest23a (x) ON UPDATE CASCADE); 2025-07-03 22:05:35.803 UTC client backend[17984] pg_regress/generated_stored ERROR: invalid ON DELETE action for foreign key constraint containing generated column 2025-07-03 22:05:35.803 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) STORED REFERENCES gtest23a (x) ON DELETE SET NULL); 2025-07-03 22:05:35.837 UTC client backend[17979] pg_regress/groupingsets LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17979.0", size 598016 2025-07-03 22:05:35.837 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select * from (values (1),(2)) v(a), lateral (select a, i, j, count(*) from bug_16784 group by cube(i,j)) s order by v.a, i, j; 2025-07-03 22:05:35.849 UTC client backend[17979] pg_regress/groupingsets LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17979.1", size 598016 2025-07-03 22:05:35.849 UTC client backend[17979] pg_regress/groupingsets STATEMENT: select * from (values (1),(2)) v(a), lateral (select a, i, j, count(*) from bug_16784 group by cube(i,j)) s order by v.a, i, j; 2025-07-03 22:05:35.864 UTC client backend[18192] pg_regress/privileges ERROR: column "nosuchcol" of relation "pg_authid" does not exist 2025-07-03 22:05:35.864 UTC client backend[18192] pg_regress/privileges STATEMENT: select has_column_privilege('pg_authid','nosuchcol','select'); 2025-07-03 22:05:35.929 UTC client backend[18192] pg_regress/privileges ERROR: column "f2" of relation "mytable" does not exist 2025-07-03 22:05:35.929 UTC client backend[18192] pg_regress/privileges STATEMENT: select has_column_privilege('mytable','f2','select'); 2025-07-03 22:05:35.968 UTC client backend[18192] pg_regress/privileges WARNING: no privileges were granted for "atest4" 2025-07-03 22:05:35.974 UTC client backend[18192] pg_regress/privileges ERROR: dependent privileges exist 2025-07-03 22:05:35.974 UTC client backend[18192] pg_regress/privileges HINT: Use CASCADE to revoke them too. 2025-07-03 22:05:35.974 UTC client backend[18192] pg_regress/privileges STATEMENT: REVOKE SELECT ON atest4 FROM regress_priv_user2; 2025-07-03 22:05:35.994 UTC not initialized[18213] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:35.998 UTC client backend[18213] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:35.998 UTC client backend[18213] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:36.001 UTC client backend[18213] pg_regress/privileges LOG: connection ready: setup total=21.877 ms, fork=13.685 ms, authentication=0.420 ms 2025-07-03 22:05:36.001 UTC client backend[18192] pg_regress/privileges LOG: disconnection: session time: 0:00:00.273 user=postgres database=regression host=[local] 2025-07-03 22:05:36.004 UTC client backend[17961] pg_regress/rowsecurity ERROR: table "copy_t" does not exist 2025-07-03 22:05:36.004 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP TABLE copy_t CASCADE; 2025-07-03 22:05:36.017 UTC client backend[17962] pg_regress/matview ERROR: too many column names were specified 2025-07-03 22:05:36.017 UTC client backend[17962] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_mv_v (ii, jj, kk) AS SELECT i, j FROM mvtest_v; 2025-07-03 22:05:36.047 UTC client backend[17984] pg_regress/generated_stored ERROR: insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey" 2025-07-03 22:05:36.047 UTC client backend[17984] pg_regress/generated_stored DETAIL: Key (b)=(10) is not present in table "gtest23a". 2025-07-03 22:05:36.047 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest23b VALUES (5); 2025-07-03 22:05:36.055 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-07-03 22:05:36.055 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.065 UTC client backend[17962] pg_regress/matview ERROR: too many column names were specified 2025-07-03 22:05:36.065 UTC client backend[17962] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_mv_v_3 (ii, jj, kk) AS SELECT i, j FROM mvtest_v WITH NO DATA; 2025-07-03 22:05:36.075 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-07-03 22:05:36.075 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.076 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-07-03 22:05:36.076 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.105 UTC client backend[17984] pg_regress/generated_stored ERROR: insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey" 2025-07-03 22:05:36.105 UTC client backend[17984] pg_regress/generated_stored DETAIL: Key (b)=(5) is not present in table "gtest23a". 2025-07-03 22:05:36.105 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest23b ALTER COLUMN b SET EXPRESSION AS (a * 5); 2025-07-03 22:05:36.119 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_rel_to" 2025-07-03 22:05:36.119 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.139 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-07-03 22:05:36.139 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.144 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-07-03 22:05:36.144 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.167 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_rel_to" 2025-07-03 22:05:36.167 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.184 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-07-03 22:05:36.184 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.185 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_rel_to 2025-07-03 22:05:36.185 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_rel_to TO STDOUT WITH DELIMITER ','; 2025-07-03 22:05:36.194 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "copy_t" 2025-07-03 22:05:36.194 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-07-03 22:05:36.195 UTC client backend[17961] pg_regress/rowsecurity ERROR: COPY FROM not supported with row-level security 2025-07-03 22:05:36.195 UTC client backend[17961] pg_regress/rowsecurity HINT: Use INSERT statements instead. 2025-07-03 22:05:36.195 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-07-03 22:05:36.201 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-07-03 22:05:36.201 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-07-03 22:05:36.201 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table copy_t 2025-07-03 22:05:36.201 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: COPY copy_t FROM STDIN; 2025-07-03 22:05:36.223 UTC client backend[17984] pg_regress/generated_stored ERROR: insert or update on table "gtest23q" violates foreign key constraint "gtest23q_b_fkey" 2025-07-03 22:05:36.223 UTC client backend[17984] pg_regress/generated_stored DETAIL: Key (b)=(5) is not present in table "gtest23p". 2025-07-03 22:05:36.223 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest23q VALUES (2, 5); 2025-07-03 22:05:36.251 UTC client backend[17984] pg_regress/generated_stored ERROR: value for domain gtestdomain1 violates check constraint "gtestdomain1_check" 2025-07-03 22:05:36.251 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24 (a) VALUES (6); 2025-07-03 22:05:36.284 UTC client backend[17984] pg_regress/generated_stored ERROR: value for domain gtestdomain1 violates check constraint "gtestdomain1_check" 2025-07-03 22:05:36.284 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24r (a) VALUES (6); 2025-07-03 22:05:36.303 UTC client backend[17984] pg_regress/generated_stored ERROR: value for domain gtestdomainnn violates check constraint "gtestdomainnn_check" 2025-07-03 22:05:36.303 UTC client backend[17984] pg_regress/generated_stored STATEMENT: INSERT INTO gtest24nn (a) VALUES (NULL); 2025-07-03 22:05:36.305 UTC client backend[17984] pg_regress/generated_stored ERROR: generated columns are not supported on typed tables 2025-07-03 22:05:36.305 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest28 OF gtest_type (f1 WITH OPTIONS GENERATED ALWAYS AS (f2 *2) STORED); 2025-07-03 22:05:36.319 UTC client backend[17984] pg_regress/generated_stored ERROR: child column "f3" specifies generation expression 2025-07-03 22:05:36.319 UTC client backend[17984] pg_regress/generated_stored HINT: A child table column cannot be generated unless its parent column is. 2025-07-03 22:05:36.319 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_child PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS (f2 * 2) STORED ) FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-07-03 22:05:36.327 UTC client backend[17980] pg_regress/identity ERROR: identity columns are not supported on typed tables 2025-07-03 22:05:36.327 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest12 OF itest_type (f1 WITH OPTIONS GENERATED ALWAYS AS IDENTITY); 2025-07-03 22:05:36.336 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" in child table must not be a generated column 2025-07-03 22:05:36.336 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-07-03 22:05:36.383 UTC client backend[17963] pg_regress/spgist ERROR: value 9 out of bounds for option "fillfactor" 2025-07-03 22:05:36.383 UTC client backend[17963] pg_regress/spgist DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:36.383 UTC client backend[17963] pg_regress/spgist STATEMENT: create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 9); 2025-07-03 22:05:36.385 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" inherits from generated column but specifies default 2025-07-03 22:05:36.385 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 DEFAULT 42 -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.385 UTC client backend[17984] pg_regress/generated_stored ERROR: identity columns are not supported on partitions 2025-07-03 22:05:36.385 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS IDENTITY -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.386 UTC client backend[17963] pg_regress/spgist ERROR: value 101 out of bounds for option "fillfactor" 2025-07-03 22:05:36.386 UTC client backend[17963] pg_regress/spgist DETAIL: Valid values are between "10" and "100". 2025-07-03 22:05:36.386 UTC client backend[17963] pg_regress/spgist STATEMENT: create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 101); 2025-07-03 22:05:36.391 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" inherits from generated column of different kind 2025-07-03 22:05:36.391 UTC client backend[17984] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-07-03 22:05:36.391 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 GENERATED ALWAYS AS (f2 * 2) VIRTUAL -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.393 UTC client backend[17980] pg_regress/identity ERROR: column "f3" in child table "pitest1_p2" must be marked NOT NULL 2025-07-03 22:05:36.393 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ATTACH PARTITION pitest1_p2 FOR VALUES FROM ('2016-08-01') TO ('2016-09-01'); 2025-07-03 22:05:36.395 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" in child table must be a generated column 2025-07-03 22:05:36.395 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.411 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" in child table must be a generated column 2025-07-03 22:05:36.411 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.430 UTC client backend[17984] pg_regress/generated_stored ERROR: table "gtest_child3" being attached contains an identity column "f3" 2025-07-03 22:05:36.430 UTC client backend[17984] pg_regress/generated_stored DETAIL: The new partition may not contain an identity column. 2025-07-03 22:05:36.430 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.444 UTC client backend[17984] pg_regress/generated_stored ERROR: column "f3" inherits from generated column of different kind 2025-07-03 22:05:36.444 UTC client backend[17984] pg_regress/generated_stored DETAIL: Parent column is STORED, child column is VIRTUAL. 2025-07-03 22:05:36.444 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:05:36.500 UTC client backend[17961] pg_regress/rowsecurity ERROR: role "regress_rls_eve" cannot be dropped because some objects depend on it 2025-07-03 22:05:36.500 UTC client backend[17961] pg_regress/rowsecurity DETAIL: privileges for table tbl1 target of policy p on table tbl1 2025-07-03 22:05:36.500 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_eve; 2025-07-03 22:05:36.504 UTC client backend[17961] pg_regress/rowsecurity ERROR: role "regress_rls_eve" cannot be dropped because some objects depend on it 2025-07-03 22:05:36.504 UTC client backend[17961] pg_regress/rowsecurity DETAIL: privileges for table tbl1 2025-07-03 22:05:36.504 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_eve; 2025-07-03 22:05:36.523 UTC client backend[17961] pg_regress/rowsecurity ERROR: role "regress_rls_frank" cannot be dropped because some objects depend on it 2025-07-03 22:05:36.523 UTC client backend[17961] pg_regress/rowsecurity DETAIL: target of policy p on table tbl1 2025-07-03 22:05:36.523 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP ROLE regress_rls_frank; 2025-07-03 22:05:36.547 UTC client backend[17980] pg_regress/identity ERROR: cannot change identity column of a partition 2025-07-03 22:05:36.547 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET GENERATED BY DEFAULT; 2025-07-03 22:05:36.548 UTC client backend[17980] pg_regress/identity ERROR: cannot change identity column of a partition 2025-07-03 22:05:36.548 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET INCREMENT BY 2; 2025-07-03 22:05:36.549 UTC client backend[17980] pg_regress/identity ERROR: cannot change identity column of only the partitioned table 2025-07-03 22:05:36.549 UTC client backend[17980] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-07-03 22:05:36.549 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE ONLY pitest2 ALTER COLUMN f3 SET GENERATED BY DEFAULT SET INCREMENT BY 2 SET START WITH 1000 RESTART; 2025-07-03 22:05:36.551 UTC client backend[17961] pg_regress/rowsecurity ERROR: aggregate functions are not allowed in policy expressions 2025-07-03 22:05:36.551 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: CREATE POLICY p ON t USING (max(c)); 2025-07-03 22:05:36.557 UTC client backend[17962] pg_regress/matview ERROR: division by zero 2025-07-03 22:05:36.557 UTC client backend[17962] pg_regress/matview STATEMENT: create materialized view mvtest_error as select 1/0 as x; 2025-07-03 22:05:36.575 UTC client backend[17980] pg_regress/identity ERROR: null value in column "f3" of relation "pitest2_p1" violates not-null constraint 2025-07-03 22:05:36.575 UTC client backend[17980] pg_regress/identity DETAIL: Failing row contains (07-07-2016, from pitest2_p1, null). 2025-07-03 22:05:36.575 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT into pitest2_p1 (f1, f2) VALUES ('2016-07-7', 'from pitest2_p1'); 2025-07-03 22:05:36.579 UTC client backend[17962] pg_regress/matview ERROR: division by zero 2025-07-03 22:05:36.579 UTC client backend[17962] pg_regress/matview STATEMENT: refresh materialized view mvtest_error; 2025-07-03 22:05:36.615 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r2" 2025-07-03 22:05:36.615 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r2 VALUES (2); 2025-07-03 22:05:36.616 UTC client backend[17980] pg_regress/identity ERROR: cannot add identity to a column of a partition 2025-07-03 22:05:36.616 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest3_p1 ALTER COLUMN f3 SET NOT NULL, ALTER COLUMN f3 ADD GENERATED ALWAYS AS IDENTITY (START WITH 3); 2025-07-03 22:05:36.621 UTC client backend[17980] pg_regress/identity ERROR: cannot add identity to a column of only the partitioned table 2025-07-03 22:05:36.621 UTC client backend[17980] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-07-03 22:05:36.621 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE ONLY pitest3 ALTER COLUMN f3 ADD GENERATED ALWAYS AS IDENTITY (START WITH 3); 2025-07-03 22:05:36.646 UTC client backend[17980] pg_regress/identity ERROR: cannot drop identity from a column of a partition 2025-07-03 22:05:36.646 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest3_p1 ALTER COLUMN f3 DROP IDENTITY; 2025-07-03 22:05:36.648 UTC client backend[17980] pg_regress/identity ERROR: cannot drop identity from a column of only the partitioned table 2025-07-03 22:05:36.648 UTC client backend[17980] pg_regress/identity HINT: Do not specify the ONLY keyword. 2025-07-03 22:05:36.648 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE ONLY pitest3 ALTER COLUMN f3 DROP IDENTITY; 2025-07-03 22:05:36.655 UTC client backend[17980] pg_regress/identity ERROR: null value in column "f3" of relation "pitest3_p1" violates not-null constraint 2025-07-03 22:05:36.655 UTC client backend[17980] pg_regress/identity DETAIL: Failing row contains (07-04-2016, from pitest3, null). 2025-07-03 22:05:36.655 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT into pitest3(f1, f2) VALUES ('2016-07-4', 'from pitest3'); 2025-07-03 22:05:36.660 UTC client backend[17980] pg_regress/identity ERROR: null value in column "f3" of relation "pitest3_p1" violates not-null constraint 2025-07-03 22:05:36.660 UTC client backend[17980] pg_regress/identity DETAIL: Failing row contains (07-05-2016, from pitest3_p1, null). 2025-07-03 22:05:36.660 UTC client backend[17980] pg_regress/identity STATEMENT: INSERT into pitest3_p1 (f1, f2) VALUES ('2016-07-5', 'from pitest3_p1'); 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity ERROR: column "f3" of relation "pitest1_p1" is an identity column 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p1 ALTER COLUMN f3 DROP NOT NULL; 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity ERROR: column "f3" of relation "pitest1" is an identity column 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 DROP NOT NULL; 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity ERROR: column "f3" of relation "pitest1_p2" is an identity column 2025-07-03 22:05:36.665 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p2 ALTER COLUMN f3 SET DEFAULT 10000; 2025-07-03 22:05:36.667 UTC client backend[17980] pg_regress/identity ERROR: column "f3" of relation "pitest1" is an identity column 2025-07-03 22:05:36.667 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 SET DEFAULT 10000; 2025-07-03 22:05:36.668 UTC client backend[17980] pg_regress/identity ERROR: cannot add identity to a column of a partition 2025-07-03 22:05:36.668 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1_p2 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY; 2025-07-03 22:05:36.674 UTC client backend[17980] pg_regress/identity ERROR: column "f3" of relation "pitest1" is already an identity column 2025-07-03 22:05:36.674 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY; 2025-07-03 22:05:36.680 UTC client backend[17980] pg_regress/identity ERROR: identity columns are not supported on partitions 2025-07-03 22:05:36.680 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE pitest1_pfail PARTITION OF pitest1 ( f3 WITH OPTIONS GENERATED ALWAYS AS IDENTITY ) FOR VALUES FROM ('2016-11-01') TO ('2016-12-01'); 2025-07-03 22:05:36.681 UTC client backend[17980] pg_regress/identity ERROR: identity columns are not supported on partitions 2025-07-03 22:05:36.681 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE pitest_pfail PARTITION OF pitest3 ( f3 WITH OPTIONS GENERATED ALWAYS AS IDENTITY ) FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-07-03 22:05:36.683 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:36.683 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (1); 2025-07-03 22:05:36.693 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-07-03 22:05:36.693 UTC client backend[17961] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-07-03 22:05:36.693 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: TABLE r1; 2025-07-03 22:05:36.694 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-07-03 22:05:36.694 UTC client backend[17961] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-07-03 22:05:36.694 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: UPDATE r1 SET a = 1; 2025-07-03 22:05:36.695 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-07-03 22:05:36.695 UTC client backend[17961] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-07-03 22:05:36.695 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DELETE FROM r1; 2025-07-03 22:05:36.705 UTC client backend[17980] pg_regress/identity ERROR: table "pitest1_pfail" being attached contains an identity column "f3" 2025-07-03 22:05:36.705 UTC client backend[17980] pg_regress/identity DETAIL: The new partition may not contain an identity column. 2025-07-03 22:05:36.705 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest1 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01'); 2025-07-03 22:05:36.706 UTC client backend[17980] pg_regress/identity ERROR: table "pitest1_pfail" being attached contains an identity column "f3" 2025-07-03 22:05:36.706 UTC client backend[17980] pg_regress/identity DETAIL: The new partition may not contain an identity column. 2025-07-03 22:05:36.706 UTC client backend[17980] pg_regress/identity STATEMENT: ALTER TABLE pitest3 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01'); 2025-07-03 22:05:36.752 UTC client backend[17980] pg_regress/identity ERROR: conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 63 2025-07-03 22:05:36.752 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest15 (id integer GENERATED ALWAYS AS IDENTITY NULL); 2025-07-03 22:05:36.752 UTC client backend[17980] pg_regress/identity ERROR: conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 39 2025-07-03 22:05:36.752 UTC client backend[17980] pg_regress/identity STATEMENT: CREATE TABLE itest15 (id integer NULL GENERATED ALWAYS AS IDENTITY); 2025-07-03 22:05:36.753 UTC client backend[17962] pg_regress/matview ERROR: relation "mvtest_mv_foo" already exists 2025-07-03 22:05:36.753 UTC client backend[17962] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW mvtest_mv_foo AS SELECT * FROM mvtest_foo_data; 2025-07-03 22:05:36.765 UTC client backend[17961] pg_regress/rowsecurity ERROR: update or delete on table "r1" violates foreign key constraint "r2_a_fkey" on table "r2" 2025-07-03 22:05:36.765 UTC client backend[17961] pg_regress/rowsecurity DETAIL: Key (a)=(10) is still referenced from table "r2". 2025-07-03 22:05:36.765 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DELETE FROM r1; 2025-07-03 22:05:36.807 UTC client backend[17980] pg_regress/identity ERROR: cannot insert a non-DEFAULT value into column "a" 2025-07-03 22:05:36.807 UTC client backend[17980] pg_regress/identity DETAIL: Column "a" is an identity column defined as GENERATED ALWAYS. 2025-07-03 22:05:36.807 UTC client backend[17980] pg_regress/identity HINT: Use OVERRIDING SYSTEM VALUE to override. 2025-07-03 22:05:36.807 UTC client backend[17980] pg_regress/identity STATEMENT: MERGE INTO itest15 t USING (SELECT 10 AS s_a, 'inserted by merge' AS s_b) s ON t.a = s.s_a WHEN NOT MATCHED THEN INSERT (a, b) VALUES (s.s_a, s.s_b); 2025-07-03 22:05:36.889 UTC client backend[17980] pg_regress/identity LOG: disconnection: session time: 0:00:04.365 user=postgres database=regression host=[local] 2025-07-03 22:05:36.958 UTC client backend[17962] pg_regress/matview ERROR: could not find suitable unique index on materialized view "drop_idx_matview" 2025-07-03 22:05:36.958 UTC client backend[17962] pg_regress/matview STATEMENT: REFRESH MATERIALIZED VIEW CONCURRENTLY drop_idx_matview; 2025-07-03 22:05:36.976 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "r1" 2025-07-03 22:05:36.976 UTC client backend[17961] pg_regress/rowsecurity HINT: To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY. 2025-07-03 22:05:36.976 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: TABLE r1; 2025-07-03 22:05:36.987 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:36.987 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10), (20) RETURNING *; 2025-07-03 22:05:37.022 UTC client backend[17962] pg_regress/matview ERROR: materialized view "mvtest2" has not been populated 2025-07-03 22:05:37.022 UTC client backend[17962] pg_regress/matview HINT: Use the REFRESH MATERIALIZED VIEW command. 2025-07-03 22:05:37.022 UTC client backend[17962] pg_regress/matview STATEMENT: SELECT * FROM mvtest2; 2025-07-03 22:05:37.023 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:37.023 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: UPDATE r1 SET a = 30 RETURNING *; 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT (a) DO UPDATE SET a = 30 RETURNING *; 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT (a) DO UPDATE SET a = 30; 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy for table "r1" 2025-07-03 22:05:37.024 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (10) ON CONFLICT ON CONSTRAINT r1_pkey DO UPDATE SET a = 30; 2025-07-03 22:05:37.069 UTC client backend[17965] pg_regress/brin ERROR: "brintest" is not an index 2025-07-03 22:05:37.069 UTC client backend[17965] pg_regress/brin STATEMENT: SELECT brin_summarize_new_values('brintest'); 2025-07-03 22:05:37.071 UTC client backend[17965] pg_regress/brin ERROR: "tenk1_unique1" is not a BRIN index 2025-07-03 22:05:37.071 UTC client backend[17965] pg_regress/brin STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-07-03 22:05:37.071 UTC client backend[17965] pg_regress/brin ERROR: block number out of range: -1 2025-07-03 22:05:37.071 UTC client backend[17965] pg_regress/brin STATEMENT: SELECT brin_desummarize_range('brinidx', -1); 2025-07-03 22:05:37.076 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p1" for table "r1" 2025-07-03 22:05:37.076 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (0); 2025-07-03 22:05:37.076 UTC client backend[17961] pg_regress/rowsecurity ERROR: new row violates row-level security policy "p2" for table "r1" 2025-07-03 22:05:37.076 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: INSERT INTO r1 VALUES (4); 2025-07-03 22:05:37.097 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.63", size 146674 2025-07-03 22:05:37.097 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.108 UTC client backend[17965] pg_regress/brin ERROR: block number out of range: -1 2025-07-03 22:05:37.108 UTC client backend[17965] pg_regress/brin STATEMENT: SELECT brin_summarize_range('brin_summarize_idx', -1); 2025-07-03 22:05:37.108 UTC client backend[17965] pg_regress/brin ERROR: block number out of range: 4294967296 2025-07-03 22:05:37.108 UTC client backend[17965] pg_regress/brin STATEMENT: SELECT brin_summarize_range('brin_summarize_idx', 4294967296); 2025-07-03 22:05:37.118 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.66", size 145199 2025-07-03 22:05:37.118 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.126 UTC client backend[17962] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-07-03 22:05:37.126 UTC client backend[17962] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0; 2025-07-03 22:05:37.131 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.68", size 149388 2025-07-03 22:05:37.131 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.134 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.65", size 149978 2025-07-03 22:05:37.134 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.135 UTC client backend[17962] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-07-03 22:05:37.135 UTC client backend[17962] pg_regress/matview STATEMENT: CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0 WITH NO DATA; 2025-07-03 22:05:37.136 UTC client backend[17962] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-07-03 22:05:37.136 UTC client backend[17962] pg_regress/matview STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF, BUFFERS OFF) CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0; 2025-07-03 22:05:37.136 UTC client backend[17962] pg_regress/matview ERROR: relation "matview_ine_tab" already exists 2025-07-03 22:05:37.136 UTC client backend[17962] pg_regress/matview STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF, BUFFERS OFF) CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0 WITH NO DATA; 2025-07-03 22:05:37.145 UTC client backend[17962] pg_regress/matview LOG: disconnection: session time: 0:00:04.698 user=postgres database=regression host=[local] 2025-07-03 22:05:37.154 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.64", size 149565 2025-07-03 22:05:37.154 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.157 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.69", size 145081 2025-07-03 22:05:37.157 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.171 UTC client backend[17961] pg_regress/rowsecurity ERROR: policy "p1" for table "dob_t1" does not exist 2025-07-03 22:05:37.171 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON dob_t1; 2025-07-03 22:05:37.184 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.67", size 147795 2025-07-03 22:05:37.184 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); 2025-07-03 22:05:37.187 UTC client backend[17961] pg_regress/rowsecurity ERROR: policy "p1" for table "dob_t1" does not exist 2025-07-03 22:05:37.187 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: DROP POLICY p1 ON dob_t1; 2025-07-03 22:05:37.191 UTC client backend[17979] pg_regress/groupingsets LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17979.6", size 1720320 2025-07-03 22:05:37.191 UTC client backend[17979] pg_regress/groupingsets STATEMENT: create table gs_hash_1 as select g100, g10, sum(g::numeric), count(*), max(g::text) from gs_data_1 group by cube (g1000, g100,g10); 2025-07-03 22:05:37.254 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table ref_tbl 2025-07-03 22:05:37.254 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM ref_tbl; 2025-07-03 22:05:37.254 UTC client backend[17961] pg_regress/rowsecurity ERROR: permission denied for table rls_tbl 2025-07-03 22:05:37.254 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: SELECT * FROM rls_tbl; 2025-07-03 22:05:37.322 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.77", size 146674 2025-07-03 22:05:37.322 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.322 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.339 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.80", size 145199 2025-07-03 22:05:37.339 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.339 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.343 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.82", size 149388 2025-07-03 22:05:37.343 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.343 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.358 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.79", size 149978 2025-07-03 22:05:37.358 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.358 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.381 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.78", size 149565 2025-07-03 22:05:37.381 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.381 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.391 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.83", size 145081 2025-07-03 22:05:37.391 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.391 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.395 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.81", size 147795 2025-07-03 22:05:37.395 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.395 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id); $$); 2025-07-03 22:05:37.464 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "rls_t" 2025-07-03 22:05:37.464 UTC client backend[17961] pg_regress/rowsecurity CONTEXT: SQL function "rls_f" statement 1 2025-07-03 22:05:37.464 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: select rls_f(c) from test_t order by rls_f; 2025-07-03 22:05:37.472 UTC client backend[17961] pg_regress/rowsecurity ERROR: query would be affected by row-level security policy for table "rls_t" 2025-07-03 22:05:37.472 UTC client backend[17961] pg_regress/rowsecurity CONTEXT: SQL function "rls_f" statement 1 2025-07-03 22:05:37.472 UTC client backend[17961] pg_regress/rowsecurity STATEMENT: select rls_f(c) from test_t order by rls_f; 2025-07-03 22:05:37.523 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.91", size 143134 2025-07-03 22:05:37.523 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.526 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.94", size 141718 2025-07-03 22:05:37.526 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.551 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.96", size 146379 2025-07-03 22:05:37.551 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.561 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.93", size 146143 2025-07-03 22:05:37.561 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.581 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.92", size 145848 2025-07-03 22:05:37.581 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.592 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.97", size 141541 2025-07-03 22:05:37.592 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.595 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.95", size 143311 2025-07-03 22:05:37.595 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:37.767 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.105", size 143016 2025-07-03 22:05:37.767 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.767 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.787 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.108", size 141777 2025-07-03 22:05:37.787 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.787 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.803 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.110", size 145789 2025-07-03 22:05:37.803 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.803 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.807 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.107", size 146556 2025-07-03 22:05:37.807 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.807 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.851 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.106", size 146379 2025-07-03 22:05:37.851 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.851 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.866 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.111", size 141541 2025-07-03 22:05:37.866 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.866 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.886 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.109", size 144550 2025-07-03 22:05:37.886 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:37.886 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:37.916 UTC client backend[17961] pg_regress/rowsecurity LOG: disconnection: session time: 0:00:05.480 user=postgres database=regression host=[local] 2025-07-03 22:05:38.004 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-07-03 22:05:38.004 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-07-03 22:05:38.004 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) STORED) PARTITION BY RANGE (f3); 2025-07-03 22:05:38.005 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use generated column in partition key at character 126 2025-07-03 22:05:38.005 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "f3" is a generated column. 2025-07-03 22:05:38.005 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) STORED) PARTITION BY RANGE ((f3 * 3)); 2025-07-03 22:05:38.045 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot use generated column "b" in column generation expression 2025-07-03 22:05:38.045 UTC client backend[17984] pg_regress/generated_stored DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:05:38.045 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (b * 4) STORED; 2025-07-03 22:05:38.047 UTC client backend[17984] pg_regress/generated_stored ERROR: column "z" does not exist 2025-07-03 22:05:38.047 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (z * 4) STORED; 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o6of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o2of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o5of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o7of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o4of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o1of8.p1.0", size 131072 2025-07-03 22:05:38.065 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/i1of4.p0.0", size 131072 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/i2of4.p0.0", size 131072 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o3of8.p1.0", size 131072 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/o0of8.p1.0", size 131072 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.13.fileset/i3of4.p0.0", size 131072 2025-07-03 22:05:38.066 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join bigger_than_it_looks s using (id); 2025-07-03 22:05:38.088 UTC client backend[17963] pg_regress/spgist LOG: disconnection: session time: 0:00:05.640 user=postgres database=regression host=[local] 2025-07-03 22:05:38.140 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter type of a column used by a generated column 2025-07-03 22:05:38.140 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "a" is used by generated column "x". 2025-07-03 22:05:38.140 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE text; 2025-07-03 22:05:38.193 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.14.fileset/i1of4.p0.0", size 131072 2025-07-03 22:05:38.193 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.193 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.14.fileset/i2of4.p0.0", size 131072 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.14.fileset/i3of4.p0.0", size 131072 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.194 UTC client backend[17982] pg_regress/join_hash STATEMENT: select original > 1 as initially_multibatch, final > original as increased_batches from hash_join_batches( $$ select count(*) from simple r join bigger_than_it_looks s using (id); $$); 2025-07-03 22:05:38.232 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot specify USING when altering type of generated column at character 34 2025-07-03 22:05:38.232 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "x" is a generated column. 2025-07-03 22:05:38.232 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x TYPE boolean USING x <> 0; 2025-07-03 22:05:38.234 UTC client backend[17984] pg_regress/generated_stored ERROR: column "x" of relation "gtest27" is a generated column 2025-07-03 22:05:38.234 UTC client backend[17984] pg_regress/generated_stored HINT: Use ALTER TABLE ... ALTER COLUMN ... DROP EXPRESSION instead. 2025-07-03 22:05:38.234 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x DROP DEFAULT; 2025-07-03 22:05:38.294 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter type of a column used by a generated column 2025-07-03 22:05:38.294 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "a" is used by generated column "x". 2025-07-03 22:05:38.294 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE float8, ALTER COLUMN b TYPE float8; 2025-07-03 22:05:38.309 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.112", size 480000 2025-07-03 22:05:38.309 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.344 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.113", size 593422 2025-07-03 22:05:38.344 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.364 UTC client backend[17984] pg_regress/generated_stored ERROR: column "a" of relation "gtest29" is not a generated column 2025-07-03 22:05:38.364 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a SET EXPRESSION AS (a * 3); 2025-07-03 22:05:38.365 UTC client backend[17984] pg_regress/generated_stored ERROR: column "a" of relation "gtest29" is not a generated column 2025-07-03 22:05:38.365 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a DROP EXPRESSION; 2025-07-03 22:05:38.409 UTC client backend[17979] pg_regress/groupingsets LOG: disconnection: session time: 0:00:05.877 user=postgres database=regression host=[local] 2025-07-03 22:05:38.438 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.114", size 480000 2025-07-03 22:05:38.438 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.438 UTC client backend[17982] pg_regress/join_hash STATEMENT: select * from hash_join_batches( $$ select count(*) from simple r join extremely_skewed s using (id); $$); 2025-07-03 22:05:38.504 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.115", size 593422 2025-07-03 22:05:38.504 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.504 UTC client backend[17982] pg_regress/join_hash STATEMENT: select * from hash_join_batches( $$ select count(*) from simple r join extremely_skewed s using (id); $$); 2025-07-03 22:05:38.577 UTC client backend[18213] pg_regress/privileges LOG: process 18213 still waiting for ShareLock on virtual transaction 31/54 after 1000.048 ms 2025-07-03 22:05:38.577 UTC client backend[18213] pg_regress/privileges DETAIL: Process holding the lock: 17982. Wait queue: 18213, 17965. 2025-07-03 22:05:38.577 UTC client backend[18213] pg_regress/privileges STATEMENT: CREATE INDEX CONCURRENTLY sro_idx ON sro_tab ((sro_ifun(a) + sro_ifun(0))) WHERE sro_ifun(a + 10) > sro_ifun(10); 2025-07-03 22:05:38.602 UTC parallel worker[18379] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp18379.0", size 480000 2025-07-03 22:05:38.602 UTC parallel worker[18379] STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.615 UTC parallel worker[18379] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp18379.1", size 218300 2025-07-03 22:05:38.615 UTC parallel worker[18379] STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.619 UTC client backend[17984] pg_regress/generated_stored ERROR: ALTER TABLE / DROP EXPRESSION must be applied to child tables too 2025-07-03 22:05:38.619 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE ONLY gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:05:38.620 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.116", size 480000 2025-07-03 22:05:38.620 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.669 UTC parallel worker[18378] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp18378.0", size 480000 2025-07-03 22:05:38.669 UTC parallel worker[18378] STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.678 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.117", size 367806 2025-07-03 22:05:38.678 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.745 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot drop generation expression from inherited column 2025-07-03 22:05:38.745 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest30_1 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:05:38.772 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:05:38.772 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-07-03 22:05:38.776 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:05:38.776 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello1'); 2025-07-03 22:05:38.796 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:05:38.796 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello2'); 2025-07-03 22:05:38.813 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:05:38.813 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b SET EXPRESSION AS ('hello3'); 2025-07-03 22:05:38.834 UTC client backend[17960] pg_regress/gist ERROR: lossy distance functions are not supported in index-only scans 2025-07-03 22:05:38.834 UTC client backend[17960] pg_regress/gist STATEMENT: select p from gist_tbl order by circle(p,1) <-> point(0,0) limit 1; 2025-07-03 22:05:38.840 UTC parallel worker[18393] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp18393.0", size 480000 2025-07-03 22:05:38.840 UTC parallel worker[18393] STATEMENT: explain (analyze, format 'json') select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.845 UTC client backend[17984] pg_regress/generated_stored ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:05:38.845 UTC client backend[17984] pg_regress/generated_stored STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-07-03 22:05:38.847 UTC parallel worker[18392] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp18392.0", size 480000 2025-07-03 22:05:38.847 UTC parallel worker[18392] STATEMENT: explain (analyze, format 'json') select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:38.851 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.118", size 480000 2025-07-03 22:05:38.851 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.851 UTC client backend[17982] pg_regress/join_hash STATEMENT: select * from hash_join_batches( $$ select count(*) from simple r join extremely_skewed s using (id); $$); 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored DETAIL: Column "b" is a generated column. 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TRIGGER gtest2a BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.b < 0) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored DETAIL: A whole-row reference is used and the table contains generated columns. 2025-07-03 22:05:38.883 UTC client backend[17984] pg_regress/generated_stored STATEMENT: CREATE TRIGGER gtest2b BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.* IS NOT NULL) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-07-03 22:05:38.893 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.119", size 407631 2025-07-03 22:05:38.893 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:38.893 UTC client backend[17982] pg_regress/join_hash STATEMENT: select * from hash_join_batches( $$ select count(*) from simple r join extremely_skewed s using (id); $$); 2025-07-03 22:05:38.960 UTC client backend[17965] pg_regress/brin LOG: process 17965 still waiting for ShareLock on virtual transaction 31/54 after 1000.050 ms 2025-07-03 22:05:38.960 UTC client backend[17965] pg_regress/brin DETAIL: Process holding the lock: 17982. Wait queue: 18213, 17965. 2025-07-03 22:05:38.960 UTC client backend[17965] pg_regress/brin STATEMENT: CREATE INDEX CONCURRENTLY brin_test_temp_idx ON brintest_3(a); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o3of4.p0.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o0of4.p1.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o3of4.p1.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o1of4.p0.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o1of4.p1.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o0of4.p0.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o2of4.p0.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/o2of4.p1.0", size 163840 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.15.fileset/i3of4.p0.0", size 491520 2025-07-03 22:05:39.020 UTC client backend[17982] pg_regress/join_hash STATEMENT: select count(*) from simple r join extremely_skewed s using (id); 2025-07-03 22:05:39.049 UTC client backend[17984] pg_regress/generated_stored LOG: disconnection: session time: 0:00:06.514 user=postgres database=regression host=[local] 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o3of4.p0.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o0of4.p1.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o3of4.p1.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o1of4.p0.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o1of4.p1.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o0of4.p0.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o2of4.p0.0", size 163840 2025-07-03 22:05:39.185 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/o2of4.p1.0", size 163840 2025-07-03 22:05:39.186 UTC parallel worker[18433] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.16.fileset/i3of4.p0.0", size 491520 2025-07-03 22:05:39.248 UTC client backend[17960] pg_regress/gist LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17960.0", size 237568 2025-07-03 22:05:39.248 UTC client backend[17960] pg_regress/gist STATEMENT: create index gist_tbl_box_index_forcing_buffering on gist_tbl using gist (p) with (buffering=on, fillfactor=50); 2025-07-03 22:05:39.295 UTC client backend[17960] pg_regress/gist LOG: disconnection: session time: 0:00:06.850 user=postgres database=regression host=[local] 2025-07-03 22:05:39.993 UTC client backend[17967] pg_regress/gin LOG: disconnection: session time: 0:00:07.538 user=postgres database=regression host=[local] 2025-07-03 22:05:46.019 UTC client backend[18213] pg_regress/privileges LOG: process 18213 still waiting for ShareLock on virtual transaction 31/54 after 8442.057 ms 2025-07-03 22:05:46.019 UTC client backend[18213] pg_regress/privileges DETAIL: Process holding the lock: 17982. Wait queue: 18213, 17965. 2025-07-03 22:05:46.019 UTC client backend[18213] pg_regress/privileges STATEMENT: CREATE INDEX CONCURRENTLY sro_idx ON sro_tab ((sro_ifun(a) + sro_ifun(0))) WHERE sro_ifun(a + 10) > sro_ifun(10); 2025-07-03 22:05:47.108 UTC client backend[17965] pg_regress/brin LOG: process 17965 still waiting for ShareLock on virtual transaction 31/54 after 9147.694 ms 2025-07-03 22:05:47.108 UTC client backend[17965] pg_regress/brin DETAIL: Process holding the lock: 17982. Wait queue: 18213, 17965. 2025-07-03 22:05:47.108 UTC client backend[17965] pg_regress/brin STATEMENT: CREATE INDEX CONCURRENTLY brin_test_temp_idx ON brintest_3(a); 2025-07-03 22:05:55.725 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.28.fileset/i5of8.p0.0", size 327680 2025-07-03 22:05:55.725 UTC client backend[17982] pg_regress/join_hash STATEMENT: select length(max(s.t)) from wide left join (select id, coalesce(t, '') || '' as t from wide) s using (id); 2025-07-03 22:05:55.725 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.28.fileset/i7of8.p0.0", size 327680 2025-07-03 22:05:55.725 UTC client backend[17982] pg_regress/join_hash STATEMENT: select length(max(s.t)) from wide left join (select id, coalesce(t, '') || '' as t from wide) s using (id); 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.29.fileset/i5of8.p0.0", size 327680 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash STATEMENT: select final > 1 as multibatch from hash_join_batches( $$ select length(max(s.t)) from wide left join (select id, coalesce(t, '') || '' as t from wide) s using (id); $$); 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp17982.29.fileset/i7of8.p0.0", size 327680 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash CONTEXT: PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement 2025-07-03 22:05:55.871 UTC client backend[17982] pg_regress/join_hash STATEMENT: select final > 1 as multibatch from hash_join_batches( $$ select length(max(s.t)) from wide left join (select id, coalesce(t, '') || '' as t from wide) s using (id); $$); 2025-07-03 22:05:56.049 UTC client backend[18213] pg_regress/privileges LOG: process 18213 acquired ShareLock on virtual transaction 31/54 after 18472.220 ms 2025-07-03 22:05:56.049 UTC client backend[18213] pg_regress/privileges STATEMENT: CREATE INDEX CONCURRENTLY sro_idx ON sro_tab ((sro_ifun(a) + sro_ifun(0))) WHERE sro_ifun(a + 10) > sro_ifun(10); 2025-07-03 22:05:56.049 UTC client backend[17965] pg_regress/brin LOG: process 17965 acquired ShareLock on virtual transaction 31/54 after 18089.050 ms 2025-07-03 22:05:56.049 UTC client backend[17965] pg_regress/brin STATEMENT: CREATE INDEX CONCURRENTLY brin_test_temp_idx ON brintest_3(a); 2025-07-03 22:05:56.290 UTC client backend[17982] pg_regress/join_hash LOG: disconnection: session time: 0:00:23.770 user=postgres database=regression host=[local] 2025-07-03 22:05:56.333 UTC client backend[17965] pg_regress/brin LOG: disconnection: session time: 0:00:23.885 user=postgres database=regression host=[local] 2025-07-03 22:05:56.358 UTC client backend[18213] pg_regress/privileges ERROR: cannot create a cursor WITH HOLD within security-restricted operation 2025-07-03 22:05:56.358 UTC client backend[18213] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-07-03 22:05:56.358 UTC client backend[18213] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-07-03 22:05:56.407 UTC not initialized[20701] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.408 UTC client backend[20701] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.408 UTC client backend[20701] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.414 UTC client backend[20701] pg_regress/privileges LOG: connection ready: setup total=40.922 ms, fork=26.000 ms, authentication=0.448 ms 2025-07-03 22:05:56.414 UTC client backend[18213] pg_regress/privileges LOG: disconnection: session time: 0:00:20.422 user=postgres database=regression host=[local] 2025-07-03 22:05:56.421 UTC client backend[20701] pg_regress/privileges ERROR: cannot create a cursor WITH HOLD within security-restricted operation 2025-07-03 22:05:56.421 UTC client backend[20701] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-07-03 22:05:56.421 UTC client backend[20701] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-07-03 22:05:56.504 UTC client backend[20701] pg_regress/privileges ERROR: cannot fire deferred trigger within security-restricted operation 2025-07-03 22:05:56.504 UTC client backend[20701] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-07-03 22:05:56.504 UTC client backend[20701] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-07-03 22:05:56.509 UTC not initialized[20709] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.515 UTC client backend[20709] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.515 UTC client backend[20709] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.519 UTC client backend[20709] pg_regress/privileges LOG: connection ready: setup total=13.536 ms, fork=1.940 ms, authentication=5.791 ms 2025-07-03 22:05:56.519 UTC client backend[20701] pg_regress/privileges LOG: disconnection: session time: 0:00:00.119 user=postgres database=regression host=[local] 2025-07-03 22:05:56.539 UTC client backend[20709] pg_regress/privileges ERROR: cannot fire deferred trigger within security-restricted operation 2025-07-03 22:05:56.539 UTC client backend[20709] pg_regress/privileges CONTEXT: SQL function "mv_action" statement 1 2025-07-03 22:05:56.539 UTC client backend[20709] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-07-03 22:05:56.550 UTC client backend[20709] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-07-03 22:05:56.550 UTC client backend[20709] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-07-03 22:05:56.550 UTC client backend[20709] pg_regress/privileges CONTEXT: SQL function "unwanted_grant" statement 1 SQL statement "SELECT public.unwanted_grant()" PL/pgSQL function public.sro_trojan() line 1 at PERFORM SQL function "mv_action" statement 1 2025-07-03 22:05:56.550 UTC client backend[20709] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW sro_mv; 2025-07-03 22:05:56.573 UTC not initialized[20715] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.575 UTC client backend[20715] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.575 UTC client backend[20715] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.578 UTC client backend[20715] pg_regress/privileges LOG: connection ready: setup total=12.992 ms, fork=7.802 ms, authentication=0.497 ms 2025-07-03 22:05:56.578 UTC client backend[20709] pg_regress/privileges LOG: disconnection: session time: 0:00:00.071 user=postgres database=regression host=[local] 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-07-03 22:05:56.674 UTC client backend[20715] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-07-03 22:05:56.675 UTC client backend[20715] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-07-03 22:05:56.675 UTC client backend[20715] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-07-03 22:05:56.675 UTC client backend[20715] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-07-03 22:05:56.676 UTC client backend[20715] pg_regress/privileges ERROR: permission denied to grant role "regress_priv_group2" 2025-07-03 22:05:56.676 UTC client backend[20715] pg_regress/privileges DETAIL: Only roles with the ADMIN option on role "regress_priv_group2" may grant this role. 2025-07-03 22:05:56.676 UTC client backend[20715] pg_regress/privileges STATEMENT: GRANT regress_priv_group2 TO regress_priv_user5; 2025-07-03 22:05:56.682 UTC not initialized[20729] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.684 UTC client backend[20729] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.684 UTC client backend[20729] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.687 UTC client backend[20729] pg_regress/privileges LOG: connection ready: setup total=9.857 ms, fork=4.681 ms, authentication=0.391 ms 2025-07-03 22:05:56.687 UTC client backend[20715] pg_regress/privileges LOG: disconnection: session time: 0:00:00.114 user=postgres database=regression host=[local] 2025-07-03 22:05:56.713 UTC client backend[20729] pg_regress/privileges ERROR: "atest1" is not a sequence 2025-07-03 22:05:56.713 UTC client backend[20729] pg_regress/privileges STATEMENT: SELECT has_sequence_privilege('regress_priv_user1', 'atest1', 'SELECT'); 2025-07-03 22:05:56.713 UTC client backend[20729] pg_regress/privileges ERROR: unrecognized privilege type: "INSERT" 2025-07-03 22:05:56.713 UTC client backend[20729] pg_regress/privileges STATEMENT: SELECT has_sequence_privilege('regress_priv_user1', 'x_seq', 'INSERT'); 2025-07-03 22:05:56.720 UTC autovacuum worker[20730] LOG: automatic analyze of table "postgres.pg_catalog.pg_authid" avg read rate: 20.221 MB/s, avg write rate: 3.676 MB/s buffer usage: 516 hits, 44 reads, 8 dirtied WAL usage: 38 records, 6 full page images, 52398 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:05:56.720 UTC not initialized[20733] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.721 UTC client backend[20733] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.721 UTC client backend[20733] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.722 UTC autovacuum worker[20730] LOG: automatic analyze of table "postgres.pg_catalog.pg_auth_members" avg read rate: 11.719 MB/s, avg write rate: 15.625 MB/s buffer usage: 137 hits, 3 reads, 4 dirtied WAL usage: 26 records, 4 full page images, 35755 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:05:56.727 UTC autovacuum worker[20730] LOG: automatic vacuum of table "postgres.pg_catalog.pg_shdepend": index scans: 1 pages: 0 removed, 5 remain, 5 scanned (100.00% of total), 0 eagerly scanned tuples: 170 removed, 72 remain, 0 are dead but not yet removable removable cutoff: 10068, which was 1 XIDs old when operation ended new relfrozenxid: 8345, which is 7601 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 5 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 5 pages from table (100.00% of total) had 300 dead item identifiers removed index "pg_shdepend_depender_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_shdepend_reference_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 21.701 MB/s buffer usage: 89 hits, 0 reads, 4 dirtied WAL usage: 24 records, 4 full page images, 36696 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:05:56.728 UTC client backend[20733] pg_regress/privileges LOG: connection ready: setup total=13.224 ms, fork=4.976 ms, authentication=0.394 ms 2025-07-03 22:05:56.728 UTC client backend[20729] pg_regress/privileges LOG: disconnection: session time: 0:00:00.046 user=postgres database=regression host=[local] 2025-07-03 22:05:56.737 UTC autovacuum worker[20730] LOG: automatic analyze of table "postgres.pg_catalog.pg_shdepend" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 134 hits, 0 reads, 0 dirtied WAL usage: 14 records, 0 full page images, 2328 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:05:56.770 UTC client backend[20733] pg_regress/privileges ERROR: invalid privilege type INSERT for large object 2025-07-03 22:05:56.770 UTC client backend[20733] pg_regress/privileges STATEMENT: GRANT SELECT, INSERT ON LARGE OBJECT 1001 TO PUBLIC; 2025-07-03 22:05:56.771 UTC client backend[20733] pg_regress/privileges ERROR: role "nosuchuser" does not exist 2025-07-03 22:05:56.771 UTC client backend[20733] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON LARGE OBJECT 1001 TO nosuchuser; 2025-07-03 22:05:56.771 UTC client backend[20733] pg_regress/privileges ERROR: large object 999 does not exist 2025-07-03 22:05:56.771 UTC client backend[20733] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON LARGE OBJECT 999 TO PUBLIC; 2025-07-03 22:05:56.790 UTC not initialized[20738] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.792 UTC client backend[20738] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.792 UTC client backend[20738] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.800 UTC client backend[20738] pg_regress/privileges LOG: connection ready: setup total=28.424 ms, fork=8.207 ms, authentication=0.379 ms 2025-07-03 22:05:56.800 UTC client backend[20733] pg_regress/privileges LOG: disconnection: session time: 0:00:00.080 user=postgres database=regression host=[local] 2025-07-03 22:05:56.824 UTC client backend[20738] pg_regress/privileges ERROR: large object descriptor 0 was not opened for writing 2025-07-03 22:05:56.824 UTC client backend[20738] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1001, x'40000'::int), 'abcd'); 2025-07-03 22:05:56.825 UTC client backend[20738] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.825 UTC client backend[20738] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1002, x'40000'::int), 32); 2025-07-03 22:05:56.827 UTC client backend[20738] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.827 UTC client backend[20738] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1002, x'20000'::int), 'abcd'); 2025-07-03 22:05:56.827 UTC client backend[20738] pg_regress/privileges ERROR: permission denied for large object 1003 2025-07-03 22:05:56.827 UTC client backend[20738] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1003, x'20000'::int), 'abcd'); 2025-07-03 22:05:56.828 UTC client backend[20738] pg_regress/privileges ERROR: large object 1006 does not exist 2025-07-03 22:05:56.828 UTC client backend[20738] pg_regress/privileges STATEMENT: GRANT UPDATE ON LARGE OBJECT 1006 TO regress_priv_user3; 2025-07-03 22:05:56.830 UTC client backend[20738] pg_regress/privileges ERROR: must be owner of large object 1001 2025-07-03 22:05:56.830 UTC client backend[20738] pg_regress/privileges STATEMENT: SELECT lo_unlink(1001); 2025-07-03 22:05:56.838 UTC not initialized[20744] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.840 UTC client backend[20744] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.840 UTC client backend[20744] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.843 UTC client backend[20744] pg_regress/privileges LOG: connection ready: setup total=10.426 ms, fork=5.383 ms, authentication=0.435 ms 2025-07-03 22:05:56.843 UTC client backend[20738] pg_regress/privileges LOG: disconnection: session time: 0:00:00.063 user=postgres database=regression host=[local] 2025-07-03 22:05:56.876 UTC client backend[20744] pg_regress/privileges ERROR: permission denied for large object 1003 2025-07-03 22:05:56.876 UTC client backend[20744] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1003, x'40000'::int), 32); 2025-07-03 22:05:56.876 UTC client backend[20744] pg_regress/privileges ERROR: permission denied for large object 1005 2025-07-03 22:05:56.876 UTC client backend[20744] pg_regress/privileges STATEMENT: SELECT lo_truncate(lo_open(1005, x'20000'::int), 10); 2025-07-03 22:05:56.884 UTC not initialized[20749] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.886 UTC client backend[20749] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.886 UTC client backend[20749] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.901 UTC client backend[20749] pg_regress/privileges LOG: connection ready: setup total=24.089 ms, fork=6.190 ms, authentication=0.393 ms 2025-07-03 22:05:56.901 UTC client backend[20744] pg_regress/privileges LOG: disconnection: session time: 0:00:00.063 user=postgres database=regression host=[local] 2025-07-03 22:05:56.934 UTC not initialized[20753] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.936 UTC client backend[20753] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.936 UTC client backend[20753] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.947 UTC client backend[20753] pg_regress/privileges LOG: connection ready: setup total=22.908 ms, fork=9.737 ms, authentication=0.416 ms 2025-07-03 22:05:56.947 UTC client backend[20749] pg_regress/privileges LOG: disconnection: session time: 0:00:00.063 user=postgres database=regression host=[local] 2025-07-03 22:05:56.952 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.952 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT loread(lo_open(1002, x'40000'::int), 32); 2025-07-03 22:05:56.954 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.954 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lowrite(lo_open(1002, x'20000'::int), 'abcd'); 2025-07-03 22:05:56.955 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.955 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_truncate(lo_open(1002, x'20000'::int), 10); 2025-07-03 22:05:56.957 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for large object 1002 2025-07-03 22:05:56.957 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_put(1002, 1, 'abcd'); 2025-07-03 22:05:56.957 UTC client backend[20753] pg_regress/privileges ERROR: must be owner of large object 1002 2025-07-03 22:05:56.957 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_unlink(1002); 2025-07-03 22:05:56.958 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for function lo_export 2025-07-03 22:05:56.958 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_export(1001, '/dev/null'); 2025-07-03 22:05:56.959 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for function lo_import 2025-07-03 22:05:56.959 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_import('/dev/null'); 2025-07-03 22:05:56.960 UTC client backend[20753] pg_regress/privileges ERROR: permission denied for function lo_import 2025-07-03 22:05:56.960 UTC client backend[20753] pg_regress/privileges STATEMENT: SELECT lo_import('/dev/null', 2003); 2025-07-03 22:05:56.986 UTC not initialized[20757] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:56.987 UTC client backend[20757] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:56.987 UTC client backend[20757] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:56.990 UTC client backend[20757] pg_regress/privileges LOG: connection ready: setup total=30.329 ms, fork=15.281 ms, authentication=0.465 ms 2025-07-03 22:05:56.991 UTC client backend[20753] pg_regress/privileges LOG: disconnection: session time: 0:00:00.057 user=postgres database=regression host=[local] 2025-07-03 22:05:57.003 UTC client backend[20757] pg_regress/privileges ERROR: permission denied for function lo_export 2025-07-03 22:05:57.003 UTC client backend[20757] pg_regress/privileges STATEMENT: SELECT lo_export(1001, '/dev/null'); 2025-07-03 22:05:57.033 UTC not initialized[20764] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.035 UTC client backend[20764] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.035 UTC client backend[20764] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.046 UTC client backend[20764] pg_regress/privileges LOG: connection ready: setup total=42.225 ms, fork=23.421 ms, authentication=0.472 ms 2025-07-03 22:05:57.046 UTC client backend[20757] pg_regress/privileges LOG: disconnection: session time: 0:00:00.071 user=postgres database=regression host=[local] 2025-07-03 22:05:57.052 UTC client backend[20764] pg_regress/privileges ERROR: permission denied for table pg_largeobject 2025-07-03 22:05:57.052 UTC client backend[20764] pg_regress/privileges STATEMENT: SELECT * FROM pg_largeobject LIMIT 0; 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14508 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14509 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14507 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14511 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14512 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges WARNING: PID 14522 is not a PostgreSQL backend process 2025-07-03 22:05:57.084 UTC client backend[20764] pg_regress/privileges CONTEXT: PL/pgSQL expression "pg_terminate_backend($1)" PL/pgSQL function terminate_nothrow(integer) line 3 at RETURN 2025-07-03 22:05:57.085 UTC client backend[20764] pg_regress/privileges ERROR: role "pg_database_owner" cannot have explicit members 2025-07-03 22:05:57.085 UTC client backend[20764] pg_regress/privileges STATEMENT: GRANT pg_database_owner TO regress_priv_user1; 2025-07-03 22:05:57.085 UTC client backend[20764] pg_regress/privileges ERROR: role "pg_database_owner" cannot be a member of any role 2025-07-03 22:05:57.085 UTC client backend[20764] pg_regress/privileges STATEMENT: GRANT regress_priv_user1 TO pg_database_owner; 2025-07-03 22:05:57.134 UTC client backend[20764] pg_regress/privileges ERROR: permission denied for table datdba_only 2025-07-03 22:05:57.134 UTC client backend[20764] pg_regress/privileges STATEMENT: DELETE FROM datdba_only; 2025-07-03 22:05:57.135 UTC client backend[20764] pg_regress/privileges ERROR: permission denied for table datdba_only 2025-07-03 22:05:57.135 UTC client backend[20764] pg_regress/privileges STATEMENT: INSERT INTO datdba_only DEFAULT VALUES; 2025-07-03 22:05:57.170 UTC not initialized[20779] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.171 UTC client backend[20779] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.171 UTC client backend[20779] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.174 UTC client backend[20779] pg_regress/privileges LOG: connection ready: setup total=39.406 ms, fork=34.494 ms, authentication=0.475 ms 2025-07-03 22:05:57.175 UTC client backend[20764] pg_regress/privileges LOG: disconnection: session time: 0:00:00.147 user=postgres database=regression host=[local] 2025-07-03 22:05:57.223 UTC client backend[20779] pg_regress/privileges ERROR: cannot use IN SCHEMA clause when using GRANT/REVOKE ON SCHEMAS 2025-07-03 22:05:57.223 UTC client backend[20779] pg_regress/privileges STATEMENT: ALTER DEFAULT PRIVILEGES IN SCHEMA testns GRANT USAGE ON SCHEMAS TO regress_priv_user2; 2025-07-03 22:05:57.225 UTC client backend[20779] pg_regress/privileges ERROR: unrecognized privilege type: "fake_privilege" 2025-07-03 22:05:57.225 UTC client backend[20779] pg_regress/privileges STATEMENT: SELECT makeaclitem('regress_priv_user1'::regrole, 'regress_priv_user2'::regrole, 'SELECT, fake_privilege', FALSE); 2025-07-03 22:05:57.242 UTC client backend[20779] pg_regress/privileges ERROR: cannot use IN SCHEMA clause when using GRANT/REVOKE ON LARGE OBJECTS 2025-07-03 22:05:57.242 UTC client backend[20779] pg_regress/privileges STATEMENT: ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON LARGE OBJECTS TO public; 2025-07-03 22:05:57.259 UTC not initialized[20803] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.260 UTC client backend[20803] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.260 UTC client backend[20803] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.265 UTC client backend[20803] pg_regress/privileges LOG: connection ready: setup total=22.872 ms, fork=16.293 ms, authentication=0.399 ms 2025-07-03 22:05:57.265 UTC client backend[20779] pg_regress/privileges LOG: disconnection: session time: 0:00:00.095 user=postgres database=regression host=[local] 2025-07-03 22:05:57.374 UTC not initialized[20819] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.376 UTC client backend[20819] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.376 UTC client backend[20819] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.380 UTC client backend[20819] pg_regress/privileges LOG: connection ready: setup total=25.495 ms, fork=16.690 ms, authentication=0.399 ms 2025-07-03 22:05:57.380 UTC client backend[20803] pg_regress/privileges LOG: disconnection: session time: 0:00:00.121 user=postgres database=regression host=[local] 2025-07-03 22:05:57.456 UTC not initialized[20837] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.458 UTC client backend[20837] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.458 UTC client backend[20837] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.461 UTC client backend[20837] pg_regress/privileges LOG: connection ready: setup total=6.860 ms, fork=1.682 ms, authentication=0.457 ms 2025-07-03 22:05:57.461 UTC client backend[20819] pg_regress/privileges LOG: disconnection: session time: 0:00:00.090 user=postgres database=regression host=[local] 2025-07-03 22:05:57.484 UTC not initialized[20839] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.486 UTC client backend[20839] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.486 UTC client backend[20839] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.489 UTC client backend[20839] pg_regress/privileges LOG: connection ready: setup total=6.538 ms, fork=1.578 ms, authentication=0.399 ms 2025-07-03 22:05:57.489 UTC client backend[20837] pg_regress/privileges LOG: disconnection: session time: 0:00:00.033 user=postgres database=regression host=[local] 2025-07-03 22:05:57.504 UTC not initialized[20844] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.505 UTC client backend[20844] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.505 UTC client backend[20844] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.509 UTC client backend[20844] pg_regress/privileges LOG: connection ready: setup total=6.468 ms, fork=1.452 ms, authentication=0.437 ms 2025-07-03 22:05:57.509 UTC client backend[20839] pg_regress/privileges LOG: disconnection: session time: 0:00:00.024 user=postgres database=regression host=[local] 2025-07-03 22:05:57.688 UTC not initialized[20866] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.692 UTC client backend[20866] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.692 UTC client backend[20866] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.697 UTC client backend[20866] pg_regress/privileges LOG: connection ready: setup total=17.039 ms, fork=6.748 ms, authentication=0.394 ms 2025-07-03 22:05:57.698 UTC client backend[20844] pg_regress/privileges LOG: disconnection: session time: 0:00:00.194 user=postgres database=regression host=[local] 2025-07-03 22:05:57.734 UTC client backend[20866] pg_regress/privileges ERROR: view "atestv4" does not exist 2025-07-03 22:05:57.734 UTC client backend[20866] pg_regress/privileges STATEMENT: DROP VIEW atestv4; 2025-07-03 22:05:57.805 UTC client backend[20866] pg_regress/privileges ERROR: role "regress_priv_user8" does not exist 2025-07-03 22:05:57.805 UTC client backend[20866] pg_regress/privileges STATEMENT: DROP USER regress_priv_user8; 2025-07-03 22:05:57.811 UTC client backend[20866] pg_regress/privileges ERROR: permission denied for table lock_table 2025-07-03 22:05:57.811 UTC client backend[20866] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ROW EXCLUSIVE MODE; 2025-07-03 22:05:57.814 UTC client backend[20866] pg_regress/privileges ERROR: permission denied for table lock_table 2025-07-03 22:05:57.814 UTC client backend[20866] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ACCESS EXCLUSIVE MODE; 2025-07-03 22:05:57.824 UTC not initialized[20895] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.826 UTC client backend[20895] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.826 UTC client backend[20895] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.832 UTC client backend[20895] pg_regress/privileges LOG: connection ready: setup total=16.974 ms, fork=9.309 ms, authentication=0.473 ms 2025-07-03 22:05:57.832 UTC client backend[20866] pg_regress/privileges LOG: disconnection: session time: 0:00:00.144 user=postgres database=regression host=[local] 2025-07-03 22:05:57.855 UTC client backend[20895] pg_regress/privileges ERROR: permission denied for table lock_table 2025-07-03 22:05:57.855 UTC client backend[20895] pg_regress/privileges STATEMENT: LOCK TABLE lock_table IN ACCESS EXCLUSIVE MODE; 2025-07-03 22:05:57.865 UTC not initialized[20901] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.866 UTC client backend[20901] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.866 UTC client backend[20901] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.876 UTC client backend[20901] pg_regress/privileges LOG: connection ready: setup total=20.076 ms, fork=7.375 ms, authentication=0.400 ms 2025-07-03 22:05:57.876 UTC client backend[20895] pg_regress/privileges LOG: disconnection: session time: 0:00:00.052 user=postgres database=regression host=[local] 2025-07-03 22:05:57.888 UTC not initialized[20907] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.889 UTC client backend[20907] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.889 UTC client backend[20907] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.893 UTC client backend[20907] pg_regress/privileges LOG: connection ready: setup total=6.988 ms, fork=2.081 ms, authentication=0.494 ms 2025-07-03 22:05:57.893 UTC client backend[20901] pg_regress/privileges LOG: disconnection: session time: 0:00:00.029 user=postgres database=regression host=[local] 2025-07-03 22:05:57.922 UTC not initialized[20910] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.923 UTC client backend[20910] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.923 UTC client backend[20910] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.927 UTC client backend[20910] pg_regress/privileges LOG: connection ready: setup total=19.769 ms, fork=13.481 ms, authentication=0.406 ms 2025-07-03 22:05:57.928 UTC client backend[20907] pg_regress/privileges LOG: disconnection: session time: 0:00:00.039 user=postgres database=regression host=[local] 2025-07-03 22:05:57.943 UTC not initialized[20912] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.944 UTC client backend[20912] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.944 UTC client backend[20912] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.954 UTC client backend[20912] pg_regress/privileges LOG: connection ready: setup total=19.704 ms, fork=6.888 ms, authentication=0.404 ms 2025-07-03 22:05:57.954 UTC client backend[20910] pg_regress/privileges LOG: disconnection: session time: 0:00:00.033 user=postgres database=regression host=[local] 2025-07-03 22:05:57.980 UTC not initialized[20916] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:57.982 UTC client backend[20916] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:57.982 UTC client backend[20916] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:57.986 UTC client backend[20916] pg_regress/privileges LOG: connection ready: setup total=23.257 ms, fork=12.743 ms, authentication=0.399 ms 2025-07-03 22:05:57.986 UTC client backend[20912] pg_regress/privileges LOG: disconnection: session time: 0:00:00.044 user=postgres database=regression host=[local] 2025-07-03 22:05:58.024 UTC not initialized[20921] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:58.026 UTC client backend[20921] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:58.026 UTC client backend[20921] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/privileges 2025-07-03 22:05:58.029 UTC client backend[20921] pg_regress/privileges LOG: connection ready: setup total=28.992 ms, fork=16.049 ms, authentication=0.410 ms 2025-07-03 22:05:58.029 UTC client backend[20916] pg_regress/privileges LOG: disconnection: session time: 0:00:00.053 user=postgres database=regression host=[local] 2025-07-03 22:05:58.114 UTC client backend[20921] pg_regress/privileges ERROR: must be able to SET ROLE "regress_roleoption_donor" 2025-07-03 22:05:58.114 UTC client backend[20921] pg_regress/privileges STATEMENT: ALTER TABLE regress_roleoption.t1 OWNER TO regress_roleoption_donor; 2025-07-03 22:05:58.116 UTC client backend[20921] pg_regress/privileges ERROR: must be owner of table t4 2025-07-03 22:05:58.116 UTC client backend[20921] pg_regress/privileges STATEMENT: ALTER TABLE regress_roleoption.t4 OWNER TO regress_roleoption_protagonist; 2025-07-03 22:05:58.161 UTC client backend[20921] pg_regress/privileges WARNING: permission denied to vacuum "maintain_test", skipping it 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges WARNING: permission denied to analyze "maintain_test", skipping it 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges WARNING: permission denied to vacuum "maintain_test", skipping it 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges ERROR: permission denied for table maintain_test 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges STATEMENT: CLUSTER maintain_test USING maintain_test_a_idx; 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges ERROR: permission denied for materialized view refresh_test 2025-07-03 22:05:58.163 UTC client backend[20921] pg_regress/privileges STATEMENT: REFRESH MATERIALIZED VIEW refresh_test; 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges ERROR: permission denied for table maintain_test 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges STATEMENT: REINDEX TABLE maintain_test; 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges ERROR: permission denied for index maintain_test_a_idx 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges STATEMENT: REINDEX INDEX maintain_test_a_idx; 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges ERROR: must be owner of schema reindex_test 2025-07-03 22:05:58.164 UTC client backend[20921] pg_regress/privileges STATEMENT: REINDEX SCHEMA reindex_test; 2025-07-03 22:05:58.186 UTC client backend[20921] pg_regress/privileges ERROR: must be owner of schema reindex_test 2025-07-03 22:05:58.186 UTC client backend[20921] pg_regress/privileges STATEMENT: REINDEX SCHEMA reindex_test; 2025-07-03 22:05:58.228 UTC client backend[20921] pg_regress/privileges ERROR: permission denied for table grantor_test1 2025-07-03 22:05:58.228 UTC client backend[20921] pg_regress/privileges STATEMENT: GRANT SELECT, UPDATE ON grantor_test1 TO regress_grantor3; 2025-07-03 22:05:58.228 UTC client backend[20921] pg_regress/privileges WARNING: not all privileges were granted for "grantor_test2" 2025-07-03 22:05:58.292 UTC client backend[20921] pg_regress/privileges LOG: disconnection: session time: 0:00:00.276 user=postgres database=regression host=[local] 2025-07-03 22:05:58.649 UTC not initialized[21028] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:58.651 UTC client backend[21028] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:58.651 UTC client backend[21028] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin_multi 2025-07-03 22:05:58.654 UTC client backend[21028] pg_regress/brin_multi LOG: connection ready: setup total=13.743 ms, fork=8.888 ms, authentication=0.401 ms 2025-07-03 22:05:58.654 UTC not initialized[21029] [unknown] LOG: connection received: host=[local] 2025-07-03 22:05:58.655 UTC client backend[21029] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:05:58.656 UTC client backend[21029] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/brin_bloom 2025-07-03 22:05:58.658 UTC client backend[21029] pg_regress/brin_bloom LOG: connection ready: setup total=16.933 ms, fork=9.743 ms, authentication=0.395 ms 2025-07-03 22:05:58.709 UTC client backend[21028] pg_regress/brin_multi ERROR: value 7 out of bounds for option "values_per_range" 2025-07-03 22:05:58.709 UTC client backend[21028] pg_regress/brin_multi DETAIL: Valid values are between "8" and "256". 2025-07-03 22:05:58.709 UTC client backend[21028] pg_regress/brin_multi STATEMENT: CREATE INDEX brinidx_multi ON brintest_multi USING brin ( int8col int8_minmax_multi_ops(values_per_range = 7) ); 2025-07-03 22:05:58.715 UTC client backend[21028] pg_regress/brin_multi ERROR: value 257 out of bounds for option "values_per_range" 2025-07-03 22:05:58.715 UTC client backend[21028] pg_regress/brin_multi DETAIL: Valid values are between "8" and "256". 2025-07-03 22:05:58.715 UTC client backend[21028] pg_regress/brin_multi STATEMENT: CREATE INDEX brinidx_multi ON brintest_multi USING brin ( int8col int8_minmax_multi_ops(values_per_range = 257) ); 2025-07-03 22:05:58.769 UTC client backend[21029] pg_regress/brin_bloom ERROR: value -1.1 out of bounds for option "n_distinct_per_range" 2025-07-03 22:05:58.769 UTC client backend[21029] pg_regress/brin_bloom DETAIL: Valid values are between "-1.000000" and "2147483647.000000". 2025-07-03 22:05:58.769 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(n_distinct_per_range = -1.1) ); 2025-07-03 22:05:58.772 UTC client backend[21029] pg_regress/brin_bloom ERROR: value 0.00009 out of bounds for option "false_positive_rate" 2025-07-03 22:05:58.772 UTC client backend[21029] pg_regress/brin_bloom DETAIL: Valid values are between "0.000100" and "0.250000". 2025-07-03 22:05:58.772 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(false_positive_rate = 0.00009) ); 2025-07-03 22:05:58.775 UTC client backend[21029] pg_regress/brin_bloom ERROR: value 0.26 out of bounds for option "false_positive_rate" 2025-07-03 22:05:58.775 UTC client backend[21029] pg_regress/brin_bloom DETAIL: Valid values are between "0.000100" and "0.250000". 2025-07-03 22:05:58.775 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: CREATE INDEX brinidx_bloom ON brintest_bloom USING brin ( byteacol bytea_bloom_ops(false_positive_rate = 0.26) ); 2025-07-03 22:05:58.946 UTC client backend[21029] pg_regress/brin_bloom ERROR: "brintest_bloom" is not an index 2025-07-03 22:05:58.946 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_new_values('brintest_bloom'); 2025-07-03 22:05:58.946 UTC client backend[21029] pg_regress/brin_bloom ERROR: "tenk1_unique1" is not a BRIN index 2025-07-03 22:05:58.946 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-07-03 22:05:58.947 UTC client backend[21029] pg_regress/brin_bloom ERROR: block number out of range: -1 2025-07-03 22:05:58.947 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: SELECT brin_desummarize_range('brinidx_bloom', -1); 2025-07-03 22:05:58.954 UTC client backend[21029] pg_regress/brin_bloom ERROR: block number out of range: -1 2025-07-03 22:05:58.954 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_range('brin_summarize_bloom_idx', -1); 2025-07-03 22:05:58.955 UTC client backend[21029] pg_regress/brin_bloom ERROR: block number out of range: 4294967296 2025-07-03 22:05:58.955 UTC client backend[21029] pg_regress/brin_bloom STATEMENT: SELECT brin_summarize_range('brin_summarize_bloom_idx', 4294967296); 2025-07-03 22:05:59.093 UTC client backend[21029] pg_regress/brin_bloom LOG: disconnection: session time: 0:00:00.441 user=postgres database=regression host=[local] 2025-07-03 22:05:59.388 UTC client backend[21028] pg_regress/brin_multi ERROR: "brintest_multi" is not an index 2025-07-03 22:05:59.388 UTC client backend[21028] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_new_values('brintest_multi'); 2025-07-03 22:05:59.388 UTC client backend[21028] pg_regress/brin_multi ERROR: "tenk1_unique1" is not a BRIN index 2025-07-03 22:05:59.388 UTC client backend[21028] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_new_values('tenk1_unique1'); 2025-07-03 22:05:59.391 UTC client backend[21028] pg_regress/brin_multi ERROR: block number out of range: -1 2025-07-03 22:05:59.391 UTC client backend[21028] pg_regress/brin_multi STATEMENT: SELECT brin_desummarize_range('brinidx_multi', -1); 2025-07-03 22:06:00.108 UTC client backend[21028] pg_regress/brin_multi ERROR: block number out of range: -1 2025-07-03 22:06:00.108 UTC client backend[21028] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_range('brin_summarize_multi_idx', -1); 2025-07-03 22:06:00.108 UTC client backend[21028] pg_regress/brin_multi ERROR: block number out of range: 4294967296 2025-07-03 22:06:00.108 UTC client backend[21028] pg_regress/brin_multi STATEMENT: SELECT brin_summarize_range('brin_summarize_multi_idx', 4294967296); 2025-07-03 22:06:00.571 UTC client backend[21028] pg_regress/brin_multi LOG: disconnection: session time: 0:00:01.922 user=postgres database=regression host=[local] 2025-07-03 22:06:00.691 UTC not initialized[21270] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.693 UTC client backend[21270] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.693 UTC client backend[21270] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/alter_generic 2025-07-03 22:06:00.711 UTC client backend[21270] pg_regress/alter_generic LOG: connection ready: setup total=37.920 ms, fork=15.442 ms, authentication=0.423 ms 2025-07-03 22:06:00.728 UTC not initialized[21272] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.730 UTC client backend[21272] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.730 UTC client backend[21272] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tid 2025-07-03 22:06:00.738 UTC not initialized[21273] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.742 UTC client backend[21273] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.742 UTC client backend[21273] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc 2025-07-03 22:06:00.739 UTC not initialized[21274] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.743 UTC not initialized[21277] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.744 UTC not initialized[21276] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.744 UTC client backend[21274] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.744 UTC client backend[21274] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/async 2025-07-03 22:06:00.747 UTC not initialized[21275] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.748 UTC client backend[21277] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.748 UTC client backend[21277] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsrf 2025-07-03 22:06:00.748 UTC not initialized[21278] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.750 UTC client backend[21278] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.750 UTC client backend[21278] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/misc_functions 2025-07-03 22:06:00.751 UTC client backend[21277] pg_regress/tsrf LOG: connection ready: setup total=22.758 ms, fork=11.904 ms, authentication=0.443 ms 2025-07-03 22:06:00.751 UTC client backend[21276] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.751 UTC client backend[21276] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/dbsize 2025-07-03 22:06:00.752 UTC client backend[21275] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.752 UTC client backend[21275] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sysviews 2025-07-03 22:06:00.756 UTC client backend[21272] pg_regress/tid LOG: connection ready: setup total=47.316 ms, fork=14.534 ms, authentication=0.397 ms 2025-07-03 22:06:00.757 UTC client backend[21273] pg_regress/misc LOG: connection ready: setup total=41.584 ms, fork=21.450 ms, authentication=0.461 ms 2025-07-03 22:06:00.759 UTC not initialized[21280] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.761 UTC client backend[21280] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.761 UTC client backend[21280] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/alter_operator 2025-07-03 22:06:00.761 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-07-03 22:06:00.761 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) RENAME TO alt_func3; 2025-07-03 22:06:00.761 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-07-03 22:06:00.761 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_func1(integer) is not an aggregate 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_func1(int) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_func2(integer) already exists in schema "alt_nsp1" 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func1(int) RENAME TO alt_func2; 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:00.762 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.764 UTC client backend[21276] pg_regress/dbsize LOG: connection ready: setup total=37.520 ms, fork=13.213 ms, authentication=0.485 ms 2025-07-03 22:06:00.764 UTC client backend[21272] pg_regress/tid ERROR: invalid input syntax for type tid: "(4294967296,1)" at character 8 2025-07-03 22:06:00.764 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT '(4294967296,1)'::tid; 2025-07-03 22:06:00.764 UTC client backend[21280] pg_regress/alter_operator LOG: connection ready: setup total=26.116 ms, fork=20.164 ms, authentication=0.417 ms 2025-07-03 22:06:00.764 UTC client backend[21272] pg_regress/tid ERROR: invalid input syntax for type tid: "(1,65536)" at character 8 2025-07-03 22:06:00.764 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT '(1,65536)'::tid; 2025-07-03 22:06:00.767 UTC not initialized[21282] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.769 UTC client backend[21282] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.769 UTC client backend[21282] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tidscan 2025-07-03 22:06:00.769 UTC client backend[21275] pg_regress/sysviews LOG: connection ready: setup total=47.572 ms, fork=20.358 ms, authentication=0.387 ms 2025-07-03 22:06:00.770 UTC not initialized[21281] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.772 UTC client backend[21282] pg_regress/tidscan LOG: connection ready: setup total=19.024 ms, fork=12.528 ms, authentication=0.403 ms 2025-07-03 22:06:00.772 UTC client backend[21274] pg_regress/async LOG: connection ready: setup total=51.800 ms, fork=17.522 ms, authentication=0.419 ms 2025-07-03 22:06:00.773 UTC client backend[21278] pg_regress/misc_functions LOG: connection ready: setup total=43.762 ms, fork=9.858 ms, authentication=0.410 ms 2025-07-03 22:06:00.775 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions must appear at top level of FROM at character 34 2025-07-03 22:06:00.775 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT * FROM generate_series(1, generate_series(1, 3)); 2025-07-03 22:06:00.777 UTC not initialized[21283] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async ERROR: channel name cannot be empty 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async STATEMENT: SELECT pg_notify('','sample message1'); 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async ERROR: channel name cannot be empty 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async STATEMENT: SELECT pg_notify(NULL,'sample message1'); 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async ERROR: channel name too long 2025-07-03 22:06:00.780 UTC client backend[21274] pg_regress/async STATEMENT: SELECT pg_notify('notify_async_channel_name_too_long______________________________','sample_message1'); 2025-07-03 22:06:00.781 UTC client backend[21281] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.781 UTC client backend[21281] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_table_like 2025-07-03 22:06:00.782 UTC not initialized[21284] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.783 UTC client backend[21284] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.783 UTC client backend[21284] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.utf8 2025-07-03 22:06:00.784 UTC not initialized[21285] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.786 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "1 AB" 2025-07-03 22:06:00.786 UTC client backend[21276] pg_regress/dbsize DETAIL: Invalid size unit: "AB". 2025-07-03 22:06:00.786 UTC client backend[21276] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-07-03 22:06:00.786 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB'); 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "1 AB A" 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize DETAIL: Invalid size unit: "AB A". 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB A'); 2025-07-03 22:06:00.787 UTC not initialized[21286] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "1 AB A " 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize DETAIL: Invalid size unit: "AB A". 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-07-03 22:06:00.787 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 AB A '); 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize ERROR: bigint out of range 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('9223372036854775807.9'); 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize ERROR: bigint out of range 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1e100'); 2025-07-03 22:06:00.788 UTC client backend[21285] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.788 UTC client backend[21285] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/generated_virtual 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize ERROR: value overflows numeric format 2025-07-03 22:06:00.788 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1e1000000000000000000'); 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "1 byte" 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize DETAIL: Invalid size unit: "byte". 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('1 byte'); 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "" 2025-07-03 22:06:00.789 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes(''); 2025-07-03 22:06:00.790 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "kb" 2025-07-03 22:06:00.790 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('kb'); 2025-07-03 22:06:00.790 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: ".." 2025-07-03 22:06:00.790 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('..'); 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "-." 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-.'); 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "-.kb" 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-.kb'); 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "-. kb" 2025-07-03 22:06:00.791 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('-. kb'); 2025-07-03 22:06:00.791 UTC client backend[21285] pg_regress/generated_virtual LOG: connection ready: setup total=26.850 ms, fork=17.049 ms, authentication=0.411 ms 2025-07-03 22:06:00.793 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_agg2(integer) already exists in schema "alt_nsp1" 2025-07-03 22:06:00.793 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg1(int) RENAME TO alt_agg2; 2025-07-03 22:06:00.793 UTC client backend[21283] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.804 UTC client backend[21283] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/merge 2025-07-03 22:06:00.794 UTC not initialized[21287] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.795 UTC client backend[21286] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.807 UTC client backend[21286] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.icu.utf8 2025-07-03 22:06:00.796 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: ".+912" 2025-07-03 22:06:00.796 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('.+912'); 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "+912+ kB" 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize DETAIL: Invalid size unit: "+ kB". 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize HINT: Valid units are "bytes", "B", "kB", "MB", "GB", "TB", and "PB". 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('+912+ kB'); 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize ERROR: invalid size: "++123 kB" 2025-07-03 22:06:00.808 UTC client backend[21276] pg_regress/dbsize STATEMENT: SELECT pg_size_bytes('++123 kB'); 2025-07-03 22:06:00.809 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:00.809 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.810 UTC client backend[21287] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.810 UTC client backend[21287] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/create_role 2025-07-03 22:06:00.810 UTC client backend[21286] pg_regress/collate.icu.utf8 LOG: connection ready: setup total=44.087 ms, fork=18.644 ms, authentication=12.719 ms 2025-07-03 22:06:00.811 UTC client backend[21276] pg_regress/dbsize LOG: disconnection: session time: 0:00:00.072 user=postgres database=regression host=[local] 2025-07-03 22:06:00.812 UTC client backend[21287] pg_regress/create_role LOG: connection ready: setup total=40.060 ms, fork=14.281 ms, authentication=0.885 ms 2025-07-03 22:06:00.798 UTC client backend[21274] pg_regress/async LOG: disconnection: session time: 0:00:00.059 user=postgres database=regression host=[local] 2025-07-03 22:06:00.798 UTC not initialized[21292] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.816 UTC client backend[21292] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.816 UTC client backend[21292] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/incremental_sort 2025-07-03 22:06:00.798 UTC not initialized[21291] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.818 UTC client backend[21291] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.818 UTC client backend[21291] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tidrangescan 2025-07-03 22:06:00.819 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-07-03 22:06:00.819 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) RENAME TO alt_func4; 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_func3 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func3(int) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_func2(integer) already exists in schema "alt_nsp2" 2025-07-03 22:06:00.820 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FUNCTION alt_func2(int) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) RENAME TO alt_agg4; 2025-07-03 22:06:00.821 UTC client backend[21291] pg_regress/tidrangescan LOG: connection ready: setup total=47.045 ms, fork=23.276 ms, authentication=0.423 ms 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of function alt_agg3 2025-07-03 22:06:00.821 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg3(int) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.822 UTC client backend[21270] pg_regress/alter_generic ERROR: function alt_agg2(integer) already exists in schema "alt_nsp2" 2025-07-03 22:06:00.822 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER AGGREGATE alt_agg2(int) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.801 UTC client backend[21284] pg_regress/collate.utf8 LOG: connection ready: setup total=44.922 ms, fork=20.948 ms, authentication=0.410 ms 2025-07-03 22:06:00.802 UTC not initialized[21293] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:00.804 UTC client backend[21281] pg_regress/create_table_like LOG: connection ready: setup total=58.233 ms, fork=20.236 ms, authentication=9.950 ms 2025-07-03 22:06:00.826 UTC client backend[21293] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:00.826 UTC client backend[21293] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/without_overlaps 2025-07-03 22:06:00.827 UTC client backend[21283] pg_regress/merge LOG: connection ready: setup total=71.798 ms, fork=16.033 ms, authentication=16.354 ms 2025-07-03 22:06:00.829 UTC client backend[21292] pg_regress/incremental_sort LOG: connection ready: setup total=50.033 ms, fork=18.859 ms, authentication=0.415 ms 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create role 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may create roles with the SUPERUSER attribute. 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_superuser SUPERUSER; 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create role 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may create roles with the REPLICATION attribute. 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_replication_bypassrls REPLICATION BYPASSRLS; 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create role 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may create roles with the REPLICATION attribute. 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_replication REPLICATION; 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create role 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the BYPASSRLS attribute may create roles with the BYPASSRLS attribute. 2025-07-03 22:06:00.841 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_bypassrls BYPASSRLS; 2025-07-03 22:06:00.842 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create role 2025-07-03 22:06:00.842 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the CREATEDB attribute may create roles with the CREATEDB attribute. 2025-07-03 22:06:00.842 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_createdb CREATEDB; 2025-07-03 22:06:00.856 UTC client backend[21293] pg_regress/without_overlaps LOG: connection ready: setup total=75.713 ms, fork=20.609 ms, authentication=1.775 ms 2025-07-03 22:06:00.860 UTC client backend[21284] pg_regress/collate.utf8 ERROR: invalid locale name "C_UTF8" for builtin provider 2025-07-03 22:06:00.860 UTC client backend[21284] pg_regress/collate.utf8 STATEMENT: CREATE COLLATION regress_pg_c_utf8 ( provider = builtin, locale = 'C_UTF8'); 2025-07-03 22:06:00.864 UTC client backend[21293] pg_regress/without_overlaps ERROR: constraint using WITHOUT OVERLAPS needs at least two columns 2025-07-03 22:06:00.864 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( valid_at daterange, CONSTRAINT temporal_rng_pk PRIMARY KEY (valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:00.865 UTC client backend[21293] pg_regress/without_overlaps ERROR: column "valid_at" named in key does not exist at character 45 2025-07-03 22:06:00.865 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( id INTEGER, CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:00.865 UTC client backend[21293] pg_regress/without_overlaps ERROR: column "valid_at" in WITHOUT OVERLAPS is not a range or multirange type at character 64 2025-07-03 22:06:00.865 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng ( id int4range, valid_at TEXT, CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited SUPERUSER; 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the REPLICATION attribute may change the REPLICATION attribute. 2025-07-03 22:06:00.867 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited REPLICATION; 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the CREATEDB attribute may change the CREATEDB attribute. 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited CREATEDB; 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the BYPASSRLS attribute may change the BYPASSRLS attribute. 2025-07-03 22:06:00.868 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_limited BYPASSRLS; 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions ERROR: function num_nonnulls() does not exist at character 8 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions STATEMENT: SELECT num_nonnulls(); 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions ERROR: function num_nulls() does not exist at character 8 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2025-07-03 22:06:00.868 UTC client backend[21278] pg_regress/misc_functions STATEMENT: SELECT num_nulls(); 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: logging memory contexts of PID 21278 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 1; TopMemoryContext: 132256 total in 6 blocks; 34568 free (15 chunks); 97688 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Operator lookup cache: 24576 total in 2 blocks; 10776 free (3 chunks); 13800 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Cached function hash: 24496 total in 2 blocks; 2640 free (0 chunks); 21856 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; CFuncHash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Rendezvous variable hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; search_path processing cache: 8192 total in 1 blocks; 5616 free (2 chunks); 2576 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6912 free (0 chunks); 1280 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5120 free (0 chunks); 11264 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; smgr relation table: 32768 total in 3 blocks; 16848 free (8 chunks); 15920 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref Hash: 9280 total in 2 blocks; 704 free (0 chunks); 8576 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref: 4096 total in 3 blocks; 416 free (3 chunks); 3680 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Pending: 16384 total in 5 blocks; 7824 free (8 chunks); 8560 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7632 free (1 chunks); 560 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32528 free (0 chunks); 240 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Portal hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TopPortalContext: 8192 total in 1 blocks; 7680 free (0 chunks); 512 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; PortalContext: 1024 total in 1 blocks; 616 free (0 chunks); 408 used: 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 4; ExecutorState: 8192 total in 1 blocks; 3560 free (0 chunks); 4632 used 2025-07-03 22:06:00.885 UTC client backend[21278] pg_regress/misc_functions LOG: level: 5; printtup: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 5; ExprContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Relcache by OID: 16384 total in 2 blocks; 3528 free (2 chunks); 12856 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; CacheMemoryContext: 524288 total in 7 blocks; 46664 free (1 chunks); 477624 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; PL/pgSQL function: 32768 total in 3 blocks; 17064 free (2 chunks); 15704 used: explain_mask_costs(text,boolean,boolean,boolean,boolean) 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_depend_reference_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_depend_depender_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (1 chunks); 1456 used: pg_index_indrelid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; EventTriggerCache: 8192 total in 1 blocks; 7952 free (5 chunks); 240 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 4; EventTriggerCacheHash: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 952 free (1 chunks); 2120 used: pg_db_role_setting_databaseid_rol_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_opclass_am_name_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_foreign_data_wrapper_name_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_enum_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_class_relname_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_server_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_pubname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_statistic_relid_att_inh_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_cast_source_target_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_language_name_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_transform_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_collation_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2240 total in 2 blocks; 152 free (0 chunks); 2088 used: pg_amop_fam_strat_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_index_indexrelid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_template_tmplname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_ts_config_map_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_opclass_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_foreign_data_wrapper_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_publication_namespace_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_event_trigger_evtname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_statistic_ext_name_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_dict_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_event_trigger_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2240 total in 2 blocks; 152 free (0 chunks); 2088 used: pg_conversion_default_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 816 free (2 chunks); 2448 used: pg_operator_oprname_l_r_n_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_trigger_tgrelid_tgname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_extension_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_enum_typid_label_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_config_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_user_mapping_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_opfamily_am_name_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_table_relid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_type_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_aggregate_fnoid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_constraint_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_rewrite_rel_rulename_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_parser_prsname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_config_cfgname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_parser_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_publication_rel_prrelid_prpubid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_operator_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_namespace_nspname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_template_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_amop_opr_fam_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 768 free (1 chunks); 2304 used: pg_default_acl_role_nsp_obj_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_collation_name_enc_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_rel_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_range_rngtypid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_dict_dictname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_type_typname_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_opfamily_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_statistic_ext_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_statistic_ext_data_stxoid_inh_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_class_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_proc_proname_args_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_partitioned_table_partrelid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_range_rngmultitypid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_transform_type_lang_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_attribute_relid_attnum_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_proc_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_language_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_namespace_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 816 free (2 chunks); 2448 used: pg_amproc_fam_proc_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_server_name_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_attribute_relid_attnam_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_publication_namespace_pnnspid_pnpubid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_conversion_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_user_mapping_user_server_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_subscription_rel_srrelid_srsubid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_sequence_seqrelid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_extension_name_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_conversion_name_nsp_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_auth_members_member_role_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_subscription_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_parameter_acl_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_tablespace_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_parameter_acl_parname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_shseclabel_object_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_replication_origin_roname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_datname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_subscription_subname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_replication_origin_roiident_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_auth_members_role_member_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_oid_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_rolname_index 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; MdSmgr: 8192 total in 1 blocks; 7336 free (5 chunks); 856 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; GUCMemoryContext: 40960 total in 3 blocks; 23784 free (9 chunks); 17176 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 11552 free (6 chunks); 21216 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (4 chunks); 240 used 2025-07-03 22:06:00.886 UTC client backend[21278] pg_regress/misc_functions LOG: Grand total: 1457784 bytes in 248 blocks; 379384 free (258 chunks); 1078400 used 2025-07-03 22:06:00.894 UTC client backend[21282] pg_regress/tidscan ERROR: cursor "c" is not positioned on a row 2025-07-03 22:06:00.894 UTC client backend[21282] pg_regress/tidscan STATEMENT: EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF, BUFFERS OFF) UPDATE tidscan SET id = -id WHERE CURRENT OF c RETURNING *; 2025-07-03 22:06:00.896 UTC client backend[21270] pg_regress/alter_generic ERROR: conversion "alt_conv2" already exists in schema "alt_nsp1" 2025-07-03 22:06:00.896 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv1 RENAME TO alt_conv2; 2025-07-03 22:06:00.897 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:00.897 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.897 UTC client backend[21281] pg_regress/create_table_like ERROR: relation "nonexistent" does not exist at character 24 2025-07-03 22:06:00.897 UTC client backend[21281] pg_regress/create_table_like STATEMENT: CREATE TABLE foo (LIKE nonexistent); 2025-07-03 22:06:00.899 UTC client backend[21272] pg_regress/tid ERROR: tid (0, 1) is not valid for relation "tid_matview" 2025-07-03 22:06:00.899 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_matview'::text, '(0,1)'::tid); 2025-07-03 22:06:00.902 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-07-03 22:06:00.902 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 RENAME TO alt_conv4; 2025-07-03 22:06:00.902 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-07-03 22:06:00.902 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.903 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.903 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-07-03 22:06:00.903 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_createdb SUPERUSER; 2025-07-03 22:06:00.904 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:00.904 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may change the SUPERUSER attribute. 2025-07-03 22:06:00.904 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_createdb NOSUPERUSER; 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of conversion alt_conv3 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv3 SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic ERROR: conversion "alt_conv2" already exists in schema "alt_nsp2" 2025-07-03 22:06:00.904 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER CONVERSION alt_conv2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.915 UTC client backend[21280] pg_regress/alter_operator ERROR: function non_existent_func(internal, oid, internal, integer) does not exist 2025-07-03 22:06:00.915 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (RESTRICT = non_existent_func); 2025-07-03 22:06:00.917 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in CASE at character 34 2025-07-03 22:06:00.917 UTC client backend[21277] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-07-03 22:06:00.917 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT q1, case when q1 > 0 then generate_series(1,3) else 0 end FROM int8_tbl; 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in COALESCE at character 21 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT q1, coalesce(generate_series(1,3), 0) FROM int8_tbl; 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf ERROR: aggregate function calls cannot contain set-returning function calls at character 12 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-07-03 22:06:00.919 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT min(generate_series(1, 3)) FROM few; 2025-07-03 22:06:00.924 UTC client backend[21270] pg_regress/alter_generic ERROR: foreign-data wrapper "alt_fdw2" already exists 2025-07-03 22:06:00.924 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER FOREIGN DATA WRAPPER alt_fdw1 RENAME TO alt_fdw2; 2025-07-03 22:06:00.924 UTC client backend[21270] pg_regress/alter_generic ERROR: server "alt_fserv2" already exists 2025-07-03 22:06:00.924 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER SERVER alt_fserv1 RENAME TO alt_fserv2; 2025-07-03 22:06:00.927 UTC client backend[21277] pg_regress/tsrf ERROR: window function calls cannot contain set-returning function calls at character 12 2025-07-03 22:06:00.927 UTC client backend[21277] pg_regress/tsrf HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2025-07-03 22:06:00.927 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT min(generate_series(1, 3)) OVER() FROM few; 2025-07-03 22:06:00.930 UTC client backend[21281] pg_regress/create_table_like ERROR: column "xx" specified more than once 2025-07-03 22:06:00.930 UTC client backend[21281] pg_regress/create_table_like STATEMENT: /* Has ee entry */ CREATE TABLE inhf (LIKE inhx, LIKE inhx); 2025-07-03 22:06:00.943 UTC client backend[21280] pg_regress/alter_operator ERROR: function non_existent_func(internal, oid, internal, smallint, internal) does not exist 2025-07-03 22:06:00.943 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (JOIN = non_existent_func); 2025-07-03 22:06:00.944 UTC client backend[21280] pg_regress/alter_operator ERROR: operator attribute "Restrict" not recognized 2025-07-03 22:06:00.944 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR & (bit, bit) SET ("Restrict" = _int_contsel, "Join" = _int_contjoinsel); 2025-07-03 22:06:00.945 UTC client backend[21280] pg_regress/alter_operator ERROR: must be owner of operator === 2025-07-03 22:06:00.945 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, boolean) SET (RESTRICT = NONE); 2025-07-03 22:06:00.945 UTC client backend[21270] pg_regress/alter_generic ERROR: language "alt_lang2" already exists 2025-07-03 22:06:00.945 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang1 RENAME TO alt_lang2; 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: logging memory contexts of PID 14511 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 1; TopMemoryContext: 61608 total in 3 blocks; 5200 free (0 chunks); 56408 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; smgr relation table: 131072 total in 5 blocks; 65728 free (19 chunks); 65344 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; Checkpointer: 16384 total in 2 blocks; 16104 free (11 chunks); 280 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; MdSmgr: 32768 total in 3 blocks; 32448 free (651 chunks); 320 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; Pending ops context: 262144 total in 6 blocks; 213480 free (1698 chunks); 48664 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 3; Pending Ops Table: 524288 total in 7 blocks; 268752 free (23 chunks); 255536 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; GUCMemoryContext: 24576 total in 2 blocks; 9784 free (8 chunks); 14792 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 11552 free (6 chunks); 21216 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (4 chunks); 240 used 2025-07-03 22:06:00.951 UTC checkpointer[14511] LOG: Grand total: 1264528 bytes in 38 blocks; 643240 free (2420 chunks); 621288 used 2025-07-03 22:06:00.951 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of language alt_lang2 2025-07-03 22:06:00.951 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang2 RENAME TO alt_lang3; 2025-07-03 22:06:00.952 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of language alt_lang2 2025-07-03 22:06:00.952 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang2 OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.952 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:00.952 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER LANGUAGE alt_lang3 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.955 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "RANDOMWORD" at character 21 2025-07-03 22:06:00.955 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t RANDOMWORD USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "INSERT" at character 75 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN INSERT DEFAULT VALUES; 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "INSERT" at character 89 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED BY SOURCE THEN INSERT DEFAULT VALUES; 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "INTO" at character 86 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT INTO target DEFAULT VALUES; 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "," at character 98 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (1,1), (2,2); 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "SELECT" at character 86 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT SELECT (1, 1); 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "UPDATE" at character 79 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN UPDATE SET balance = 0; 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "UPDATE" at character 89 2025-07-03 22:06:00.956 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED BY TARGET THEN UPDATE SET balance = 0; 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge ERROR: syntax error at or near "target" at character 82 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE target SET balance = 0; 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge ERROR: name "target" specified more than once 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge DETAIL: The name is used both as MERGE target table and data source. 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target USING target ON tid = tid WHEN MATCHED THEN DO NOTHING; 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge ERROR: WITH query "foo" does not have a RETURNING clause at character 101 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge STATEMENT: WITH foo AS ( MERGE INTO target USING source ON (true) WHEN MATCHED THEN DELETE ) SELECT * FROM foo; 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge ERROR: COPY query must have a RETURNING clause 2025-07-03 22:06:00.957 UTC client backend[21283] pg_regress/merge STATEMENT: COPY ( MERGE INTO target USING source ON (true) WHEN MATCHED THEN DELETE ) TO stdout; 2025-07-03 22:06:00.963 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in UPDATE at character 27 2025-07-03 22:06:00.963 UTC client backend[21277] pg_regress/tsrf STATEMENT: UPDATE fewmore SET data = generate_series(4,9); 2025-07-03 22:06:00.965 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in RETURNING at character 41 2025-07-03 22:06:00.965 UTC client backend[21277] pg_regress/tsrf STATEMENT: INSERT INTO fewmore VALUES(1) RETURNING generate_series(1,3); 2025-07-03 22:06:00.965 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in VALUES at character 11 2025-07-03 22:06:00.965 UTC client backend[21277] pg_regress/tsrf STATEMENT: VALUES(1, generate_series(1,2)); 2025-07-03 22:06:00.968 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:00.968 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.969 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions must appear at top level of FROM at character 23 2025-07-03 22:06:00.969 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT * FROM int4mul(generate_series(1,2), 10); 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator @+@ 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @-@(int4, int4) OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator @+@ 2025-07-03 22:06:00.972 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR @+@(int4, int4) SET SCHEMA alt_nsp2; 2025-07-03 22:06:00.978 UTC client backend[21277] pg_regress/tsrf ERROR: set-returning functions are not allowed in LIMIT at character 16 2025-07-03 22:06:00.978 UTC client backend[21277] pg_regress/tsrf STATEMENT: SELECT 1 LIMIT generate_series(1,3); 2025-07-03 22:06:00.978 UTC client backend[21278] pg_regress/misc_functions LOG: logging memory contexts of PID 21278 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 1; TopMemoryContext: 132256 total in 6 blocks; 34488 free (18 chunks); 97768 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Map from relid to OID of cached composite type: 8192 total in 1 blocks; 2512 free (0 chunks); 5680 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Type information cache: 24640 total in 2 blocks; 2640 free (0 chunks); 22000 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Record information cache: 8192 total in 1 blocks; 1600 free (0 chunks); 6592 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Operator lookup cache: 24576 total in 2 blocks; 10776 free (3 chunks); 13800 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Cached function hash: 24496 total in 2 blocks; 2640 free (0 chunks); 21856 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; CFuncHash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Rendezvous variable hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; search_path processing cache: 8192 total in 1 blocks; 5424 free (8 chunks); 2768 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; RowDescriptionContext: 8192 total in 1 blocks; 6912 free (0 chunks); 1280 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; MessageContext: 16384 total in 2 blocks; 5200 free (1 chunks); 11184 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Operator class cache: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; smgr relation table: 32768 total in 3 blocks; 16848 free (8 chunks); 15920 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref Hash: 9280 total in 2 blocks; 704 free (0 chunks); 8576 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Shared Ref: 8192 total in 4 blocks; 2952 free (2 chunks); 5240 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PgStat Pending: 24576 total in 6 blocks; 9448 free (11 chunks); 15128 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TopTransactionContext: 8192 total in 1 blocks; 7760 free (1 chunks); 432 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TransactionAbortContext: 32768 total in 1 blocks; 32528 free (0 chunks); 240 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Portal hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; TopPortalContext: 8192 total in 1 blocks; 7680 free (0 chunks); 512 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; PortalContext: 1024 total in 1 blocks; 616 free (0 chunks); 408 used: 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 4; ExecutorState: 8192 total in 1 blocks; 3560 free (0 chunks); 4632 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 5; printtup: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 5; ExprContext: 8192 total in 1 blocks; 7952 free (0 chunks); 240 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Relcache by OID: 16384 total in 2 blocks; 3528 free (2 chunks); 12856 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; CacheMemoryContext: 1048576 total in 8 blocks; 494536 free (0 chunks); 554040 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_shdepend_reference_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 736 free (2 chunks); 2528 used: pg_shdepend_depender_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 928 free (1 chunks); 2144 used: pg_constraint_conrelid_contypid_conname_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (1 chunks); 1456 used: pg_statistic_ext_relid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1064 free (2 chunks); 2008 used: pg_toast_2618_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; relation rules: 40960 total in 8 blocks; 5208 free (1 chunks); 35752 used: pg_stat_activity 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; PL/pgSQL function: 32768 total in 3 blocks; 17064 free (2 chunks); 15704 used: explain_mask_costs(text,boolean,boolean,boolean,boolean) 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_depend_reference_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_depend_depender_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (1 chunks); 1456 used: pg_index_indrelid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; EventTriggerCache: 8192 total in 1 blocks; 7952 free (5 chunks); 240 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 4; EventTriggerCacheHash: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 952 free (1 chunks); 2120 used: pg_db_role_setting_databaseid_rol_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 960 free (1 chunks); 2112 used: pg_opclass_am_name_nsp_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_foreign_data_wrapper_name_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_enum_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_class_relname_nsp_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_server_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_pubname_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_statistic_relid_att_inh_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_cast_source_target_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_language_name_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_transform_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_collation_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 736 free (2 chunks); 2528 used: pg_amop_fam_strat_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_index_indexrelid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_template_tmplname_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_ts_config_map_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_opclass_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_foreign_data_wrapper_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_publication_namespace_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_event_trigger_evtname_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_statistic_ext_name_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_dict_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_event_trigger_oid_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2240 total in 2 blocks; 152 free (0 chunks); 2088 used: pg_conversion_default_index 2025-07-03 22:06:00.983 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 816 free (2 chunks); 2448 used: pg_operator_oprname_l_r_n_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_trigger_tgrelid_tgname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_extension_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_enum_typid_label_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_config_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_user_mapping_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_opfamily_am_name_nsp_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_table_relid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_type_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_aggregate_fnoid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_constraint_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1064 free (2 chunks); 2008 used: pg_rewrite_rel_rulename_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_parser_prsname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_config_cfgname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_parser_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_publication_rel_prrelid_prpubid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_operator_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_namespace_nspname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_ts_template_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 960 free (1 chunks); 2112 used: pg_amop_opr_fam_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 768 free (1 chunks); 2304 used: pg_default_acl_role_nsp_obj_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_collation_name_enc_nsp_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_publication_rel_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_range_rngtypid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_ts_dict_dictname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_type_typname_nsp_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_opfamily_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_statistic_ext_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_statistic_ext_data_stxoid_inh_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_class_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 800 free (1 chunks); 2272 used: pg_proc_proname_args_nsp_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_partitioned_table_partrelid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_range_rngmultitypid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_transform_type_lang_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 984 free (2 chunks); 2088 used: pg_attribute_relid_attnum_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_proc_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_language_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_namespace_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3264 total in 3 blocks; 736 free (2 chunks); 2528 used: pg_amproc_fam_proc_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_foreign_server_name_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_attribute_relid_attnam_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_publication_namespace_pnnspid_pnpubid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_conversion_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_user_mapping_user_server_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1192 free (2 chunks); 1880 used: pg_subscription_rel_srrelid_srsubid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_sequence_seqrelid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_extension_name_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_conversion_name_nsp_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 928 free (1 chunks); 2144 used: pg_auth_members_member_role_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_subscription_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_parameter_acl_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_tablespace_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 752 free (2 chunks); 1296 used: pg_parameter_acl_parname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1120 free (1 chunks); 1952 used: pg_shseclabel_object_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_replication_origin_roname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_datname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1224 free (3 chunks); 1848 used: pg_subscription_subname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 720 free (3 chunks); 1328 used: pg_replication_origin_roiident_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 3072 total in 2 blocks; 1088 free (2 chunks); 1984 used: pg_auth_members_role_member_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_database_oid_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; index info: 2048 total in 2 blocks; 592 free (2 chunks); 1456 used: pg_authid_rolname_index 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; LOCALLOCK hash: 8192 total in 1 blocks; 576 free (0 chunks); 7616 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; WAL record construction: 50216 total in 2 blocks; 6384 free (0 chunks); 43832 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; PrivateRefCount: 8192 total in 1 blocks; 2640 free (0 chunks); 5552 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; MdSmgr: 8192 total in 1 blocks; 7120 free (4 chunks); 1072 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; GUCMemoryContext: 40960 total in 3 blocks; 23712 free (9 chunks); 17248 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 3; GUC hash table: 32768 total in 3 blocks; 11552 free (6 chunks); 21216 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; Timezones: 104128 total in 2 blocks; 2640 free (0 chunks); 101488 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: level: 2; ErrorContext: 8192 total in 1 blocks; 7952 free (4 chunks); 240 used 2025-07-03 22:06:00.984 UTC client backend[21278] pg_regress/misc_functions LOG: Grand total: 2091896 bytes in 275 blocks; 846552 free (275 chunks); 1245344 used 2025-07-03 22:06:00.990 UTC client backend[21284] pg_regress/collate.utf8 ERROR: invalid locale name "unicode" for builtin provider 2025-07-03 22:06:00.990 UTC client backend[21284] pg_regress/collate.utf8 STATEMENT: CREATE COLLATION regress_pg_unicode_fast ( provider = builtin, locale = 'unicode'); 2025-07-03 22:06:00.995 UTC client backend[21280] pg_regress/alter_operator ERROR: operator cannot be its own negator 2025-07-03 22:06:00.995 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (NEGATOR = ===); 2025-07-03 22:06:00.996 UTC client backend[21272] pg_regress/tid ERROR: cannot open relation "tid_ind" 2025-07-03 22:06:00.996 UTC client backend[21272] pg_regress/tid DETAIL: This operation is not supported for indexes. 2025-07-03 22:06:00.996 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_ind'::text, '(0,1)'::tid); 2025-07-03 22:06:01.006 UTC client backend[21270] pg_regress/alter_generic ERROR: operator family "alt_opf2" for access method "hash" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.006 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf1 USING hash RENAME TO alt_opf2; 2025-07-03 22:06:01.007 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:01.007 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.018 UTC client backend[21272] pg_regress/tid ERROR: cannot look at latest visible tid for relation "public.tid_part" 2025-07-03 22:06:01.018 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_part'::text, '(0,1)'::tid); 2025-07-03 22:06:01.022 UTC client backend[21272] pg_regress/tid ERROR: currtid cannot handle views with no CTID 2025-07-03 22:06:01.022 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_no_ctid'::text, '(0,1)'::tid); 2025-07-03 22:06:01.022 UTC client backend[21270] pg_regress/alter_generic ERROR: operator class "alt_opc2" for access method "hash" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.022 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc1 USING hash RENAME TO alt_opc2; 2025-07-03 22:06:01.022 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:01.022 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.023 UTC client backend[21283] pg_regress/merge ERROR: cannot execute MERGE on relation "mv" 2025-07-03 22:06:01.023 UTC client backend[21283] pg_regress/merge DETAIL: This operation is not supported for materialized views. 2025-07-03 22:06:01.023 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO mv t USING source s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator ERROR: operator attribute "commutator" cannot be changed if it has already been set 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (COMMUTATOR = @=); 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator ERROR: operator attribute "negator" cannot be changed if it has already been set 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (NEGATOR = @!=); 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator ERROR: operator attribute "merges" cannot be changed if it has already been set 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (MERGES = false); 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator ERROR: operator attribute "hashes" cannot be changed if it has already been set 2025-07-03 22:06:01.028 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR === (boolean, real) SET (HASHES = false); 2025-07-03 22:06:01.029 UTC client backend[21280] pg_regress/alter_operator ERROR: commutator operator === is already the commutator of operator ==== 2025-07-03 22:06:01.029 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR @=(real, boolean) SET (COMMUTATOR = ===); 2025-07-03 22:06:01.029 UTC client backend[21280] pg_regress/alter_operator ERROR: negator operator === is already the negator of operator !==== 2025-07-03 22:06:01.029 UTC client backend[21280] pg_regress/alter_operator STATEMENT: ALTER OPERATOR @!=(boolean, real) SET (NEGATOR = ===); 2025-07-03 22:06:01.031 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "regress_role_super" 2025-07-03 22:06:01.031 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may grant roles with the SUPERUSER attribute. 2025-07-03 22:06:01.031 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_super IN ROLE regress_role_super; 2025-07-03 22:06:01.032 UTC client backend[21287] pg_regress/create_role ERROR: role "pg_database_owner" cannot have explicit members 2025-07-03 22:06:01.032 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_dbowner IN ROLE pg_database_owner; 2025-07-03 22:06:01.034 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_recursive" is a member of role "regress_nosuch_recursive" 2025-07-03 22:06:01.034 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_recursive ROLE regress_nosuch_recursive; 2025-07-03 22:06:01.035 UTC client backend[21277] pg_regress/tsrf LOG: disconnection: session time: 0:00:00.294 user=postgres database=regression host=[local] 2025-07-03 22:06:01.036 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-07-03 22:06:01.036 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash RENAME TO alt_opf4; 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator family alt_opf3 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf3 USING hash SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic ERROR: operator family "alt_opf2" for access method "hash" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.040 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf2 USING hash SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash RENAME TO alt_opc4; 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.041 UTC client backend[21272] pg_regress/tid ERROR: tid (0, 1) is not valid for relation "tid_tab" 2025-07-03 22:06:01.041 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_with_ctid'::text, '(0,1)'::tid); 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of operator class alt_opc3 2025-07-03 22:06:01.041 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc3 USING hash SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.042 UTC client backend[21270] pg_regress/alter_generic ERROR: operator class "alt_opc2" for access method "hash" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.042 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR CLASS alt_opc2 USING hash SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.044 UTC client backend[21283] pg_regress/merge ERROR: permission denied for table target 2025-07-03 22:06:01.044 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target USING (SELECT 1) ON true WHEN MATCHED THEN DO NOTHING; 2025-07-03 22:06:01.045 UTC client backend[21283] pg_regress/merge ERROR: permission denied for table source2 2025-07-03 22:06:01.045 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target USING source2 ON target.tid = source2.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-07-03 22:06:01.046 UTC client backend[21283] pg_regress/merge ERROR: permission denied for table target 2025-07-03 22:06:01.046 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target USING source2 ON target.tid = source2.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-07-03 22:06:01.047 UTC client backend[21283] pg_regress/merge ERROR: permission denied for table target2 2025-07-03 22:06:01.047 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target2 USING source ON target2.tid = source.sid WHEN MATCHED THEN DELETE; 2025-07-03 22:06:01.048 UTC client backend[21283] pg_regress/merge ERROR: permission denied for table target2 2025-07-03 22:06:01.048 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target2 USING source ON target2.tid = source.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-07-03 22:06:01.049 UTC client backend[21283] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 55 2025-07-03 22:06:01.049 UTC client backend[21283] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-07-03 22:06:01.049 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING (SELECT * FROM source WHERE t.tid > sid) s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT DEFAULT VALUES; 2025-07-03 22:06:01.065 UTC client backend[21278] pg_regress/misc_functions ERROR: could not open file "does not exist" for reading: No such file or directory 2025-07-03 22:06:01.065 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist'); 2025-07-03 22:06:01.066 UTC client backend[21278] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-07-03 22:06:01.066 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist', 0, -1); 2025-07-03 22:06:01.066 UTC client backend[21278] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-07-03 22:06:01.066 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_file('does not exist', 0, -1, true); 2025-07-03 22:06:01.068 UTC client backend[21278] pg_regress/misc_functions ERROR: could not open file "does not exist" for reading: No such file or directory 2025-07-03 22:06:01.068 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist'); 2025-07-03 22:06:01.068 UTC client backend[21278] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-07-03 22:06:01.068 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist', 0, -1); 2025-07-03 22:06:01.069 UTC client backend[21281] pg_regress/create_table_like ERROR: new row for relation "inhg" violates check constraint "foo" 2025-07-03 22:06:01.069 UTC client backend[21281] pg_regress/create_table_like DETAIL: Failing row contains (x, foo, y). 2025-07-03 22:06:01.069 UTC client backend[21281] pg_regress/create_table_like STATEMENT: /* Succeeds -- Unique constraints not copied */ INSERT INTO inhg VALUES ('x', 'foo', 'y'); 2025-07-03 22:06:01.069 UTC client backend[21278] pg_regress/misc_functions ERROR: requested length cannot be negative 2025-07-03 22:06:01.069 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_read_binary_file('does not exist', 0, -1, true); 2025-07-03 22:06:01.072 UTC client backend[21278] pg_regress/misc_functions ERROR: could not open directory "does not exist": No such file or directory 2025-07-03 22:06:01.072 UTC client backend[21278] pg_regress/misc_functions STATEMENT: select pg_ls_dir('does not exist', false, false); 2025-07-03 22:06:01.083 UTC client backend[21284] pg_regress/collate.utf8 LOG: disconnection: session time: 0:00:00.305 user=postgres database=regression host=[local] 2025-07-03 22:06:01.088 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_admin_recursive" is a member of role "regress_nosuch_admin_recursive" 2025-07-03 22:06:01.088 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_nosuch_admin_recursive ADMIN regress_nosuch_admin_recursive; 2025-07-03 22:06:01.088 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to create database 2025-07-03 22:06:01.088 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE DATABASE regress_nosuch_db; 2025-07-03 22:06:01.113 UTC client backend[21272] pg_regress/tid ERROR: ctid isn't of type TID 2025-07-03 22:06:01.113 UTC client backend[21272] pg_regress/tid STATEMENT: SELECT currtid2('tid_view_fake_ctid'::text, '(0,1)'::tid); 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role ERROR: permission denied 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role DETAIL: The current user must have the ADMIN option on role "regress_role_normal". 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role STATEMENT: COMMENT ON ROLE regress_role_normal IS 'some comment'; 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to rename role 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_role_normal" may rename this role. 2025-07-03 22:06:01.113 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_normal RENAME TO regress_role_abnormal; 2025-07-03 22:06:01.114 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to alter role 2025-07-03 22:06:01.114 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_role_normal" may alter this role. 2025-07-03 22:06:01.114 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER ROLE regress_role_normal NOINHERIT NOLOGIN CONNECTION LIMIT 7; 2025-07-03 22:06:01.115 UTC client backend[21270] pg_regress/alter_generic ERROR: access method "invalid_index_method" does not exist 2025-07-03 22:06:01.115 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING invalid_index_method ADD OPERATOR 1 < (int4, int2); 2025-07-03 22:06:01.115 UTC client backend[21270] pg_regress/alter_generic ERROR: invalid operator number 6, must be between 1 and 5 2025-07-03 22:06:01.115 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 6 < (int4, int2); 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic ERROR: invalid operator number 0, must be between 1 and 5 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 0 < (int4, int2); 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic ERROR: operator argument types must be specified in ALTER OPERATOR FAMILY 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD OPERATOR 1 < ; 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic ERROR: invalid function number 0, must be between 1 and 6 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD FUNCTION 0 btint42cmp(int4, int2); 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic ERROR: invalid function number 7, must be between 1 and 6 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD FUNCTION 7 btint42cmp(int4, int2); 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic ERROR: STORAGE cannot be specified in ALTER OPERATOR FAMILY 2025-07-03 22:06:01.117 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf4 USING btree ADD STORAGE invalid_storage; 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic ERROR: must be superuser to alter an operator family 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf5 USING btree ADD OPERATOR 1 < (int4, int2), FUNCTION 1 btint42cmp(int4, int2); 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic STATEMENT: RESET ROLE; 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.123 UTC client backend[21270] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf5 USING btree; 2025-07-03 22:06:01.127 UTC client backend[21272] pg_regress/tid LOG: disconnection: session time: 0:00:00.404 user=postgres database=regression host=[local] 2025-07-03 22:06:01.128 UTC client backend[21280] pg_regress/alter_operator LOG: disconnection: session time: 0:00:00.369 user=postgres database=regression host=[local] 2025-07-03 22:06:01.133 UTC client backend[21270] pg_regress/alter_generic ERROR: permission denied for schema alt_nsp6 2025-07-03 22:06:01.133 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_nsp6.alt_opf6 USING btree ADD OPERATOR 1 < (int4, int2); 2025-07-03 22:06:01.139 UTC client backend[21270] pg_regress/alter_generic ERROR: one or two argument types must be specified 2025-07-03 22:06:01.139 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf7 USING btree DROP OPERATOR 1 (int4, int2, int8); 2025-07-03 22:06:01.158 UTC client backend[21270] pg_regress/alter_generic ERROR: access method "btree" does not support ordering operators 2025-07-03 22:06:01.158 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf10 USING btree ADD OPERATOR 1 < (int4, int4) FOR ORDER BY float_ops; 2025-07-03 22:06:01.172 UTC client backend[21270] pg_regress/alter_generic ERROR: ordering comparison functions must return integer 2025-07-03 22:06:01.172 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf12 USING btree ADD FUNCTION 1 fn_opf12(int4, int2); 2025-07-03 22:06:01.175 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of index tenant_idx 2025-07-03 22:06:01.175 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP INDEX tenant_idx; 2025-07-03 22:06:01.175 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of table tenant_table 2025-07-03 22:06:01.175 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER TABLE tenant_table ADD COLUMN t text; 2025-07-03 22:06:01.177 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.177 UTC client backend[21270] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf12 USING btree; 2025-07-03 22:06:01.178 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of table tenant_table 2025-07-03 22:06:01.178 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP TABLE tenant_table; 2025-07-03 22:06:01.178 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of view tenant_view 2025-07-03 22:06:01.178 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER VIEW tenant_view OWNER TO regress_role_admin; 2025-07-03 22:06:01.179 UTC client backend[21282] pg_regress/tidscan LOG: disconnection: session time: 0:00:00.413 user=postgres database=regression host=[local] 2025-07-03 22:06:01.181 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of view tenant_view 2025-07-03 22:06:01.181 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP VIEW tenant_view; 2025-07-03 22:06:01.182 UTC client backend[21287] pg_regress/create_role ERROR: must be able to SET ROLE "regress_tenant" 2025-07-03 22:06:01.182 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE SCHEMA regress_tenant_schema AUTHORIZATION regress_tenant; 2025-07-03 22:06:01.182 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to reassign objects 2025-07-03 22:06:01.182 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with privileges of role "regress_tenant" may reassign objects owned by it. 2025-07-03 22:06:01.182 UTC client backend[21287] pg_regress/create_role STATEMENT: REASSIGN OWNED BY regress_tenant TO regress_createrole; 2025-07-03 22:06:01.189 UTC client backend[21270] pg_regress/alter_generic ERROR: hash function 1 must return integer 2025-07-03 22:06:01.189 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf13 USING hash ADD FUNCTION 1 fn_opf13(int4); 2025-07-03 22:06:01.194 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.194 UTC client backend[21270] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf13 USING hash; 2025-07-03 22:06:01.195 UTC client backend[21291] pg_regress/tidrangescan LOG: disconnection: session time: 0:00:00.398 user=postgres database=regression host=[local] 2025-07-03 22:06:01.198 UTC client backend[21270] pg_regress/alter_generic ERROR: ordering comparison functions must have two arguments 2025-07-03 22:06:01.198 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf14 USING btree ADD FUNCTION 1 fn_opf14(int4); 2025-07-03 22:06:01.198 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.198 UTC client backend[21270] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf14 USING btree; 2025-07-03 22:06:01.203 UTC client backend[21270] pg_regress/alter_generic ERROR: hash function 1 must have one argument 2025-07-03 22:06:01.203 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf15 USING hash ADD FUNCTION 1 fn_opf15(int4, int2); 2025-07-03 22:06:01.204 UTC client backend[21270] pg_regress/alter_generic ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.204 UTC client backend[21270] pg_regress/alter_generic STATEMENT: DROP OPERATOR FAMILY alt_opf15 USING hash; 2025-07-03 22:06:01.207 UTC client backend[21270] pg_regress/alter_generic ERROR: associated data types must be specified for index support function 2025-07-03 22:06:01.207 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf16 USING gist ADD FUNCTION 1 btint42cmp(int4, int2); 2025-07-03 22:06:01.216 UTC client backend[21270] pg_regress/alter_generic ERROR: operator number 1 for (integer,integer) appears more than once 2025-07-03 22:06:01.216 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int4), OPERATOR 1 < (int4, int4); 2025-07-03 22:06:01.220 UTC client backend[21287] pg_regress/create_role ERROR: must be owner of table tenant2_table 2025-07-03 22:06:01.220 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER TABLE tenant2_table OWNER TO regress_createrole; 2025-07-03 22:06:01.222 UTC client backend[21270] pg_regress/alter_generic ERROR: operator 1(integer,integer) already exists in operator family "alt_opf17" 2025-07-03 22:06:01.222 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int4); 2025-07-03 22:06:01.222 UTC client backend[21270] pg_regress/alter_generic ERROR: function number 1 for (integer,smallint) appears more than once 2025-07-03 22:06:01.222 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int2) , OPERATOR 2 <= (int4, int2) , OPERATOR 3 = (int4, int2) , OPERATOR 4 >= (int4, int2) , OPERATOR 5 > (int4, int2) , FUNCTION 1 btint42cmp(int4, int2) , FUNCTION 1 btint42cmp(int4, int2); 2025-07-03 22:06:01.228 UTC client backend[21270] pg_regress/alter_generic ERROR: operator 1(integer,smallint) already exists in operator family "alt_opf17" 2025-07-03 22:06:01.228 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf17 USING btree ADD OPERATOR 1 < (int4, int2) , OPERATOR 2 <= (int4, int2) , OPERATOR 3 = (int4, int2) , OPERATOR 4 >= (int4, int2) , OPERATOR 5 > (int4, int2) , FUNCTION 1 btint42cmp(int4, int2); 2025-07-03 22:06:01.229 UTC client backend[21287] pg_regress/create_role ERROR: must be able to SET ROLE "regress_tenant2" 2025-07-03 22:06:01.229 UTC client backend[21287] pg_regress/create_role STATEMENT: ALTER TABLE tenant2_table OWNER TO regress_tenant2; 2025-07-03 22:06:01.237 UTC client backend[21283] pg_regress/merge ERROR: MERGE command cannot affect row a second time 2025-07-03 22:06:01.237 UTC client backend[21283] pg_regress/merge HINT: Ensure that not more than one source row matches any one target row. 2025-07-03 22:06:01.237 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN UPDATE SET balance = 0; 2025-07-03 22:06:01.239 UTC client backend[21283] pg_regress/merge ERROR: MERGE command cannot affect row a second time 2025-07-03 22:06:01.239 UTC client backend[21283] pg_regress/merge HINT: Ensure that not more than one source row matches any one target row. 2025-07-03 22:06:01.239 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN DELETE; 2025-07-03 22:06:01.247 UTC client backend[21270] pg_regress/alter_generic ERROR: operator 1(integer,integer) does not exist in operator family "alt_opf18" 2025-07-03 22:06:01.247 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree DROP OPERATOR 1 (int4, int4); 2025-07-03 22:06:01.249 UTC client backend[21283] pg_regress/merge ERROR: duplicate key value violates unique constraint "target_pkey" 2025-07-03 22:06:01.249 UTC client backend[21283] pg_regress/merge DETAIL: Key (tid)=(4) already exists. 2025-07-03 22:06:01.249 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (4, NULL); 2025-07-03 22:06:01.249 UTC client backend[21283] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.249 UTC client backend[21283] pg_regress/merge STATEMENT: SELECT * FROM target ORDER BY tid; 2025-07-03 22:06:01.251 UTC client backend[21270] pg_regress/alter_generic ERROR: ordering equal image functions must not be cross-type 2025-07-03 22:06:01.251 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree ADD FUNCTION 4 (int4, int2) btequalimage(oid); 2025-07-03 22:06:01.255 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_data" 2025-07-03 22:06:01.255 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_data" may grant this role. 2025-07-03 22:06:01.255 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_data IN ROLE pg_read_all_data; 2025-07-03 22:06:01.256 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_write_all_data" 2025-07-03 22:06:01.256 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_write_all_data" may grant this role. 2025-07-03 22:06:01.256 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_write_all_data IN ROLE pg_write_all_data; 2025-07-03 22:06:01.258 UTC client backend[21270] pg_regress/alter_generic ERROR: btree skip support functions must not be cross-type 2025-07-03 22:06:01.258 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree ADD FUNCTION 6 (int4, int2) btint4skipsupport(internal); 2025-07-03 22:06:01.258 UTC client backend[21270] pg_regress/alter_generic ERROR: function 2(integer,integer) does not exist in operator family "alt_opf18" 2025-07-03 22:06:01.258 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf18 USING btree DROP FUNCTION 2 (int4, int4); 2025-07-03 22:06:01.258 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_monitor" 2025-07-03 22:06:01.258 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_monitor" may grant this role. 2025-07-03 22:06:01.258 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_monitor IN ROLE pg_monitor; 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_settings" 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_settings" may grant this role. 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_settings IN ROLE pg_read_all_settings; 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_read_all_stats" 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_all_stats" may grant this role. 2025-07-03 22:06:01.259 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_all_stats IN ROLE pg_read_all_stats; 2025-07-03 22:06:01.259 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "ja_JP.eucjp-x-icu" for encoding "UTF8" does not exist at character 56 2025-07-03 22:06:01.259 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "ja_JP.eucjp-x-icu" ); 2025-07-03 22:06:01.260 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_stat_scan_tables" 2025-07-03 22:06:01.260 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_stat_scan_tables" may grant this role. 2025-07-03 22:06:01.260 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_stat_scan_tables IN ROLE pg_stat_scan_tables; 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_read_server_files" 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_read_server_files" may grant this role. 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_read_server_files IN ROLE pg_read_server_files; 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_write_server_files" 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_write_server_files" may grant this role. 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_write_server_files IN ROLE pg_write_server_files; 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_execute_server_program" 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_execute_server_program" may grant this role. 2025-07-03 22:06:01.265 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_execute_server_program IN ROLE pg_execute_server_program; 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to grant role "pg_signal_backend" 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the ADMIN option on role "pg_signal_backend" may grant this role. 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role STATEMENT: CREATE ROLE regress_signal_backend IN ROLE pg_signal_backend; 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_tenant" cannot be dropped because some objects depend on it 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role DETAIL: owner of table tenant_table owner of view tenant_view 2025-07-03 22:06:01.267 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_tenant; 2025-07-03 22:06:01.267 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "foo-x-icu" for encoding "UTF8" does not exist at character 56 2025-07-03 22:06:01.267 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "foo-x-icu" ); 2025-07-03 22:06:01.268 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 44 2025-07-03 22:06:01.268 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int COLLATE "en-x-icu", b text ); 2025-07-03 22:06:01.268 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_superuser" does not exist 2025-07-03 22:06:01.268 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_superuser; 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic ERROR: function test_opclass_options_func(internal, text[], boolean) does not exist 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 test_opclass_options_func(internal, text[], bool); 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic ERROR: invalid operator class options parsing function 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic HINT: Valid signature of operator class options parsing function is (internal) RETURNS void. 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 (int4) btint42cmp(int4, int2); 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic ERROR: left and right associated data types for operator class options parsing functions must match 2025-07-03 22:06:01.269 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER OPERATOR FAMILY alt_opf19 USING btree ADD FUNCTION 5 (int4, int2) btint42cmp(int4, int2); 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_replication_bypassrls" does not exist 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_replication_bypassrls; 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_replication" does not exist 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_replication; 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_bypassrls" does not exist 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_bypassrls; 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_super" does not exist 2025-07-03 22:06:01.270 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_super; 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_dbowner" does not exist 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_dbowner; 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_recursive" does not exist 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_recursive; 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role ERROR: role "regress_nosuch_admin_recursive" does not exist 2025-07-03 22:06:01.271 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_nosuch_admin_recursive; 2025-07-03 22:06:01.292 UTC client backend[21270] pg_regress/alter_generic ERROR: statistics object "alt_stat2" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.292 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat1 RENAME TO alt_stat2; 2025-07-03 22:06:01.293 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:01.293 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.303 UTC client backend[21283] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 109 2025-07-03 22:06:01.303 UTC client backend[21283] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-07-03 22:06:01.303 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT (tid, balance) VALUES (t.tid, s.delta); 2025-07-03 22:06:01.303 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-07-03 22:06:01.303 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 RENAME TO alt_stat4; 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of statistics object alt_stat3 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat3 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic ERROR: statistics object "alt_stat2" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.304 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER STATISTICS alt_stat2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.307 UTC client backend[21283] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 109 2025-07-03 22:06:01.307 UTC client backend[21283] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-07-03 22:06:01.307 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON (SELECT true) WHEN NOT MATCHED THEN INSERT (tid, balance) VALUES (t.tid, s.delta); 2025-07-03 22:06:01.307 UTC client backend[21283] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.307 UTC client backend[21283] pg_regress/merge STATEMENT: SELECT * FROM target ORDER BY tid; 2025-07-03 22:06:01.312 UTC client backend[21270] pg_regress/alter_generic ERROR: text search dictionary "alt_ts_dict2" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.312 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict1 RENAME TO alt_ts_dict2; 2025-07-03 22:06:01.312 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:01.312 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.314 UTC client backend[21283] pg_regress/merge ERROR: unreachable WHEN clause specified after unconditional WHEN clause 2025-07-03 22:06:01.314 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO target t USING source AS s ON t.tid = s.sid WHEN MATCHED THEN /* Terminal WHEN clause for MATCHED */ DELETE WHEN MATCHED THEN UPDATE SET balance = t.balance - s.delta; 2025-07-03 22:06:01.320 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-07-03 22:06:01.320 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 RENAME TO alt_ts_dict4; 2025-07-03 22:06:01.320 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-07-03 22:06:01.320 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.321 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:01.321 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:01.321 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search dictionary alt_ts_dict3 2025-07-03 22:06:01.321 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict3 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.325 UTC client backend[21270] pg_regress/alter_generic ERROR: text search dictionary "alt_ts_dict2" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.325 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH DICTIONARY alt_ts_dict2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.327 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to drop role 2025-07-03 22:06:01.327 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the SUPERUSER attribute may drop roles with the SUPERUSER attribute. 2025-07-03 22:06:01.327 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_role_super; 2025-07-03 22:06:01.327 UTC client backend[21287] pg_regress/create_role ERROR: current user cannot be dropped 2025-07-03 22:06:01.327 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_role_admin; 2025-07-03 22:06:01.328 UTC client backend[21287] pg_regress/create_role ERROR: permission denied to drop role 2025-07-03 22:06:01.328 UTC client backend[21287] pg_regress/create_role DETAIL: Only roles with the CREATEROLE attribute and the ADMIN option on role "regress_rolecreator" may drop this role. 2025-07-03 22:06:01.328 UTC client backend[21287] pg_regress/create_role STATEMENT: DROP ROLE regress_rolecreator; 2025-07-03 22:06:01.336 UTC client backend[21270] pg_regress/alter_generic ERROR: text search configuration "alt_ts_conf2" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.336 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf1 RENAME TO alt_ts_conf2; 2025-07-03 22:06:01.339 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user2" 2025-07-03 22:06:01.339 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.352 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-07-03 22:06:01.352 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 RENAME TO alt_ts_conf4; 2025-07-03 22:06:01.358 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-07-03 22:06:01.358 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 OWNER TO regress_alter_generic_user2; 2025-07-03 22:06:01.358 UTC client backend[21270] pg_regress/alter_generic ERROR: must be able to SET ROLE "regress_alter_generic_user3" 2025-07-03 22:06:01.358 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 OWNER TO regress_alter_generic_user3; 2025-07-03 22:06:01.359 UTC client backend[21283] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "t" at character 80 2025-07-03 22:06:01.359 UTC client backend[21283] pg_regress/merge DETAIL: There is an entry for table "t", but it cannot be referenced from this part of the query. 2025-07-03 22:06:01.359 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN NOT MATCHED AND t.balance = 100 THEN INSERT (tid) VALUES (s.sid); 2025-07-03 22:06:01.359 UTC client backend[21283] pg_regress/merge ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:01.359 UTC client backend[21283] pg_regress/merge STATEMENT: SELECT * FROM wq_target; 2025-07-03 22:06:01.361 UTC client backend[21283] pg_regress/merge ERROR: invalid reference to FROM-clause entry for table "s" at character 90 2025-07-03 22:06:01.361 UTC client backend[21283] pg_regress/merge DETAIL: There is an entry for table "s", but it cannot be referenced from this part of the query. 2025-07-03 22:06:01.361 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN NOT MATCHED BY SOURCE AND s.balance = 100 THEN DELETE; 2025-07-03 22:06:01.364 UTC client backend[21287] pg_regress/create_role LOG: disconnection: session time: 0:00:00.576 user=postgres database=regression host=[local] 2025-07-03 22:06:01.365 UTC client backend[21270] pg_regress/alter_generic ERROR: must be owner of text search configuration alt_ts_conf3 2025-07-03 22:06:01.365 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf3 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.365 UTC client backend[21270] pg_regress/alter_generic ERROR: text search configuration "alt_ts_conf2" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.365 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH CONFIGURATION alt_ts_conf2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.373 UTC client backend[21270] pg_regress/alter_generic ERROR: text search template "alt_ts_temp2" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.373 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH TEMPLATE alt_ts_temp1 RENAME TO alt_ts_temp2; 2025-07-03 22:06:01.374 UTC client backend[21270] pg_regress/alter_generic ERROR: text search template "alt_ts_temp2" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.374 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH TEMPLATE alt_ts_temp2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.374 UTC client backend[21270] pg_regress/alter_generic ERROR: text search template parameter "Init" not recognized 2025-07-03 22:06:01.374 UTC client backend[21270] pg_regress/alter_generic STATEMENT: CREATE TEXT SEARCH TEMPLATE tstemp_case ("Init" = init_function); 2025-07-03 22:06:01.388 UTC client backend[21270] pg_regress/alter_generic ERROR: text search parser "alt_ts_prs2" already exists in schema "alt_nsp1" 2025-07-03 22:06:01.388 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH PARSER alt_ts_prs1 RENAME TO alt_ts_prs2; 2025-07-03 22:06:01.392 UTC client backend[21285] pg_regress/generated_virtual ERROR: multiple generation clauses specified for column "b" of table "gtest_err_1" at character 88 2025-07-03 22:06:01.392 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_1 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL GENERATED ALWAYS AS (a * 3) VIRTUAL); 2025-07-03 22:06:01.392 UTC client backend[21270] pg_regress/alter_generic ERROR: text search parser "alt_ts_prs2" already exists in schema "alt_nsp2" 2025-07-03 22:06:01.392 UTC client backend[21270] pg_regress/alter_generic STATEMENT: ALTER TEXT SEARCH PARSER alt_ts_prs2 SET SCHEMA alt_nsp2; 2025-07-03 22:06:01.393 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression at character 74 2025-07-03 22:06:01.393 UTC client backend[21285] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:06:01.393 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (b * 2) VIRTUAL); 2025-07-03 22:06:01.395 UTC client backend[21270] pg_regress/alter_generic ERROR: text search parser parameter "Start" not recognized 2025-07-03 22:06:01.395 UTC client backend[21270] pg_regress/alter_generic STATEMENT: CREATE TEXT SEARCH PARSER tspars_case ("Start" = start_function); 2025-07-03 22:06:01.396 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression at character 117 2025-07-03 22:06:01.396 UTC client backend[21285] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:06:01.396 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL, c int GENERATED ALWAYS AS (b * 3) VIRTUAL); 2025-07-03 22:06:01.407 UTC client backend[21283] pg_regress/merge ERROR: cannot use system column "xmin" in MERGE WHEN condition at character 76 2025-07-03 22:06:01.407 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO wq_target t USING wq_source s ON t.tid = s.sid WHEN MATCHED AND t.xmin = t.xmax THEN UPDATE SET balance = t.balance + s.balance; 2025-07-03 22:06:01.420 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use whole-row variable in column generation expression at character 88 2025-07-03 22:06:01.420 UTC client backend[21285] pg_regress/generated_virtual DETAIL: This would cause the generated column to depend on its own value. 2025-07-03 22:06:01.420 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_2c (a int PRIMARY KEY, b int GENERATED ALWAYS AS (num_nulls(gtest_err_2c)) VIRTUAL); 2025-07-03 22:06:01.423 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "c" does not exist at character 73 2025-07-03 22:06:01.423 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_3 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (c * 2) VIRTUAL); 2025-07-03 22:06:01.434 UTC client backend[21285] pg_regress/generated_virtual ERROR: generation expression is not immutable 2025-07-03 22:06:01.434 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) VIRTUAL); 2025-07-03 22:06:01.463 UTC client backend[21278] pg_regress/misc_functions ERROR: step size cannot equal zero 2025-07-03 22:06:01.463 UTC client backend[21278] pg_regress/misc_functions STATEMENT: SELECT * FROM generate_series(TIMESTAMPTZ '2024-02-01', TIMESTAMPTZ '2024-03-01', INTERVAL '0 day') g(s); 2025-07-03 22:06:01.466 UTC client backend[21285] pg_regress/generated_virtual ERROR: both default and generation expression specified for column "b" of table "gtest_err_5a" at character 63 2025-07-03 22:06:01.466 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_5a (a int PRIMARY KEY, b int DEFAULT 5 GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-07-03 22:06:01.467 UTC client backend[21285] pg_regress/generated_virtual ERROR: both identity and generation expression specified for column "b" of table "gtest_err_5b" at character 82 2025-07-03 22:06:01.467 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_5b (a int PRIMARY KEY, b int GENERATED ALWAYS AS identity GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-07-03 22:06:01.475 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use system column "xmin" in column generation expression at character 75 2025-07-03 22:06:01.475 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_6a (a int PRIMARY KEY, b bool GENERATED ALWAYS AS (xmin <> 37) VIRTUAL); 2025-07-03 22:06:01.477 UTC client backend[21285] pg_regress/generated_virtual ERROR: aggregate functions are not allowed in column generation expressions at character 74 2025-07-03 22:06:01.477 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (avg(a)) VIRTUAL); 2025-07-03 22:06:01.480 UTC client backend[21285] pg_regress/generated_virtual ERROR: window functions are not allowed in column generation expressions at character 74 2025-07-03 22:06:01.480 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (row_number() OVER (ORDER BY a)) VIRTUAL); 2025-07-03 22:06:01.490 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use subquery in column generation expression at character 74 2025-07-03 22:06:01.490 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7c (a int PRIMARY KEY, b int GENERATED ALWAYS AS ((SELECT a)) VIRTUAL); 2025-07-03 22:06:01.492 UTC client backend[21275] pg_regress/sysviews LOG: disconnection: session time: 0:00:00.750 user=postgres database=regression host=[local] 2025-07-03 22:06:01.493 UTC client backend[21285] pg_regress/generated_virtual ERROR: set-returning functions are not allowed in column generation expressions at character 74 2025-07-03 22:06:01.493 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_7d (a int PRIMARY KEY, b int GENERATED ALWAYS AS (generate_series(1, a)) VIRTUAL); 2025-07-03 22:06:01.493 UTC client backend[21285] pg_regress/generated_virtual ERROR: for a generated column, GENERATED ALWAYS must be specified at character 62 2025-07-03 22:06:01.493 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_err_8 (a int PRIMARY KEY, b int GENERATED BY DEFAULT AS (a * 2) VIRTUAL); 2025-07-03 22:06:01.494 UTC client backend[21270] pg_regress/alter_generic LOG: disconnection: session time: 0:00:00.806 user=postgres database=regression host=[local] 2025-07-03 22:06:01.498 UTC client backend[21278] pg_regress/misc_functions ERROR: invalid WAL file name "invalid" 2025-07-03 22:06:01.498 UTC client backend[21278] pg_regress/misc_functions STATEMENT: SELECT * FROM pg_split_walfile_name('invalid'); 2025-07-03 22:06:01.501 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.501 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.501 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33); 2025-07-03 22:06:01.507 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.507 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.507 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, 44); 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, DEFAULT), (4, 44); 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.508 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1 VALUES (3, 33), (4, DEFAULT); 2025-07-03 22:06:01.515 UTC client backend[21281] pg_regress/create_table_like ERROR: null value in column "a" of relation "test_like_id_2" violates not-null constraint 2025-07-03 22:06:01.515 UTC client backend[21281] pg_regress/create_table_like DETAIL: Failing row contains (null, b2). 2025-07-03 22:06:01.515 UTC client backend[21281] pg_regress/create_table_like STATEMENT: INSERT INTO test_like_id_2 (b) VALUES ('b2'); 2025-07-03 22:06:01.530 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" can only be updated to DEFAULT 2025-07-03 22:06:01.530 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.530 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: UPDATE gtest1 SET b = 11 WHERE a = 1; 2025-07-03 22:06:01.533 UTC client backend[21285] pg_regress/generated_virtual ERROR: integer out of range 2025-07-03 22:06:01.533 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: SELECT * FROM gtest1; 2025-07-03 22:06:01.540 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation mismatch between explicit collations "C" and "en-x-icu" at character 58 2025-07-03 22:06:01.540 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "en-x-icu"; 2025-07-03 22:06:01.545 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 31 2025-07-03 22:06:01.545 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE DOMAIN testdomain_i AS int COLLATE "sv-x-icu"; 2025-07-03 22:06:01.605 UTC client backend[21278] pg_regress/misc_functions ERROR: replication origin name is too long 2025-07-03 22:06:01.605 UTC client backend[21278] pg_regress/misc_functions DETAIL: Replication origin names must be no longer than 512 bytes. 2025-07-03 22:06:01.605 UTC client backend[21278] pg_regress/misc_functions STATEMENT: SELECT pg_replication_origin_create('regress_' || repeat('a', 505)); 2025-07-03 22:06:01.610 UTC client backend[21278] pg_regress/misc_functions LOG: disconnection: session time: 0:00:00.871 user=postgres database=regression host=[local] 2025-07-03 22:06:01.676 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.676 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.676 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (4, 8); 2025-07-03 22:06:01.677 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.677 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.677 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, 77); 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, DEFAULT), (7, 77); 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.678 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (6, 66), (7, DEFAULT); 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT); 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:01.681 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest1v VALUES (8, DEFAULT), (9, DEFAULT); 2025-07-03 22:06:01.702 UTC client backend[21283] pg_regress/merge ERROR: column reference "balance" is ambiguous at character 99 2025-07-03 22:06:01.702 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO sq_target USING v ON tid = sid WHEN MATCHED AND tid >= 2 THEN UPDATE SET balance = balance + delta WHEN NOT MATCHED THEN INSERT (balance, tid) VALUES (balance + delta, sid) WHEN MATCHED AND tid < 2 THEN DELETE; 2025-07-03 22:06:01.705 UTC client backend[21292] pg_regress/incremental_sort LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp21292.0.fileset/0.0", size 204800 2025-07-03 22:06:01.705 UTC client backend[21292] pg_regress/incremental_sort STATEMENT: create index on t (a); 2025-07-03 22:06:01.738 UTC client backend[21283] pg_regress/merge ERROR: MERGE_ACTION() can only be used in the RETURNING list of a MERGE command at character 8 2025-07-03 22:06:01.738 UTC client backend[21283] pg_regress/merge STATEMENT: SELECT merge_action() FROM sq_target; 2025-07-03 22:06:01.739 UTC client backend[21283] pg_regress/merge ERROR: MERGE_ACTION() can only be used in the RETURNING list of a MERGE command at character 54 2025-07-03 22:06:01.739 UTC client backend[21283] pg_regress/merge STATEMENT: UPDATE sq_target SET balance = balance + 1 RETURNING merge_action(); 2025-07-03 22:06:01.771 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:01.771 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:01.771 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:01.773 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 48 2025-07-03 22:06:01.773 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:01.773 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:01.775 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 52 2025-07-03 22:06:01.775 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:01.775 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "C" at character 49 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: no collation was derived for column "b" with collatable type text 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:01.776 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3; 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: select x < y from collate_test10; 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation mismatch between implicit collations "en-x-icu" and "tr-x-icu" at character 47 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:01.777 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: select x, y from collate_test10 order by x || y; 2025-07-03 22:06:01.778 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: recursive query "foo" column 1 has collation "en-x-icu" in non-recursive term but collation "de-x-icu" overall at character 37 2025-07-03 22:06:01.778 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation of the non-recursive term. 2025-07-03 22:06:01.778 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: WITH RECURSIVE foo(x) AS (SELECT x FROM (VALUES('a' COLLATE "en-x-icu"),('b')) t(x) UNION ALL SELECT (x || 'c') COLLATE "de-x-icu" FROM foo WHERE length(x) < 10) SELECT * FROM foo; 2025-07-03 22:06:01.779 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: syntax error at or near "COLLATE" at character 26 2025-07-03 22:06:01.779 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT CAST('42' AS text COLLATE "C"); 2025-07-03 22:06:01.796 UTC client backend[21285] pg_regress/generated_virtual ERROR: child column "b" specifies generation expression 2025-07-03 22:06:01.796 UTC client backend[21285] pg_regress/generated_virtual HINT: A child table column cannot be generated unless its parent column is. 2025-07-03 22:06:01.796 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_normal_child (a int, b int GENERATED ALWAYS AS (a * 2) VIRTUAL) INHERITS (gtest_normal); 2025-07-03 22:06:01.816 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" in child table must not be a generated column 2025-07-03 22:06:01.816 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_normal_child INHERIT gtest_normal; 2025-07-03 22:06:01.819 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" inherits from generated column but specifies default 2025-07-03 22:06:01.819 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int DEFAULT 10) INHERITS (gtest1); 2025-07-03 22:06:01.820 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" inherits from generated column but specifies identity 2025-07-03 22:06:01.820 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS IDENTITY) INHERITS (gtest1); 2025-07-03 22:06:01.820 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" inherits from generated column of different kind 2025-07-03 22:06:01.820 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-07-03 22:06:01.820 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS (a * 22) STORED) INHERITS (gtest1); 2025-07-03 22:06:01.988 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" in child table must be a generated column 2025-07-03 22:06:01.988 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestxx_1 INHERIT gtest1; 2025-07-03 22:06:02.027 UTC client backend[21292] pg_regress/incremental_sort LOG: disconnection: session time: 0:00:01.229 user=postgres database=regression host=[local] 2025-07-03 22:06:02.052 UTC client backend[21285] pg_regress/generated_virtual ERROR: inherited column "b" has a generation conflict 2025-07-03 22:06:02.052 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest0, gtesty); 2025-07-03 22:06:02.075 UTC client backend[21285] pg_regress/generated_virtual ERROR: inherited column "b" has a generation conflict 2025-07-03 22:06:02.075 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-07-03 22:06:02.089 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" inherits conflicting generation expressions 2025-07-03 22:06:02.089 UTC client backend[21285] pg_regress/generated_virtual HINT: To resolve the conflict, specify a generation expression explicitly. 2025-07-03 22:06:02.089 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty); 2025-07-03 22:06:02.248 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:02.248 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:02.248 UTC client backend[21286] pg_regress/collate.icu.utf8 CONTEXT: PL/pgSQL function mylt2(text,text) line 6 at RETURN 2025-07-03 22:06:02.248 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT mylt2('a', 'B' collate "C") as fail; 2025-07-03 22:06:02.279 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer 2025-07-03 22:06:02.279 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "C"); 2025-07-03 22:06:02.280 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collations are not supported by type integer at character 54 2025-07-03 22:06:02.280 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "C")); 2025-07-03 22:06:02.287 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "test0" already exists 2025-07-03 22:06:02.287 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test0 FROM "C"; 2025-07-03 22:06:02.289 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: parameter "locale" must be specified 2025-07-03 22:06:02.289 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test3 (provider = icu, lc_collate = 'en_US.utf8'); 2025-07-03 22:06:02.292 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: ICU locale "nonsense-nowhere" has unknown language "nonsense" 2025-07-03 22:06:02.292 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: To disable ICU locale validation, set the parameter "icu_validation_level" to "disabled". 2025-07-03 22:06:02.292 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testx (provider = icu, locale = 'nonsense-nowhere'); 2025-07-03 22:06:02.303 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not convert locale name "@colStrength=primary;nonsense=yes" to language tag: U_ILLEGAL_ARGUMENT_ERROR 2025-07-03 22:06:02.303 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testx (provider = icu, locale = '@colStrength=primary;nonsense=yes'); 2025-07-03 22:06:02.307 UTC client backend[21286] pg_regress/collate.icu.utf8 WARNING: could not convert locale name "@colStrength=primary;nonsense=yes" to language tag: U_ILLEGAL_ARGUMENT_ERROR 2025-07-03 22:06:02.311 UTC client backend[21286] pg_regress/collate.icu.utf8 WARNING: ICU locale "nonsense-nowhere" has unknown language "nonsense" 2025-07-03 22:06:02.311 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: To disable ICU locale validation, set the parameter "icu_validation_level" to "disabled". 2025-07-03 22:06:02.312 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "nonsense" for encoding "UTF8" does not exist 2025-07-03 22:06:02.312 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION test4 FROM nonsense; 2025-07-03 22:06:02.314 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "test11" already exists in schema "collate_tests" 2025-07-03 22:06:02.314 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test0 RENAME TO test11; 2025-07-03 22:06:02.314 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "test1" for encoding "UTF8" does not exist 2025-07-03 22:06:02.314 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test1 RENAME TO test22; 2025-07-03 22:06:02.315 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: role "nonsense" does not exist 2025-07-03 22:06:02.315 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: ALTER COLLATION test11 OWNER TO nonsense; 2025-07-03 22:06:02.320 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: collation "test0" for encoding "UTF8" does not exist 2025-07-03 22:06:02.320 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: DROP COLLATION test0; 2025-07-03 22:06:02.338 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: cannot drop collation test0 because other objects depend on it 2025-07-03 22:06:02.338 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: column b of table collate_dep_test1 depends on collation test0 type collate_dep_dom1 depends on collation test0 column y of composite type collate_dep_test2 depends on collation test0 view collate_dep_test3 depends on collation test0 index collate_dep_test4i depends on collation test0 2025-07-03 22:06:02.338 UTC client backend[21286] pg_regress/collate.icu.utf8 HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:02.338 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: DROP COLLATION test0 RESTRICT; 2025-07-03 22:06:02.360 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-07-03 22:06:02.360 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:06:02.360 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: COPY gtest1 (a, b) TO stdout; 2025-07-03 22:06:02.362 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-07-03 22:06:02.362 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:06:02.362 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: COPY gtest1 (a, b) FROM stdin; 2025-07-03 22:06:02.372 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-07-03 22:06:02.372 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:06:02.372 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: COPY gtest3 (a, b) TO stdout; 2025-07-03 22:06:02.374 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" is a generated column 2025-07-03 22:06:02.374 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Generated columns cannot be used in COPY. 2025-07-03 22:06:02.374 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: COPY gtest3 (a, b) FROM stdin; 2025-07-03 22:06:02.432 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a user-defined type 2025-07-03 22:06:02.432 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined types are not yet supported. 2025-07-03 22:06:02.432 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest4 ( a int, b double_int GENERATED ALWAYS AS ((a * 2, a * 3)) VIRTUAL ); 2025-07-03 22:06:02.491 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot drop column b of table gtest10 because other objects depend on it 2025-07-03 22:06:02.491 UTC client backend[21285] pg_regress/generated_virtual DETAIL: column c of table gtest10 depends on column b of table gtest10 2025-07-03 22:06:02.491 UTC client backend[21285] pg_regress/generated_virtual HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:02.491 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest10 DROP COLUMN b; 2025-07-03 22:06:02.596 UTC client backend[21281] pg_regress/create_table_like ERROR: duplicate key value violates unique constraint "inhg_pkey" 2025-07-03 22:06:02.596 UTC client backend[21281] pg_regress/create_table_like DETAIL: Key (xx)=(10) already exists. 2025-07-03 22:06:02.596 UTC client backend[21281] pg_regress/create_table_like STATEMENT: INSERT INTO inhg VALUES (20, 10); 2025-07-03 22:06:02.605 UTC client backend[21281] pg_regress/create_table_like ERROR: multiple primary keys for table "inhg" are not allowed 2025-07-03 22:06:02.605 UTC client backend[21281] pg_regress/create_table_like STATEMENT: /* Multiple primary keys creation should fail */ CREATE TABLE inhg (x text, LIKE inhx INCLUDING INDEXES, PRIMARY KEY(x)); 2025-07-03 22:06:02.605 UTC client backend[21285] pg_regress/generated_virtual ERROR: generation expression uses user-defined function at character 76 2025-07-03 22:06:02.605 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined functions are not yet supported. 2025-07-03 22:06:02.605 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest12 (a int PRIMARY KEY, b int, c int GENERATED ALWAYS AS (gf1(b)) VIRTUAL); 2025-07-03 22:06:02.609 UTC client backend[21285] pg_regress/generated_virtual ERROR: permission denied for table gtest11 2025-07-03 22:06:02.609 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: SELECT a, b FROM gtest11; 2025-07-03 22:06:02.611 UTC client backend[21285] pg_regress/generated_virtual ERROR: permission denied for function gf1 2025-07-03 22:06:02.611 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: SELECT gf1(10); 2025-07-03 22:06:02.624 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not open collator for locale "und-u-kn-lower": U_ILLEGAL_ARGUMENT_ERROR 2025-07-03 22:06:02.624 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testcoll_error1 (provider = icu, locale = '@colNumeric=lower'); 2025-07-03 22:06:02.645 UTC client backend[21285] pg_regress/generated_virtual ERROR: new row for relation "gtest20" violates check constraint "gtest20_b_check" 2025-07-03 22:06:02.645 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (30, virtual). 2025-07-03 22:06:02.645 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest20 (a) VALUES (30); 2025-07-03 22:06:02.647 UTC client backend[21281] pg_regress/create_table_like ERROR: duplicate key value violates unique constraint "inhg_x_key" 2025-07-03 22:06:02.647 UTC client backend[21281] pg_regress/create_table_like DETAIL: Key (x)=(15) already exists. 2025-07-03 22:06:02.647 UTC client backend[21281] pg_regress/create_table_like STATEMENT: INSERT INTO inhg (xx, yy, x) VALUES ('foo', 10, 15); 2025-07-03 22:06:02.647 UTC client backend[21285] pg_regress/generated_virtual ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables with check constraints 2025-07-03 22:06:02.647 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest20" is a virtual generated column. 2025-07-03 22:06:02.647 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 100); 2025-07-03 22:06:02.648 UTC client backend[21285] pg_regress/generated_virtual ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables with check constraints 2025-07-03 22:06:02.648 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest20" is a virtual generated column. 2025-07-03 22:06:02.648 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 3); 2025-07-03 22:06:02.668 UTC client backend[21285] pg_regress/generated_virtual ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-07-03 22:06:02.668 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20a ADD CHECK (b < 50); 2025-07-03 22:06:02.671 UTC client backend[21285] pg_regress/generated_virtual ERROR: check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row 2025-07-03 22:06:02.671 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20a ADD COLUMN c float8 DEFAULT random() CHECK (b < 50); 2025-07-03 22:06:02.675 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not open collator for locale "und" with rules "!!wrong!!": U_INVALID_FORMAT_ERROR 2025-07-03 22:06:02.675 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE COLLATION testcoll_rulesx (provider = icu, locale = '', rules = '!!wrong!!'); 2025-07-03 22:06:02.715 UTC client backend[21283] pg_regress/merge ERROR: new row violates row-level security policy for table "pa_target" 2025-07-03 22:06:02.715 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO pa_target t USING pa_source s ON t.tid = s.sid AND t.tid IN (1,2,3,4) WHEN MATCHED THEN UPDATE SET tid = tid - 1; 2025-07-03 22:06:02.738 UTC client backend[21285] pg_regress/generated_virtual ERROR: check constraint "chk" of relation "gtest20b" is violated by some row 2025-07-03 22:06:02.738 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest20b VALIDATE CONSTRAINT chk; 2025-07-03 22:06:02.758 UTC client backend[21285] pg_regress/generated_virtual ERROR: new row for relation "gtest20c" violates check constraint "whole_row_check" 2025-07-03 22:06:02.758 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (null, virtual). 2025-07-03 22:06:02.758 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest20c VALUES (NULL); 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps ERROR: constraint using WITHOUT OVERLAPS needs at least two columns 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( valid_at daterange, CONSTRAINT temporal_rng3_uq UNIQUE (valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps ERROR: column "valid_at" named in key does not exist at character 46 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( id INTEGER, CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps ERROR: column "valid_at" in WITHOUT OVERLAPS is not a range or multirange type at character 65 2025-07-03 22:06:02.763 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_rng3 ( id int4range, valid_at TEXT, CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS) ); 2025-07-03 22:06:02.779 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21a" violates not-null constraint 2025-07-03 22:06:02.779 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-07-03 22:06:02.779 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21a (a) VALUES (0); 2025-07-03 22:06:02.800 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21ax" violates not-null constraint 2025-07-03 22:06:02.800 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-07-03 22:06:02.800 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21ax (a) VALUES (0); 2025-07-03 22:06:02.810 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "b" of relation "gtest21ax" contains null values 2025-07-03 22:06:02.810 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest21ax ALTER COLUMN b SET EXPRESSION AS (nullif(a, 1)); 2025-07-03 22:06:02.848 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21ax" violates not-null constraint 2025-07-03 22:06:02.848 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-07-03 22:06:02.848 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21ax (a) VALUES (0); 2025-07-03 22:06:02.885 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-07-03 22:06:02.885 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (0, virtual). 2025-07-03 22:06:02.885 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21b (a) VALUES (2), (0); 2025-07-03 22:06:02.886 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for operator class "text_pattern_ops" 2025-07-03 22:06:02.886 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX ON test3ci (x text_pattern_ops); 2025-07-03 22:06:02.886 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "b" of relation "gtest21b" violates not-null constraint 2025-07-03 22:06:02.886 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (null, virtual). 2025-07-03 22:06:02.886 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest21b (a) VALUES (NULL); 2025-07-03 22:06:02.921 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for ILIKE 2025-07-03 22:06:02.921 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x ILIKE 'a%'; 2025-07-03 22:06:02.922 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-07-03 22:06:02.922 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x SIMILAR TO 'a%'; 2025-07-03 22:06:02.922 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-07-03 22:06:02.922 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3ci WHERE x ~ 'a'; 2025-07-03 22:06:02.943 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: duplicate key value violates unique constraint "test1ci_x_idx" 2025-07-03 22:06:02.943 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(ABC) already exists. 2025-07-03 22:06:02.943 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: INSERT INTO test1ci VALUES ('ABC'); 2025-07-03 22:06:02.945 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not create unique index "test3ci_x_idx" 2025-07-03 22:06:02.945 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is duplicated. 2025-07-03 22:06:02.945 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE UNIQUE INDEX ON test3ci (x); 2025-07-03 22:06:02.957 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "f3" of relation "gtestnn_child" violates not-null constraint 2025-07-03 22:06:02.957 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (1, 2, virtual). 2025-07-03 22:06:02.957 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtestnn_parent VALUES (1, 2, default); 2025-07-03 22:06:02.958 UTC client backend[21285] pg_regress/generated_virtual ERROR: null value in column "f3" of relation "gtestnn_child" violates not-null constraint 2025-07-03 22:06:02.958 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Failing row contains (2, 10, virtual). 2025-07-03 22:06:02.958 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtestnn_parent VALUES (2, 10, default); 2025-07-03 22:06:02.966 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for operator class "bpchar_pattern_ops" 2025-07-03 22:06:02.966 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE INDEX ON test3bpci (x bpchar_pattern_ops); 2025-07-03 22:06:02.970 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" of relation "gtestnn_child" contains null values 2025-07-03 22:06:02.970 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ALTER COLUMN f3 SET EXPRESSION AS (nullif(f1, 2) + nullif(f2, 11)); 2025-07-03 22:06:02.972 UTC client backend[21293] pg_regress/without_overlaps ERROR: "idx_temporal3_uq" is not a unique index at character 29 2025-07-03 22:06:02.972 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-07-03 22:06:02.972 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ADD CONSTRAINT temporal3_pk PRIMARY KEY USING INDEX idx_temporal3_uq; 2025-07-03 22:06:02.977 UTC client backend[21283] pg_regress/merge ERROR: no partition of relation "pa_target" found for row 2025-07-03 22:06:02.977 UTC client backend[21283] pg_regress/merge DETAIL: Partition key of the failing row contains (tid) = (1). 2025-07-03 22:06:02.977 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO pa_target t USING pa_source s ON t.tid = s.sid WHEN NOT MATCHED THEN INSERT VALUES (s.sid); 2025-07-03 22:06:02.977 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for ILIKE 2025-07-03 22:06:02.977 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x ILIKE 'a%'; 2025-07-03 22:06:02.978 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-07-03 22:06:02.978 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x SIMILAR TO 'a%'; 2025-07-03 22:06:02.978 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: nondeterministic collations are not supported for regular expressions 2025-07-03 22:06:02.978 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT x FROM test3bpci WHERE x ~ 'a'; 2025-07-03 22:06:02.991 UTC client backend[21293] pg_regress/without_overlaps ERROR: "idx_temporal3_uq" is not a unique index at character 29 2025-07-03 22:06:02.991 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Cannot create a primary key or unique constraint using such an index. 2025-07-03 22:06:02.991 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ADD CONSTRAINT temporal3_uq UNIQUE USING INDEX idx_temporal3_uq; 2025-07-03 22:06:02.997 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "c" of relation "gtestnn_childdef" contains null values 2025-07-03 22:06:02.997 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ADD COLUMN c int NOT NULL GENERATED ALWAYS AS (nullif(f1, 14) + nullif(f2, 10)) VIRTUAL; 2025-07-03 22:06:02.998 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: duplicate key value violates unique constraint "test1bpci_x_idx" 2025-07-03 22:06:02.998 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(ABC) already exists. 2025-07-03 22:06:02.998 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: INSERT INTO test1bpci VALUES ('ABC'); 2025-07-03 22:06:02.999 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: could not create unique index "test3bpci_x_idx" 2025-07-03 22:06:02.999 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is duplicated. 2025-07-03 22:06:02.999 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE UNIQUE INDEX ON test3bpci (x); 2025-07-03 22:06:03.011 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "c" of relation "gtestnn_child" contains null values 2025-07-03 22:06:03.011 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtestnn_parent ADD COLUMN c int NOT NULL GENERATED ALWAYS AS (nullif(f1, 13) + nullif(f2, 5)) VIRTUAL; 2025-07-03 22:06:03.044 UTC client backend[21285] pg_regress/generated_virtual ERROR: unique constraints on virtual generated columns are not supported 2025-07-03 22:06:03.044 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest22a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a / 2) VIRTUAL UNIQUE); 2025-07-03 22:06:03.053 UTC client backend[21285] pg_regress/generated_virtual ERROR: primary keys on virtual generated columns are not supported 2025-07-03 22:06:03.053 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest22b (a int, b int GENERATED ALWAYS AS (a / 2) VIRTUAL, PRIMARY KEY (a, b)); 2025-07-03 22:06:03.072 UTC client backend[21293] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_rng_pk" 2025-07-03 22:06:03.072 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)) conflicts with key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)). 2025-07-03 22:06:03.072 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng ADD CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.078 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-07-03 22:06:03.078 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng ADD CONSTRAINT temporal_rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.084 UTC client backend[21285] pg_regress/generated_virtual ERROR: invalid ON UPDATE action for foreign key constraint containing generated column 2025-07-03 22:06:03.084 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x) ON UPDATE CASCADE); 2025-07-03 22:06:03.099 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng_pk" 2025-07-03 22:06:03.099 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)). 2025-07-03 22:06:03.099 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2018-01-01', '2018-01-05')); 2025-07-03 22:06:03.104 UTC client backend[21285] pg_regress/generated_virtual ERROR: invalid ON DELETE action for foreign key constraint containing generated column 2025-07-03 22:06:03.104 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23x (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x) ON DELETE SET NULL); 2025-07-03 22:06:03.108 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_rng" violates not-null constraint 2025-07-03 22:06:03.108 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains (null, [2018-01-01,2018-01-05)). 2025-07-03 22:06:03.108 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES (NULL, daterange('2018-01-01', '2018-01-05')); 2025-07-03 22:06:03.111 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_rng" violates not-null constraint 2025-07-03 22:06:03.111 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains ([3,4), null). 2025-07-03 22:06:03.111 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[3,4)', NULL); 2025-07-03 22:06:03.111 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-07-03 22:06:03.111 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[3,4)', 'empty'); 2025-07-03 22:06:03.119 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: LIKE pattern must not end with escape character 2025-07-03 22:06:03.119 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: SELECT 'foox' LIKE 'foo\' COLLATE ignore_accents; 2025-07-03 22:06:03.130 UTC client backend[21285] pg_regress/generated_virtual ERROR: foreign key constraints on virtual generated columns are not supported 2025-07-03 22:06:03.130 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23b (a int PRIMARY KEY, b int GENERATED ALWAYS AS (a * 2) VIRTUAL REFERENCES gtest23a (x)); 2025-07-03 22:06:03.132 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng_pk" 2025-07-03 22:06:03.132 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-03-05,2018-05-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-03-03,2018-04-04)). 2025-07-03 22:06:03.132 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = daterange('2018-03-05', '2018-05-05') WHERE id = '[21,22)'; 2025-07-03 22:06:03.134 UTC client backend[21285] pg_regress/generated_virtual ERROR: primary keys on virtual generated columns are not supported 2025-07-03 22:06:03.134 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23p (x int, y int GENERATED ALWAYS AS (x * 2) VIRTUAL, PRIMARY KEY (y)); 2025-07-03 22:06:03.137 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_rng" violates not-null constraint 2025-07-03 22:06:03.137 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains (null, [2018-03-05,2018-05-05)). 2025-07-03 22:06:03.137 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = NULL, valid_at = daterange('2018-03-05', '2018-05-05') WHERE id = '[21,22)'; 2025-07-03 22:06:03.143 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_rng" violates not-null constraint 2025-07-03 22:06:03.143 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains ([1,2), null). 2025-07-03 22:06:03.143 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = NULL WHERE id = '[21,22)'; 2025-07-03 22:06:03.145 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng" 2025-07-03 22:06:03.145 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[1,2)', valid_at = 'empty' WHERE id = '[21,22)'; 2025-07-03 22:06:03.152 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: foreign key constraint "test10fk_x_fkey" cannot be implemented 2025-07-03 22:06:03.152 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key columns "x" of the referencing table and "x" of the referenced table have incompatible collations: "case_insensitive" and "case_sensitive". If either collation is nondeterministic, then both collations have to be the same. 2025-07-03 22:06:03.152 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test10fk (x text COLLATE case_insensitive REFERENCES test10pk (x) ON UPDATE CASCADE ON DELETE CASCADE); 2025-07-03 22:06:03.154 UTC client backend[21285] pg_regress/generated_virtual ERROR: relation "gtest23p" does not exist 2025-07-03 22:06:03.154 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest23q (a int PRIMARY KEY, b int REFERENCES gtest23p (y)); 2025-07-03 22:06:03.157 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-07-03 22:06:03.157 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24 (a int PRIMARY KEY, b gtestdomain1 GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-07-03 22:06:03.167 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-07-03 22:06:03.167 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24r (a int PRIMARY KEY, b gtestdomain1range GENERATED ALWAYS AS (gtestdomain1range(a, a + 5)) VIRTUAL); 2025-07-03 22:06:03.175 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: foreign key constraint "test11fk_x_fkey" cannot be implemented 2025-07-03 22:06:03.175 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key columns "x" of the referencing table and "x" of the referenced table have incompatible collations: "case_sensitive" and "case_insensitive". If either collation is nondeterministic, then both collations have to be the same. 2025-07-03 22:06:03.175 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: CREATE TABLE test11fk (x text COLLATE case_sensitive REFERENCES test11pk (x) ON UPDATE CASCADE ON DELETE CASCADE); 2025-07-03 22:06:03.179 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-07-03 22:06:03.179 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest24at ADD COLUMN b gtestdomain1 GENERATED ALWAYS AS (a * 2) VIRTUAL; 2025-07-03 22:06:03.193 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-07-03 22:06:03.193 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest24ata ALTER COLUMN b TYPE gtestdomain1; 2025-07-03 22:06:03.194 UTC client backend[21293] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_rng3_uq" 2025-07-03 22:06:03.194 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)) conflicts with key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)). 2025-07-03 22:06:03.194 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng3 ADD CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.196 UTC client backend[21285] pg_regress/generated_virtual ERROR: virtual generated column "b" cannot have a domain type 2025-07-03 22:06:03.196 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24nn (a int, b gtestdomainnn GENERATED ALWAYS AS (a * 2) VIRTUAL); 2025-07-03 22:06:03.199 UTC client backend[21285] pg_regress/generated_virtual ERROR: generation expression uses user-defined type at character 85 2025-07-03 22:06:03.199 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Virtual generated columns that make use of user-defined types are not yet supported. 2025-07-03 22:06:03.199 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest24xxx (a gtestdomain1, b gtestdomain1, c int GENERATED ALWAYS AS (greatest(a, b)) VIRTUAL); 2025-07-03 22:06:03.205 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-07-03 22:06:03.205 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_rng3 ADD CONSTRAINT temporal_rng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.205 UTC client backend[21285] pg_regress/generated_virtual ERROR: generated columns are not supported on typed tables 2025-07-03 22:06:03.205 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest28 OF gtest_type (f1 WITH OPTIONS GENERATED ALWAYS AS (f2 *2) VIRTUAL); 2025-07-03 22:06:03.213 UTC client backend[21285] pg_regress/generated_virtual ERROR: child column "f3" specifies generation expression 2025-07-03 22:06:03.213 UTC client backend[21285] pg_regress/generated_virtual HINT: A child table column cannot be generated unless its parent column is. 2025-07-03 22:06:03.213 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS (f2 * 2) VIRTUAL ) FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-07-03 22:06:03.222 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" in child table must not be a generated column 2025-07-03 22:06:03.222 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child FOR VALUES FROM ('2016-07-01') TO ('2016-08-01'); 2025-07-03 22:06:03.240 UTC client backend[21283] pg_regress/merge ERROR: new row violates row-level security policy for table "measurement" 2025-07-03 22:06:03.240 UTC client backend[21283] pg_regress/merge STATEMENT: MERGE INTO measurement m USING (VALUES (1, '01-17-2007'::date)) nm(city_id, logdate) ON (m.city_id = nm.city_id and m.logdate=nm.logdate) WHEN NOT MATCHED THEN INSERT (city_id, logdate, peaktemp, unitsales) VALUES (city_id - 1, logdate, NULL, 100); 2025-07-03 22:06:03.242 UTC client backend[21281] pg_regress/create_table_like ERROR: inherited column "a" has a storage parameter conflict 2025-07-03 22:06:03.242 UTC client backend[21281] pg_regress/create_table_like DETAIL: MAIN versus EXTENDED 2025-07-03 22:06:03.242 UTC client backend[21281] pg_regress/create_table_like STATEMENT: CREATE TABLE inh_error1 () INHERITS (ctlt1, ctlt4); 2025-07-03 22:06:03.243 UTC client backend[21281] pg_regress/create_table_like ERROR: column "a" has a storage parameter conflict 2025-07-03 22:06:03.243 UTC client backend[21281] pg_regress/create_table_like DETAIL: MAIN versus EXTENDED 2025-07-03 22:06:03.243 UTC client backend[21281] pg_regress/create_table_like STATEMENT: CREATE TABLE inh_error2 (LIKE ctlt4 INCLUDING STORAGE) INHERITS (ctlt1); 2025-07-03 22:06:03.246 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng3_uq" 2025-07-03 22:06:03.246 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-01-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-01-02,2018-02-03)). 2025-07-03 22:06:03.246 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng3 (id, valid_at) VALUES ('[1,2)', daterange('2018-01-01', '2018-01-05')); 2025-07-03 22:06:03.249 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-07-03 22:06:03.249 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng3 (id, valid_at) VALUES ('[3,4)', 'empty'); 2025-07-03 22:06:03.253 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_rng3_uq" 2025-07-03 22:06:03.253 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-03-01,2018-05-05)) conflicts with existing key (id, valid_at)=([1,2), [2018-03-03,2018-04-04)). 2025-07-03 22:06:03.253 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET valid_at = daterange('2018-03-01', '2018-05-05') WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.253 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-07-03 22:06:03.253 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET valid_at = 'empty' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.256 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_rng3" 2025-07-03 22:06:03.256 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng3 SET id = NULL, valid_at = 'empty' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.280 UTC client backend[21293] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_mltrng_pk" 2025-07-03 22:06:03.280 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}) conflicts with key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}). 2025-07-03 22:06:03.280 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng ADD CONSTRAINT temporal_mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.287 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column but specifies default 2025-07-03 22:06:03.287 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 DEFAULT 42 -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.288 UTC client backend[21285] pg_regress/generated_virtual ERROR: identity columns are not supported on partitions 2025-07-03 22:06:03.288 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 WITH OPTIONS GENERATED ALWAYS AS IDENTITY -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.288 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column of different kind 2025-07-03 22:06:03.288 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-07-03 22:06:03.288 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_child3 PARTITION OF gtest_parent ( f3 GENERATED ALWAYS AS (f2 * 2) STORED -- error ) FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.291 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-07-03 22:06:03.291 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng ADD CONSTRAINT temporal_mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.293 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" in child table must be a generated column 2025-07-03 22:06:03.293 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.302 UTC client backend[21286] pg_regress/collate.icu.utf8 ERROR: update or delete on table "test12pk" violates RESTRICT setting of foreign key constraint "test12fk_b_fkey" on table "test12fk" 2025-07-03 22:06:03.302 UTC client backend[21286] pg_regress/collate.icu.utf8 DETAIL: Key (x)=(abc) is referenced from table "test12fk". 2025-07-03 22:06:03.302 UTC client backend[21286] pg_regress/collate.icu.utf8 STATEMENT: UPDATE test12pk SET x = 'ABC' WHERE x = 'abc'; 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng_pk" 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}). 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_mltrng" violates not-null constraint 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains (null, {[2018-01-01,2018-01-05)}). 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES (NULL, datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_mltrng" violates not-null constraint 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains ([3,4), null). 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[3,4)', NULL); 2025-07-03 22:06:03.317 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" in child table must be a generated column 2025-07-03 22:06:03.317 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-07-03 22:06:03.317 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[3,4)', '{}'); 2025-07-03 22:06:03.335 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng_pk" 2025-07-03 22:06:03.335 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-03-05,2018-05-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-03-03,2018-04-04)}). 2025-07-03 22:06:03.335 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = datemultirange(daterange('2018-03-05', '2018-05-05')) WHERE id = '[21,22)'; 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "id" of relation "temporal_mltrng" violates not-null constraint 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains (null, {[2018-03-05,2018-05-05)}). 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = NULL, valid_at = datemultirange(daterange('2018-03-05', '2018-05-05')) WHERE id = '[21,22)'; 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps ERROR: null value in column "valid_at" of relation "temporal_mltrng" violates not-null constraint 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Failing row contains ([1,2), null). 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = NULL WHERE id = '[21,22)'; 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng" 2025-07-03 22:06:03.336 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[1,2)', valid_at = '{}' WHERE id = '[21,22)'; 2025-07-03 22:06:03.343 UTC client backend[21285] pg_regress/generated_virtual ERROR: table "gtest_child3" being attached contains an identity column "f3" 2025-07-03 22:06:03.343 UTC client backend[21285] pg_regress/generated_virtual DETAIL: The new partition may not contain an identity column. 2025-07-03 22:06:03.343 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.365 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "f3" inherits from generated column of different kind 2025-07-03 22:06:03.365 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Parent column is VIRTUAL, child column is STORED. 2025-07-03 22:06:03.365 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01'); 2025-07-03 22:06:03.373 UTC client backend[21293] pg_regress/without_overlaps ERROR: could not create exclusion constraint "temporal_mltrng3_uq" 2025-07-03 22:06:03.373 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}) conflicts with key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}). 2025-07-03 22:06:03.373 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng3 ADD CONSTRAINT temporal_mltrng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.404 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-07-03 22:06:03.404 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_mltrng3 ADD CONSTRAINT temporal_mltrng3_uq UNIQUE (id, valid_at WITHOUT OVERLAPS); 2025-07-03 22:06:03.415 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng3_uq" 2025-07-03 22:06:03.415 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-01-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-01-02,2018-02-03)}). 2025-07-03 22:06:03.415 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2018-01-01', '2018-01-05'))); 2025-07-03 22:06:03.416 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-07-03 22:06:03.416 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[3,4)', '{}'); 2025-07-03 22:06:03.436 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "temporal_mltrng3_uq" 2025-07-03 22:06:03.436 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-03-01,2018-05-05)}) conflicts with existing key (id, valid_at)=([1,2), {[2018-03-03,2018-04-04)}). 2025-07-03 22:06:03.436 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET valid_at = datemultirange(daterange('2018-03-01', '2018-05-05')) WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.437 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-07-03 22:06:03.437 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET valid_at = '{}' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.438 UTC client backend[21293] pg_regress/without_overlaps ERROR: empty WITHOUT OVERLAPS value found in column "valid_at" in relation "temporal_mltrng3" 2025-07-03 22:06:03.438 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng3 SET id = NULL, valid_at = '{}' WHERE id = '[1,2)' AND valid_at IS NULL; 2025-07-03 22:06:03.500 UTC client backend[21293] pg_regress/without_overlaps ERROR: column "valid_at" is in a primary key 2025-07-03 22:06:03.500 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 ALTER COLUMN valid_at DROP NOT NULL; 2025-07-03 22:06:03.541 UTC client backend[21283] pg_regress/merge LOG: disconnection: session time: 0:00:02.769 user=postgres database=regression host=[local] 2025-07-03 22:06:03.590 UTC client backend[21281] pg_regress/create_table_like ERROR: cannot add NO INHERIT constraint to partitioned table "noinh_con_copy1_parted" 2025-07-03 22:06:03.590 UTC client backend[21281] pg_regress/create_table_like STATEMENT: CREATE TABLE noinh_con_copy1_parted (LIKE noinh_con_copy INCLUDING ALL) PARTITION BY LIST (a); 2025-07-03 22:06:03.613 UTC client backend[21281] pg_regress/create_table_like ERROR: relation "ctlseq1" is invalid in LIKE clause at character 27 2025-07-03 22:06:03.613 UTC client backend[21281] pg_regress/create_table_like DETAIL: This operation is not supported for sequences. 2025-07-03 22:06:03.613 UTC client backend[21281] pg_regress/create_table_like STATEMENT: CREATE TABLE ctlt10 (LIKE ctlseq1); 2025-07-03 22:06:03.940 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.940 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:03.941 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.941 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:03.942 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.942 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:03.973 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.973 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:03.978 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.978 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:03.979 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:03.979 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:03.983 UTC client backend[21273] pg_regress/misc LOG: disconnection: session time: 0:00:03.246 user=postgres database=regression host=[local] 2025-07-03 22:06:03.997 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:03.997 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:03.998 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:03.998 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:03.998 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:03.998 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_rng (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal_rng_pk DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.058 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.058 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.060 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.060 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.061 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.061 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.074 UTC client backend[21281] pg_regress/create_table_like LOG: disconnection: session time: 0:00:03.308 user=postgres database=regression host=[local] 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.096 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[1,2)', daterange('2010-01-01', '2020-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.117 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal3 (id, valid_at) VALUES ('[2,3)', daterange('2005-01-01', '2006-01-01')) ON CONFLICT ON CONSTRAINT temporal3_uq DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.173 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.173 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.177 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.177 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.177 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.177 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.215 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.215 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.216 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.216 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.216 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.216 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.238 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.238 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.238 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.238 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.239 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.239 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng_pk DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.302 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO NOTHING; 2025-07-03 22:06:04.339 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.339 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.340 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.340 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.341 UTC client backend[21293] pg_regress/without_overlaps ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification 2025-07-03 22:06:04.341 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT (id, valid_at) DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.358 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.358 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[2,3)'; 2025-07-03 22:06:04.359 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.359 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[1,2)', datemultirange(daterange('2010-01-01', '2020-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[3,4)'; 2025-07-03 22:06:04.360 UTC client backend[21293] pg_regress/without_overlaps ERROR: ON CONFLICT DO UPDATE not supported with exclusion constraints 2025-07-03 22:06:04.360 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_mltrng3 (id, valid_at) VALUES ('[2,3)', datemultirange(daterange('2005-01-01', '2006-01-01'))) ON CONFLICT ON CONSTRAINT temporal_mltrng3_uq DO UPDATE SET id = EXCLUDED.id + '[4,5)'; 2025-07-03 22:06:04.427 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-07-03 22:06:04.427 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-07-03 22:06:04.427 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE (f3); 2025-07-03 22:06:04.428 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use generated column in partition key at character 127 2025-07-03 22:06:04.428 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "f3" is a generated column. 2025-07-03 22:06:04.428 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TABLE gtest_part_key (f1 date NOT NULL, f2 bigint, f3 bigint GENERATED ALWAYS AS (f2 * 2) VIRTUAL) PARTITION BY RANGE ((f3 * 3)); 2025-07-03 22:06:04.435 UTC client backend[21293] pg_regress/without_overlaps ERROR: cannot drop column valid_at of table temporal3 because other objects depend on it 2025-07-03 22:06:04.435 UTC client backend[21293] pg_regress/without_overlaps DETAIL: constraint temporal_fk_rng2rng_fk on table temporal_fk_rng2rng depends on column valid_at of table temporal3 2025-07-03 22:06:04.435 UTC client backend[21293] pg_regress/without_overlaps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:04.435 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal3 DROP COLUMN valid_at; 2025-07-03 22:06:04.439 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot use generated column "b" in column generation expression 2025-07-03 22:06:04.439 UTC client backend[21285] pg_regress/generated_virtual DETAIL: A generated column cannot reference another generated column. 2025-07-03 22:06:04.439 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (b * 4) VIRTUAL; 2025-07-03 22:06:04.444 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "z" does not exist 2025-07-03 22:06:04.444 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (z * 4) VIRTUAL; 2025-07-03 22:06:04.499 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot alter type of a column used by a generated column 2025-07-03 22:06:04.499 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "a" is used by generated column "x". 2025-07-03 22:06:04.499 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE text; 2025-07-03 22:06:04.517 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_rng2rng_fk2" cannot be implemented 2025-07-03 22:06:04.517 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: int4range and daterange. 2025-07-03 22:06:04.517 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at int4range, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk2 PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk2 FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-07-03 22:06:04.529 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot specify USING when altering type of generated column at character 34 2025-07-03 22:06:04.529 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "x" is a generated column. 2025-07-03 22:06:04.529 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x TYPE boolean USING x <> 0; 2025-07-03 22:06:04.534 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "x" of relation "gtest27" is a generated column 2025-07-03 22:06:04.534 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN x DROP DEFAULT; 2025-07-03 22:06:04.537 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "x" of relation "gtest27" contains null values 2025-07-03 22:06:04.537 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 DROP COLUMN x, ALTER COLUMN a TYPE bigint, ALTER COLUMN b TYPE bigint, ADD COLUMN x bigint GENERATED ALWAYS AS ((a + b) * 2) VIRTUAL NOT NULL; 2025-07-03 22:06:04.582 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-07-03 22:06:04.582 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id, valid_at) ); 2025-07-03 22:06:04.585 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot alter type of a column used by a generated column 2025-07-03 22:06:04.585 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "a" is used by generated column "x". 2025-07-03 22:06:04.585 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest27 ALTER COLUMN a TYPE float8, ALTER COLUMN b TYPE float8; 2025-07-03 22:06:04.602 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key must use PERIOD when referencing a primary key using WITHOUT OVERLAPS 2025-07-03 22:06:04.602 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng (id, valid_at) ); 2025-07-03 22:06:04.624 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:04.624 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-07-03 22:06:04.632 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:04.632 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_rng ); 2025-07-03 22:06:04.636 UTC client backend[21286] pg_regress/collate.icu.utf8 LOG: disconnection: session time: 0:00:03.851 user=postgres database=regression host=[local] 2025-07-03 22:06:04.655 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-07-03 22:06:04.655 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng (id) ); 2025-07-03 22:06:04.658 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "a" of relation "gtest29" is not a generated column 2025-07-03 22:06:04.658 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a SET EXPRESSION AS (a * 3); 2025-07-03 22:06:04.658 UTC client backend[21285] pg_regress/generated_virtual ERROR: column "a" of relation "gtest29" is not a generated column 2025-07-03 22:06:04.658 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN a DROP EXPRESSION; 2025-07-03 22:06:04.665 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:04.665 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id) REFERENCES temporal_rng (id, PERIOD valid_at) ); 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION is not supported for virtual generated columns 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest29" is a virtual generated column. 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest29 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot insert a non-DEFAULT value into column "b" 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:04.685 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: INSERT INTO gtest29 (a, b) VALUES (6, 66); 2025-07-03 22:06:04.718 UTC client backend[21285] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION is not supported for virtual generated columns 2025-07-03 22:06:04.718 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" of relation "gtest30" is a virtual generated column. 2025-07-03 22:06:04.718 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:06:04.719 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:04.719 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id) REFERENCES temporal_rng ); 2025-07-03 22:06:04.732 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-07-03 22:06:04.732 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_rng2rng ( id int4range, valid_at daterange, parent_id int4range, CONSTRAINT temporal_fk_rng2rng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_rng (id, PERIOD id) ); 2025-07-03 22:06:04.791 UTC client backend[21285] pg_regress/generated_virtual ERROR: ALTER TABLE / DROP EXPRESSION must be applied to child tables too 2025-07-03 22:06:04.791 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE ONLY gtest30 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:06:04.858 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot drop generation expression from inherited column 2025-07-03 22:06:04.858 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest30_1 ALTER COLUMN b DROP EXPRESSION; 2025-07-03 22:06:04.868 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:06:04.868 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-07-03 22:06:04.905 UTC client backend[21285] pg_regress/generated_virtual ERROR: cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type 2025-07-03 22:06:04.905 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar; 2025-07-03 22:06:04.924 UTC client backend[21285] pg_regress/generated_virtual ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-07-03 22:06:04.924 UTC client backend[21285] pg_regress/generated_virtual DETAIL: Column "b" is a generated column. 2025-07-03 22:06:04.924 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TRIGGER gtest2a BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.b < 0) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-07-03 22:06:04.925 UTC client backend[21285] pg_regress/generated_virtual ERROR: BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82 2025-07-03 22:06:04.925 UTC client backend[21285] pg_regress/generated_virtual DETAIL: A whole-row reference is used and the table contains generated columns. 2025-07-03 22:06:04.925 UTC client backend[21285] pg_regress/generated_virtual STATEMENT: CREATE TRIGGER gtest2b BEFORE INSERT OR UPDATE ON gtest26 FOR EACH ROW WHEN (NEW.* IS NOT NULL) -- error EXECUTE PROCEDURE gtest_trigger_func(); 2025-07-03 22:06:04.958 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_rng2rng_fk" cannot be implemented 2025-07-03 22:06:04.958 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: tsrange and daterange. 2025-07-03 22:06:04.958 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng; 2025-07-03 22:06:04.991 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-07-03 22:06:04.991 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk2 FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_rng (id, PERIOD id); 2025-07-03 22:06:05.006 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-07-03 22:06:05.006 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-04-01)) is not present in table "temporal_rng". 2025-07-03 22:06:05.006 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng; 2025-07-03 22:06:05.014 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-07-03 22:06:05.014 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-04-01)) is not present in table "temporal_rng". 2025-07-03 22:06:05.014 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_rng2rng (id, valid_at, parent_id) VALUES ('[2,3)', daterange('2018-01-02', '2018-04-01'), '[1,2)'); 2025-07-03 22:06:05.017 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-07-03 22:06:05.017 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2018-01-02,2018-05-01)) is not present in table "temporal_rng". 2025-07-03 22:06:05.017 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_rng2rng SET valid_at = daterange('2018-01-02', '2018-05-01') WHERE id = '[1,2)'; 2025-07-03 22:06:05.018 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_rng2rng" violates foreign key constraint "temporal_fk_rng2rng_fk" 2025-07-03 22:06:05.018 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([8,9), [2018-01-02,2018-02-20)) is not present in table "temporal_rng". 2025-07-03 22:06:05.018 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_rng2rng SET parent_id = '[8,9)' WHERE id = '[1,2)'; 2025-07-03 22:06:05.033 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.033 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.033 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-03-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[2,3)', valid_at = daterange('2018-01-15', '2018-03-01') WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2018-01-01,2018-03-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.065 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[2,3)' WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-07-03 22:06:05.069 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.069 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.069 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET valid_at = daterange('2016-01-01', '2016-02-01') WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-07-03 22:06:05.073 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.073 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.073 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.080 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.080 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.080 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_rng SET id = '[7,8)' WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-07-03 22:06:05.092 UTC client backend[21285] pg_regress/generated_virtual LOG: disconnection: session time: 0:00:04.310 user=postgres database=regression host=[local] 2025-07-03 22:06:05.097 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.097 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON UPDATE RESTRICT; 2025-07-03 22:06:05.124 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.124 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.124 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_rng WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-07-03 22:06:05.126 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_rng" violates foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng" 2025-07-03 22:06:05.126 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_fk_rng2rng". 2025-07-03 22:06:05.126 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.149 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON DELETE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.149 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE RESTRICT; 2025-07-03 22:06:05.151 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.151 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE CASCADE ON UPDATE CASCADE; 2025-07-03 22:06:05.156 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.156 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE SET NULL ON UPDATE SET NULL; 2025-07-03 22:06:05.157 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.157 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_rng2rng ALTER COLUMN parent_id SET DEFAULT '[-1,-1]', ADD CONSTRAINT temporal_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_rng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-07-03 22:06:05.182 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key constraint "temporal_fk_mltrng2mltrng_fk2" cannot be implemented 2025-07-03 22:06:05.182 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key columns "valid_at" of the referencing table and "valid_at" of the referenced table are of incompatible types: int4multirange and datemultirange. 2025-07-03 22:06:05.182 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at int4multirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk2 PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk2 FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-07-03 22:06:05.214 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-07-03 22:06:05.214 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, valid_at) ); 2025-07-03 22:06:05.232 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key must use PERIOD when referencing a primary key using WITHOUT OVERLAPS 2025-07-03 22:06:05.232 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng (id, valid_at) ); 2025-07-03 22:06:05.235 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:05.235 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-07-03 22:06:05.239 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:05.239 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, valid_at) REFERENCES temporal_mltrng ); 2025-07-03 22:06:05.243 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referencing table but not the referenced table 2025-07-03 22:06:05.243 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id) ); 2025-07-03 22:06:05.250 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:05.250 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id) REFERENCES temporal_mltrng (id, PERIOD valid_at) ); 2025-07-03 22:06:05.290 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key uses PERIOD on the referenced table but not the referencing table 2025-07-03 22:06:05.290 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id) REFERENCES temporal_mltrng ); 2025-07-03 22:06:05.300 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-07-03 22:06:05.300 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: CREATE TABLE temporal_fk_mltrng2mltrng ( id int4range, valid_at datemultirange, parent_id int4range, CONSTRAINT temporal_fk_mltrng2mltrng_pk PRIMARY KEY (id, valid_at WITHOUT OVERLAPS), CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_mltrng (id, PERIOD id) ); 2025-07-03 22:06:05.464 UTC client backend[21293] pg_regress/without_overlaps ERROR: foreign key referenced-columns list must not contain duplicates 2025-07-03 22:06:05.464 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk2 FOREIGN KEY (parent_id, PERIOD parent_id) REFERENCES temporal_mltrng (id, PERIOD id); 2025-07-03 22:06:05.478 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.478 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-04-01)}) is not present in table "temporal_mltrng". 2025-07-03 22:06:05.478 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at); 2025-07-03 22:06:05.495 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.495 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-04-01)}) is not present in table "temporal_mltrng". 2025-07-03 22:06:05.495 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[2,3)', datemultirange(daterange('2018-01-02', '2018-04-01')), '[1,2)'); 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2018-01-02,2018-05-01)}) is not present in table "temporal_mltrng". 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_mltrng2mltrng SET valid_at = datemultirange(daterange('2018-01-02', '2018-05-01')) WHERE id = '[1,2)'; 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "temporal_fk_mltrng2mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([8,9), {[2018-01-02,2018-02-20)}) is not present in table "temporal_mltrng". 2025-07-03 22:06:05.504 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_fk_mltrng2mltrng SET parent_id = '[8,9)' WHERE id = '[1,2)'; 2025-07-03 22:06:05.512 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.512 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.512 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.547 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.547 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-03-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.547 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[2,3)', valid_at = datemultirange(daterange('2018-01-15', '2018-03-01')) WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-07-03 22:06:05.548 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.548 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2018-01-01,2018-03-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.548 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[2,3)' WHERE id = '[1,2)' AND valid_at @> '2018-01-15'::date; 2025-07-03 22:06:05.552 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.552 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.552 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET valid_at = datemultirange(daterange('2016-01-01', '2016-02-01')) WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-07-03 22:06:05.555 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.555 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.555 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.558 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.558 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.558 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_mltrng SET id = '[7,8)' WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-07-03 22:06:05.569 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.569 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_fk_mltrng2mltrng ADD CONSTRAINT temporal_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_mltrng (id, PERIOD valid_at) ON UPDATE RESTRICT; 2025-07-03 22:06:05.600 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.600 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.600 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_mltrng WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-07-03 22:06:05.605 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "temporal_mltrng" violates foreign key constraint "temporal_fk_mltrng2mltrng_fk" on table "temporal_fk_mltrng2mltrng" 2025-07-03 22:06:05.605 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_fk_mltrng2mltrng". 2025-07-03 22:06:05.605 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: COMMIT; 2025-07-03 22:06:05.659 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk" 2025-07-03 22:06:05.659 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), [2010-01-01,2010-02-15)) is not present in table "temporal_partitioned_rng". 2025-07-03 22:06:05.659 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_rng2rng (id, valid_at, parent_id) VALUES ('[3,4)', daterange('2010-01-01', '2010-02-15'), '[1,2)'); 2025-07-03 22:06:05.664 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk" 2025-07-03 22:06:05.664 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([3,4), [2000-01-01,2000-02-15)) is not present in table "temporal_partitioned_rng". 2025-07-03 22:06:05.664 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_rng2rng (id, valid_at, parent_id) VALUES ('[3,4)', daterange('2000-01-01', '2000-02-15'), '[3,4)'); 2025-07-03 22:06:05.669 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "tfkp1_pkey" 2025-07-03 22:06:05.669 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), [2000-01-01,2000-04-01)) conflicts with existing key (id, valid_at)=([1,2), [2000-01-01,2000-04-01)). 2025-07-03 22:06:05.669 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_fk_rng2rng SET valid_at = daterange('2000-01-01', '2000-04-01') WHERE id = '[1,2)'; 2025-07-03 22:06:05.698 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk_1" on table "temporal_partitioned_fk_rng2rng" 2025-07-03 22:06:05.698 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_partitioned_fk_rng2rng". 2025-07-03 22:06:05.698 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_rng SET valid_at = daterange('2016-01-01', '2016-02-01') WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-07-03 22:06:05.723 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_rng2rng_fk_1" on table "temporal_partitioned_fk_rng2rng" 2025-07-03 22:06:05.723 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), [2018-01-01,2018-02-01)) is still referenced from table "temporal_partitioned_fk_rng2rng". 2025-07-03 22:06:05.723 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_partitioned_rng WHERE id = '[5,6)' AND valid_at = daterange('2018-01-01', '2018-02-01'); 2025-07-03 22:06:05.734 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.734 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE CASCADE ON UPDATE CASCADE; 2025-07-03 22:06:05.737 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.737 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE SET NULL ON UPDATE SET NULL; 2025-07-03 22:06:05.742 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.742 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_rng2rng ALTER COLUMN parent_id SET DEFAULT '[-1,-1]', DROP CONSTRAINT temporal_partitioned_fk_rng2rng_fk, ADD CONSTRAINT temporal_partitioned_fk_rng2rng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_rng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-07-03 22:06:05.864 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.864 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([1,2), {[2010-01-01,2010-02-15)}) is not present in table "temporal_partitioned_mltrng". 2025-07-03 22:06:05.864 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[3,4)', datemultirange(daterange('2010-01-01', '2010-02-15')), '[1,2)'); 2025-07-03 22:06:05.865 UTC client backend[21293] pg_regress/without_overlaps ERROR: insert or update on table "tfkp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk" 2025-07-03 22:06:05.865 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (parent_id, valid_at)=([3,4), {[2000-01-01,2000-02-15)}) is not present in table "temporal_partitioned_mltrng". 2025-07-03 22:06:05.865 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: INSERT INTO temporal_partitioned_fk_mltrng2mltrng (id, valid_at, parent_id) VALUES ('[3,4)', datemultirange(daterange('2000-01-01', '2000-02-15')), '[3,4)'); 2025-07-03 22:06:05.877 UTC client backend[21293] pg_regress/without_overlaps ERROR: conflicting key value violates exclusion constraint "tfkp1_pkey" 2025-07-03 22:06:05.877 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([1,2), {[2000-01-01,2000-04-01)}) conflicts with existing key (id, valid_at)=([1,2), {[2000-01-01,2000-04-01)}). 2025-07-03 22:06:05.877 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_fk_mltrng2mltrng SET valid_at = datemultirange(daterange('2000-01-01', '2000-04-01')) WHERE id = '[1,2)'; 2025-07-03 22:06:05.928 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk_2" on table "temporal_partitioned_fk_mltrng2mltrng" 2025-07-03 22:06:05.928 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_partitioned_fk_mltrng2mltrng". 2025-07-03 22:06:05.928 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: UPDATE temporal_partitioned_mltrng SET valid_at = datemultirange(daterange('2016-01-01', '2016-02-01')) WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-07-03 22:06:05.952 UTC client backend[21293] pg_regress/without_overlaps ERROR: update or delete on table "tp1" violates foreign key constraint "temporal_partitioned_fk_mltrng2mltrng_fk_2" on table "temporal_partitioned_fk_mltrng2mltrng" 2025-07-03 22:06:05.952 UTC client backend[21293] pg_regress/without_overlaps DETAIL: Key (id, valid_at)=([5,6), {[2018-01-01,2018-02-01)}) is still referenced from table "temporal_partitioned_fk_mltrng2mltrng". 2025-07-03 22:06:05.952 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: DELETE FROM temporal_partitioned_mltrng WHERE id = '[5,6)' AND valid_at = datemultirange(daterange('2018-01-01', '2018-02-01')); 2025-07-03 22:06:05.956 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.956 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE CASCADE ON UPDATE CASCADE; 2025-07-03 22:06:05.977 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.977 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE SET NULL ON UPDATE SET NULL; 2025-07-03 22:06:05.987 UTC client backend[21293] pg_regress/without_overlaps ERROR: unsupported ON UPDATE action for foreign key constraint using PERIOD 2025-07-03 22:06:05.987 UTC client backend[21293] pg_regress/without_overlaps STATEMENT: ALTER TABLE temporal_partitioned_fk_mltrng2mltrng ALTER COLUMN parent_id SET DEFAULT '[0,1)', DROP CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk, ADD CONSTRAINT temporal_partitioned_fk_mltrng2mltrng_fk FOREIGN KEY (parent_id, PERIOD valid_at) REFERENCES temporal_partitioned_mltrng ON DELETE SET DEFAULT ON UPDATE SET DEFAULT; 2025-07-03 22:06:06.044 UTC client backend[21293] pg_regress/without_overlaps LOG: disconnection: session time: 0:00:05.243 user=postgres database=regression host=[local] 2025-07-03 22:06:06.585 UTC not initialized[21757] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.585 UTC not initialized[21758] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.587 UTC client backend[21758] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.587 UTC client backend[21758] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/amutils 2025-07-03 22:06:06.590 UTC client backend[21758] pg_regress/amutils LOG: connection ready: setup total=6.714 ms, fork=1.837 ms, authentication=0.417 ms 2025-07-03 22:06:06.595 UTC not initialized[21762] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.595 UTC not initialized[21759] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.597 UTC client backend[21759] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.597 UTC client backend[21759] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/stats_ext 2025-07-03 22:06:06.600 UTC client backend[21759] pg_regress/stats_ext LOG: connection ready: setup total=15.432 ms, fork=6.013 ms, authentication=0.386 ms 2025-07-03 22:06:06.601 UTC not initialized[21764] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.602 UTC client backend[21757] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.602 UTC client backend[21757] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql 2025-07-03 22:06:06.602 UTC client backend[21764] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.602 UTC client backend[21764] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql_pipeline 2025-07-03 22:06:06.603 UTC not initialized[21765] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.603 UTC client backend[21762] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.603 UTC client backend[21762] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.windows.win1252 2025-07-03 22:06:06.605 UTC client backend[21765] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.605 UTC client backend[21765] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/psql_crosstab 2025-07-03 22:06:06.605 UTC client backend[21757] pg_regress/psql LOG: connection ready: setup total=23.237 ms, fork=2.796 ms, authentication=0.387 ms 2025-07-03 22:06:06.607 UTC not initialized[21761] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.607 UTC client backend[21762] pg_regress/collate.windows.win1252 LOG: connection ready: setup total=20.284 ms, fork=7.154 ms, authentication=6.080 ms 2025-07-03 22:06:06.608 UTC client backend[21761] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.608 UTC client backend[21761] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/collate.linux.utf8 2025-07-03 22:06:06.609 UTC client backend[21764] pg_regress/psql_pipeline LOG: connection ready: setup total=19.137 ms, fork=9.696 ms, authentication=0.376 ms 2025-07-03 22:06:06.611 UTC client backend[21765] pg_regress/psql_crosstab LOG: connection ready: setup total=17.524 ms, fork=7.163 ms, authentication=0.370 ms 2025-07-03 22:06:06.614 UTC client backend[21757] pg_regress/psql ERROR: there is no parameter $1 at character 8 2025-07-03 22:06:06.614 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT $1, $2 2025-07-03 22:06:06.619 UTC client backend[21757] pg_regress/psql ERROR: column "foo" does not exist at character 8 2025-07-03 22:06:06.619 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT foo 2025-07-03 22:06:06.620 UTC client backend[21757] pg_regress/psql ERROR: cannot insert multiple commands into a prepared statement 2025-07-03 22:06:06.620 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 1 ; SELECT 2 2025-07-03 22:06:06.622 UTC client backend[21757] pg_regress/psql ERROR: bind message supplies 1 parameters, but prepared statement "" requires 2 2025-07-03 22:06:06.622 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT $1, $2 2025-07-03 22:06:06.622 UTC client backend[21757] pg_regress/psql ERROR: prepared statement "stmt2" does not exist 2025-07-03 22:06:06.622 UTC client backend[21757] pg_regress/psql ERROR: bind message supplies 1 parameters, but prepared statement "stmt3" requires 2 2025-07-03 22:06:06.622 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT $1, $2 2025-07-03 22:06:06.624 UTC not initialized[21766] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:06.625 UTC client backend[21762] pg_regress/collate.windows.win1252 LOG: disconnection: session time: 0:00:00.030 user=postgres database=regression host=[local] 2025-07-03 22:06:06.625 UTC client backend[21766] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:06.625 UTC client backend[21766] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/rules 2025-07-03 22:06:06.636 UTC client backend[21761] pg_regress/collate.linux.utf8 LOG: connection ready: setup total=50.825 ms, fork=19.271 ms, authentication=0.428 ms 2025-07-03 22:06:06.640 UTC client backend[21766] pg_regress/rules LOG: connection ready: setup total=40.939 ms, fork=24.118 ms, authentication=0.398 ms 2025-07-03 22:06:06.647 UTC client backend[21757] pg_regress/psql ERROR: syntax error at end of input at character 12 2025-07-03 22:06:06.647 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 1 + 2025-07-03 22:06:06.649 UTC client backend[21757] pg_regress/psql ERROR: relation "bububu" does not exist at character 7 2025-07-03 22:06:06.649 UTC client backend[21757] pg_regress/psql STATEMENT: TABLE bububu; 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext ERROR: syntax error at or near ";" at character 22 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst; 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext ERROR: syntax error at or near ";" at character 30 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b; 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext ERROR: syntax error at or near "FROM" at character 23 2025-07-03 22:06:06.655 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst FROM sometab; 2025-07-03 22:06:06.656 UTC client backend[21759] pg_regress/stats_ext ERROR: relation "nonexistent" does not exist 2025-07-03 22:06:06.656 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b FROM nonexistent; 2025-07-03 22:06:06.656 UTC client backend[21759] pg_regress/stats_ext ERROR: column "a" does not exist 2025-07-03 22:06:06.656 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON a, b FROM ext_stats_test; 2025-07-03 22:06:06.657 UTC client backend[21757] pg_regress/psql ERROR: syntax error at or near "bogus" at character 1 2025-07-03 22:06:06.657 UTC client backend[21757] pg_regress/psql STATEMENT: bogus; 2025-07-03 22:06:06.660 UTC client backend[21759] pg_regress/stats_ext ERROR: duplicate column name in statistics definition 2025-07-03 22:06:06.660 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y FROM ext_stats_test; 2025-07-03 22:06:06.663 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-07-03 22:06:06.663 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y, x, x, y, x, x, y FROM ext_stats_test; 2025-07-03 22:06:06.663 UTC client backend[21764] pg_regress/psql_pipeline ERROR: could not determine data type of parameter $1 2025-07-03 22:06:06.663 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $2 2025-07-03 22:06:06.664 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-07-03 22:06:06.664 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON x, x, y, x, x, (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1) FROM ext_stats_test; 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 1 parameters, but prepared statement "" requires 0 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.671 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1; 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot have more than 8 columns in statistics 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x || 'x'), (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1), (x || 'x'), (x || 'x'), (y + 1) FROM ext_stats_test; 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: duplicate expression in statistics definition 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x || 'x'), (x || 'x'), y FROM ext_stats_test; 2025-07-03 22:06:06.672 UTC client backend[21764] pg_regress/psql_pipeline ERROR: duplicate key value violates unique constraint "psql_pipeline_pkey" 2025-07-03 22:06:06.672 UTC client backend[21764] pg_regress/psql_pipeline DETAIL: Key (a)=(1) already exists. 2025-07-03 22:06:06.672 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: INSERT INTO psql_pipeline VALUES ($1) 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: unrecognized statistics kind "unrecognized" 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (unrecognized) ON x, y FROM ext_stats_test; 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: extended statistics require at least 2 columns 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (y) FROM ext_stats_test; 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: syntax error at or near "+" at character 28 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON y + z FROM ext_stats_test; 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext ERROR: syntax error at or near "," at character 28 2025-07-03 22:06:06.672 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst ON (x, y) FROM ext_stats_test; 2025-07-03 22:06:06.674 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.674 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-07-03 22:06:06.678 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.678 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-07-03 22:06:06.679 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.679 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-07-03 22:06:06.680 UTC client backend[21764] pg_regress/psql_pipeline ERROR: bind message supplies 0 parameters, but prepared statement "" requires 1 2025-07-03 22:06:06.680 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SELECT $1 2025-07-03 22:06:06.681 UTC client backend[21764] pg_regress/psql_pipeline WARNING: SET LOCAL can only be used in transaction blocks 2025-07-03 22:06:06.683 UTC client backend[21764] pg_regress/psql_pipeline ERROR: REINDEX CONCURRENTLY cannot run inside a transaction block 2025-07-03 22:06:06.683 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: REINDEX TABLE CONCURRENTLY psql_pipeline 2025-07-03 22:06:06.699 UTC client backend[21766] pg_regress/rules ERROR: rule "rtest_v1_bad" for relation "rtest_v1" does not exist 2025-07-03 22:06:06.699 UTC client backend[21766] pg_regress/rules STATEMENT: COMMENT ON RULE rtest_v1_bad ON rtest_v1 IS 'bad rule'; 2025-07-03 22:06:06.702 UTC client backend[21758] pg_regress/amutils LOG: disconnection: session time: 0:00:00.117 user=postgres database=regression host=[local] 2025-07-03 22:06:06.703 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-07-03 22:06:06.703 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on z from ext_stats_test1; 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (z) from ext_stats_test1; 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (z+1) from ext_stats_test1; 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on virtual generated columns is not supported 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON z from ext_stats_test1; 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on tableoid from ext_stats_test1; 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-07-03 22:06:06.704 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (tableoid) from ext_stats_test1; 2025-07-03 22:06:06.705 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-07-03 22:06:06.705 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst on (tableoid::int+1) from ext_stats_test1; 2025-07-03 22:06:06.705 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics creation on system columns is not supported 2025-07-03 22:06:06.705 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON xmin from ext_stats_test1; 2025-07-03 22:06:06.706 UTC client backend[21759] pg_regress/stats_ext ERROR: column "w" cannot be used in statistics because its type xid has no default btree operator class 2025-07-03 22:06:06.706 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tst (ndistinct) ON w from ext_stats_test1; 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext STATEMENT: COMMENT ON STATISTICS ab1_a_b_stats IS 'changed comment'; 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext STATEMENT: DROP STATISTICS ab1_a_b_stats; 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext ERROR: must be owner of statistics object ab1_a_b_stats 2025-07-03 22:06:06.736 UTC client backend[21759] pg_regress/stats_ext STATEMENT: ALTER STATISTICS ab1_a_b_stats RENAME TO ab1_a_b_stats_new; 2025-07-03 22:06:06.747 UTC client backend[21765] pg_regress/psql_crosstab LOG: disconnection: session time: 0:00:00.146 user=postgres database=regression host=[local] 2025-07-03 22:06:06.775 UTC client backend[21757] pg_regress/psql ERROR: table "gexec_test" does not exist 2025-07-03 22:06:06.775 UTC client backend[21757] pg_regress/psql STATEMENT: drop table gexec_test 2025-07-03 22:06:06.785 UTC client backend[21764] pg_regress/psql_pipeline ERROR: SAVEPOINT can only be used in transaction blocks 2025-07-03 22:06:06.785 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: SAVEPOINT a 2025-07-03 22:06:06.785 UTC client backend[21764] pg_regress/psql_pipeline ERROR: LOCK TABLE can only be used in transaction blocks 2025-07-03 22:06:06.785 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: LOCK psql_pipeline 2025-07-03 22:06:06.789 UTC client backend[21764] pg_regress/psql_pipeline ERROR: VACUUM cannot run inside a transaction block 2025-07-03 22:06:06.789 UTC client backend[21764] pg_regress/psql_pipeline STATEMENT: VACUUM psql_pipeline 2025-07-03 22:06:06.812 UTC client backend[21764] pg_regress/psql_pipeline LOG: disconnection: session time: 0:00:00.211 user=postgres database=regression host=[local] 2025-07-03 22:06:06.871 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "ja_JP.eucjp" for encoding "UTF8" does not exist at character 56 2025-07-03 22:06:06.871 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "ja_JP.eucjp" ); 2025-07-03 22:06:06.873 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "foo" for encoding "UTF8" does not exist at character 56 2025-07-03 22:06:06.873 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int, b text COLLATE "foo" ); 2025-07-03 22:06:06.874 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collations are not supported by type integer at character 44 2025-07-03 22:06:06.874 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE TABLE collate_test_fail ( a int COLLATE "en_US", b text ); 2025-07-03 22:06:06.921 UTC client backend[21759] pg_regress/stats_ext WARNING: statistics object "public.ab1_a_b_stats" could not be computed for relation "public.ab1" 2025-07-03 22:06:07.072 UTC client backend[21759] pg_regress/stats_ext WARNING: statistics object "public.ab1_a_b_stats" could not be computed for relation "public.ab1" 2025-07-03 22:06:07.090 UTC client backend[21759] pg_regress/stats_ext ERROR: statistics object "ab1_a_b_stats" does not exist 2025-07-03 22:06:07.090 UTC client backend[21759] pg_regress/stats_ext STATEMENT: ALTER STATISTICS ab1_a_b_stats SET STATISTICS 0; 2025-07-03 22:06:07.109 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation mismatch between explicit collations "C" and "en_US" at character 58 2025-07-03 22:06:07.109 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "en_US"; 2025-07-03 22:06:07.110 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collations are not supported by type integer at character 31 2025-07-03 22:06:07.110 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE DOMAIN testdomain_i AS int COLLATE "sv_SE"; 2025-07-03 22:06:07.214 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: invalid value "1234567890ab" for "MONTH" 2025-07-03 22:06:07.214 UTC client backend[21761] pg_regress/collate.linux.utf8 DETAIL: The given value did not match any of the allowed values for this field. 2025-07-03 22:06:07.214 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT to_date('1234567890ab 2010', 'TMMONTH YYYY'); 2025-07-03 22:06:07.298 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:07.298 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:07.298 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:07.299 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation mismatch between implicit collations "en_US" and "C" at character 48 2025-07-03 22:06:07.299 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:07.299 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:07.303 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation mismatch between implicit collations "en_US" and "C" at character 52 2025-07-03 22:06:07.303 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:07.303 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation mismatch between implicit collations "en_US" and "C" at character 49 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test3 ORDER BY 2; 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: no collation was derived for column "b" with collatable type text 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3; 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:07.304 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: select x < y from collate_test10; 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation mismatch between implicit collations "en_US" and "tr_TR" at character 47 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: You can choose the collation by applying the COLLATE clause to one or both expressions. 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: select x, y from collate_test10 order by x || y; 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: recursive query "foo" column 1 has collation "en_US" in non-recursive term but collation "de_DE" overall at character 37 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use the COLLATE clause to set the collation of the non-recursive term. 2025-07-03 22:06:07.305 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: WITH RECURSIVE foo(x) AS (SELECT x FROM (VALUES('a' COLLATE "en_US"),('b')) t(x) UNION ALL SELECT (x || 'c') COLLATE "de_DE" FROM foo WHERE length(x) < 10) SELECT * FROM foo; 2025-07-03 22:06:07.306 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: syntax error at or near "COLLATE" at character 26 2025-07-03 22:06:07.306 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT CAST('42' AS text COLLATE "C"); 2025-07-03 22:06:07.535 UTC client backend[21766] pg_regress/rules ERROR: INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules 2025-07-03 22:06:07.535 UTC client backend[21766] pg_regress/rules STATEMENT: insert into shoelace values ('sl10', 1000, 'magenta', 40.0, 'inch', 0.0) on conflict do nothing; 2025-07-03 22:06:07.571 UTC client backend[21766] pg_regress/rules ERROR: column "f1" does not exist at character 110 2025-07-03 22:06:07.571 UTC client backend[21766] pg_regress/rules DETAIL: There are columns named "f1", but they are in tables that cannot be referenced from this part of the query. 2025-07-03 22:06:07.571 UTC client backend[21766] pg_regress/rules HINT: Try using a table-qualified name. 2025-07-03 22:06:07.571 UTC client backend[21766] pg_regress/rules STATEMENT: create rule rules_foorule as on insert to rules_foo where f1 < 100 do instead insert into rules_foo2 values (f1); 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot define statistics for relation "ti" 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext DETAIL: This operation is not supported for indexes. 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s2 ON a, b FROM tststats.ti; 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot define statistics for relation "s" 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext DETAIL: This operation is not supported for sequences. 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s3 ON a, b FROM tststats.s; 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot define statistics for relation "v" 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext DETAIL: This operation is not supported for views. 2025-07-03 22:06:07.654 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s4 ON a, b FROM tststats.v; 2025-07-03 22:06:07.656 UTC client backend[21759] pg_regress/stats_ext ERROR: cannot define statistics for relation "ty" 2025-07-03 22:06:07.656 UTC client backend[21759] pg_regress/stats_ext DETAIL: This operation is not supported for composite types. 2025-07-03 22:06:07.656 UTC client backend[21759] pg_regress/stats_ext STATEMENT: CREATE STATISTICS tststats.s6 ON a, b FROM tststats.ty; 2025-07-03 22:06:08.189 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3c_fkey" 2025-07-03 22:06:08.189 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3c)=(1, 13) is not present in table "rule_and_refint_t2". 2025-07-03 22:06:08.189 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 11, 13, 'row5'); 2025-07-03 22:06:08.191 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-07-03 22:06:08.191 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-07-03 22:06:08.191 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6'); 2025-07-03 22:06:08.202 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-07-03 22:06:08.202 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-07-03 22:06:08.202 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6') on conflict do nothing; 2025-07-03 22:06:08.205 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-07-03 22:06:08.205 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-07-03 22:06:08.205 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row6') on conflict (id3a, id3b, id3c) do update set id3b = excluded.id3b; 2025-07-03 22:06:08.206 UTC client backend[21766] pg_regress/rules ERROR: INSERT with ON CONFLICT clause cannot be used with table that has INSERT or UPDATE rules 2025-07-03 22:06:08.206 UTC client backend[21766] pg_regress/rules STATEMENT: insert into shoelace values ('sl9', 0, 'pink', 35.0, 'inch', 0.0) on conflict (sl_name) do update set sl_avail = excluded.sl_avail; 2025-07-03 22:06:08.210 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3c_fkey" 2025-07-03 22:06:08.210 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3c)=(1, 13) is not present in table "rule_and_refint_t2". 2025-07-03 22:06:08.210 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 11, 13, 'row7'); 2025-07-03 22:06:08.213 UTC client backend[21766] pg_regress/rules ERROR: insert or update on table "rule_and_refint_t3" violates foreign key constraint "rule_and_refint_t3_id3a_id3b_fkey" 2025-07-03 22:06:08.213 UTC client backend[21766] pg_regress/rules DETAIL: Key (id3a, id3b)=(1, 13) is not present in table "rule_and_refint_t1". 2025-07-03 22:06:08.213 UTC client backend[21766] pg_regress/rules STATEMENT: insert into rule_and_refint_t3 values (1, 13, 11, 'row8'); 2025-07-03 22:06:08.222 UTC client backend[21766] pg_regress/rules ERROR: cannot drop rule _RETURN on view rules_fooview because view rules_fooview requires it 2025-07-03 22:06:08.222 UTC client backend[21766] pg_regress/rules HINT: You can drop view rules_fooview instead. 2025-07-03 22:06:08.222 UTC client backend[21766] pg_regress/rules STATEMENT: drop rule "_RETURN" on rules_fooview; 2025-07-03 22:06:08.251 UTC client backend[21766] pg_regress/rules ERROR: relation "rules_fooview" cannot have ON SELECT rules 2025-07-03 22:06:08.251 UTC client backend[21766] pg_regress/rules DETAIL: This operation is not supported for tables. 2025-07-03 22:06:08.251 UTC client backend[21766] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview do instead select 1 as x, 'aaa'::text as y; 2025-07-03 22:06:08.271 UTC client backend[21766] pg_regress/rules ERROR: relation "rules_fooview" cannot have ON SELECT rules 2025-07-03 22:06:08.271 UTC client backend[21766] pg_regress/rules DETAIL: This operation is not supported for partitioned tables. 2025-07-03 22:06:08.271 UTC client backend[21766] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview do instead select 1 as x, 'aaa'::text as y; 2025-07-03 22:06:08.284 UTC client backend[21766] pg_regress/rules ERROR: relation "rules_fooview_part" cannot have ON SELECT rules 2025-07-03 22:06:08.284 UTC client backend[21766] pg_regress/rules DETAIL: This operation is not supported for tables. 2025-07-03 22:06:08.284 UTC client backend[21766] pg_regress/rules STATEMENT: create rule "_RETURN" as on select to rules_fooview_part do instead select 1 as x, 'aaa'::text as y; 2025-07-03 22:06:08.502 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: could not determine which collation to use for string comparison 2025-07-03 22:06:08.502 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use the COLLATE clause to set the collation explicitly. 2025-07-03 22:06:08.502 UTC client backend[21761] pg_regress/collate.linux.utf8 CONTEXT: PL/pgSQL function mylt2(text,text) line 6 at RETURN 2025-07-03 22:06:08.502 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: SELECT mylt2('a', 'B' collate "C") as fail; 2025-07-03 22:06:08.539 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collations are not supported by type integer 2025-07-03 22:06:08.539 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "C"); 2025-07-03 22:06:08.539 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collations are not supported by type integer at character 54 2025-07-03 22:06:08.539 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "C")); 2025-07-03 22:06:08.551 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "test0" already exists 2025-07-03 22:06:08.551 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE COLLATION test0 FROM "C"; 2025-07-03 22:06:08.555 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: parameter "lc_ctype" must be specified 2025-07-03 22:06:08.555 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE COLLATION test3 (lc_collate = 'en_US.utf8'); 2025-07-03 22:06:08.555 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: could not create locale "nonsense": No such file or directory 2025-07-03 22:06:08.555 UTC client backend[21761] pg_regress/collate.linux.utf8 DETAIL: The operating system could not find any locale data for the locale name "nonsense". 2025-07-03 22:06:08.555 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE COLLATION testx (locale = 'nonsense'); 2025-07-03 22:06:08.557 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "nonsense" for encoding "UTF8" does not exist 2025-07-03 22:06:08.557 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE COLLATION test4 FROM nonsense; 2025-07-03 22:06:08.567 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "test11" for encoding "UTF8" already exists in schema "collate_tests" 2025-07-03 22:06:08.567 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: ALTER COLLATION test0 RENAME TO test11; 2025-07-03 22:06:08.567 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "test1" for encoding "UTF8" does not exist 2025-07-03 22:06:08.567 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: ALTER COLLATION test1 RENAME TO test22; 2025-07-03 22:06:08.569 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: role "nonsense" does not exist 2025-07-03 22:06:08.569 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: ALTER COLLATION test11 OWNER TO nonsense; 2025-07-03 22:06:08.588 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: collation "test0" for encoding "UTF8" does not exist 2025-07-03 22:06:08.588 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: DROP COLLATION test0; 2025-07-03 22:06:08.616 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: cannot drop collation test0 because other objects depend on it 2025-07-03 22:06:08.616 UTC client backend[21761] pg_regress/collate.linux.utf8 DETAIL: column b of table collate_dep_test1 depends on collation test0 type collate_dep_dom1 depends on collation test0 column y of composite type collate_dep_test2 depends on collation test0 view collate_dep_test3 depends on collation test0 index collate_dep_test4i depends on collation test0 2025-07-03 22:06:08.616 UTC client backend[21761] pg_regress/collate.linux.utf8 HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:08.616 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: DROP COLLATION test0 RESTRICT; 2025-07-03 22:06:08.670 UTC client backend[21766] pg_regress/rules ERROR: relation "old" in FOR UPDATE clause not found in FROM clause at character 120 2025-07-03 22:06:08.670 UTC client backend[21766] pg_regress/rules STATEMENT: create or replace rule r1 as on update to rules_base do instead select * from rules_base where f1 = 11 for update of old; 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql ERROR: bar 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql ERROR: bar 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql ERROR: bar 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE 2025-07-03 22:06:08.852 UTC client backend[21757] pg_regress/psql STATEMENT: do $$ begin raise notice 'foo'; raise exception 'bar'; end $$; 2025-07-03 22:06:08.853 UTC client backend[21757] pg_regress/psql ERROR: syntax error at or near ";" at character 15 2025-07-03 22:06:08.853 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 1 UNION; 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql ERROR: table "this_table_does_not_exist" does not exist 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql STATEMENT: DROP TABLE this_table_does_not_exist; 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql ERROR: syntax error at or near ";" at character 15 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 1 UNION; 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql ERROR: division by zero 2025-07-03 22:06:08.854 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 1/0; 2025-07-03 22:06:08.855 UTC client backend[21757] pg_regress/psql ERROR: syntax error at end of input at character 13 2025-07-03 22:06:08.855 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 4 AS 2025-07-03 22:06:08.860 UTC client backend[21757] pg_regress/psql ERROR: division by zero 2025-07-03 22:06:08.860 UTC client backend[21757] pg_regress/psql STATEMENT: select 1/(15-unique2) from tenk1 order by unique2 limit 19; 2025-07-03 22:06:08.888 UTC client backend[21761] pg_regress/collate.linux.utf8 ERROR: nondeterministic collations not supported with this provider 2025-07-03 22:06:08.888 UTC client backend[21761] pg_regress/collate.linux.utf8 STATEMENT: CREATE COLLATION ctest_nondet (locale = 'en_US.utf8', deterministic = false); 2025-07-03 22:06:08.968 UTC client backend[21761] pg_regress/collate.linux.utf8 LOG: disconnection: session time: 0:00:02.363 user=postgres database=regression host=[local] 2025-07-03 22:06:09.263 UTC client backend[21766] pg_regress/rules ERROR: rule "insertrule" for relation "rule_v1" does not exist 2025-07-03 22:06:09.263 UTC client backend[21766] pg_regress/rules STATEMENT: ALTER RULE InsertRule ON rule_v1 RENAME TO NewInsertRule; 2025-07-03 22:06:09.264 UTC client backend[21766] pg_regress/rules ERROR: rule "_RETURN" for relation "rule_v1" already exists 2025-07-03 22:06:09.264 UTC client backend[21766] pg_regress/rules STATEMENT: ALTER RULE NewInsertRule ON rule_v1 RENAME TO "_RETURN"; 2025-07-03 22:06:09.269 UTC client backend[21766] pg_regress/rules ERROR: renaming an ON SELECT rule is not allowed 2025-07-03 22:06:09.269 UTC client backend[21766] pg_regress/rules STATEMENT: ALTER RULE "_RETURN" ON rule_v1 RENAME TO abc; 2025-07-03 22:06:09.604 UTC client backend[21766] pg_regress/rules ERROR: cannot execute MERGE on relation "rule_merge1" 2025-07-03 22:06:09.604 UTC client backend[21766] pg_regress/rules DETAIL: MERGE is not supported for relations with rules. 2025-07-03 22:06:09.604 UTC client backend[21766] pg_regress/rules STATEMENT: MERGE INTO rule_merge1 t USING (SELECT 1 AS a) s ON t.a = s.a WHEN MATCHED AND t.a < 2 THEN UPDATE SET b = b || ' updated by merge' WHEN MATCHED AND t.a > 2 THEN DELETE WHEN NOT MATCHED THEN INSERT VALUES (s.a, ''); 2025-07-03 22:06:09.744 UTC client backend[21766] pg_regress/rules ERROR: permission denied for table ruletest_t3 2025-07-03 22:06:09.744 UTC client backend[21766] pg_regress/rules STATEMENT: UPDATE ruletest_t1 t1 SET x = 0 FROM ruletest_t3 t3 WHERE t1.x = t3.x; 2025-07-03 22:06:09.778 UTC client backend[21766] pg_regress/rules LOG: disconnection: session time: 0:00:03.155 user=postgres database=regression host=[local] 2025-07-03 22:06:10.156 UTC client backend[21757] pg_regress/psql ERROR: relation "ac_test" does not exist at character 15 2025-07-03 22:06:10.156 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT * FROM ac_test; 2025-07-03 22:06:10.159 UTC client backend[21757] pg_regress/psql ERROR: invalid input syntax for type integer: "foo" at character 30 2025-07-03 22:06:10.159 UTC client backend[21757] pg_regress/psql STATEMENT: INSERT INTO oer_test VALUES ('foo'); 2025-07-03 22:06:10.173 UTC client backend[21757] pg_regress/psql ERROR: relation "notexists" does not exist at character 15 2025-07-03 22:06:10.173 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT * FROM notexists; 2025-07-03 22:06:10.182 UTC client backend[21757] pg_regress/psql ERROR: syntax error at or near ";" at character 23 2025-07-03 22:06:10.182 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT 5 ; SELECT 6 + ; SELECT warn('6.5') ; SELECT 7 ; 2025-07-03 22:06:10.182 UTC client backend[21757] pg_regress/psql ERROR: division by zero 2025-07-03 22:06:10.182 UTC client backend[21757] pg_regress/psql STATEMENT: BEGIN ; SELECT 8 AS eight ; SELECT 9/0 AS nine ; ROLLBACK ; SELECT 10 AS ten ; 2025-07-03 22:06:10.316 UTC client backend[21757] pg_regress/psql ERROR: type "no_such_type" does not exist at character 20 2025-07-03 22:06:10.316 UTC client backend[21757] pg_regress/psql STATEMENT: CREATE TABLE bla(s NO_SUCH_TYPE); 2025-07-03 22:06:10.322 UTC client backend[21757] pg_regress/psql ERROR: error oops! 2025-07-03 22:06:10.322 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-07-03 22:06:10.322 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT psql_error('oops!'); 2025-07-03 22:06:10.341 UTC client backend[21757] pg_regress/psql ERROR: error boum! 2025-07-03 22:06:10.341 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-07-03 22:06:10.341 UTC client backend[21757] pg_regress/psql STATEMENT: INSERT INTO bla VALUES ('Rosalyn') ; -- will rollback SELECT 'before error' AS show ; -- will show nevertheless! SELECT psql_error('boum!') ; -- failure SELECT 'after error' AS noshow; 2025-07-03 22:06:10.342 UTC client backend[21757] pg_regress/psql ERROR: error bam! 2025-07-03 22:06:10.342 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-07-03 22:06:10.342 UTC client backend[21757] pg_regress/psql STATEMENT: INSERT INTO bla(s) VALUES ('Moe') ; -- will rollback SELECT psql_error('bam!'); 2025-07-03 22:06:10.346 UTC client backend[21757] pg_regress/psql ERROR: error bad! 2025-07-03 22:06:10.346 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-07-03 22:06:10.346 UTC client backend[21757] pg_regress/psql STATEMENT: SELECT psql_error('bad!'); 2025-07-03 22:06:10.347 UTC client backend[21757] pg_regress/psql ERROR: error bad! 2025-07-03 22:06:10.347 UTC client backend[21757] pg_regress/psql CONTEXT: PL/pgSQL function psql_error(text) line 3 at RAISE 2025-07-03 22:06:10.347 UTC client backend[21757] pg_regress/psql STATEMENT: INSERT INTO bla VALUES ('Mum') ; -- will rollback SELECT COUNT(*) AS "#mum" FROM bla WHERE s = 'Mum' ; -- but be counted here SELECT psql_error('bad!'); 2025-07-03 22:06:11.736 UTC autovacuum worker[22282] LOG: automatic vacuum of table "postgres.pg_catalog.pg_authid": index scans: 1 pages: 2 removed, 1 remain, 3 scanned (100.00% of total), 0 eagerly scanned tuples: 17 removed, 17 remain, 0 are dead but not yet removable removable cutoff: 13037, which was 1 XIDs old when operation ended new relfrozenxid: 13037, which is 6094 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 3 pages set all-visible, 3 pages set all-frozen (0 were all-visible) index scan needed: 3 pages from table (100.00% of total) had 132 dead item identifiers removed index "pg_authid_rolname_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_authid_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 4.718 MB/s buffer usage: 59 hits, 0 reads, 1 dirtied WAL usage: 18 records, 3 full page images, 26999 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:11.763 UTC autovacuum worker[22282] LOG: automatic analyze of table "postgres.pg_catalog.pg_authid" avg read rate: 0.579 MB/s, avg write rate: 1.447 MB/s buffer usage: 555 hits, 2 reads, 5 dirtied WAL usage: 31 records, 4 full page images, 36203 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:11.765 UTC autovacuum worker[22282] LOG: automatic vacuum of table "postgres.pg_catalog.pg_auth_members": index scans: 1 pages: 0 removed, 1 remain, 1 scanned (100.00% of total), 0 eagerly scanned tuples: 89 removed, 3 remain, 0 are dead but not yet removable removable cutoff: 13037, which was 3 XIDs old when operation ended new relfrozenxid: 13037, which is 6086 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 1 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (100.00% of total) had 79 dead item identifiers removed index "pg_auth_members_role_member_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_auth_members_member_role_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_auth_members_grantor_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_auth_members_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 72 hits, 0 reads, 0 dirtied WAL usage: 12 records, 1 full page images, 10873 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:11.774 UTC autovacuum worker[22282] LOG: automatic analyze of table "postgres.pg_catalog.pg_auth_members" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 116 hits, 0 reads, 0 dirtied WAL usage: 11 records, 0 full page images, 1167 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:11.775 UTC autovacuum worker[22282] LOG: automatic vacuum of table "postgres.pg_catalog.pg_shdepend": index scans: 1 pages: 5 removed, 0 remain, 5 scanned (100.00% of total), 0 eagerly scanned tuples: 378 removed, 0 remain, 0 are dead but not yet removable removable cutoff: 13038, which was 4 XIDs old when operation ended new relfrozenxid: 13038, which is 4693 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 5 pages set all-visible, 5 pages set all-frozen (0 were all-visible) index scan needed: 5 pages from table (100.00% of total) had 409 dead item identifiers removed index "pg_shdepend_depender_index": pages: 4 in total, 1 newly deleted, 1 currently deleted, 0 reusable index "pg_shdepend_reference_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 98 hits, 0 reads, 0 dirtied WAL usage: 26 records, 0 full page images, 3982 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:11.777 UTC autovacuum worker[22282] LOG: automatic analyze of table "postgres.pg_catalog.pg_shdepend" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 82 hits, 0 reads, 0 dirtied WAL usage: 0 records, 0 full page images, 0 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:12.217 UTC client backend[21757] pg_regress/psql LOG: disconnection: session time: 0:00:05.633 user=postgres database=regression host=[local] 2025-07-03 22:06:14.126 UTC client backend[21759] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-07-03 22:06:14.126 UTC client backend[21759] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl; 2025-07-03 22:06:14.126 UTC client backend[21759] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-07-03 22:06:14.126 UTC client backend[21759] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a = 1 and tststats.priv_test_tbl.* > (1, 1) is not null; 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a <<< 0 AND b <<< 0; 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext STATEMENT: SELECT * FROM tststats.priv_test_tbl WHERE a <<< 0 OR b <<< 0; 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext ERROR: permission denied for table priv_test_tbl 2025-07-03 22:06:14.128 UTC client backend[21759] pg_regress/stats_ext STATEMENT: DELETE FROM tststats.priv_test_tbl WHERE a <<< 0 AND b <<< 0; 2025-07-03 22:06:14.862 UTC client backend[21759] pg_regress/stats_ext LOG: disconnection: session time: 0:00:08.271 user=postgres database=regression host=[local] 2025-07-03 22:06:15.001 UTC not initialized[22830] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:15.002 UTC client backend[22830] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:15.002 UTC client backend[22830] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_parallel 2025-07-03 22:06:15.018 UTC client backend[22830] pg_regress/select_parallel LOG: connection ready: setup total=19.548 ms, fork=1.930 ms, authentication=0.390 ms 2025-07-03 22:06:20.494 UTC client backend[22830] pg_regress/select_parallel LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp22830.0", size 1400000 2025-07-03 22:06:20.494 UTC client backend[22830] pg_regress/select_parallel STATEMENT: insert into bmscantest select r, 'fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo' FROM generate_series(1,100000) r; 2025-07-03 22:06:20.659 UTC client backend[22830] pg_regress/select_parallel LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp22830.2.fileset/0.0", size 1949696 2025-07-03 22:06:20.659 UTC client backend[22830] pg_regress/select_parallel STATEMENT: create index i_bmtest ON bmscantest(a); 2025-07-03 22:06:25.473 UTC parallel worker[24035] ERROR: invalid input syntax for type smallint: "BAAAAAabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcd" 2025-07-03 22:06:25.473 UTC parallel worker[24035] STATEMENT: select (stringu1 || repeat('abcd', 5000))::int2 from tenk1 where unique1 = 1; 2025-07-03 22:06:25.475 UTC client backend[22830] pg_regress/select_parallel ERROR: invalid input syntax for type smallint: "BAAAAAabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcdabcd" 2025-07-03 22:06:25.475 UTC client backend[22830] pg_regress/select_parallel CONTEXT: parallel worker 2025-07-03 22:06:25.475 UTC client backend[22830] pg_regress/select_parallel STATEMENT: select (stringu1 || repeat('abcd', 5000))::int2 from tenk1 where unique1 = 1; 2025-07-03 22:06:25.506 UTC postmaster[14495] LOG: background worker "parallel worker" (PID 24035) exited with exit code 1 2025-07-03 22:06:26.117 UTC client backend[22830] pg_regress/select_parallel ERROR: division by zero 2025-07-03 22:06:26.117 UTC client backend[22830] pg_regress/select_parallel CONTEXT: SQL function "set_role_and_error" statement 1 2025-07-03 22:06:26.117 UTC client backend[22830] pg_regress/select_parallel STATEMENT: select set_role_and_error(0); 2025-07-03 22:06:26.286 UTC parallel worker[24127] ERROR: division by zero 2025-07-03 22:06:26.286 UTC parallel worker[24127] CONTEXT: SQL function "set_role_and_error" statement 1 2025-07-03 22:06:26.286 UTC parallel worker[24127] STATEMENT: select set_role_and_error(0); 2025-07-03 22:06:26.291 UTC client backend[22830] pg_regress/select_parallel ERROR: division by zero 2025-07-03 22:06:26.291 UTC client backend[22830] pg_regress/select_parallel CONTEXT: SQL function "set_role_and_error" statement 1 parallel worker 2025-07-03 22:06:26.291 UTC client backend[22830] pg_regress/select_parallel STATEMENT: select set_role_and_error(0); 2025-07-03 22:06:26.314 UTC postmaster[14495] LOG: background worker "parallel worker" (PID 24127) exited with exit code 1 2025-07-03 22:06:26.346 UTC client backend[22830] pg_regress/select_parallel LOG: disconnection: session time: 0:00:11.345 user=postgres database=regression host=[local] 2025-07-03 22:06:26.447 UTC not initialized[24155] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:26.449 UTC client backend[24155] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:26.449 UTC client backend[24155] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/write_parallel 2025-07-03 22:06:26.452 UTC client backend[24155] pg_regress/write_parallel LOG: connection ready: setup total=30.365 ms, fork=17.806 ms, authentication=0.409 ms 2025-07-03 22:06:26.852 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_type" avg read rate: 15.381 MB/s, avg write rate: 2.930 MB/s buffer usage: 1025 hits, 63 reads, 12 dirtied WAL usage: 97 records, 9 full page images, 87378 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:26.912 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_attribute" avg read rate: 1.562 MB/s, avg write rate: 1.172 MB/s buffer usage: 492 hits, 12 reads, 9 dirtied WAL usage: 82 records, 6 full page images, 39127 bytes, 0 buffers full system usage: CPU: user: 0.02 s, system: 0.00 s, elapsed: 0.05 s 2025-07-03 22:06:26.943 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_class" avg read rate: 1.465 MB/s, avg write rate: 0.977 MB/s buffer usage: 551 hits, 6 reads, 4 dirtied WAL usage: 100 records, 3 full page images, 40336 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:26.961 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.information_schema.sql_features" avg read rate: 6.611 MB/s, avg write rate: 3.005 MB/s buffer usage: 194 hits, 11 reads, 5 dirtied WAL usage: 33 records, 4 full page images, 42926 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:26.971 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_rewrite" avg read rate: 11.364 MB/s, avg write rate: 1.420 MB/s buffer usage: 112 hits, 16 reads, 2 dirtied WAL usage: 22 records, 1 full page images, 11593 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:26.973 UTC autovacuum worker[24204] LOG: automatic aggressive vacuum of table "template1.pg_catalog.pg_depend": index scans: 0 pages: 0 removed, 13 remain, 13 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 1725 remain, 0 are dead but not yet removable removable cutoff: 13230, which was 0 XIDs old when operation ended new relfrozenxid: 13230, which is 12486 XIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 0 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 81.113 MB/s, avg write rate: 4.269 MB/s buffer usage: 60 hits, 19 reads, 1 dirtied WAL usage: 1 records, 1 full page images, 7935 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:26.991 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_depend" avg read rate: 0.434 MB/s, avg write rate: 0.868 MB/s buffer usage: 107 hits, 1 reads, 2 dirtied WAL usage: 21 records, 2 full page images, 22064 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:26.992 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_shdepend" avg read rate: 0.000 MB/s, avg write rate: 3.906 MB/s buffer usage: 81 hits, 0 reads, 1 dirtied WAL usage: 3 records, 1 full page images, 8812 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:27.002 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_ts_config_map" avg read rate: 3.906 MB/s, avg write rate: 0.781 MB/s buffer usage: 58 hits, 5 reads, 1 dirtied WAL usage: 12 records, 0 full page images, 2022 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:27.006 UTC autovacuum worker[24204] LOG: automatic analyze of table "template1.pg_catalog.pg_init_privs" avg read rate: 7.812 MB/s, avg write rate: 0.000 MB/s buffer usage: 84 hits, 4 reads, 0 dirtied WAL usage: 15 records, 0 full page images, 2795 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:27.255 UTC client backend[24155] pg_regress/write_parallel LOG: disconnection: session time: 0:00:00.815 user=postgres database=regression host=[local] 2025-07-03 22:06:27.350 UTC not initialized[24273] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:27.354 UTC client backend[24273] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:27.354 UTC client backend[24273] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/vacuum_parallel 2025-07-03 22:06:27.360 UTC client backend[24273] pg_regress/vacuum_parallel LOG: connection ready: setup total=14.520 ms, fork=1.604 ms, authentication=2.701 ms 2025-07-03 22:06:27.932 UTC client backend[24273] pg_regress/vacuum_parallel LOG: disconnection: session time: 0:00:00.582 user=postgres database=regression host=[local] 2025-07-03 22:06:28.076 UTC not initialized[24339] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:28.079 UTC client backend[24339] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:28.079 UTC client backend[24339] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/maintain_every 2025-07-03 22:06:28.082 UTC client backend[24339] pg_regress/maintain_every LOG: connection ready: setup total=33.871 ms, fork=20.249 ms, authentication=1.948 ms 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "char_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "float8_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "int2_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "int4_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "int8_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "point_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "text_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "varchar_tbl", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "onek", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "onek2", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tenk1", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tenk2", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "road", skipping it 2025-07-03 22:06:28.122 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "person", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "emp", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "student", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "stud_emp", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ihighway", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_type", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shighway", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "money_data", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "numrange_test", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "textrange_test", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_table", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_authid", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "float4_tbl", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic_ext_data", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_gist", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bit_defaults", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_spgist", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "test_range_excl", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "inet_tbl", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "box_tbl", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "timetz_tbl", skipping it 2025-07-03 22:06:28.123 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "date_tbl", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "time_tbl", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "polygon_tbl", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_user_mapping", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_subscription", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_attribute", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "aggtest", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_attrdef", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sql_features", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sql_implementation_info", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_constraint", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_inherits", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_index", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_operator", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_opfamily", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_opclass", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_amop", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_amproc", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_language", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_largeobject_metadata", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_aggregate", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_statistic_ext", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_rewrite", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_trigger", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_event_trigger", skipping it 2025-07-03 22:06:28.124 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_description", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_cast", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_enum", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_namespace", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_conversion", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_db_role_setting", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_tablespace", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_auth_members", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shdepend", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shdescription", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_config", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_config_map", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_dict", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_parser", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_ts_template", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_am", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_extension", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_data_wrapper", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_foreign_server", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_policy", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_replication_origin", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_default_acl", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_init_privs", skipping it 2025-07-03 22:06:28.125 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_seclabel", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_shseclabel", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_collation", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_parameter_acl", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_partitioned_table", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_range", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_transform", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_sequence", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication_namespace", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_publication_rel", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_subscription_rel", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_largeobject", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sql_parts", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sql_sizing", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_data", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_add", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_sub", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_div", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_mul", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_sqrt", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_ln", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_log10", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_exp_power_10_ln", skipping it 2025-07-03 22:06:28.126 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_result", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_input_test", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "num_typemod_test", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "interval_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "lseg_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "line_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "path_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "circle_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "quad_poly_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "nummultirange_test", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "reservations", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl_ord_seq1", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "quad_box_tbl_ord_seq2", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "infinite_interval_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "timestamp_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "timestamptz_tbl", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tab_core_types", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted11", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted2", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted1", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted12", skipping it 2025-07-03 22:06:28.127 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_defd", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted3", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted4", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def1", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mlparted_def2", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "e_star", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "city", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "b_star", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "d_star", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "f_star", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "a_star", skipping it 2025-07-03 22:06:28.128 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "c_star", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "extra_wide_table", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_box", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_box_pk", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "real_city", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ramp", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_reg", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "quad_point_tbl", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_unique1", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_unique2", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "view_base_table", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tbl_include_pk", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "slow_emp4000", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "fast_emp4000", skipping it 2025-07-03 22:06:28.131 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "array_index_op_test", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "func_index_heap", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "kd_point_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "radix_text_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "dupindexcols", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "default_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "defaultexpr_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "check_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ne_check_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "check2_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "insert_tbl", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "xacttest", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "log_table", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "main_table", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bt_i4_heap", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bt_name_heap", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bt_txt_heap", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bt_f8_heap", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "dedup_unique_test_table", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tbl_heap2", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tblas_heap2", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_tblmv_heap2", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_heap2", skipping it 2025-07-03 22:06:28.132 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_a_heap2", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_b_heap2", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_c_heap2", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "tableam_parted_d_heap2", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "copy_tbl", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "past_inh_parent", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "past_parted", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_class", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "subselect_tbl", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_database", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "arrtest", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "array_op_test", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "hash_i4_heap", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "hash_name_heap", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "hash_txt_heap", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "hash_f8_heap", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "persons", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "persons2", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "a", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "b", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "c", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "persons3", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "d", skipping it 2025-07-03 22:06:28.133 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "regress_constr_partition1", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "regress_constr_partitioned", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl1_copy", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl3", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "cnn_uq", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk2", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_lk3", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld2", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl4_cld3", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl5_child", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl5", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl6_1", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl6", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "invalid_check_con_child", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "invalid_check_con", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pp1", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "cc1", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "cc2", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p2_2", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted", skipping it 2025-07-03 22:06:28.134 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p1", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p1_1", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "trigger_parted_p2", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child3", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent3", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_tbl1_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_child_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_parent_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_1_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_2_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "notnull_part1_3_upg", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_child2", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "constr_parent2", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "agg_data_2k", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "agg_data_20k", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sk", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "emp1", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sj", skipping it 2025-07-03 22:06:28.135 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sl", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t1", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t2", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t3", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "sj_t4", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "btree_tall_tbl", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "delete_test_table", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_point_tbl", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gist_point_tbl", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brintest", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_proc", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_t", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gin_test_tbl", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "test_tablesample", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest0", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest1", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest2", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest4", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest9", skipping it 2025-07-03 22:06:28.136 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest10", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest11", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest13", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_bb", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tm", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvm", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tmm", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest5", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest17", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_1", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtesty", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3a", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_1", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestx", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_3", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_4", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_y", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest2", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_tableoid", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest18", skipping it 2025-07-03 22:06:28.137 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest3", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest6", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7a", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10a", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20a", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20b", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20c", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21a", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21b", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22a", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvmm", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mvtest_tvvm", skipping it 2025-07-03 22:06:28.148 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22b", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22c", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23p", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23q", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7c", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7b", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7e", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest7d", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_box_tbl", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_text_tbl", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "bug_16784", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gs_data_1", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24r", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24nn", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_parent", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child2", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p1", skipping it 2025-07-03 22:06:28.149 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p2", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest1_p1_like", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest2", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pitest2_p2", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "itest14", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "identity_dump_logged", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "identity_dump_unlogged", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rls_tbl", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rls_tbl_force", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child3", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_domain_tbl", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "spgist_unlogged_tbl", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest25", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest27", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest29", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30_1", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest26", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28a", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28b", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "datdba_only", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brintest_multi", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brintest_bloom", skipping it 2025-07-03 22:06:28.150 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers_bloom", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brinopers_multi", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize_bloom", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test_bloom", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_summarize_multi", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "brin_test_multi", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest0", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "inhf", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "inhx", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_1", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "point_table", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "hobbies_r", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "equipment_r", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtesty", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21a", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3a", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_1", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestx", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_3", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestxx_4", skipping it 2025-07-03 22:06:28.151 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest1_y", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest3", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest2", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_tableoid", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest10a", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20a", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20b", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest20c", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest21b", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_parent", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_child", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtestnn_childdef", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest22c", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest23a", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24at", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest24ata", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_parent", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child2", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest_child3", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest25", skipping it 2025-07-03 22:06:28.152 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "pg_depend", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest27", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest29", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_rng2", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk2_rng2rng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30_1", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest30", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28a", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest28b", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "gtest26", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_rng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk_rng2rng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_mltrng2", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk2_mltrng2mltrng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_mltrng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "temporal_fk_mltrng2mltrng", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_admin", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_system", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_person", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_emplog", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_empmass", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_emp", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t7", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t8", skipping it 2025-07-03 22:06:28.153 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t9", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t4", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t5", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t6", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_order2", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t1", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t2", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_t3", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_interface", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_order1", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn3", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn4", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn1", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_nothn2", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view1", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view2", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view3", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_view4", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_comp", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rtest_unitfact", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shoe_data", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "unit", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rules_log", skipping it 2025-07-03 22:06:28.154 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rules_src", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rule_merge2", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rule_merge1", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_log", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_data", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_arrive", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "shoelace_ok", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ruletest_tbl2", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ruletest_tbl", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t1", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t2", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "rule_and_refint_t3", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "ndistinct", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "functional_dependencies", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists_arrays", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "mcv_lists_bool", skipping it 2025-07-03 22:06:28.155 UTC client backend[24339] pg_regress/maintain_every WARNING: permission denied to analyze "parallel_vacuum_table", skipping it 2025-07-03 22:06:28.169 UTC client backend[24339] pg_regress/maintain_every LOG: disconnection: session time: 0:00:00.100 user=postgres database=regression host=[local] 2025-07-03 22:06:28.255 UTC not initialized[24359] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:28.255 UTC not initialized[24360] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:28.256 UTC client backend[24359] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:28.256 UTC client backend[24359] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/publication 2025-07-03 22:06:28.256 UTC client backend[24360] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:28.257 UTC client backend[24360] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/subscription 2025-07-03 22:06:28.259 UTC client backend[24359] pg_regress/publication LOG: connection ready: setup total=14.359 ms, fork=8.931 ms, authentication=0.401 ms 2025-07-03 22:06:28.271 UTC client backend[24360] pg_regress/subscription LOG: connection ready: setup total=24.686 ms, fork=6.889 ms, authentication=0.380 ms 2025-07-03 22:06:28.275 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.275 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription ERROR: syntax error at or near ";" at character 53 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'foo'; 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription ERROR: syntax error at or near "PUBLICATION" at character 37 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub PUBLICATION foo; 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription ERROR: CREATE SUBSCRIPTION ... WITH (create_slot = true) cannot run inside a transaction block 2025-07-03 22:06:28.280 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'testconn' PUBLICATION testpub WITH (create_slot); 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription ERROR: invalid connection string syntax: missing "=" after "testconn" in connection info string 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'testconn' PUBLICATION testpub; 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription ERROR: publication name "foo" used more than once 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION foo, testpub, foo WITH (connect = false); 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.289 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.290 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.290 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication ERROR: unrecognized publication parameter: "foo" 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (foo); 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication ERROR: unrecognized value for publication option "publish": "cluster" 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish = 'cluster, vacuum'); 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant options at character 75 2025-07-03 22:06:28.291 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_via_partition_root = 'true', publish_via_partition_root = '0'); 2025-07-03 22:06:28.292 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant options at character 74 2025-07-03 22:06:28.292 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_generated_columns = stored, publish_generated_columns = none); 2025-07-03 22:06:28.292 UTC client backend[24359] pg_regress/publication ERROR: invalid value for publication parameter "publish_generated_columns": "foo" 2025-07-03 22:06:28.292 UTC client backend[24359] pg_regress/publication DETAIL: Valid values are "none" and "stored". 2025-07-03 22:06:28.292 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_xxx WITH (publish_generated_columns = foo); 2025-07-03 22:06:28.317 UTC client backend[24360] pg_regress/subscription ERROR: subscription "regress_testsub" already exists 2025-07-03 22:06:28.317 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription ERROR: permission denied to create subscription 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription DETAIL: Only roles with privileges of the "pg_create_subscription" role may create subscriptions. 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION foo WITH (connect = false); 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription ERROR: connect = false and copy_data = true are mutually exclusive options 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, copy_data = true); 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription ERROR: connect = false and enabled = true are mutually exclusive options 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, enabled = true); 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription ERROR: connect = false and create_slot = true are mutually exclusive options 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, create_slot = true); 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription ERROR: slot_name = NONE and enabled = true are mutually exclusive options 2025-07-03 22:06:28.318 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = true); 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription ERROR: slot_name = NONE and create_slot = true are mutually exclusive options 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = false, create_slot = true); 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set enabled = false 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE); 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set create_slot = false 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, enabled = false); 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription ERROR: subscription with slot_name = NONE must also set enabled = false 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub2 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, create_slot = false); 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.319 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription ERROR: cannot enable subscription that does not have a slot name 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub3 ENABLE; 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... REFRESH is not allowed for disabled subscriptions 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub3 REFRESH PUBLICATION; 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription ERROR: unrecognized origin value: "foo" 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub4 CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (slot_name = NONE, connect = false, origin = foo); 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.320 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.331 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.331 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.340 UTC client backend[24360] pg_regress/subscription ERROR: invalid connection string syntax: invalid connection option "i_dont_exist" 2025-07-03 22:06:28.340 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub5 CONNECTION 'i_dont_exist=param' PUBLICATION testpub; 2025-07-03 22:06:28.341 UTC client backend[24360] pg_regress/subscription ERROR: subscription "regress_testsub5" could not connect to the publisher: invalid port number: "-1" 2025-07-03 22:06:28.341 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub5 CONNECTION 'port=-1' PUBLICATION testpub; 2025-07-03 22:06:28.343 UTC client backend[24360] pg_regress/subscription ERROR: invalid connection string syntax: missing "=" after "foobar" in connection info string 2025-07-03 22:06:28.343 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub CONNECTION 'foobar'; 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription ERROR: replication slot name "" is too short 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (slot_name = ''); 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription ERROR: subscription "regress_doesnotexist" does not exist 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_doesnotexist CONNECTION 'dbname=regress_doesnotexist2'; 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription ERROR: unrecognized subscription parameter: "create_slot" 2025-07-03 22:06:28.349 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (create_slot = false); 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication DETAIL: Tables cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables ADD TABLE testpub_tbl2; 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication DETAIL: Tables cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.353 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables DROP TABLE testpub_tbl2; 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication DETAIL: Tables cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables SET TABLE pub_test.testpub_nopk; 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables ADD TABLES IN SCHEMA pub_test; 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables DROP TABLES IN SCHEMA pub_test; 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_foralltables" is defined as FOR ALL TABLES 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication DETAIL: Schemas cannot be added to or dropped from FOR ALL TABLES publications. 2025-07-03 22:06:28.354 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_foralltables SET TABLES IN SCHEMA pub_test; 2025-07-03 22:06:28.356 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.356 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.357 UTC client backend[24360] pg_regress/subscription ERROR: invalid WAL location (LSN): 0/0 2025-07-03 22:06:28.357 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SKIP (lsn = '0/0'); 2025-07-03 22:06:28.364 UTC client backend[24360] pg_regress/subscription ERROR: must be owner of subscription regress_testsub 2025-07-03 22:06:28.364 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub RENAME TO regress_testsub_dummy; 2025-07-03 22:06:28.372 UTC client backend[24360] pg_regress/subscription ERROR: invalid value for parameter "synchronous_commit": "foobar" 2025-07-03 22:06:28.372 UTC client backend[24360] pg_regress/subscription HINT: Available values: local, remote_write, remote_apply, on, off. 2025-07-03 22:06:28.372 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub_foo SET (synchronous_commit = foobar); 2025-07-03 22:06:28.375 UTC client backend[24360] pg_regress/subscription ERROR: DROP SUBSCRIPTION cannot run inside a transaction block 2025-07-03 22:06:28.375 UTC client backend[24360] pg_regress/subscription STATEMENT: DROP SUBSCRIPTION regress_testsub; 2025-07-03 22:06:28.376 UTC client backend[24360] pg_regress/subscription ERROR: subscription "regress_testsub" does not exist 2025-07-03 22:06:28.376 UTC client backend[24360] pg_regress/subscription STATEMENT: DROP SUBSCRIPTION regress_testsub; 2025-07-03 22:06:28.377 UTC client backend[24360] pg_regress/subscription ERROR: binary requires a Boolean value 2025-07-03 22:06:28.377 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, binary = foo); 2025-07-03 22:06:28.377 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.377 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.379 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.379 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.380 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.380 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.383 UTC client backend[24359] pg_regress/publication ERROR: invalid table name at character 71 2025-07-03 22:06:28.383 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_parsertst FOR TABLE pub_test.testpub_nopk, CURRENT_SCHEMA; 2025-07-03 22:06:28.383 UTC client backend[24359] pg_regress/publication ERROR: invalid schema name at character 64 2025-07-03 22:06:28.383 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_parsertst FOR TABLES IN SCHEMA foo, test.foo; 2025-07-03 22:06:28.384 UTC client backend[24360] pg_regress/subscription ERROR: streaming requires a Boolean value or "parallel" 2025-07-03 22:06:28.384 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, streaming = foo); 2025-07-03 22:06:28.384 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.384 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.392 UTC client backend[24360] pg_regress/subscription ERROR: publication "testpub" is already in subscription "regress_testsub" 2025-07-03 22:06:28.392 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub WITH (refresh = false); 2025-07-03 22:06:28.392 UTC client backend[24360] pg_regress/subscription ERROR: publication name "testpub1" used more than once 2025-07-03 22:06:28.392 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub1, testpub1 WITH (refresh = false); 2025-07-03 22:06:28.393 UTC client backend[24360] pg_regress/subscription ERROR: publication "testpub1" is already in subscription "regress_testsub" 2025-07-03 22:06:28.393 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub ADD PUBLICATION testpub1, testpub2 WITH (refresh = false); 2025-07-03 22:06:28.393 UTC client backend[24360] pg_regress/subscription ERROR: publication name "testpub1" used more than once 2025-07-03 22:06:28.393 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub1, testpub1 WITH (refresh = false); 2025-07-03 22:06:28.394 UTC client backend[24360] pg_regress/subscription ERROR: cannot drop all the publications from a subscription 2025-07-03 22:06:28.394 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub, testpub1, testpub2 WITH (refresh = false); 2025-07-03 22:06:28.394 UTC client backend[24360] pg_regress/subscription ERROR: publication "testpub3" is not in subscription "regress_testsub" 2025-07-03 22:06:28.394 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub DROP PUBLICATION testpub3 WITH (refresh = false); 2025-07-03 22:06:28.395 UTC client backend[24359] pg_regress/publication ERROR: relation "testpub_nopk" is not part of the publication 2025-07-03 22:06:28.395 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_forschema DROP TABLE pub_test.testpub_nopk; 2025-07-03 22:06:28.396 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.396 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.408 UTC client backend[24360] pg_regress/subscription ERROR: ALTER SUBSCRIPTION with refresh cannot run inside a transaction block 2025-07-03 22:06:28.408 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET PUBLICATION mypub WITH (refresh = true); 2025-07-03 22:06:28.408 UTC client backend[24360] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... REFRESH cannot run inside a transaction block 2025-07-03 22:06:28.408 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub REFRESH PUBLICATION; 2025-07-03 22:06:28.412 UTC client backend[24360] pg_regress/subscription ERROR: ALTER SUBSCRIPTION with refresh cannot be executed from a function 2025-07-03 22:06:28.412 UTC client backend[24360] pg_regress/subscription CONTEXT: SQL function "func" statement 1 2025-07-03 22:06:28.412 UTC client backend[24360] pg_regress/subscription STATEMENT: SELECT func(); 2025-07-03 22:06:28.442 UTC logical replication apply worker[24366] FATAL: terminating logical replication worker due to administrator command 2025-07-03 22:06:28.454 UTC client backend[24360] pg_regress/subscription ERROR: two_phase requires a Boolean value 2025-07-03 22:06:28.454 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, two_phase = foo); 2025-07-03 22:06:28.455 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.455 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.460 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.460 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.461 UTC client backend[24360] pg_regress/subscription ERROR: disable_on_error requires a Boolean value 2025-07-03 22:06:28.461 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, disable_on_error = foo); 2025-07-03 22:06:28.462 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.462 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.464 UTC postmaster[14495] LOG: background worker "logical replication apply worker" (PID 24366) exited with exit code 1 2025-07-03 22:06:28.469 UTC client backend[24360] pg_regress/subscription ERROR: permission denied for database regression 2025-07-03 22:06:28.469 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription ERROR: password is required 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription DETAIL: Non-superusers must provide a password in the connection string. 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false); 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription ERROR: password_required=false is superuser-only 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription HINT: Subscriptions with the password_required option set to false may only be created or modified by the superuser. 2025-07-03 22:06:28.470 UTC client backend[24360] pg_regress/subscription STATEMENT: CREATE SUBSCRIPTION regress_testsub CONNECTION 'dbname=regress_doesnotexist' PUBLICATION testpub WITH (connect = false, password_required = false); 2025-07-03 22:06:28.480 UTC client backend[24360] pg_regress/subscription WARNING: subscription was created, but is not connected 2025-07-03 22:06:28.480 UTC client backend[24360] pg_regress/subscription HINT: To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription. 2025-07-03 22:06:28.480 UTC client backend[24360] pg_regress/subscription ERROR: must be able to SET ROLE "regress_subscription_user" 2025-07-03 22:06:28.480 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub OWNER TO regress_subscription_user; 2025-07-03 22:06:28.484 UTC client backend[24360] pg_regress/subscription ERROR: permission denied for database regression 2025-07-03 22:06:28.484 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub RENAME TO regress_testsub2; 2025-07-03 22:06:28.484 UTC client backend[24360] pg_regress/subscription ERROR: ALTER SUBSCRIPTION ... SET (failover) cannot run inside a transaction block 2025-07-03 22:06:28.484 UTC client backend[24360] pg_regress/subscription STATEMENT: ALTER SUBSCRIPTION regress_testsub SET (failover); 2025-07-03 22:06:28.495 UTC client backend[24360] pg_regress/subscription LOG: disconnection: session time: 0:00:00.241 user=postgres database=regression host=[local] 2025-07-03 22:06:28.585 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.585 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.586 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.586 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.615 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.615 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.616 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.616 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.641 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_parted1" because it does not have a replica identity and publishes updates 2025-07-03 22:06:28.641 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:28.641 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_parted1 SET a = 1; 2025-07-03 22:06:28.645 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_parted2" because it does not have a replica identity and publishes updates 2025-07-03 22:06:28.645 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:28.645 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_parted2 SET a = 2; 2025-07-03 22:06:28.690 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.690 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.988 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.988 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:28.996 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:28.996 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.056 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.056 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.067 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.067 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication ERROR: syntax error at or near "WHERE" at character 76 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax3 FOR TABLES IN SCHEMA testpub_rf_schema1 WHERE (a = 123); 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication ERROR: WHERE clause not allowed for schema at character 77 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_syntax3 FOR TABLES IN SCHEMA testpub_rf_schema1, testpub_rf_schema1 WHERE (a = 123); 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant WHERE clauses for table "testpub_rf_tbl1" 2025-07-03 22:06:29.079 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_rf_tbl1 WHERE (a = 1), testpub_rf_tbl1 WITH (publish = 'insert'); 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant WHERE clauses for table "testpub_rf_tbl1" 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_rf_tbl1, testpub_rf_tbl1 WHERE (a = 2) WITH (publish = 'insert'); 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication ERROR: argument of PUBLICATION WHERE must be type boolean, not type integer at character 61 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 SET TABLE testpub_rf_tbl3 WHERE (1234); 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication ERROR: aggregate functions are not allowed in WHERE at character 65 2025-07-03 22:06:29.080 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 SET TABLE testpub_rf_tbl3 WHERE (e < AVG(e)); 2025-07-03 22:06:29.082 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 62 2025-07-03 22:06:29.082 UTC client backend[24359] pg_regress/publication DETAIL: User-defined operators are not allowed. 2025-07-03 22:06:29.082 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl3 WHERE (e =#> 27); 2025-07-03 22:06:29.083 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 66 2025-07-03 22:06:29.083 UTC client backend[24359] pg_regress/publication DETAIL: User-defined or built-in mutable functions are not allowed. 2025-07-03 22:06:29.083 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (a >= testpub_rf_func2()); 2025-07-03 22:06:29.084 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 65 2025-07-03 22:06:29.084 UTC client backend[24359] pg_regress/publication DETAIL: User-defined or built-in mutable functions are not allowed. 2025-07-03 22:06:29.084 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (a < random()); 2025-07-03 22:06:29.086 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 61 2025-07-03 22:06:29.086 UTC client backend[24359] pg_regress/publication DETAIL: User-defined collations are not allowed. 2025-07-03 22:06:29.086 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 ADD TABLE testpub_rf_tbl1 WHERE (b < '2' COLLATE user_collation); 2025-07-03 22:06:29.100 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 53 2025-07-03 22:06:29.100 UTC client backend[24359] pg_regress/publication DETAIL: User-defined types are not allowed. 2025-07-03 22:06:29.100 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE rf_bug WHERE (status = 'open') WITH (publish = 'insert'); 2025-07-03 22:06:29.104 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 62 2025-07-03 22:06:29.104 UTC client backend[24359] pg_regress/publication DETAIL: Only columns, constants, built-in operators, built-in data types, built-in collations, and immutable built-in functions are allowed. 2025-07-03 22:06:29.104 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl1 WHERE (a IN (SELECT generate_series(1,5))); 2025-07-03 22:06:29.105 UTC client backend[24359] pg_regress/publication ERROR: invalid publication WHERE expression at character 77 2025-07-03 22:06:29.105 UTC client backend[24359] pg_regress/publication DETAIL: System columns are not allowed. 2025-07-03 22:06:29.105 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub6 FOR TABLE testpub_rf_tbl1 WHERE ('(0,1)'::tid = ctid); 2025-07-03 22:06:29.111 UTC client backend[24359] pg_regress/publication ERROR: cannot use a WHERE clause when removing a table from a publication 2025-07-03 22:06:29.111 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub5 DROP TABLE testpub_rf_tbl1 WHERE (e < 27); 2025-07-03 22:06:29.112 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.112 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.117 UTC client backend[24359] pg_regress/publication ERROR: generation expression uses user-defined function at character 89 2025-07-03 22:06:29.117 UTC client backend[24359] pg_regress/publication DETAIL: Virtual generated columns that make use of user-defined functions are not yet supported. 2025-07-03 22:06:29.117 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE TABLE testpub_rf_tbl6 (id int PRIMARY KEY, x int, y int GENERATED ALWAYS AS (x * testpub_rf_func2()) VIRTUAL); 2025-07-03 22:06:29.118 UTC client backend[24359] pg_regress/publication ERROR: relation "testpub_rf_tbl6" does not exist 2025-07-03 22:06:29.118 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub7 FOR TABLE testpub_rf_tbl6 WHERE (y > 100); 2025-07-03 22:06:29.121 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.121 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.122 UTC client backend[24359] pg_regress/publication ERROR: ALTER TABLE / SET EXPRESSION is not supported for virtual generated columns in tables that are part of a publication 2025-07-03 22:06:29.122 UTC client backend[24359] pg_regress/publication DETAIL: Column "y" of relation "testpub_rf_tbl7" is a virtual generated column. 2025-07-03 22:06:29.122 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER TABLE testpub_rf_tbl7 ALTER COLUMN y SET EXPRESSION AS (x * testpub_rf_func2()); 2025-07-03 22:06:29.182 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.182 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.190 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.190 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.190 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.192 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.192 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.192 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.197 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-07-03 22:06:29.197 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.197 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.216 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.216 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.216 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.218 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.218 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.218 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.220 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-07-03 22:06:29.220 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.220 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.232 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.232 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.232 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.237 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-07-03 22:06:29.237 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.237 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.239 UTC client backend[24359] pg_regress/publication ERROR: cannot use publication WHERE clause for relation "rf_tbl_abcd_part_pk" 2025-07-03 22:06:29.239 UTC client backend[24359] pg_regress/publication DETAIL: WHERE clause cannot be used for a partitioned table when publish_via_partition_root is false. 2025-07-03 22:06:29.239 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET TABLE rf_tbl_abcd_part_pk WHERE (a > 99); 2025-07-03 22:06:29.243 UTC client backend[24359] pg_regress/publication ERROR: cannot set parameter "publish_via_partition_root" to false for publication "testpub6" 2025-07-03 22:06:29.243 UTC client backend[24359] pg_regress/publication DETAIL: The publication contains a WHERE clause for partitioned table "rf_tbl_abcd_part_pk", which is not allowed when "publish_via_partition_root" is false. 2025-07-03 22:06:29.243 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET (PUBLISH_VIA_PARTITION_ROOT=0); 2025-07-03 22:06:29.247 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-07-03 22:06:29.247 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.247 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-07-03 22:06:29.248 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-07-03 22:06:29.248 UTC client backend[24359] pg_regress/publication DETAIL: Column used in the publication WHERE expression is not part of the replica identity. 2025-07-03 22:06:29.248 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-07-03 22:06:29.272 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.272 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.273 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-07-03 22:06:29.273 UTC client backend[24359] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-07-03 22:06:29.273 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-07-03 22:06:29.287 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-07-03 22:06:29.287 UTC client backend[24359] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-07-03 22:06:29.287 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-07-03 22:06:29.289 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.289 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.296 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.296 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.296 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-07-03 22:06:29.296 UTC client backend[24359] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-07-03 22:06:29.296 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-07-03 22:06:29.297 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.297 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.298 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_gencol" 2025-07-03 22:06:29.298 UTC client backend[24359] pg_regress/publication DETAIL: Replica identity must not contain unpublished generated columns. 2025-07-03 22:06:29.298 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_gencol SET a = 100 WHERE a = 1; 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant column lists for table "testpub_tbl1" 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_tbl1 (a), testpub_tbl1 WITH (publish = 'insert'); 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication ERROR: conflicting or redundant column lists for table "testpub_tbl1" 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_dups FOR TABLE testpub_tbl1, testpub_tbl1 (a) WITH (publish = 'insert'); 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.300 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.301 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.301 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.312 UTC client backend[24359] pg_regress/publication ERROR: column "x" of relation "testpub_tbl5" does not exist 2025-07-03 22:06:29.312 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, x); 2025-07-03 22:06:29.313 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-07-03 22:06:29.313 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.313 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication ERROR: cannot use system column "ctid" in publication column list 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, ctid); 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication ERROR: cannot use system column "ctid" in publication column list 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable SET TABLE testpub_tbl1 (id, ctid); 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication ERROR: duplicate column "a" in publication column list 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, a); 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication ERROR: duplicate column "a" in publication column list 2025-07-03 22:06:29.314 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable SET TABLE testpub_tbl5 (a, a); 2025-07-03 22:06:29.315 UTC client backend[24359] pg_regress/publication ERROR: cannot drop column c of table testpub_tbl5 because other objects depend on it 2025-07-03 22:06:29.315 UTC client backend[24359] pg_regress/publication DETAIL: publication of table testpub_tbl5 in publication testpub_fortable depends on column c of table testpub_tbl5 2025-07-03 22:06:29.315 UTC client backend[24359] pg_regress/publication HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:29.315 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER TABLE testpub_tbl5 DROP COLUMN c; 2025-07-03 22:06:29.318 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-07-03 22:06:29.318 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.318 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-07-03 22:06:29.320 UTC client backend[24359] pg_regress/publication ERROR: cannot use virtual generated column "e" in publication column list 2025-07-03 22:06:29.320 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortable ADD TABLE testpub_tbl5 (a, e); 2025-07-03 22:06:29.321 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl5" 2025-07-03 22:06:29.321 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.321 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl5 SET a = 1; 2025-07-03 22:06:29.321 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.321 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.337 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl5d" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.337 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.337 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl5d SET a = 1; 2025-07-03 22:06:29.351 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl6" 2025-07-03 22:06:29.351 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.351 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl6 SET a = 1; 2025-07-03 22:06:29.556 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.556 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.563 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-07-03 22:06:29.563 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.563 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.572 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-07-03 22:06:29.572 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.572 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.576 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-07-03 22:06:29.576 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.576 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.596 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-07-03 22:06:29.596 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.596 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.646 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_1" 2025-07-03 22:06:29.646 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.646 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl8_0" 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl8 SET a = 1; 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-07-03 22:06:29.654 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_tbl9 FOR TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-07-03 22:06:29.680 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.680 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.684 UTC client backend[24359] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-07-03 22:06:29.684 UTC client backend[24359] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-07-03 22:06:29.684 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLE public.testpub_tbl7(a); 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication ERROR: cannot add schema to publication "testpub_tbl9" 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication DETAIL: Schemas cannot be added if any tables that specify a column list are already part of the publication. 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLES IN SCHEMA public; 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-07-03 22:06:29.686 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 SET TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-07-03 22:06:29.687 UTC client backend[24359] pg_regress/publication ERROR: cannot use column list for relation "public.testpub_tbl7" in publication "testpub_tbl9" 2025-07-03 22:06:29.687 UTC client backend[24359] pg_regress/publication DETAIL: Column lists cannot be specified in publications containing FOR TABLES IN SCHEMA elements. 2025-07-03 22:06:29.687 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_tbl9 ADD TABLES IN SCHEMA public, TABLE public.testpub_tbl7(a); 2025-07-03 22:06:29.730 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.730 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.879 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.879 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.891 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.891 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.891 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.893 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.893 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.893 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.898 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.898 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.898 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.900 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.900 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.900 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.901 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-07-03 22:06:29.901 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.901 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.902 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.902 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.902 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.903 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.903 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.903 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.907 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.907 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.907 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.912 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_pk" 2025-07-03 22:06:29.912 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.912 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_pk SET a = 1; 2025-07-03 22:06:29.915 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_nopk" 2025-07-03 22:06:29.915 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.915 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_nopk SET a = 1; 2025-07-03 22:06:29.916 UTC client backend[24359] pg_regress/publication ERROR: cannot use column list for relation "public.rf_tbl_abcd_part_pk" in publication "testpub6" 2025-07-03 22:06:29.916 UTC client backend[24359] pg_regress/publication DETAIL: Column lists cannot be specified for partitioned tables when publish_via_partition_root is false. 2025-07-03 22:06:29.916 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET TABLE rf_tbl_abcd_part_pk (a); 2025-07-03 22:06:29.919 UTC client backend[24359] pg_regress/publication ERROR: cannot set parameter "publish_via_partition_root" to false for publication "testpub6" 2025-07-03 22:06:29.919 UTC client backend[24359] pg_regress/publication DETAIL: The publication contains a column list for partitioned table "rf_tbl_abcd_part_pk", which is not allowed when "publish_via_partition_root" is false. 2025-07-03 22:06:29.919 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub6 SET (PUBLISH_VIA_PARTITION_ROOT=0); 2025-07-03 22:06:29.921 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-07-03 22:06:29.921 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.921 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-07-03 22:06:29.922 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "rf_tbl_abcd_part_pk_1" 2025-07-03 22:06:29.922 UTC client backend[24359] pg_regress/publication DETAIL: Column list used by the publication does not cover the replica identity. 2025-07-03 22:06:29.922 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE rf_tbl_abcd_part_pk SET a = 1; 2025-07-03 22:06:29.934 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.934 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.940 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_tbl4" because it does not have a replica identity and publishes updates 2025-07-03 22:06:29.940 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:29.940 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE testpub_tbl4 set a = 3; 2025-07-03 22:06:29.949 UTC client backend[24359] pg_regress/publication ERROR: cannot add relation "testpub_view" to publication 2025-07-03 22:06:29.949 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for views. 2025-07-03 22:06:29.949 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortbl FOR TABLE testpub_view; 2025-07-03 22:06:29.951 UTC client backend[24359] pg_regress/publication ERROR: cannot add relation "testpub_temptbl" to publication 2025-07-03 22:06:29.951 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for temporary tables. 2025-07-03 22:06:29.951 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortemptbl FOR TABLE testpub_temptbl; 2025-07-03 22:06:29.953 UTC client backend[24359] pg_regress/publication ERROR: cannot add relation "testpub_unloggedtbl" to publication 2025-07-03 22:06:29.953 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for unlogged tables. 2025-07-03 22:06:29.953 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forunloggedtbl FOR TABLE testpub_unloggedtbl; 2025-07-03 22:06:29.956 UTC client backend[24359] pg_regress/publication ERROR: cannot add relation "pg_publication" to publication 2025-07-03 22:06:29.956 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for system tables. 2025-07-03 22:06:29.956 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forsystemtbl FOR TABLE pg_publication; 2025-07-03 22:06:29.957 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:29.957 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:29.959 UTC client backend[24359] pg_regress/publication ERROR: relation "testpub_tbl1" is already member of publication "testpub_fortbl" 2025-07-03 22:06:29.959 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_fortbl ADD TABLE testpub_tbl1; 2025-07-03 22:06:29.960 UTC client backend[24359] pg_regress/publication ERROR: publication "testpub_fortbl" already exists 2025-07-03 22:06:29.960 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_fortbl FOR TABLE testpub_tbl1; 2025-07-03 22:06:29.964 UTC client backend[24359] pg_regress/publication ERROR: cannot add relation "testpub_view" to publication 2025-07-03 22:06:29.964 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for views. 2025-07-03 22:06:29.964 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default ADD TABLE testpub_view; 2025-07-03 22:06:30.047 UTC client backend[24359] pg_regress/publication ERROR: relation "testpub_nopk" is not part of the publication 2025-07-03 22:06:30.047 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default DROP TABLE pub_test.testpub_nopk; 2025-07-03 22:06:30.089 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "testpub_addpk" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.089 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.089 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_test.testpub_addpk SET id = 2; 2025-07-03 22:06:30.094 UTC client backend[24359] pg_regress/publication ERROR: permission denied for database regression 2025-07-03 22:06:30.094 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub2; 2025-07-03 22:06:30.095 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.095 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.103 UTC client backend[24359] pg_regress/publication ERROR: must be superuser to create FOR TABLES IN SCHEMA publication 2025-07-03 22:06:30.103 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub3 FOR TABLES IN SCHEMA pub_test; 2025-07-03 22:06:30.103 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.103 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.104 UTC client backend[24359] pg_regress/publication ERROR: must be owner of table testpub_tbl1 2025-07-03 22:06:30.104 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub2 ADD TABLE testpub_tbl1; 2025-07-03 22:06:30.104 UTC client backend[24359] pg_regress/publication ERROR: must be superuser to add or set schemas 2025-07-03 22:06:30.104 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub3 ADD TABLES IN SCHEMA pub_test; 2025-07-03 22:06:30.109 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.109 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.110 UTC client backend[24359] pg_regress/publication ERROR: permission denied to change owner of publication "testpub4" 2025-07-03 22:06:30.110 UTC client backend[24359] pg_regress/publication HINT: The owner of a FOR TABLES IN SCHEMA publication must be a superuser. 2025-07-03 22:06:30.110 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub4 owner to regress_publication_user2; 2025-07-03 22:06:30.128 UTC client backend[24359] pg_regress/publication ERROR: must be owner of publication testpub_default 2025-07-03 22:06:30.128 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub_default RENAME TO testpub_dummy; 2025-07-03 22:06:30.192 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.192 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.202 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.202 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.212 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.212 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.214 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.214 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.216 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.216 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.220 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.220 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.222 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.222 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.251 UTC client backend[24359] pg_regress/publication ERROR: no schema has been selected for CURRENT_SCHEMA 2025-07-03 22:06:30.251 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA CURRENT_SCHEMA; 2025-07-03 22:06:30.251 UTC client backend[24359] pg_regress/publication ERROR: invalid publication object list at character 43 2025-07-03 22:06:30.251 UTC client backend[24359] pg_regress/publication DETAIL: One of TABLE or TABLES IN SCHEMA must be specified before a standalone table or schema name. 2025-07-03 22:06:30.251 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema1 FOR CURRENT_SCHEMA; 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication ERROR: syntax error at or near "CURRENT_SCHEMA" at character 49 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema1 FOR TABLE CURRENT_SCHEMA; 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA non_existent_schema; 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication ERROR: cannot add schema "pg_catalog" to publication 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication DETAIL: This operation is not supported for system schemas. 2025-07-03 22:06:30.252 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_forschema FOR TABLES IN SCHEMA pg_catalog; 2025-07-03 22:06:30.255 UTC client backend[24359] pg_regress/publication ERROR: schema "testpub_view" does not exist 2025-07-03 22:06:30.255 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub1_forschema1 FOR TABLES IN SCHEMA testpub_view; 2025-07-03 22:06:30.268 UTC client backend[24359] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-07-03 22:06:30.268 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA non_existent_schema; 2025-07-03 22:06:30.270 UTC client backend[24359] pg_regress/publication ERROR: schema "pub_test1" is already member of publication "testpub1_forschema" 2025-07-03 22:06:30.270 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA pub_test1; 2025-07-03 22:06:30.275 UTC client backend[24359] pg_regress/publication ERROR: tables from schema "pub_test2" are not part of the publication 2025-07-03 22:06:30.275 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema DROP TABLES IN SCHEMA pub_test2; 2025-07-03 22:06:30.278 UTC client backend[24359] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-07-03 22:06:30.278 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema DROP TABLES IN SCHEMA non_existent_schema; 2025-07-03 22:06:30.286 UTC client backend[24359] pg_regress/publication ERROR: schema "non_existent_schema" does not exist 2025-07-03 22:06:30.286 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema SET TABLES IN SCHEMA non_existent_schema; 2025-07-03 22:06:30.293 UTC client backend[24359] pg_regress/publication ERROR: syntax error at or near "(" at character 63 2025-07-03 22:06:30.293 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA foo (a, b); 2025-07-03 22:06:30.294 UTC client backend[24359] pg_regress/publication ERROR: column specification not allowed for schema at character 64 2025-07-03 22:06:30.294 UTC client backend[24359] pg_regress/publication STATEMENT: ALTER PUBLICATION testpub1_forschema ADD TABLES IN SCHEMA foo, bar (a, b); 2025-07-03 22:06:30.303 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "tbl" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.303 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.303 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_test1.tbl SET id = 2; 2025-07-03 22:06:30.305 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "tbl" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.305 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.305 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_test1.tbl SET id = 2; 2025-07-03 22:06:30.318 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.318 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_testpart1.parent1 set a = 1; 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.319 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_testpart2.child_parent1 set a = 1; 2025-07-03 22:06:30.336 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.336 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.336 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "child_parent1" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.336 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.336 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_testpart2.child_parent1 set a = 1; 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "child_parent2" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_testpart2.parent2 set a = 1; 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication ERROR: cannot update table "child_parent2" because it does not have a replica identity and publishes updates 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. 2025-07-03 22:06:30.337 UTC client backend[24359] pg_regress/publication STATEMENT: UPDATE pub_testpart1.child_parent2 set a = 1; 2025-07-03 22:06:30.338 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.338 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.349 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.349 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.352 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.352 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:30.375 UTC client backend[24359] pg_regress/publication ERROR: invalid publication object list at character 38 2025-07-03 22:06:30.375 UTC client backend[24359] pg_regress/publication DETAIL: One of TABLE or TABLES IN SCHEMA must be specified before a standalone table or schema name. 2025-07-03 22:06:30.375 UTC client backend[24359] pg_regress/publication STATEMENT: CREATE PUBLICATION testpub_error FOR pub_test2.tbl1; 2025-07-03 22:06:30.472 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:30.472 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:31.488 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:31.488 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:33.050 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:33.050 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:33.907 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:33.907 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.246 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.246 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.797 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.797 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.804 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.804 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.816 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.816 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.862 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.862 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.876 UTC client backend[24359] pg_regress/publication WARNING: "wal_level" is insufficient to publish logical changes 2025-07-03 22:06:35.876 UTC client backend[24359] pg_regress/publication HINT: Set "wal_level" to "logical" before creating subscriptions. 2025-07-03 22:06:35.927 UTC client backend[24359] pg_regress/publication LOG: disconnection: session time: 0:00:07.673 user=postgres database=regression host=[local] 2025-07-03 22:06:36.083 UTC not initialized[25217] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.091 UTC not initialized[25221] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.093 UTC client backend[25221] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.093 UTC client backend[25221] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_key 2025-07-03 22:06:36.094 UTC client backend[25217] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.094 UTC client backend[25217] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/guc 2025-07-03 22:06:36.107 UTC not initialized[25223] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.111 UTC not initialized[25222] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.112 UTC not initialized[25224] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.112 UTC client backend[25222] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.112 UTC client backend[25222] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/dependency 2025-07-03 22:06:36.113 UTC client backend[25224] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.113 UTC client backend[25224] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/select_views 2025-07-03 22:06:36.116 UTC client backend[25223] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.116 UTC client backend[25223] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/cluster 2025-07-03 22:06:36.123 UTC not initialized[25228] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.123 UTC not initialized[25229] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.124 UTC client backend[25228] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.124 UTC client backend[25228] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsdicts 2025-07-03 22:06:36.124 UTC client backend[25229] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.124 UTC client backend[25229] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/combocid 2025-07-03 22:06:36.125 UTC not initialized[25230] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.126 UTC client backend[25230] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.126 UTC client backend[25230] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/tsearch 2025-07-03 22:06:36.126 UTC not initialized[25231] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.136 UTC client backend[25231] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.136 UTC client backend[25231] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/bitmapops 2025-07-03 22:06:36.147 UTC not initialized[25232] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.148 UTC not initialized[25233] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.148 UTC client backend[25232] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.148 UTC client backend[25232] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/window 2025-07-03 22:06:36.157 UTC not initialized[25237] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.158 UTC client backend[25237] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.158 UTC client backend[25237] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/xmlmap 2025-07-03 22:06:36.158 UTC client backend[25233] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.158 UTC client backend[25233] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/portals_p2 2025-07-03 22:06:36.163 UTC not initialized[25238] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.171 UTC client backend[25238] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.171 UTC client backend[25238] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_data 2025-07-03 22:06:36.183 UTC not initialized[25242] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.183 UTC not initialized[25241] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.183 UTC not initialized[25240] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.190 UTC client backend[25241] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.190 UTC client backend[25241] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/indirect_toast 2025-07-03 22:06:36.191 UTC client backend[25242] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.191 UTC client backend[25242] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/functional_deps 2025-07-03 22:06:36.192 UTC client backend[25240] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.192 UTC client backend[25240] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/advisory_lock 2025-07-03 22:06:36.211 UTC not initialized[25243] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:36.212 UTC client backend[25243] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:36.212 UTC client backend[25243] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/equivclass 2025-07-03 22:06:36.235 UTC client backend[25224] pg_regress/select_views LOG: connection ready: setup total=142.518 ms, fork=19.124 ms, authentication=0.385 ms 2025-07-03 22:06:36.256 UTC client backend[25217] pg_regress/guc LOG: connection ready: setup total=194.998 ms, fork=19.203 ms, authentication=1.576 ms 2025-07-03 22:06:36.266 UTC client backend[25223] pg_regress/cluster LOG: connection ready: setup total=178.297 ms, fork=16.235 ms, authentication=0.391 ms 2025-07-03 22:06:36.269 UTC client backend[25221] pg_regress/foreign_key LOG: connection ready: setup total=190.566 ms, fork=11.877 ms, authentication=0.416 ms 2025-07-03 22:06:36.271 UTC client backend[25217] pg_regress/guc ERROR: invalid value for parameter "IntervalStyle": "asd" 2025-07-03 22:06:36.271 UTC client backend[25217] pg_regress/guc HINT: Available values: postgres, postgres_verbose, sql_standard, iso_8601. 2025-07-03 22:06:36.271 UTC client backend[25217] pg_regress/guc STATEMENT: SET intervalstyle to 'asd'; 2025-07-03 22:06:36.272 UTC client backend[25237] pg_regress/xmlmap LOG: connection ready: setup total=148.722 ms, fork=33.119 ms, authentication=0.368 ms 2025-07-03 22:06:36.275 UTC client backend[25217] pg_regress/guc WARNING: SET LOCAL can only be used in transaction blocks 2025-07-03 22:06:36.275 UTC client backend[25217] pg_regress/guc WARNING: SET LOCAL can only be used in transaction blocks 2025-07-03 22:06:36.279 UTC client backend[25238] pg_regress/foreign_data LOG: connection ready: setup total=130.312 ms, fork=4.530 ms, authentication=6.540 ms 2025-07-03 22:06:36.280 UTC client backend[25222] pg_regress/dependency LOG: connection ready: setup total=194.949 ms, fork=21.646 ms, authentication=0.406 ms 2025-07-03 22:06:36.283 UTC client backend[25230] pg_regress/tsearch LOG: connection ready: setup total=178.405 ms, fork=19.190 ms, authentication=0.369 ms 2025-07-03 22:06:36.284 UTC client backend[25229] pg_regress/combocid LOG: connection ready: setup total=180.972 ms, fork=16.636 ms, authentication=0.374 ms 2025-07-03 22:06:36.299 UTC client backend[25242] pg_regress/functional_deps LOG: connection ready: setup total=132.093 ms, fork=9.892 ms, authentication=7.088 ms 2025-07-03 22:06:36.302 UTC client backend[25233] pg_regress/portals_p2 LOG: connection ready: setup total=180.619 ms, fork=22.899 ms, authentication=3.268 ms 2025-07-03 22:06:36.311 UTC client backend[25232] pg_regress/window LOG: connection ready: setup total=194.804 ms, fork=27.166 ms, authentication=0.387 ms 2025-07-03 22:06:36.313 UTC client backend[25231] pg_regress/bitmapops LOG: connection ready: setup total=204.445 ms, fork=14.291 ms, authentication=9.706 ms 2025-07-03 22:06:36.315 UTC client backend[25228] pg_regress/tsdicts LOG: connection ready: setup total=214.220 ms, fork=19.609 ms, authentication=0.398 ms 2025-07-03 22:06:36.350 UTC client backend[25240] pg_regress/advisory_lock LOG: connection ready: setup total=199.846 ms, fork=26.676 ms, authentication=0.385 ms 2025-07-03 22:06:36.353 UTC client backend[25241] pg_regress/indirect_toast LOG: connection ready: setup total=187.550 ms, fork=12.468 ms, authentication=0.406 ms 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc ERROR: invalid value for parameter "seq_page_cost": "NaN" 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc STATEMENT: SET seq_page_cost TO 'NaN'; 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc ERROR: 10000 ms is outside the valid range for parameter "vacuum_cost_delay" (0 ms .. 100 ms) 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc STATEMENT: SET vacuum_cost_delay TO '10s'; 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "no_such_variable" 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc STATEMENT: SET no_such_variable TO 42; 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "custom.my_guc" 2025-07-03 22:06:36.368 UTC client backend[25217] pg_regress/guc STATEMENT: SHOW custom.my_guc; 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc ERROR: invalid configuration parameter name "custom.bad-guc" 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc DETAIL: Custom parameter names must be two or more simple identifiers separated by dots. 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc STATEMENT: SET custom."bad-guc" = 42; 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "custom.bad-guc" 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc STATEMENT: SHOW custom."bad-guc"; 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc ERROR: invalid configuration parameter name "special.weird name" 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc DETAIL: Custom parameter names must be two or more simple identifiers separated by dots. 2025-07-03 22:06:36.374 UTC client backend[25217] pg_regress/guc STATEMENT: SET special."weird name" = 'foo'; 2025-07-03 22:06:36.375 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "special.weird name" 2025-07-03 22:06:36.375 UTC client backend[25217] pg_regress/guc STATEMENT: SHOW special."weird name"; 2025-07-03 22:06:36.376 UTC client backend[25217] pg_regress/guc WARNING: invalid configuration parameter name "plpgsql.extra_foo_warnings", removing it 2025-07-03 22:06:36.376 UTC client backend[25217] pg_regress/guc DETAIL: "plpgsql" is now a reserved prefix. 2025-07-03 22:06:36.377 UTC client backend[25217] pg_regress/guc ERROR: invalid configuration parameter name "plpgsql.extra_foo_warnings" 2025-07-03 22:06:36.377 UTC client backend[25217] pg_regress/guc DETAIL: "plpgsql" is a reserved prefix. 2025-07-03 22:06:36.377 UTC client backend[25217] pg_regress/guc STATEMENT: SET plpgsql.extra_foo_warnings = true; 2025-07-03 22:06:36.378 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "plpgsql.extra_foo_warnings" 2025-07-03 22:06:36.378 UTC client backend[25217] pg_regress/guc STATEMENT: SHOW plpgsql.extra_foo_warnings; 2025-07-03 22:06:36.394 UTC client backend[25238] pg_regress/foreign_data ERROR: function bar(text[], oid) does not exist 2025-07-03 22:06:36.394 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo VALIDATOR bar; 2025-07-03 22:06:36.401 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_user" cannot be dropped because some objects depend on it 2025-07-03 22:06:36.401 UTC client backend[25222] pg_regress/dependency DETAIL: privileges for table deptest 2025-07-03 22:06:36.401 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP USER regress_dep_user; 2025-07-03 22:06:36.401 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" already exists 2025-07-03 22:06:36.401 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:36.404 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_group" cannot be dropped because some objects depend on it 2025-07-03 22:06:36.404 UTC client backend[25222] pg_regress/dependency DETAIL: privileges for table deptest 2025-07-03 22:06:36.404 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP GROUP regress_dep_group; 2025-07-03 22:06:36.415 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_user" cannot be dropped because some objects depend on it 2025-07-03 22:06:36.415 UTC client backend[25222] pg_regress/dependency DETAIL: privileges for table deptest 2025-07-03 22:06:36.415 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP USER regress_dep_user; 2025-07-03 22:06:36.422 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-07-03 22:06:36.429 UTC client backend[25243] pg_regress/equivclass LOG: connection ready: setup total=260.957 ms, fork=38.894 ms, authentication=0.397 ms 2025-07-03 22:06:36.434 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:36.434 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(1) is not present in table "pktable". 2025-07-03 22:06:36.434 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE FKTABLE ALTER CONSTRAINT fktable_ftest1_fkey ENFORCED; 2025-07-03 22:06:36.436 UTC client backend[25233] pg_regress/portals_p2 LOG: disconnection: session time: 0:00:00.291 user=postgres database=regression host=[local] 2025-07-03 22:06:36.436 UTC client backend[25242] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.436 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY title; 2025-07-03 22:06:36.439 UTC client backend[25242] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.439 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY body; 2025-07-03 22:06:36.440 UTC client backend[25242] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.440 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT id, keywords, title, body, created FROM articles GROUP BY keywords; 2025-07-03 22:06:36.446 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_user3" cannot be dropped because some objects depend on it 2025-07-03 22:06:36.446 UTC client backend[25222] pg_regress/dependency DETAIL: owner of sequence deptest_f1_seq owner of table deptest 2025-07-03 22:06:36.446 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP USER regress_dep_user3; 2025-07-03 22:06:36.449 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-07-03 22:06:36.449 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-07-03 22:06:36.449 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-07-03 22:06:36.455 UTC client backend[25242] pg_regress/functional_deps ERROR: column "a.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.455 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT a.id, a.keywords, a.title, a.body, a.created FROM articles AS a, articles_in_category AS aic WHERE a.id = aic.article_id AND aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id, aic.category_id; 2025-07-03 22:06:36.463 UTC client backend[25242] pg_regress/functional_deps ERROR: column "a.id" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.463 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT a.id, a.keywords, a.title, a.body, a.created FROM articles AS a JOIN articles_in_category AS aic ON a.id = aic.article_id WHERE aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id, aic.category_id; 2025-07-03 22:06:36.465 UTC client backend[25238] pg_regress/foreign_data ERROR: option "testing" provided more than once 2025-07-03 22:06:36.465 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo OPTIONS (testing '1', testing '2'); 2025-07-03 22:06:36.469 UTC client backend[25242] pg_regress/functional_deps ERROR: column "aic.changed" must appear in the GROUP BY clause or be used in an aggregate function at character 8 2025-07-03 22:06:36.469 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT aic.changed FROM articles AS a JOIN articles_in_category AS aic ON a.id = aic.article_id WHERE aic.category_id in (14,62,70,53,138) GROUP BY aic.article_id; 2025-07-03 22:06:36.471 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-07-03 22:06:36.471 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-07-03 22:06:36.471 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ExclusiveLock 2025-07-03 22:06:36.471 UTC client backend[25240] pg_regress/advisory_lock WARNING: you don't own a lock of type ShareLock 2025-07-03 22:06:36.484 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:36.484 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(3) is not present in table "pktable". 2025-07-03 22:06:36.484 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (3, 4); 2025-07-03 22:06:36.487 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:36.487 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(100) is not present in table "pktable". 2025-07-03 22:06:36.487 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2); 2025-07-03 22:06:36.495 UTC client backend[25222] pg_regress/dependency ERROR: permission denied to drop objects 2025-07-03 22:06:36.495 UTC client backend[25222] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may drop objects owned by it. 2025-07-03 22:06:36.495 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP OWNED BY regress_dep_user1; 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency ERROR: permission denied to drop objects 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user2" may drop objects owned by it. 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP OWNED BY regress_dep_user0, regress_dep_user2; 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency ERROR: permission denied to reassign objects 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may reassign objects to it. 2025-07-03 22:06:36.496 UTC client backend[25222] pg_regress/dependency STATEMENT: REASSIGN OWNED BY regress_dep_user0 TO regress_dep_user1; 2025-07-03 22:06:36.497 UTC client backend[25222] pg_regress/dependency ERROR: permission denied to reassign objects 2025-07-03 22:06:36.497 UTC client backend[25222] pg_regress/dependency DETAIL: Only roles with privileges of role "regress_dep_user1" may reassign objects owned by it. 2025-07-03 22:06:36.497 UTC client backend[25222] pg_regress/dependency STATEMENT: REASSIGN OWNED BY regress_dep_user1 TO regress_dep_user0; 2025-07-03 22:06:36.497 UTC client backend[25228] pg_regress/tsdicts ERROR: invalid affix alias "GJUS" 2025-07-03 22:06:36.497 UTC client backend[25228] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=ispell_sample, AffFile=hunspell_sample_long ); 2025-07-03 22:06:36.497 UTC client backend[25228] pg_regress/tsdicts ERROR: invalid affix flag "SZ\" 2025-07-03 22:06:36.497 UTC client backend[25228] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=ispell_sample, AffFile=hunspell_sample_num ); 2025-07-03 22:06:36.513 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foo" 2025-07-03 22:06:36.513 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-07-03 22:06:36.513 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:36.528 UTC client backend[25228] pg_regress/tsdicts ERROR: invalid affix alias "302,301,202,303" 2025-07-03 22:06:36.528 UTC client backend[25228] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY hunspell_err ( Template=ispell, DictFile=hunspell_sample_num, AffFile=hunspell_sample_long ); 2025-07-03 22:06:36.529 UTC client backend[25242] pg_regress/functional_deps ERROR: column "p.name" must appear in the GROUP BY clause or be used in an aggregate function at character 20 2025-07-03 22:06:36.529 UTC client backend[25242] pg_regress/functional_deps STATEMENT: SELECT product_id, p.name, (sum(s.units) * p.price) AS sales FROM products p LEFT JOIN sales s USING (product_id) GROUP BY product_id; 2025-07-03 22:06:36.536 UTC client backend[25229] pg_regress/combocid LOG: disconnection: session time: 0:00:00.416 user=postgres database=regression host=[local] 2025-07-03 22:06:36.549 UTC client backend[25228] pg_regress/tsdicts ERROR: casesensitive requires a Boolean value 2025-07-03 22:06:36.549 UTC client backend[25228] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH DICTIONARY synonym (CaseSensitive = 2); 2025-07-03 22:06:36.560 UTC client backend[25238] pg_regress/foreign_data ERROR: function invalid_fdw_handler must return type fdw_handler 2025-07-03 22:06:36.560 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER test_fdw HANDLER invalid_fdw_handler; 2025-07-03 22:06:36.564 UTC client backend[25238] pg_regress/foreign_data ERROR: conflicting or redundant options at character 63 2025-07-03 22:06:36.564 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER test_fdw HANDLER test_fdw_handler HANDLER invalid_fdw_handler; 2025-07-03 22:06:36.567 UTC client backend[25240] pg_regress/advisory_lock LOG: disconnection: session time: 0:00:00.389 user=postgres database=regression host=[local] 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data ERROR: invalid option "nonexistent" 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data HINT: There are no valid options in this context. 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (nonexistent 'fdw'); 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 31 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data ERROR: function bar(text[], oid) does not exist 2025-07-03 22:06:36.570 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo VALIDATOR bar; 2025-07-03 22:06:36.575 UTC client backend[25217] pg_regress/guc ERROR: division by zero 2025-07-03 22:06:36.575 UTC client backend[25217] pg_regress/guc CONTEXT: SQL statement "SELECT 1/$1" PL/pgSQL function myfunc(integer) line 4 at PERFORM 2025-07-03 22:06:36.575 UTC client backend[25217] pg_regress/guc STATEMENT: select myfunc(0); 2025-07-03 22:06:36.600 UTC client backend[25238] pg_regress/foreign_data ERROR: option "c" not found 2025-07-03 22:06:36.600 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (SET c '4'); 2025-07-03 22:06:36.600 UTC client backend[25238] pg_regress/foreign_data ERROR: option "c" not found 2025-07-03 22:06:36.600 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (DROP c); 2025-07-03 22:06:36.603 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "nosuch.setting" 2025-07-03 22:06:36.603 UTC client backend[25217] pg_regress/guc STATEMENT: select current_setting('nosuch.setting'); 2025-07-03 22:06:36.604 UTC client backend[25217] pg_regress/guc ERROR: unrecognized configuration parameter "nosuch.setting" 2025-07-03 22:06:36.604 UTC client backend[25217] pg_regress/guc STATEMENT: select current_setting('nosuch.setting', false); 2025-07-03 22:06:36.614 UTC client backend[25217] pg_regress/guc ERROR: invalid value for parameter "default_text_search_config": "no_such_config" 2025-07-03 22:06:36.614 UTC client backend[25217] pg_regress/guc STATEMENT: create function func_with_bad_set() returns int as $$ select 1 $$ language sql set default_text_search_config = no_such_config; 2025-07-03 22:06:36.628 UTC client backend[25217] pg_regress/guc ERROR: invalid value for parameter "default_text_search_config": "no_such_config" 2025-07-03 22:06:36.628 UTC client backend[25217] pg_regress/guc STATEMENT: select func_with_bad_set(); 2025-07-03 22:06:36.633 UTC client backend[25217] pg_regress/guc ERROR: tables declared WITH OIDS are not supported 2025-07-03 22:06:36.633 UTC client backend[25217] pg_regress/guc STATEMENT: set default_with_oids to t; 2025-07-03 22:06:36.634 UTC client backend[25237] pg_regress/xmlmap LOG: disconnection: session time: 0:00:00.477 user=postgres database=regression host=[local] 2025-07-03 22:06:36.671 UTC client backend[25238] pg_regress/foreign_data ERROR: option "b" provided more than once 2025-07-03 22:06:36.671 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (b '4'); 2025-07-03 22:06:36.679 UTC client backend[25221] pg_regress/foreign_key ERROR: constraint "constrname_wrong" for table "fktable" does not exist 2025-07-03 22:06:36.679 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMENT ON CONSTRAINT constrname_wrong ON FKTABLE IS 'fk constraint comment'; 2025-07-03 22:06:36.691 UTC client backend[25242] pg_regress/functional_deps ERROR: column "articles.id" must appear in the GROUP BY clause or be used in an aggregate function at character 33 2025-07-03 22:06:36.691 UTC client backend[25242] pg_regress/functional_deps STATEMENT: CREATE TEMP VIEW fdv1 AS SELECT id, keywords, title, body, created FROM articles GROUP BY body; 2025-07-03 22:06:36.706 UTC client backend[25242] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-07-03 22:06:36.706 UTC client backend[25242] pg_regress/functional_deps DETAIL: view fdv1 depends on constraint articles_pkey on table articles 2025-07-03 22:06:36.706 UTC client backend[25242] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.706 UTC client backend[25242] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(100, 2) is not present in table "pktable". 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2, 4); 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(2, 2) is not present in table "pktable". 2025-07-03 22:06:36.712 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (2, 2, 4); 2025-07-03 22:06:36.717 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-07-03 22:06:36.717 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-07-03 22:06:36.717 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (ADD d '5'); 2025-07-03 22:06:36.742 UTC client backend[25228] pg_regress/tsdicts ERROR: unrecognized Ispell parameter: "DictFile" 2025-07-03 22:06:36.742 UTC client backend[25228] pg_regress/tsdicts STATEMENT: CREATE TEXT SEARCH DICTIONARY tsdict_case ( Template = ispell, "DictFile" = ispell_sample, "AffFile" = ispell_sample ); 2025-07-03 22:06:36.744 UTC client backend[25228] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-07-03 22:06:36.744 UTC client backend[25228] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING FOR not_a_token, not_a_token; 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (NULL, 2, 4); 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:36.745 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, NULL, 4); 2025-07-03 22:06:36.758 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname" 2025-07-03 22:06:36.758 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:36.758 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = NULL WHERE ftest1 = 1; 2025-07-03 22:06:36.759 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to change owner of foreign-data wrapper "foo" 2025-07-03 22:06:36.759 UTC client backend[25238] pg_regress/foreign_data HINT: The owner of a foreign-data wrapper must be a superuser. 2025-07-03 22:06:36.759 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OWNER TO regress_test_role; 2025-07-03 22:06:36.760 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-07-03 22:06:36.760 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-07-03 22:06:36.760 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (ADD e '6'); 2025-07-03 22:06:36.763 UTC client backend[25228] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-07-03 22:06:36.763 UTC client backend[25228] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING IF EXISTS FOR not_a_token, not_a_token; 2025-07-03 22:06:36.764 UTC client backend[25228] pg_regress/tsdicts ERROR: mapping for token type "word" does not exist 2025-07-03 22:06:36.764 UTC client backend[25228] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst DROP MAPPING FOR word; 2025-07-03 22:06:36.765 UTC client backend[25228] pg_regress/tsdicts ERROR: token type "not_a_token" does not exist 2025-07-03 22:06:36.765 UTC client backend[25228] pg_regress/tsdicts STATEMENT: ALTER TEXT SEARCH CONFIGURATION dummy_tst ADD MAPPING FOR not_a_token WITH ispell; 2025-07-03 22:06:36.768 UTC client backend[25242] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-07-03 22:06:36.768 UTC client backend[25242] pg_regress/functional_deps DETAIL: view fdv2 depends on constraint articles_pkey on table articles 2025-07-03 22:06:36.768 UTC client backend[25242] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.768 UTC client backend[25242] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-07-03 22:06:36.770 UTC client backend[25228] pg_regress/tsdicts LOG: disconnection: session time: 0:00:00.649 user=postgres database=regression host=[local] 2025-07-03 22:06:36.771 UTC client backend[25242] pg_regress/functional_deps ERROR: cannot drop constraint articles_in_category_pkey on table articles_in_category because other objects depend on it 2025-07-03 22:06:36.771 UTC client backend[25242] pg_regress/functional_deps DETAIL: view fdv2 depends on constraint articles_in_category_pkey on table articles_in_category 2025-07-03 22:06:36.771 UTC client backend[25242] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.771 UTC client backend[25242] pg_regress/functional_deps STATEMENT: ALTER TABLE articles_in_category DROP CONSTRAINT articles_in_category_pkey RESTRICT; 2025-07-03 22:06:36.804 UTC client backend[25242] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-07-03 22:06:36.804 UTC client backend[25242] pg_regress/functional_deps DETAIL: view fdv3 depends on constraint articles_pkey on table articles 2025-07-03 22:06:36.804 UTC client backend[25242] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.804 UTC client backend[25242] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-07-03 22:06:36.808 UTC client backend[25238] pg_regress/foreign_data ERROR: function invalid_fdw_handler must return type fdw_handler 2025-07-03 22:06:36.808 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo HANDLER invalid_fdw_handler; 2025-07-03 22:06:36.808 UTC client backend[25238] pg_regress/foreign_data ERROR: conflicting or redundant options at character 57 2025-07-03 22:06:36.808 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo HANDLER test_fdw_handler HANDLER anything; 2025-07-03 22:06:36.823 UTC client backend[25238] pg_regress/foreign_data WARNING: changing the foreign-data wrapper handler can change behavior of existing foreign tables 2025-07-03 22:06:36.832 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "nonexistent" does not exist 2025-07-03 22:06:36.832 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER nonexistent; 2025-07-03 22:06:36.836 UTC client backend[25242] pg_regress/functional_deps ERROR: cannot drop constraint articles_pkey on table articles because other objects depend on it 2025-07-03 22:06:36.836 UTC client backend[25242] pg_regress/functional_deps DETAIL: view fdv4 depends on constraint articles_pkey on table articles 2025-07-03 22:06:36.836 UTC client backend[25242] pg_regress/functional_deps HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.836 UTC client backend[25242] pg_regress/functional_deps STATEMENT: ALTER TABLE articles DROP CONSTRAINT articles_pkey RESTRICT; 2025-07-03 22:06:36.865 UTC client backend[25242] pg_regress/functional_deps ERROR: column "articles.keywords" must appear in the GROUP BY clause or be used in an aggregate function at character 29 2025-07-03 22:06:36.865 UTC client backend[25242] pg_regress/functional_deps STATEMENT: EXECUTE foo; 2025-07-03 22:06:36.866 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_role_super" cannot be dropped because some objects depend on it 2025-07-03 22:06:36.866 UTC client backend[25238] pg_regress/foreign_data DETAIL: owner of foreign-data wrapper foo 2025-07-03 22:06:36.866 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_role_super; 2025-07-03 22:06:36.908 UTC client backend[25238] pg_regress/foreign_data ERROR: user mapping for "regress_foreign_data_user" already exists for server "s1" 2025-07-03 22:06:36.908 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s1; 2025-07-03 22:06:36.938 UTC client backend[25217] pg_regress/guc LOG: disconnection: session time: 0:00:00.858 user=postgres database=regression host=[local] 2025-07-03 22:06:36.970 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot drop foreign-data wrapper foo because other objects depend on it 2025-07-03 22:06:36.970 UTC client backend[25238] pg_regress/foreign_data DETAIL: server s1 depends on foreign-data wrapper foo user mapping for regress_foreign_data_user on server s1 depends on server s1 2025-07-03 22:06:36.970 UTC client backend[25238] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:36.970 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:36.971 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-07-03 22:06:36.971 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo CASCADE; 2025-07-03 22:06:36.987 UTC client backend[25242] pg_regress/functional_deps LOG: disconnection: session time: 0:00:00.809 user=postgres database=regression host=[local] 2025-07-03 22:06:36.996 UTC client backend[25223] pg_regress/cluster ERROR: insert or update on table "clstr_tst" violates foreign key constraint "clstr_tst_con" 2025-07-03 22:06:36.996 UTC client backend[25223] pg_regress/cluster DETAIL: Key (b)=(1111) is not present in table "clstr_tst_s". 2025-07-03 22:06:36.996 UTC client backend[25223] pg_regress/cluster STATEMENT: INSERT INTO clstr_tst (b, c) VALUES (1111, 'this should fail'); 2025-07-03 22:06:37.023 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" does not exist 2025-07-03 22:06:37.023 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER s1 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:37.024 UTC client backend[25238] pg_regress/foreign_data ERROR: server "s1" already exists 2025-07-03 22:06:37.024 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER s1 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:37.035 UTC client backend[25238] pg_regress/foreign_data ERROR: invalid option "foo" 2025-07-03 22:06:37.035 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER s8 FOREIGN DATA WRAPPER postgresql OPTIONS (foo '1'); 2025-07-03 22:06:37.074 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:37.074 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER t1 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:37.080 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-07-03 22:06:37.080 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(100, 2) is not present in table "pktable". 2025-07-03 22:06:37.080 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2, 4); 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(2, 2) is not present in table "pktable". 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (2, 2, 4); 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (NULL, 2, 4); 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname2" 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:37.081 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, NULL, 4); 2025-07-03 22:06:37.086 UTC client backend[25243] pg_regress/equivclass LOG: disconnection: session time: 0:00:00.878 user=postgres database=regression host=[local] 2025-07-03 22:06:37.095 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:37.095 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER t2 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:37.113 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_user1" cannot be dropped because some objects depend on it 2025-07-03 22:06:37.113 UTC client backend[25222] pg_regress/dependency DETAIL: privileges for database regression privileges for table deptest1 owner of default privileges on new relations belonging to role regress_dep_user1 in schema deptest 2025-07-03 22:06:37.113 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP USER regress_dep_user1; 2025-07-03 22:06:37.119 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table pktable because other objects depend on it 2025-07-03 22:06:37.119 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint constrname2 on table fktable depends on table pktable 2025-07-03 22:06:37.119 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:37.119 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE PKTABLE; 2025-07-03 22:06:37.125 UTC client backend[25222] pg_regress/dependency ERROR: role "regress_dep_user2" cannot be dropped because some objects depend on it 2025-07-03 22:06:37.125 UTC client backend[25222] pg_regress/dependency DETAIL: owner of schema deptest owner of sequence deptest_a_seq owner of table deptest owner of function deptest_func() owner of type deptest_enum owner of type deptest_range owner of table deptest2 owner of sequence ss1 owner of type deptest_t 2025-07-03 22:06:37.125 UTC client backend[25222] pg_regress/dependency STATEMENT: DROP USER regress_dep_user2; 2025-07-03 22:06:37.127 UTC client backend[25230] pg_regress/tsearch ERROR: unrecognized parameter "foo" 2025-07-03 22:06:37.127 UTC client backend[25230] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(foo=1)); 2025-07-03 22:06:37.129 UTC client backend[25230] pg_regress/tsearch ERROR: value 0 out of bounds for option "siglen" 2025-07-03 22:06:37.129 UTC client backend[25230] pg_regress/tsearch DETAIL: Valid values are between "1" and "2024". 2025-07-03 22:06:37.129 UTC client backend[25230] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=0)); 2025-07-03 22:06:37.130 UTC client backend[25230] pg_regress/tsearch ERROR: value 2048 out of bounds for option "siglen" 2025-07-03 22:06:37.130 UTC client backend[25230] pg_regress/tsearch DETAIL: Valid values are between "1" and "2024". 2025-07-03 22:06:37.130 UTC client backend[25230] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=2048)); 2025-07-03 22:06:37.131 UTC client backend[25238] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 16 2025-07-03 22:06:37.131 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s0; 2025-07-03 22:06:37.131 UTC client backend[25238] pg_regress/foreign_data ERROR: server "s0" does not exist 2025-07-03 22:06:37.131 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s0 OPTIONS (a '1'); 2025-07-03 22:06:37.132 UTC client backend[25230] pg_regress/tsearch ERROR: unrecognized parameter "foo" 2025-07-03 22:06:37.132 UTC client backend[25230] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=100,foo='bar')); 2025-07-03 22:06:37.135 UTC client backend[25230] pg_regress/tsearch ERROR: parameter "siglen" specified more than once 2025-07-03 22:06:37.135 UTC client backend[25230] pg_regress/tsearch STATEMENT: CREATE INDEX wowidx1 ON test_tsvector USING gist (a tsvector_ops(siglen=100, siglen = 200)); 2025-07-03 22:06:37.151 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s1 2025-07-03 22:06:37.151 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 VERSION '1.1'; 2025-07-03 22:06:37.151 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s1 2025-07-03 22:06:37.151 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_role; 2025-07-03 22:06:37.154 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:37.154 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_role2; 2025-07-03 22:06:37.163 UTC client backend[25238] pg_regress/foreign_data ERROR: invalid option "foo" 2025-07-03 22:06:37.163 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s8 OPTIONS (foo '1'); 2025-07-03 22:06:37.164 UTC client backend[25238] pg_regress/foreign_data ERROR: must be able to SET ROLE "regress_test_indirect" 2025-07-03 22:06:37.164 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s1 OWNER TO regress_test_indirect; 2025-07-03 22:06:37.176 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_indirect" cannot be dropped because some objects depend on it 2025-07-03 22:06:37.176 UTC client backend[25238] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper foo owner of server s1 2025-07-03 22:06:37.176 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_indirect; 2025-07-03 22:06:37.178 UTC client backend[25223] pg_regress/cluster ERROR: there is no previously clustered index for table "clstr_2" 2025-07-03 22:06:37.178 UTC client backend[25223] pg_regress/cluster STATEMENT: CLUSTER clstr_2; 2025-07-03 22:06:37.228 UTC client backend[25238] pg_regress/foreign_data ERROR: server "nonexistent" does not exist 2025-07-03 22:06:37.228 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER nonexistent; 2025-07-03 22:06:37.230 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s2 2025-07-03 22:06:37.230 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER s2; 2025-07-03 22:06:37.232 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:37.232 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(100) is not present in table "pktable". 2025-07-03 22:06:37.232 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (100, 2); 2025-07-03 22:06:37.235 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-07-03 22:06:37.235 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ptest1)=(1) is still referenced from table "fktable". 2025-07-03 22:06:37.235 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM PKTABLE WHERE ptest1=1; 2025-07-03 22:06:37.239 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-07-03 22:06:37.239 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ptest1)=(2) is still referenced from table "fktable". 2025-07-03 22:06:37.239 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE SET ptest1=0 WHERE ptest1=2; 2025-07-03 22:06:37.243 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot drop server s3 because other objects depend on it 2025-07-03 22:06:37.243 UTC client backend[25238] pg_regress/foreign_data DETAIL: user mapping for regress_foreign_data_user on server s3 depends on server s3 2025-07-03 22:06:37.243 UTC client backend[25238] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:37.243 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER s3; 2025-07-03 22:06:37.245 UTC client backend[25222] pg_regress/dependency LOG: disconnection: session time: 0:00:01.137 user=postgres database=regression host=[local] 2025-07-03 22:06:37.257 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-07-03 22:06:37.257 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR regress_test_missing_role SERVER s1; 2025-07-03 22:06:37.257 UTC client backend[25238] pg_regress/foreign_data ERROR: server "s1" does not exist 2025-07-03 22:06:37.257 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s1; 2025-07-03 22:06:37.258 UTC client backend[25238] pg_regress/foreign_data ERROR: user mapping for "regress_foreign_data_user" already exists for server "s4" 2025-07-03 22:06:37.258 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR user SERVER s4; 2025-07-03 22:06:37.260 UTC client backend[25238] pg_regress/foreign_data ERROR: invalid option "username" 2025-07-03 22:06:37.260 UTC client backend[25238] pg_regress/foreign_data HINT: Perhaps you meant the option "user". 2025-07-03 22:06:37.260 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR user SERVER s8 OPTIONS (username 'test', password 'secret'); 2025-07-03 22:06:37.263 UTC client backend[25223] pg_regress/cluster WARNING: permission denied to cluster "pg_toast_826", skipping it 2025-07-03 22:06:37.263 UTC client backend[25223] pg_regress/cluster WARNING: permission denied to cluster "clstr_2", skipping it 2025-07-03 22:06:37.265 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign server s7 2025-07-03 22:06:37.265 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR current_user SERVER s7; 2025-07-03 22:06:37.265 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s8 2025-07-03 22:06:37.265 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s8; 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_missing_role SERVER s4 OPTIONS (gotcha 'true'); 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data ERROR: server "ss4" does not exist 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR user SERVER ss4 OPTIONS (gotcha 'true'); 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data ERROR: user mapping for "public" does not exist for server "s5" 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR public SERVER s5 OPTIONS (gotcha 'true'); 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data ERROR: invalid option "username" 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data HINT: Perhaps you meant the option "user". 2025-07-03 22:06:37.287 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR current_user SERVER s8 OPTIONS (username 'test'); 2025-07-03 22:06:37.290 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-07-03 22:06:37.290 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR public SERVER s4 OPTIONS (ADD modified '1'); 2025-07-03 22:06:37.303 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_missing_role" does not exist 2025-07-03 22:06:37.303 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_missing_role SERVER s4; 2025-07-03 22:06:37.304 UTC client backend[25238] pg_regress/foreign_data ERROR: server "ss4" does not exist 2025-07-03 22:06:37.304 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR user SERVER ss4; 2025-07-03 22:06:37.304 UTC client backend[25238] pg_regress/foreign_data ERROR: user mapping for "public" does not exist for server "s7" 2025-07-03 22:06:37.304 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR public SERVER s7; 2025-07-03 22:06:37.308 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s8 2025-07-03 22:06:37.308 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR public SERVER s8; 2025-07-03 22:06:37.323 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" 2025-07-03 22:06:37.323 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:37.323 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) REFERENCES PKTABLE MATCH FULL; 2025-07-03 22:06:37.329 UTC client backend[25238] pg_regress/foreign_data ERROR: syntax error at or near ";" at character 28 2025-07-03 22:06:37.329 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 (); 2025-07-03 22:06:37.331 UTC client backend[25238] pg_regress/foreign_data ERROR: server "no_server" does not exist 2025-07-03 22:06:37.331 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 () SERVER no_server; 2025-07-03 22:06:37.331 UTC client backend[25238] pg_regress/foreign_data ERROR: primary key constraints are not supported on foreign tables at character 67 2025-07-03 22:06:37.331 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') PRIMARY KEY, c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-07-03 22:06:37.352 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign key constraints are not supported on foreign tables at character 67 2025-07-03 22:06:37.352 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') REFERENCES ref_table (id), c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-07-03 22:06:37.359 UTC client backend[25238] pg_regress/foreign_data ERROR: unique constraints are not supported on foreign tables at character 137 2025-07-03 22:06:37.359 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft1 ( c1 integer OPTIONS ("param 1" 'val1') NOT NULL, c2 text OPTIONS (param2 'val2', param3 'val3'), c3 date, UNIQUE (c3) ) SERVER s0 OPTIONS (delimiter ',', quote '"', "be quoted" 'value'); 2025-07-03 22:06:37.384 UTC client backend[25224] pg_regress/select_views LOG: disconnection: session time: 0:00:01.272 user=postgres database=regression host=[local] 2025-07-03 22:06:37.479 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-07-03 22:06:37.479 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-07-03 22:06:37.479 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-07-03 22:06:37.484 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "constrname3" on table "fktable" 2025-07-03 22:06:37.484 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ptest1, ptest2, ptest3)=(1, 2, 3) is still referenced from table "fktable". 2025-07-03 22:06:37.484 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE set ptest2=5 where ptest2=2; 2025-07-03 22:06:37.499 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "constrname3" on table "fktable" 2025-07-03 22:06:37.499 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ptest1, ptest2, ptest3)=(1, 2, 3) is still referenced from table "fktable". 2025-07-03 22:06:37.499 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM PKTABLE where ptest1=1 and ptest2=2 and ptest3=3; 2025-07-03 22:06:37.557 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create index on relation "ft1" 2025-07-03 22:06:37.557 UTC client backend[25238] pg_regress/foreign_data DETAIL: This operation is not supported for foreign tables. 2025-07-03 22:06:37.557 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE INDEX id_ft1_c2 ON ft1 (c2); 2025-07-03 22:06:37.568 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "dummy" has no handler 2025-07-03 22:06:37.568 UTC client backend[25238] pg_regress/foreign_data STATEMENT: SELECT * FROM ft1; 2025-07-03 22:06:37.568 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "dummy" has no handler 2025-07-03 22:06:37.568 UTC client backend[25238] pg_regress/foreign_data STATEMENT: EXPLAIN SELECT * FROM ft1; 2025-07-03 22:06:37.585 UTC client backend[25223] pg_regress/cluster ERROR: cannot cluster on invalid index "clstrpart_only_idx" 2025-07-03 22:06:37.585 UTC client backend[25223] pg_regress/cluster STATEMENT: CLUSTER clstrpart USING clstrpart_only_idx; 2025-07-03 22:06:37.593 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-07-03 22:06:37.593 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-07-03 22:06:37.593 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE UNIQUE INDEX ON lt1 (a); 2025-07-03 22:06:37.599 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-07-03 22:06:37.599 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-07-03 22:06:37.599 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ADD PRIMARY KEY (a); 2025-07-03 22:06:37.702 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create foreign partition of partitioned table "lt1" 2025-07-03 22:06:37.702 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1" contains indexes that are unique. 2025-07-03 22:06:37.702 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft_part1 PARTITION OF lt1 FOR VALUES FROM (0) TO (1000) SERVER s0; 2025-07-03 22:06:37.704 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-07-03 22:06:37.704 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-07-03 22:06:37.704 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-07-03 22:06:37.705 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot attach foreign table "ft_part2" as partition of partitioned table "lt1" 2025-07-03 22:06:37.705 UTC client backend[25238] pg_regress/foreign_data DETAIL: Partitioned table "lt1" contains unique indexes. 2025-07-03 22:06:37.705 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ATTACH PARTITION ft_part2 FOR VALUES FROM (1000) TO (2000); 2025-07-03 22:06:37.790 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1" 2025-07-03 22:06:37.790 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1" contains partitions that are foreign tables. 2025-07-03 22:06:37.790 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE UNIQUE INDEX ON lt1 (a); 2025-07-03 22:06:37.825 UTC client backend[25232] pg_regress/window ERROR: argument of ROWS must not contain variables at character 40 2025-07-03 22:06:37.825 UTC client backend[25232] pg_regress/window STATEMENT: SELECT sum(unique1) over (rows between unbounded.x preceding and unbounded.x following), unique1, four FROM tenk1, (values (1)) as unbounded(x) WHERE unique1 < 10; 2025-07-03 22:06:37.827 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create unique index on partitioned table "lt1_part1" 2025-07-03 22:06:37.827 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1_part1" contains partitions that are foreign tables. 2025-07-03 22:06:37.827 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1 ADD PRIMARY KEY (a); 2025-07-03 22:06:37.838 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-07-03 22:06:37.838 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-07-03 22:06:37.838 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-07-03 22:06:37.876 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.876 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_float4, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_float4 range between 1.1 preceding and 'NaN' following); 2025-07-03 22:06:37.884 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create foreign partition of partitioned table "lt1_part1" 2025-07-03 22:06:37.884 UTC client backend[25238] pg_regress/foreign_data DETAIL: Table "lt1_part1" contains indexes that are unique. 2025-07-03 22:06:37.884 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE ft_part_1_1 PARTITION OF lt1_part1 FOR VALUES FROM (0) TO (100) SERVER s0; 2025-07-03 22:06:37.893 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.893 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_float8, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_float8 range between 1.1 preceding and 'NaN' following); 2025-07-03 22:06:37.901 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot attach foreign table "ft_part_1_2" as partition of partitioned table "lt1_part1" 2025-07-03 22:06:37.901 UTC client backend[25238] pg_regress/foreign_data DETAIL: Partitioned table "lt1_part1" contains unique indexes. 2025-07-03 22:06:37.901 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE lt1_part1 ATTACH PARTITION ft_part_1_2 FOR VALUES FROM (100) TO (200); 2025-07-03 22:06:37.904 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type numeric and offset type double precision at character 158 2025-07-03 22:06:37.904 UTC client backend[25232] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-07-03 22:06:37.904 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_numeric, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_numeric range between 1 preceding and 1.1::float8 following); 2025-07-03 22:06:37.914 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.914 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_numeric, first_value(id) over w, last_value(id) over w from numerics window w as (order by f_numeric range between 1.1 preceding and 'NaN' following); 2025-07-03 22:06:37.934 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.934 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_time, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_time desc range between '-70 min' preceding and '2 hours' following); 2025-07-03 22:06:37.940 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.940 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_time, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_time range between '-infinity'::interval following and 'infinity'::interval following); 2025-07-03 22:06:37.951 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.951 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timetz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timetz desc range between '70 min' preceding and '-2 hours' following); 2025-07-03 22:06:37.963 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.963 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timetz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timetz range between 'infinity'::interval following and '-infinity'::interval following); 2025-07-03 22:06:37.967 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-07-03 22:06:37.967 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(1, 2, 7) is not present in table "pktable". 2025-07-03 22:06:37.967 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES (1, 2, 7, 6); 2025-07-03 22:06:37.970 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "constrname3" 2025-07-03 22:06:37.970 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2, ftest3)=(0, -1, -2) is not present in table "pktable". 2025-07-03 22:06:37.970 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE PKTABLE set ptest2=5 where ptest2=2; 2025-07-03 22:06:37.974 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.974 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_interval, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_interval desc range between '-1 year' preceding and '1 year' following); 2025-07-03 22:06:37.977 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.977 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_interval, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_interval range between '-infinity'::interval following and 'infinity'::interval following); 2025-07-03 22:06:37.984 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.984 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timestamptz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamptz desc range between '1 year' preceding and '-1 year' following); 2025-07-03 22:06:37.988 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:37.988 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timestamptz, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamptz range between '-infinity'::interval following and 'infinity'::interval following); 2025-07-03 22:06:37.991 UTC client backend[25223] pg_regress/cluster ERROR: there is no previously clustered index for table "clstrpart" 2025-07-03 22:06:37.991 UTC client backend[25223] pg_regress/cluster STATEMENT: CLUSTER clstrpart; 2025-07-03 22:06:37.992 UTC client backend[25223] pg_regress/cluster ERROR: cannot mark index clustered in partitioned table 2025-07-03 22:06:37.992 UTC client backend[25223] pg_regress/cluster STATEMENT: ALTER TABLE clstrpart SET WITHOUT CLUSTER; 2025-07-03 22:06:37.993 UTC client backend[25223] pg_regress/cluster ERROR: cannot mark index clustered in partitioned table 2025-07-03 22:06:37.993 UTC client backend[25223] pg_regress/cluster STATEMENT: ALTER TABLE clstrpart CLUSTER ON clstrpart_idx; 2025-07-03 22:06:38.003 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:38.003 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timestamp, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamp desc range between '-1 year' preceding and '1 year' following); 2025-07-03 22:06:38.005 UTC client backend[25238] pg_regress/foreign_data ERROR: "ft1" is not a table 2025-07-03 22:06:38.005 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN c8 TYPE char(10) USING '0'; 2025-07-03 22:06:38.006 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:38.006 UTC client backend[25232] pg_regress/window STATEMENT: select id, f_timestamp, first_value(id) over w, last_value(id) over w from datetimes window w as (order by f_timestamp range between '-infinity'::interval following and 'infinity'::interval following); 2025-07-03 22:06:38.006 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-07-03 22:06:38.006 UTC client backend[25232] pg_regress/window STATEMENT: select sum(salary) over (order by enroll_date, salary range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.011 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-07-03 22:06:38.011 UTC client backend[25232] pg_regress/window STATEMENT: select sum(salary) over (range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.011 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type text at character 57 2025-07-03 22:06:38.011 UTC client backend[25232] pg_regress/window STATEMENT: select sum(salary) over (order by depname range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.014 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type date and offset type integer at character 66 2025-07-03 22:06:38.014 UTC client backend[25232] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-07-03 22:06:38.014 UTC client backend[25232] pg_regress/window STATEMENT: select max(enroll_date) over (order by enroll_date range between 1 preceding and 2 following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.014 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:38.014 UTC client backend[25232] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between -1 preceding and 2 following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.015 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:38.015 UTC client backend[25232] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between 1 preceding and -2 following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.015 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot alter system column "xmin" 2025-07-03 22:06:38.015 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN xmin OPTIONS (ADD p1 'v1'); 2025-07-03 22:06:38.017 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING is not supported for column type integer and offset type interval at character 61 2025-07-03 22:06:38.017 UTC client backend[25232] pg_regress/window HINT: Cast the offset value to an appropriate type. 2025-07-03 22:06:38.017 UTC client backend[25232] pg_regress/window STATEMENT: select max(enroll_date) over (order by salary range between '1 year'::interval preceding and '2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.018 UTC client backend[25232] pg_regress/window ERROR: invalid preceding or following size in window function 2025-07-03 22:06:38.018 UTC client backend[25232] pg_regress/window STATEMENT: select max(enroll_date) over (order by enroll_date range between '1 year'::interval preceding and '-2 years'::interval following exclude ties), salary, enroll_date from empsalary; 2025-07-03 22:06:38.052 UTC client backend[25231] pg_regress/bitmapops LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp25231.0.fileset/0.0", size 1335296 2025-07-03 22:06:38.052 UTC client backend[25231] pg_regress/bitmapops STATEMENT: CREATE INDEX i_bmtest_a ON bmscantest(a); 2025-07-03 22:06:38.052 UTC client backend[25221] pg_regress/foreign_key ERROR: column "bar" referenced in foreign key constraint does not exist 2025-07-03 22:06:38.052 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, id) REFERENCES PKTABLE ON DELETE SET NULL (bar)); 2025-07-03 22:06:38.054 UTC client backend[25221] pg_regress/foreign_key ERROR: column "foo" referenced in ON DELETE SET action must be part of foreign key 2025-07-03 22:06:38.054 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, id) REFERENCES PKTABLE ON DELETE SET NULL (foo)); 2025-07-03 22:06:38.065 UTC client backend[25221] pg_regress/foreign_key ERROR: a column list with SET NULL is only supported for ON DELETE actions at character 91 2025-07-03 22:06:38.065 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (tid int, id int, foo int, FOREIGN KEY (tid, foo) REFERENCES PKTABLE ON UPDATE SET NULL (foo)); 2025-07-03 22:06:38.095 UTC client backend[25223] pg_regress/cluster ERROR: permission denied for table ptnowner 2025-07-03 22:06:38.095 UTC client backend[25223] pg_regress/cluster STATEMENT: CLUSTER ptnowner USING ptnowner_i_idx; 2025-07-03 22:06:38.109 UTC client backend[25232] pg_regress/window ERROR: RANGE with offset PRECEDING/FOLLOWING requires exactly one ORDER BY column at character 25 2025-07-03 22:06:38.109 UTC client backend[25232] pg_regress/window STATEMENT: select f1, sum(f1) over (partition by f1 range between 1 preceding and 1 following) from t1 where f1 = f2; 2025-07-03 22:06:38.118 UTC client backend[25232] pg_regress/window ERROR: GROUPS mode requires an ORDER BY clause at character 25 2025-07-03 22:06:38.118 UTC client backend[25232] pg_regress/window STATEMENT: select f1, sum(f1) over (partition by f1 groups between 1 preceding and 1 following) from t1 where f1 = f2; 2025-07-03 22:06:38.128 UTC client backend[25223] pg_regress/cluster WARNING: permission denied to cluster "ptnowner2", skipping it 2025-07-03 22:06:38.135 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in window definitions at character 30 2025-07-03 22:06:38.135 UTC client backend[25232] pg_regress/window STATEMENT: SELECT rank() OVER (ORDER BY rank() OVER (ORDER BY random())); 2025-07-03 22:06:38.137 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in WHERE at character 31 2025-07-03 22:06:38.137 UTC client backend[25232] pg_regress/window STATEMENT: SELECT * FROM empsalary WHERE row_number() OVER (ORDER BY salary) < 10; 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in JOIN conditions at character 45 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: SELECT * FROM empsalary INNER JOIN tenk1 ON row_number() OVER (ORDER BY salary) < 10; 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in GROUP BY at character 8 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: SELECT rank() OVER (ORDER BY 1), count(*) FROM empsalary GROUP BY 1; 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: syntax error at or near "ORDER" at character 28 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: SELECT * FROM rank() OVER (ORDER BY random()); 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in WHERE at character 30 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: DELETE FROM empsalary WHERE (rank() OVER (ORDER BY random())) > 10; 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: window functions are not allowed in RETURNING at character 33 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: DELETE FROM empsalary RETURNING rank() OVER (ORDER BY random()); 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: window "w" is already defined at character 72 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: SELECT count(*) OVER w FROM tenk1 WINDOW w AS (ORDER BY unique1), w AS (ORDER BY unique1); 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window ERROR: syntax error at or near "ORDER" at character 40 2025-07-03 22:06:38.138 UTC client backend[25232] pg_regress/window STATEMENT: SELECT rank() OVER (PARTITION BY four, ORDER BY ten) FROM tenk1; 2025-07-03 22:06:38.139 UTC client backend[25232] pg_regress/window ERROR: count(*) must be used to call a parameterless aggregate function at character 8 2025-07-03 22:06:38.139 UTC client backend[25232] pg_regress/window STATEMENT: SELECT count() OVER () FROM tenk1; 2025-07-03 22:06:38.139 UTC client backend[25232] pg_regress/window ERROR: OVER specified, but generate_series is not a window function nor an aggregate function at character 8 2025-07-03 22:06:38.139 UTC client backend[25232] pg_regress/window STATEMENT: SELECT generate_series(1, 100) OVER () FROM empsalary; 2025-07-03 22:06:38.146 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot alter foreign table "ft1" because column "use_ft1_column_type.x" uses its row type 2025-07-03 22:06:38.146 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER COLUMN c8 SET DATA TYPE integer; 2025-07-03 22:06:38.167 UTC client backend[25238] pg_regress/foreign_data ERROR: primary key constraints are not supported on foreign tables at character 29 2025-07-03 22:06:38.167 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ADD PRIMARY KEY (c7); 2025-07-03 22:06:38.171 UTC client backend[25238] pg_regress/foreign_data ERROR: ALTER action ALTER CONSTRAINT cannot be performed on relation "ft1" 2025-07-03 22:06:38.171 UTC client backend[25238] pg_regress/foreign_data DETAIL: This operation is not supported for foreign tables. 2025-07-03 22:06:38.171 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 ALTER CONSTRAINT ft1_c9_check DEFERRABLE; 2025-07-03 22:06:38.175 UTC client backend[25238] pg_regress/foreign_data ERROR: constraint "no_const" of relation "ft1" does not exist 2025-07-03 22:06:38.175 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 DROP CONSTRAINT no_const; 2025-07-03 22:06:38.182 UTC client backend[25232] pg_regress/window ERROR: argument of ntile must be greater than zero 2025-07-03 22:06:38.182 UTC client backend[25232] pg_regress/window STATEMENT: SELECT ntile(0) OVER (ORDER BY ten), ten, four FROM tenk1; 2025-07-03 22:06:38.194 UTC client backend[25238] pg_regress/foreign_data ERROR: column "no_column" of relation "ft1" does not exist 2025-07-03 22:06:38.194 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 DROP COLUMN no_column; 2025-07-03 22:06:38.195 UTC client backend[25221] pg_regress/foreign_key ERROR: column "ftest2" referenced in foreign key constraint does not exist 2025-07-03 22:06:38.195 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL1 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (ftest2) REFERENCES PKTABLE); 2025-07-03 22:06:38.200 UTC client backend[25221] pg_regress/foreign_key ERROR: column "ptest2" referenced in foreign key constraint does not exist 2025-07-03 22:06:38.200 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL2 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (ftest1) REFERENCES PKTABLE(ptest2)); 2025-07-03 22:06:38.218 UTC client backend[25221] pg_regress/foreign_key ERROR: system columns cannot be used in foreign keys 2025-07-03 22:06:38.218 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL3 ( ftest1 int, CONSTRAINT fkfail1 FOREIGN KEY (tableoid) REFERENCES PKTABLE(someoid)); 2025-07-03 22:06:38.221 UTC client backend[25221] pg_regress/foreign_key ERROR: system columns cannot be used in foreign keys 2025-07-03 22:06:38.221 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL4 ( ftest1 oid, CONSTRAINT fkfail1 FOREIGN KEY (ftest1) REFERENCES PKTABLE(tableoid)); 2025-07-03 22:06:38.227 UTC client backend[25238] pg_regress/foreign_data ERROR: relation "ft1" does not exist 2025-07-03 22:06:38.227 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft1 SET TABLESPACE ts; 2025-07-03 22:06:38.229 UTC client backend[25241] pg_regress/indirect_toast LOG: disconnection: session time: 0:00:02.050 user=postgres database=regression host=[local] 2025-07-03 22:06:38.231 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot move an owned sequence into another schema 2025-07-03 22:06:38.231 UTC client backend[25238] pg_regress/foreign_data DETAIL: Sequence "ft1_c11_seq" is linked to table "ft1". 2025-07-03 22:06:38.231 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SEQUENCE foreign_schema.ft1_c11_seq SET SCHEMA public; 2025-07-03 22:06:38.269 UTC client backend[25232] pg_regress/window ERROR: argument of nth_value must be greater than zero 2025-07-03 22:06:38.269 UTC client backend[25232] pg_regress/window STATEMENT: SELECT nth_value(four, 0) OVER (ORDER BY ten), ten, four FROM tenk1; 2025-07-03 22:06:38.388 UTC client backend[25231] pg_regress/bitmapops LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp25231.1.fileset/1.0", size 761856 2025-07-03 22:06:38.388 UTC client backend[25231] pg_regress/bitmapops STATEMENT: CREATE INDEX i_bmtest_b ON bmscantest(b); 2025-07-03 22:06:38.388 UTC client backend[25231] pg_regress/bitmapops LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp25231.1.fileset/0.0", size 647168 2025-07-03 22:06:38.388 UTC client backend[25231] pg_regress/bitmapops STATEMENT: CREATE INDEX i_bmtest_b ON bmscantest(b); 2025-07-03 22:06:38.405 UTC client backend[25221] pg_regress/foreign_key ERROR: there is no unique constraint matching given keys for referenced table "pktable" 2025-07-03 22:06:38.405 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE_FAIL1 (ftest1 int REFERENCES pktable(ptest1)); 2025-07-03 22:06:38.406 UTC client backend[25221] pg_regress/foreign_key ERROR: table "fktable_fail1" does not exist 2025-07-03 22:06:38.406 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE FKTABLE_FAIL1; 2025-07-03 22:06:38.421 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-07-03 22:06:38.421 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:38.421 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 inet REFERENCES pktable); 2025-07-03 22:06:38.442 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-07-03 22:06:38.442 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:38.442 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 inet REFERENCES pktable(ptest1)); 2025-07-03 22:06:38.494 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:38.494 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-07-03 22:06:38.494 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-07-03 22:06:38.517 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:38.517 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-07-03 22:06:38.517 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = ftest1 + 1; 2025-07-03 22:06:38.561 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_fkey" cannot be implemented 2025-07-03 22:06:38.561 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: numeric and integer. 2025-07-03 22:06:38.561 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 numeric REFERENCES pktable); 2025-07-03 22:06:38.666 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:38.666 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-07-03 22:06:38.666 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO FKTABLE VALUES(43); 2025-07-03 22:06:38.670 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:38.670 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(43) is not present in table "pktable". 2025-07-03 22:06:38.670 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE FKTABLE SET ftest1 = ftest1 + 1; 2025-07-03 22:06:38.755 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:38.755 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer. 2025-07-03 22:06:38.755 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 cidr, ftest2 timestamp, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable); 2025-07-03 22:06:38.765 UTC client backend[25232] pg_regress/window ERROR: interval out of range 2025-07-03 22:06:38.765 UTC client backend[25232] pg_regress/window STATEMENT: SELECT x, avg(x) OVER(ROWS BETWEEN CURRENT ROW AND 2 FOLLOWING) FROM (VALUES (NULL::interval), ('3 days'::interval), ('infinity'::timestamptz - now()), ('6 days'::interval), ('-infinity'::interval)) v(x); 2025-07-03 22:06:38.768 UTC client backend[25232] pg_regress/window ERROR: interval out of range 2025-07-03 22:06:38.768 UTC client backend[25232] pg_regress/window STATEMENT: SELECT x, sum(x) OVER(ROWS BETWEEN CURRENT ROW AND 2 FOLLOWING) FROM (VALUES (NULL::interval), ('3 days'::interval), ('infinity'::timestamptz - now()), ('6 days'::interval), ('-infinity'::interval)) v(x); 2025-07-03 22:06:38.816 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:38.816 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer. 2025-07-03 22:06:38.816 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 cidr, ftest2 timestamp, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable(ptest1, ptest2)); 2025-07-03 22:06:38.846 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-07-03 22:06:38.846 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:38.846 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest2, ftest1) REFERENCES pktable); 2025-07-03 22:06:38.849 UTC client backend[25230] pg_regress/tsearch LOG: disconnection: session time: 0:00:02.726 user=postgres database=regression host=[local] 2025-07-03 22:06:38.861 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-07-03 22:06:38.861 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:38.861 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest2, ftest1) REFERENCES pktable(ptest1, ptest2)); 2025-07-03 22:06:38.888 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:38.888 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest2" of the referenced table are of incompatible types: integer and inet. 2025-07-03 22:06:38.888 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE FKTABLE (ftest1 int, ftest2 inet, FOREIGN KEY(ftest1, ftest2) REFERENCES pktable(ptest2, ptest1)); 2025-07-03 22:06:38.925 UTC client backend[25231] pg_regress/bitmapops LOG: disconnection: session time: 0:00:02.802 user=postgres database=regression host=[local] 2025-07-03 22:06:38.952 UTC client backend[25238] pg_regress/foreign_data WARNING: changing the foreign-data wrapper validator can cause the options for dependent objects to become invalid 2025-07-03 22:06:38.953 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foobar" 2025-07-03 22:06:38.953 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-07-03 22:06:38.953 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foobar; 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (gotcha 'true'); 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to change owner of foreign-data wrapper "foo" 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to change owner of a foreign-data wrapper. 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OWNER TO regress_unprivileged_role; 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-07-03 22:06:38.954 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:38.954 UTC client backend[25223] pg_regress/cluster LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp25223.0", size 2801664 2025-07-03 22:06:38.954 UTC client backend[25223] pg_regress/cluster STATEMENT: cluster clstr_4 using cluster_sort; 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN DATA WRAPPER foo TO regress_test_role; 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER s9 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s4 VERSION '0.5'; 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-07-03 22:06:38.955 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s4 OWNER TO regress_unprivileged_role; 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER s4; 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign server s4 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN SERVER s4 TO regress_test_role; 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s4 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s4; 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.956 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_role SERVER s6 OPTIONS (gotcha 'true'); 2025-07-03 22:06:38.957 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.957 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_role SERVER s6; 2025-07-03 22:06:38.959 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to create foreign-data wrapper "foobar" 2025-07-03 22:06:38.959 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to create a foreign-data wrapper. 2025-07-03 22:06:38.959 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN DATA WRAPPER foobar; 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied to alter foreign-data wrapper "foo" 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data HINT: Must be superuser to alter a foreign-data wrapper. 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN DATA WRAPPER foo OPTIONS (gotcha 'true'); 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign-data wrapper foo 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:38.960 UTC client backend[25238] pg_regress/foreign_data WARNING: no privileges were granted for "postgresql" 2025-07-03 22:06:38.963 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.963 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s6 VERSION '0.5'; 2025-07-03 22:06:38.963 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.963 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER s6; 2025-07-03 22:06:38.964 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign server s6 2025-07-03 22:06:38.964 UTC client backend[25238] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN SERVER s6 TO regress_test_role; 2025-07-03 22:06:38.965 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.965 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE USER MAPPING FOR public SERVER s6; 2025-07-03 22:06:38.968 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.968 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER USER MAPPING FOR regress_test_role SERVER s6 OPTIONS (gotcha 'true'); 2025-07-03 22:06:38.968 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s6 2025-07-03 22:06:38.968 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP USER MAPPING FOR regress_test_role SERVER s6; 2025-07-03 22:06:38.973 UTC client backend[25238] pg_regress/foreign_data ERROR: dependent privileges exist 2025-07-03 22:06:38.973 UTC client backend[25238] pg_regress/foreign_data HINT: Use CASCADE to revoke them too. 2025-07-03 22:06:38.973 UTC client backend[25238] pg_regress/foreign_data STATEMENT: REVOKE USAGE ON FOREIGN DATA WRAPPER foo FROM regress_unprivileged_role; 2025-07-03 22:06:38.979 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:38.979 UTC client backend[25238] pg_regress/foreign_data STATEMENT: GRANT USAGE ON FOREIGN DATA WRAPPER foo TO regress_test_role; 2025-07-03 22:06:38.983 UTC client backend[25238] pg_regress/foreign_data ERROR: permission denied for foreign-data wrapper foo 2025-07-03 22:06:38.983 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE SERVER s10 FOREIGN DATA WRAPPER foo; 2025-07-03 22:06:38.999 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s9 2025-07-03 22:06:38.999 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER SERVER s9 VERSION '1.2'; 2025-07-03 22:06:39.003 UTC client backend[25238] pg_regress/foreign_data WARNING: no privileges were granted for "s9" 2025-07-03 22:06:39.005 UTC client backend[25238] pg_regress/foreign_data ERROR: must be owner of foreign server s9 2025-07-03 22:06:39.005 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP SERVER s9 CASCADE; 2025-07-03 22:06:39.006 UTC client backend[25232] pg_regress/window LOG: disconnection: session time: 0:00:02.862 user=postgres database=regression host=[local] 2025-07-03 22:06:39.079 UTC client backend[25238] pg_regress/foreign_data ERROR: "foreign_table_1" is a foreign table 2025-07-03 22:06:39.079 UTC client backend[25238] pg_regress/foreign_data DETAIL: Triggers on foreign tables cannot have transition tables. 2025-07-03 22:06:39.079 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE TRIGGER trigtest_after_stmt_tt AFTER INSERT OR UPDATE OR DELETE -- ERROR ON foreign_schema.foreign_table_1 REFERENCING NEW TABLE AS new_table FOR EACH STATEMENT EXECUTE PROCEDURE dummy_trigger(); 2025-07-03 22:06:39.087 UTC client backend[25238] pg_regress/foreign_data ERROR: "foreign_table_1" is a foreign table 2025-07-03 22:06:39.087 UTC client backend[25238] pg_regress/foreign_data DETAIL: Foreign tables cannot have constraint triggers. 2025-07-03 22:06:39.087 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE CONSTRAINT TRIGGER trigtest_constraint AFTER INSERT OR UPDATE OR DELETE ON foreign_schema.foreign_table_1 FOR EACH ROW EXECUTE PROCEDURE dummy_trigger(); 2025-07-03 22:06:39.186 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest3_ptest4_fkey" cannot be implemented 2025-07-03 22:06:39.186 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest3" of the referencing table and "ptest2" of the referenced table are of incompatible types: integer and inet. 2025-07-03 22:06:39.186 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest3, ptest4) REFERENCES pktable(ptest2, ptest1)); 2025-07-03 22:06:39.206 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest4_ptest3_fkey" cannot be implemented 2025-07-03 22:06:39.206 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest4" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.206 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest4, ptest3) REFERENCES pktable(ptest1, ptest2)); 2025-07-03 22:06:39.222 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest4_ptest3_fkey" cannot be implemented 2025-07-03 22:06:39.222 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest4" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.222 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TABLE PKTABLE (ptest1 int, ptest2 inet, ptest3 int, ptest4 inet, PRIMARY KEY(ptest1, ptest2), FOREIGN KEY(ptest4, ptest3) REFERENCES pktable); 2025-07-03 22:06:39.268 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey" 2025-07-03 22:06:39.268 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1)=(3) is not present in table "pktable". 2025-07-03 22:06:39.268 UTC client backend[25221] pg_regress/foreign_key STATEMENT: insert into fktable(ftest1) values (3); 2025-07-03 22:06:39.279 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-07-03 22:06:39.279 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1)=(3) is still referenced from table "fktable". 2025-07-03 22:06:39.279 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pktable where base1>2; 2025-07-03 22:06:39.281 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_fkey" on table "fktable" 2025-07-03 22:06:39.281 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1)=(3) is still referenced from table "fktable". 2025-07-03 22:06:39.281 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pktable set base1=base1*4; 2025-07-03 22:06:39.313 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" 2025-07-03 22:06:39.313 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (ftest1, ftest2)=(3, 1) is not present in table "pktable". 2025-07-03 22:06:39.313 UTC client backend[25221] pg_regress/foreign_key STATEMENT: insert into fktable(ftest1, ftest2) values (3, 1); 2025-07-03 22:06:39.317 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" on table "fktable" 2025-07-03 22:06:39.317 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(3, 1) is still referenced from table "fktable". 2025-07-03 22:06:39.317 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pktable where base1>2; 2025-07-03 22:06:39.323 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_ftest1_ftest2_fkey" on table "fktable" 2025-07-03 22:06:39.323 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(3, 1) is still referenced from table "fktable". 2025-07-03 22:06:39.323 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pktable set base1=base1*4; 2025-07-03 22:06:39.432 UTC client backend[25223] pg_regress/cluster LOG: disconnection: session time: 0:00:03.327 user=postgres database=regression host=[local] 2025-07-03 22:06:39.440 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" 2025-07-03 22:06:39.440 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base2, ptest2)=(3, 2) is not present in table "pktable". 2025-07-03 22:06:39.440 UTC client backend[25221] pg_regress/foreign_key STATEMENT: insert into pktable (base1, ptest1, base2, ptest2) values (2, 3, 3, 2); 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" on table "pktable" 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(2, 2) is still referenced from table "pktable". 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pktable where base1=2; 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "pktable_base2_ptest2_fkey" on table "pktable" 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (base1, ptest1)=(1, 1) is still referenced from table "pktable". 2025-07-03 22:06:39.442 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pktable set base1=3 where base1=1; 2025-07-03 22:06:39.489 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:39.489 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "base1" of the referenced table are of incompatible types: cidr and integer. 2025-07-03 22:06:39.489 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 cidr, ftest2 int[], foreign key (ftest1, ftest2) references pktable); 2025-07-03 22:06:39.495 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:39.495 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "base1" of the referenced table are of incompatible types: cidr and integer. 2025-07-03 22:06:39.495 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 cidr, ftest2 int[], foreign key (ftest1, ftest2) references pktable(base1, ptest1)); 2025-07-03 22:06:39.500 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-07-03 22:06:39.500 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.500 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest2, ftest1) references pktable); 2025-07-03 22:06:39.506 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented 2025-07-03 22:06:39.506 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.506 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest2, ftest1) references pktable(base1, ptest1)); 2025-07-03 22:06:39.516 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented 2025-07-03 22:06:39.516 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: integer and inet. 2025-07-03 22:06:39.516 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table fktable(ftest1 int, ftest2 inet, foreign key(ftest1, ftest2) references pktable(ptest1, base1)); 2025-07-03 22:06:39.552 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_base2_ptest2_fkey" cannot be implemented 2025-07-03 22:06:39.552 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet[] and inet. 2025-07-03 22:06:39.552 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet[], primary key(base1, ptest1), foreign key(base2, ptest2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-07-03 22:06:39.562 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_base2_ptest2_fkey" cannot be implemented 2025-07-03 22:06:39.562 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "base2" of the referencing table and "ptest1" of the referenced table are of incompatible types: integer and inet. 2025-07-03 22:06:39.562 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(base2, ptest2) references pktable(ptest1, base1)) inherits (pktable_base); 2025-07-03 22:06:39.576 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest2_base2_fkey" cannot be implemented 2025-07-03 22:06:39.576 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.576 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(ptest2, base2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-07-03 22:06:39.597 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "pktable_ptest2_base2_fkey" cannot be implemented 2025-07-03 22:06:39.597 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "ptest2" of the referencing table and "base1" of the referenced table are of incompatible types: inet and integer. 2025-07-03 22:06:39.597 UTC client backend[25221] pg_regress/foreign_key STATEMENT: create table pktable(ptest1 inet, ptest2 inet, primary key(base1, ptest1), foreign key(ptest2, base2) references pktable(base1, ptest1)) inherits (pktable_base); 2025-07-03 22:06:39.607 UTC client backend[25221] pg_regress/foreign_key ERROR: table "pktable" does not exist 2025-07-03 22:06:39.607 UTC client backend[25221] pg_regress/foreign_key STATEMENT: drop table pktable; 2025-07-03 22:06:39.633 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.633 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(10) is not present in table "pktable". 2025-07-03 22:06:39.633 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (5, 10); 2025-07-03 22:06:39.679 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.679 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(1000) is not present in table "pktable". 2025-07-03 22:06:39.679 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (500, 1000); 2025-07-03 22:06:39.700 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.700 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(2000) is not present in table "pktable". 2025-07-03 22:06:39.700 UTC client backend[25221] pg_regress/foreign_key STATEMENT: SET CONSTRAINTS ALL IMMEDIATE; 2025-07-03 22:06:39.707 UTC client backend[25221] pg_regress/foreign_key ERROR: current transaction is aborted, commands ignored until end of transaction block 2025-07-03 22:06:39.707 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO pktable VALUES (2000, 3); 2025-07-03 22:06:39.728 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.728 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(200) is not present in table "pktable". 2025-07-03 22:06:39.728 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_2_3" cannot be implemented 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id3" of the referenced table are of incompatible types: character varying and real. 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_2_3 FOREIGN KEY (x2) REFERENCES pktable(id3); 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_2_1" cannot be implemented 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id1" of the referenced table are of incompatible types: character varying and integer. 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_2_1 FOREIGN KEY (x2) REFERENCES pktable(id1); 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_3_1" cannot be implemented 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x3" of the referencing table and "id1" of the referenced table are of incompatible types: real and integer. 2025-07-03 22:06:39.748 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_3_1 FOREIGN KEY (x3) REFERENCES pktable(id1); 2025-07-03 22:06:39.749 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_1_2" cannot be implemented 2025-07-03 22:06:39.749 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x1" of the referencing table and "id2" of the referenced table are of incompatible types: integer and character varying. 2025-07-03 22:06:39.749 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_1_2 FOREIGN KEY (x1) REFERENCES pktable(id2); 2025-07-03 22:06:39.825 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_123_231" cannot be implemented 2025-07-03 22:06:39.825 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x1" of the referencing table and "id2" of the referenced table are of incompatible types: integer and character varying. 2025-07-03 22:06:39.825 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_123_231 FOREIGN KEY (x1,x2,x3) REFERENCES pktable(id2,id3,id1); 2025-07-03 22:06:39.828 UTC client backend[25221] pg_regress/foreign_key ERROR: foreign key constraint "fk_241_132" cannot be implemented 2025-07-03 22:06:39.828 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key columns "x2" of the referencing table and "id1" of the referenced table are of incompatible types: character varying and integer. 2025-07-03 22:06:39.828 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ADD CONSTRAINT fk_241_132 FOREIGN KEY (x2,x4,x1) REFERENCES pktable(id1,id3,id2); 2025-07-03 22:06:39.869 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.869 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-07-03 22:06:39.869 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:39.879 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.879 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-07-03 22:06:39.879 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:39.881 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.881 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-07-03 22:06:39.881 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:39.883 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.883 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-07-03 22:06:39.883 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:39.886 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable" violates foreign key constraint "fktable_fk_fkey" on table "fktable" 2025-07-03 22:06:39.886 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id)=(5) is still referenced from table "fktable". 2025-07-03 22:06:39.886 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pktable SET id = 10 WHERE id = 5; 2025-07-03 22:06:39.887 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable" violates foreign key constraint "fktable_fk_fkey" 2025-07-03 22:06:39.887 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (fk)=(20) is not present in table "pktable". 2025-07-03 22:06:39.887 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fktable VALUES (0, 20); 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key ERROR: constraint declared INITIALLY DEFERRED must be DEFERRABLE at character 69 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NOT DEFERRABLE INITIALLY DEFERRED; 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key ERROR: constraint "fktable_fk_fkey" of relation "fktable" is not a not-null constraint 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NO INHERIT; 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key ERROR: constraints cannot be altered to be NOT VALID at character 54 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey NOT VALID; 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key ERROR: conflicting constraint properties at character 63 2025-07-03 22:06:39.891 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fktable ALTER CONSTRAINT fktable_fk_fkey ENFORCED NOT ENFORCED; 2025-07-03 22:06:39.892 UTC client backend[25221] pg_regress/foreign_key ERROR: multiple ENFORCED/NOT ENFORCED clauses not allowed at character 64 2025-07-03 22:06:39.892 UTC client backend[25221] pg_regress/foreign_key STATEMENT: CREATE TEMP TABLE fktable2 (fk int references pktable ENFORCED NOT ENFORCED); 2025-07-03 22:06:39.941 UTC client backend[25238] pg_regress/foreign_data ERROR: "ft2" is not a table 2025-07-03 22:06:39.941 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt1 ALTER COLUMN c8 TYPE char(10) USING '0'; 2025-07-03 22:06:40.153 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "defp" violates foreign key constraint "defc_f1_fkey" on table "defc" 2025-07-03 22:06:40.153 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(0) is still referenced from table "defc". 2025-07-03 22:06:40.153 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from defp where f1 = 0; 2025-07-03 22:06:40.157 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "defp" violates foreign key constraint "defc_f1_fkey" on table "defc" 2025-07-03 22:06:40.157 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(1) is still referenced from table "defc". 2025-07-03 22:06:40.157 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from defp where f1 = 1; 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pp" violates foreign key constraint "cc_f1_fkey" on table "cc" 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(13) is still referenced from table "cc". 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pp set f1=f1+1; 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pp" violates foreign key constraint "cc_f1_fkey" on table "cc" 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(13) is still referenced from table "cc". 2025-07-03 22:06:40.174 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pp where f1 = 13; 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pp" violates RESTRICT setting of foreign key constraint "cc_f1_fkey" on table "cc" 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(13) is referenced from table "cc". 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pp set f1=f1+1; 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pp" violates RESTRICT setting of foreign key constraint "cc_f1_fkey" on table "cc" 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(13) is referenced from table "cc". 2025-07-03 22:06:40.234 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pp where f1 = 13; 2025-07-03 22:06:40.297 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable2" violates foreign key constraint "fktable2_d_e_fkey" on table "fktable2" 2025-07-03 22:06:40.297 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (d, e)=(4, 5) is still referenced from table "fktable2". 2025-07-03 22:06:40.297 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from pktable2; 2025-07-03 22:06:40.298 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pktable2" violates foreign key constraint "fktable2_d_e_fkey" on table "fktable2" 2025-07-03 22:06:40.298 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (d, e)=(4, 5) is still referenced from table "fktable2". 2025-07-03 22:06:40.298 UTC client backend[25221] pg_regress/foreign_key STATEMENT: update pktable2 set d = 5; 2025-07-03 22:06:40.388 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fktable2" violates foreign key constraint "fktable2_f1_fkey" 2025-07-03 22:06:40.388 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(2) is not present in table "pktable2". 2025-07-03 22:06:40.388 UTC client backend[25221] pg_regress/foreign_key STATEMENT: commit; 2025-07-03 22:06:40.391 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot ALTER TABLE "fktable2" because it has pending trigger events 2025-07-03 22:06:40.391 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fktable2 drop constraint fktable2_f1_fkey; 2025-07-03 22:06:40.393 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot ALTER TABLE "pktable2" because it has pending trigger events 2025-07-03 22:06:40.393 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fktable2 drop constraint fktable2_f1_fkey; 2025-07-03 22:06:40.491 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot drop foreign table ft2 because other objects depend on it 2025-07-03 22:06:40.491 UTC client backend[25238] pg_regress/foreign_data DETAIL: table ct3 depends on foreign table ft2 foreign table ft3 depends on foreign table ft2 2025-07-03 22:06:40.491 UTC client backend[25238] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:40.491 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN TABLE ft2; 2025-07-03 22:06:40.517 UTC client backend[25238] pg_regress/foreign_data ERROR: child table is missing constraint "fd_pt1chk2" 2025-07-03 22:06:40.517 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER FOREIGN TABLE ft2 INHERIT fd_pt1; 2025-07-03 22:06:40.526 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot use ONLY for foreign key on partitioned table "fk_partitioned_fk" referencing relation "fk_notpartitioned_pk" 2025-07-03 22:06:40.526 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE ONLY fk_partitioned_fk ADD FOREIGN KEY (a, b) REFERENCES fk_notpartitioned_pk; 2025-07-03 22:06:40.529 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.529 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.529 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (500, 501); 2025-07-03 22:06:40.531 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.531 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.531 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_1 (a,b) VALUES (500, 501); 2025-07-03 22:06:40.532 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.532 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.532 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (1500, 1501); 2025-07-03 22:06:40.538 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.538 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.538 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_2 (a,b) VALUES (1500, 1501); 2025-07-03 22:06:40.539 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.539 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.539 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (2500, 2502); 2025-07-03 22:06:40.540 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.540 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.540 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a,b) VALUES (2500, 2502); 2025-07-03 22:06:40.541 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_0" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.541 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 2503) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.541 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a,b) VALUES (2501, 2503); 2025-07-03 22:06:40.547 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_0" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.547 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 2503) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.547 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a,b) VALUES (2501, 2503); 2025-07-03 22:06:40.553 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:40.553 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:40.553 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fk_partitioned_fk SET a = a + 1 WHERE a = 2501; 2025-07-03 22:06:40.557 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-07-03 22:06:40.557 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(500, 501) is still referenced from table "fk_partitioned_fk". 2025-07-03 22:06:40.557 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 502 WHERE a = 500; 2025-07-03 22:06:40.560 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-07-03 22:06:40.560 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(1500, 1501) is still referenced from table "fk_partitioned_fk". 2025-07-03 22:06:40.560 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 1502 WHERE a = 1500; 2025-07-03 22:06:40.566 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" on table "fk_partitioned_fk" 2025-07-03 22:06:40.566 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2500, 2502) is still referenced from table "fk_partitioned_fk". 2025-07-03 22:06:40.566 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET b = 2504 WHERE a = 2500; 2025-07-03 22:06:40.968 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_notpartitioned_pk" violates foreign key constraint "fk_partitioned_fk_a_fkey" on table "fk_partitioned_fk" 2025-07-03 22:06:40.968 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_partitioned_fk". 2025-07-03 22:06:40.968 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM fk_notpartitioned_pk WHERE a = 1; 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 FROM SERVER s9 INTO public; 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 LIMIT TO (t1) FROM SERVER s9 INTO public; 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-07-03 22:06:40.988 UTC client backend[25238] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 EXCEPT (t1) FROM SERVER s9 INTO public; 2025-07-03 22:06:40.989 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign-data wrapper "foo" has no handler 2025-07-03 22:06:40.989 UTC client backend[25238] pg_regress/foreign_data STATEMENT: IMPORT FOREIGN SCHEMA s1 EXCEPT (t1, t2) FROM SERVER s9 INTO public OPTIONS (option1 'value1', option2 'value2'); 2025-07-03 22:06:40.990 UTC client backend[25238] pg_regress/foreign_data ERROR: foreign table "no_table" does not exist 2025-07-03 22:06:40.990 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP FOREIGN TABLE no_table; 2025-07-03 22:06:41.000 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot drop desired object(s) because other objects depend on them 2025-07-03 22:06:41.000 UTC client backend[25238] pg_regress/foreign_data DETAIL: user mapping for regress_test_role on server s5 depends on server s5 2025-07-03 22:06:41.000 UTC client backend[25238] pg_regress/foreign_data HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:41.000 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP OWNED BY regress_test_role2; 2025-07-03 22:06:41.067 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2" violates foreign key constraint "fk_partitioned_fk_2_a_b_fkey" 2025-07-03 22:06:41.067 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(1000, 1000) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:41.067 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES FROM (1000,1000) TO (2000,2000); 2025-07-03 22:06:41.245 UTC client backend[25238] pg_regress/foreign_data ERROR: table "fd_pt2_1" contains column "c4" not found in parent "fd_pt2" 2025-07-03 22:06:41.245 UTC client backend[25238] pg_regress/foreign_data DETAIL: The new partition may contain only the columns present in parent. 2025-07-03 22:06:41.245 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-07-03 22:06:41.409 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot add column to a partition 2025-07-03 22:06:41.409 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2_1 ADD c4 char; 2025-07-03 22:06:41.420 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:41.420 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:41.420 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk (a, b) VALUES (2502, 2503); 2025-07-03 22:06:41.421 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:41.421 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2502, 2503) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:41.421 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_3 (a, b) VALUES (2502, 2503); 2025-07-03 22:06:41.446 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_full_1" violates foreign key constraint "fk_partitioned_fk_full_x_y_fkey" 2025-07-03 22:06:41.446 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:41.446 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_full ADD FOREIGN KEY (x, y) REFERENCES fk_notpartitioned_pk MATCH FULL; 2025-07-03 22:06:41.471 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_full_1" violates foreign key constraint "fk_partitioned_fk_full_x_y_fkey" 2025-07-03 22:06:41.471 UTC client backend[25221] pg_regress/foreign_key DETAIL: MATCH FULL does not allow mixing of null and nonnull key values. 2025-07-03 22:06:41.471 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_partitioned_fk_full VALUES (1, NULL); 2025-07-03 22:06:41.516 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_3" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:41.516 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2501, 142857) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:41.516 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fk_notpartitioned_pk SET a = 1500 WHERE a = 2502; 2025-07-03 22:06:41.575 UTC client backend[25238] pg_regress/foreign_data ERROR: column "c1" is marked NOT NULL in parent table 2025-07-03 22:06:41.575 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2_1 ALTER c1 DROP NOT NULL; 2025-07-03 22:06:41.730 UTC client backend[25238] pg_regress/foreign_data ERROR: column "c2" in child table "fd_pt2_1" must be marked NOT NULL 2025-07-03 22:06:41.730 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-07-03 22:06:41.828 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.onek": index scans: 1 pages: 0 removed, 104 remain, 104 scanned (100.00% of total), 0 eagerly scanned tuples: 15 removed, 1000 remain, 0 are dead but not yet removable removable cutoff: 15071, which was 3 XIDs old when operation ended new relfrozenxid: 10625, which is 9852 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 104 pages set all-visible, 68 pages set all-frozen (0 were all-visible) index scan needed: 69 pages from table (66.35% of total) had 2000 dead item identifiers removed index "onek_unique1": pages: 11 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "onek_unique2": pages: 11 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "onek_hundred": pages: 6 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "onek_stringu1": pages: 7 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 433 hits, 0 reads, 0 dirtied WAL usage: 206 records, 1 full page images, 45383 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:41.866 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.onek" avg read rate: 0.000 MB/s, avg write rate: 0.617 MB/s buffer usage: 469 hits, 0 reads, 3 dirtied WAL usage: 47 records, 2 full page images, 27970 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:41.877 UTC client backend[25238] pg_regress/foreign_data ERROR: child table is missing constraint "fd_pt2chk1" 2025-07-03 22:06:41.877 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE fd_pt2 ATTACH PARTITION fd_pt2_1 FOR VALUES IN (1); 2025-07-03 22:06:41.897 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot create a permanent relation as partition of temporary relation "temp_parted" 2025-07-03 22:06:41.897 UTC client backend[25238] pg_regress/foreign_data STATEMENT: CREATE FOREIGN TABLE foreign_part PARTITION OF temp_parted DEFAULT SERVER s0; 2025-07-03 22:06:41.898 UTC client backend[25238] pg_regress/foreign_data ERROR: cannot attach a permanent relation as partition of temporary relation "temp_parted" 2025-07-03 22:06:41.898 UTC client backend[25238] pg_regress/foreign_data STATEMENT: ALTER TABLE temp_parted ATTACH PARTITION foreign_part DEFAULT; 2025-07-03 22:06:41.900 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_test_role" cannot be dropped because some objects depend on it 2025-07-03 22:06:41.900 UTC client backend[25238] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper foo privileges for server s4 owner of user mapping for regress_test_role on server s6 2025-07-03 22:06:41.900 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP ROLE regress_test_role; 2025-07-03 22:06:41.903 UTC client backend[25238] pg_regress/foreign_data ERROR: role "regress_unprivileged_role" cannot be dropped because some objects depend on it 2025-07-03 22:06:41.903 UTC client backend[25238] pg_regress/foreign_data DETAIL: privileges for foreign-data wrapper postgresql 2025-07-03 22:06:41.903 UTC client backend[25238] pg_regress/foreign_data STATEMENT: DROP ROLE regress_unprivileged_role; 2025-07-03 22:06:41.918 UTC not initialized[25638] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:41.919 UTC client backend[25638] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:41.919 UTC client backend[25638] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/foreign_data 2025-07-03 22:06:41.923 UTC client backend[25638] pg_regress/foreign_data LOG: connection ready: setup total=17.643 ms, fork=10.204 ms, authentication=0.639 ms 2025-07-03 22:06:41.923 UTC client backend[25238] pg_regress/foreign_data LOG: disconnection: session time: 0:00:05.769 user=postgres database=regression host=[local] 2025-07-03 22:06:41.959 UTC client backend[25638] pg_regress/foreign_data LOG: disconnection: session time: 0:00:00.043 user=postgres database=regression host=[local] 2025-07-03 22:06:42.049 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.tenk1" avg read rate: 0.000 MB/s, avg write rate: 0.128 MB/s buffer usage: 569 hits, 0 reads, 3 dirtied WAL usage: 36 records, 2 full page images, 27883 bytes, 0 buffers full system usage: CPU: user: 0.06 s, system: 0.00 s, elapsed: 0.18 s 2025-07-03 22:06:42.053 UTC client backend[25221] pg_regress/foreign_key ERROR: constraint "fk_partitioned_fk_a_b_fkey" enforceability conflicts with constraint "fk_part_con" on relation "fk_partitioned_fk_2" 2025-07-03 22:06:42.053 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES IN (1500,1502); 2025-07-03 22:06:42.229 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.tenk2" avg read rate: 0.000 MB/s, avg write rate: 0.131 MB/s buffer usage: 556 hits, 0 reads, 3 dirtied WAL usage: 37 records, 1 full page images, 20652 bytes, 0 buffers full system usage: CPU: user: 0.06 s, system: 0.00 s, elapsed: 0.17 s 2025-07-03 22:06:42.247 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.road" avg read rate: 0.000 MB/s, avg write rate: 0.919 MB/s buffer usage: 303 hits, 0 reads, 2 dirtied WAL usage: 8 records, 1 full page images, 10501 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.264 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.road" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 136 hits, 0 reads, 0 dirtied WAL usage: 6 records, 0 full page images, 3007 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.265 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.ihighway" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 47 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 152 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.267 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_statistic": index scans: 1 pages: 0 removed, 53 remain, 53 scanned (100.00% of total), 0 eagerly scanned tuples: 143 removed, 647 remain, 4 are dead but not yet removable removable cutoff: 15106, which was 3 XIDs old when operation ended new relfrozenxid: 787, which is 13 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 35 pages set all-visible, 6 pages set all-frozen (0 were all-visible) index scan needed: 31 pages from table (58.49% of total) had 271 dead item identifiers removed index "pg_statistic_relid_att_inh_index": pages: 5 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 12.839 MB/s buffer usage: 164 hits, 0 reads, 2 dirtied WAL usage: 91 records, 3 full page images, 31023 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.275 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_type": index scans: 1 pages: 0 removed, 87 remain, 87 scanned (100.00% of total), 0 eagerly scanned tuples: 613 removed, 1580 remain, 0 are dead but not yet removable removable cutoff: 15106, which was 3 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 72 pages set all-visible, 12 pages set all-frozen (0 were all-visible) index scan needed: 70 pages from table (80.46% of total) had 3000 dead item identifiers removed index "pg_type_oid_index": pages: 21 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_type_typname_nsp_index": pages: 21 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 314 hits, 0 reads, 0 dirtied WAL usage: 214 records, 1 full page images, 37700 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.320 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_type" avg read rate: 0.000 MB/s, avg write rate: 0.347 MB/s buffer usage: 997 hits, 0 reads, 2 dirtied WAL usage: 96 records, 2 full page images, 32347 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.04 s 2025-07-03 22:06:42.321 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.shighway" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 51 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 1080 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.330 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_authid" avg read rate: 0.000 MB/s, avg write rate: 0.868 MB/s buffer usage: 226 hits, 0 reads, 1 dirtied WAL usage: 37 records, 1 full page images, 13364 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.331 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_statistic_ext_data": index scans: 1 pages: 1 removed, 4 remain, 5 scanned (100.00% of total), 0 eagerly scanned tuples: 43 removed, 4 remain, 0 are dead but not yet removable removable cutoff: 15106, which was 7 XIDs old when operation ended new relfrozenxid: 13015, which is 6072 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 5 pages set all-visible, 3 pages set all-frozen (0 were all-visible) index scan needed: 5 pages from table (100.00% of total) had 58 dead item identifiers removed index "pg_statistic_ext_data_stxoid_inh_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 23.046 MB/s buffer usage: 47 hits, 0 reads, 3 dirtied WAL usage: 24 records, 5 full page images, 42985 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.369 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_statistic_ext_data" avg read rate: 0.000 MB/s, avg write rate: 0.200 MB/s buffer usage: 769 hits, 0 reads, 1 dirtied WAL usage: 13 records, 0 full page images, 5060 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:42.384 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.test_range_gist" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 80 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 1944 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.391 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.test_range_spgist" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 71 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 1871 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.415 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_subscription" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 222 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 811 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.457 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_attribute": index scans: 1 pages: 0 removed, 473 remain, 425 scanned (89.85% of total), 0 eagerly scanned tuples: 4851 removed, 8681 remain, 6 are dead but not yet removable removable cutoff: 15121, which was 3 XIDs old when operation ended frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 391 pages set all-visible, 201 pages set all-frozen (0 were all-visible) index scan needed: 369 pages from table (78.01% of total) had 18500 dead item identifiers removed index "pg_attribute_relid_attnam_index": pages: 161 in total, 17 newly deleted, 42 currently deleted, 25 reusable index "pg_attribute_relid_attnum_index": pages: 113 in total, 6 newly deleted, 20 currently deleted, 14 reusable avg read rate: 0.000 MB/s, avg write rate: 4.283 MB/s buffer usage: 1726 hits, 0 reads, 23 dirtied WAL usage: 1121 records, 22 full page images, 273678 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.04 s 2025-07-03 22:06:42.666 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_attribute" avg read rate: 0.000 MB/s, avg write rate: 0.075 MB/s buffer usage: 801 hits, 0 reads, 2 dirtied WAL usage: 78 records, 2 full page images, 30447 bytes, 0 buffers full system usage: CPU: user: 0.06 s, system: 0.00 s, elapsed: 0.20 s 2025-07-03 22:06:42.677 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_attrdef": index scans: 1 pages: 0 removed, 17 remain, 17 scanned (100.00% of total), 0 eagerly scanned tuples: 62 removed, 121 remain, 0 are dead but not yet removable removable cutoff: 15125, which was 0 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 17 pages set all-visible, 2 pages set all-frozen (0 were all-visible) index scan needed: 17 pages from table (100.00% of total) had 203 dead item identifiers removed index "pg_attrdef_adrelid_adnum_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_attrdef_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.775 MB/s buffer usage: 114 hits, 0 reads, 1 dirtied WAL usage: 52 records, 1 full page images, 13017 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.679 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_attrdef" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 85 hits, 0 reads, 0 dirtied WAL usage: 10 records, 0 full page images, 4649 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.693 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_constraint": index scans: 1 pages: 0 removed, 23 remain, 23 scanned (100.00% of total), 0 eagerly scanned tuples: 122 removed, 549 remain, 0 are dead but not yet removable removable cutoff: 15126, which was 0 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 19 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 19 pages from table (82.61% of total) had 1146 dead item identifiers removed index "pg_constraint_conparentid_index": pages: 6 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_constraint_conname_nsp_index": pages: 10 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_constraint_conrelid_contypid_conname_index": pages: 12 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_constraint_contypid_index": pages: 6 in total, 1 newly deleted, 1 currently deleted, 0 reusable index "pg_constraint_oid_index": pages: 6 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 221 hits, 0 reads, 0 dirtied WAL usage: 83 records, 1 full page images, 24893 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.719 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_constraint" avg read rate: 0.000 MB/s, avg write rate: 0.868 MB/s buffer usage: 516 hits, 0 reads, 3 dirtied WAL usage: 84 records, 3 full page images, 44588 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.721 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_inherits": index scans: 1 pages: 0 removed, 5 remain, 5 scanned (100.00% of total), 0 eagerly scanned tuples: 274 removed, 92 remain, 0 are dead but not yet removable removable cutoff: 15126, which was 1 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 5 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan needed: 5 pages from table (100.00% of total) had 274 dead item identifiers removed index "pg_inherits_parent_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_inherits_relid_seqno_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 32.999 MB/s buffer usage: 65 hits, 0 reads, 4 dirtied WAL usage: 23 records, 4 full page images, 36854 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.722 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_inherits" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 67 hits, 0 reads, 0 dirtied WAL usage: 8 records, 0 full page images, 1803 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.727 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_index": index scans: 1 pages: 0 removed, 23 remain, 23 scanned (100.00% of total), 0 eagerly scanned tuples: 132 removed, 509 remain, 0 are dead but not yet removable removable cutoff: 15126, which was 2 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 21 pages set all-visible, 2 pages set all-frozen (0 were all-visible) index scan needed: 21 pages from table (91.30% of total) had 1065 dead item identifiers removed index "pg_index_indrelid_index": pages: 6 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_index_indexrelid_index": pages: 7 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 111 hits, 0 reads, 0 dirtied WAL usage: 65 records, 1 full page images, 17365 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.748 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_index" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 399 hits, 0 reads, 0 dirtied WAL usage: 63 records, 0 full page images, 14215 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.749 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_statistic_ext": index scans: 1 pages: 1 removed, 1 remain, 2 scanned (100.00% of total), 0 eagerly scanned tuples: 21 removed, 4 remain, 0 are dead but not yet removable removable cutoff: 15126, which was 4 XIDs old when operation ended new relfrozenxid: 13014, which is 6066 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 2 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 2 pages from table (100.00% of total) had 91 dead item identifiers removed index "pg_statistic_ext_relid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_statistic_ext_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_statistic_ext_name_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 22.258 MB/s buffer usage: 53 hits, 0 reads, 3 dirtied WAL usage: 19 records, 5 full page images, 43580 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.769 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_statistic_ext" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 213 hits, 0 reads, 0 dirtied WAL usage: 18 records, 0 full page images, 3154 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.770 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_rewrite": index scans: 1 pages: 0 removed, 55 remain, 55 scanned (100.00% of total), 0 eagerly scanned tuples: 51 removed, 223 remain, 0 are dead but not yet removable removable cutoff: 15130, which was 1 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 41 pages set all-visible, 17 pages set all-frozen (0 were all-visible) index scan needed: 33 pages from table (60.00% of total) had 159 dead item identifiers removed index "pg_rewrite_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_rewrite_rel_rulename_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 192 hits, 0 reads, 0 dirtied WAL usage: 95 records, 1 full page images, 15119 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.781 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_rewrite" avg read rate: 0.000 MB/s, avg write rate: 0.710 MB/s buffer usage: 164 hits, 0 reads, 1 dirtied WAL usage: 22 records, 1 full page images, 13447 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.783 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_trigger": index scans: 1 pages: 0 removed, 5 remain, 5 scanned (100.00% of total), 0 eagerly scanned tuples: 4 removed, 104 remain, 0 are dead but not yet removable removable cutoff: 15131, which was 1 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 5 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan needed: 5 pages from table (100.00% of total) had 598 dead item identifiers removed index "pg_trigger_tgconstraint_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_trigger_tgrelid_tgname_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_trigger_oid_index": pages: 4 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 13.646 MB/s buffer usage: 87 hits, 0 reads, 2 dirtied WAL usage: 22 records, 3 full page images, 29949 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.793 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_trigger" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 210 hits, 0 reads, 0 dirtied WAL usage: 38 records, 0 full page images, 8400 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.812 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_enum" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 98 hits, 0 reads, 0 dirtied WAL usage: 9 records, 0 full page images, 2078 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:42.814 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_namespace" avg read rate: 0.000 MB/s, avg write rate: 3.906 MB/s buffer usage: 79 hits, 0 reads, 1 dirtied WAL usage: 15 records, 1 full page images, 11445 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.816 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_shdepend": index scans: 1 pages: 3 removed, 0 remain, 3 scanned (100.00% of total), 0 eagerly scanned tuples: 79 removed, 0 remain, 0 are dead but not yet removable removable cutoff: 15135, which was 1 XIDs old when operation ended new relfrozenxid: 15135, which is 8184 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 3 pages set all-visible, 3 pages set all-frozen (0 were all-visible) index scan needed: 3 pages from table (100.00% of total) had 362 dead item identifiers removed index "pg_shdepend_depender_index": pages: 4 in total, 0 newly deleted, 1 currently deleted, 1 reusable index "pg_shdepend_reference_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 30.819 MB/s buffer usage: 85 hits, 0 reads, 6 dirtied WAL usage: 20 records, 6 full page images, 52360 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.817 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_shdepend" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 40 hits, 0 reads, 0 dirtied WAL usage: 0 records, 0 full page images, 0 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.819 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_ts_config_map" avg read rate: 0.000 MB/s, avg write rate: 3.906 MB/s buffer usage: 71 hits, 0 reads, 1 dirtied WAL usage: 14 records, 1 full page images, 10836 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.819 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_foreign_server" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 44 hits, 0 reads, 0 dirtied WAL usage: 1 records, 0 full page images, 311 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.826 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_policy": index scans: 1 pages: 0 removed, 11 remain, 11 scanned (100.00% of total), 0 eagerly scanned tuples: 104 removed, 9 remain, 0 are dead but not yet removable removable cutoff: 15137, which was 0 XIDs old when operation ended new relfrozenxid: 9851, which is 2897 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 11 pages set all-visible, 9 pages set all-frozen (0 were all-visible) index scan needed: 11 pages from table (100.00% of total) had 99 dead item identifiers removed index "pg_policy_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_policy_polrelid_polname_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 19.629 MB/s buffer usage: 94 hits, 0 reads, 3 dirtied WAL usage: 40 records, 3 full page images, 28211 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.832 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_policy" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 105 hits, 0 reads, 0 dirtied WAL usage: 16 records, 0 full page images, 5508 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.833 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_partitioned_table": index scans: 1 pages: 0 removed, 1 remain, 1 scanned (100.00% of total), 0 eagerly scanned tuples: 12 removed, 18 remain, 0 are dead but not yet removable removable cutoff: 15138, which was 0 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 1 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (100.00% of total) had 94 dead item identifiers removed index "pg_partitioned_table_partrelid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 68.985 MB/s buffer usage: 31 hits, 0 reads, 4 dirtied WAL usage: 9 records, 4 full page images, 34104 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.834 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_partitioned_table" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 89 hits, 0 reads, 0 dirtied WAL usage: 16 records, 0 full page images, 2480 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.835 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_sequence": index scans: 1 pages: 0 removed, 2 remain, 2 scanned (100.00% of total), 0 eagerly scanned tuples: 66 removed, 37 remain, 0 are dead but not yet removable removable cutoff: 15139, which was 0 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 2 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan needed: 2 pages from table (100.00% of total) had 60 dead item identifiers removed index "pg_sequence_seqrelid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 16.413 MB/s buffer usage: 33 hits, 0 reads, 1 dirtied WAL usage: 8 records, 1 full page images, 9480 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.837 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_sequence" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 147 hits, 0 reads, 0 dirtied WAL usage: 16 records, 0 full page images, 2415 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.838 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_publication": index scans: 1 pages: 1 removed, 0 remain, 1 scanned (100.00% of total), 0 eagerly scanned tuples: 33 removed, 0 remain, 0 are dead but not yet removable removable cutoff: 15140, which was 1 XIDs old when operation ended new relfrozenxid: 15140, which is 8186 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 1 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (100.00% of total) had 79 dead item identifiers removed index "pg_publication_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_publication_pubname_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 30.910 MB/s buffer usage: 37 hits, 0 reads, 4 dirtied WAL usage: 13 records, 4 full page images, 34642 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.845 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_publication" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 67 hits, 0 reads, 0 dirtied WAL usage: 0 records, 0 full page images, 0 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.845 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_publication_namespace" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 35 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 827 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.847 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_publication_rel": index scans: 1 pages: 1 removed, 0 remain, 1 scanned (100.00% of total), 0 eagerly scanned tuples: 39 removed, 0 remain, 0 are dead but not yet removable removable cutoff: 15141, which was 2 XIDs old when operation ended new relfrozenxid: 15141, which is 8187 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 1 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (100.00% of total) had 118 dead item identifiers removed index "pg_publication_rel_oid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_publication_rel_prrelid_prpubid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_publication_rel_prpubid_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 24.960 MB/s buffer usage: 57 hits, 0 reads, 4 dirtied WAL usage: 15 records, 4 full page images, 35428 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.848 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_publication_rel" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 64 hits, 0 reads, 0 dirtied WAL usage: 0 records, 0 full page images, 0 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.850 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.num_exp_add" avg read rate: 0.000 MB/s, avg write rate: 7.812 MB/s buffer usage: 126 hits, 0 reads, 2 dirtied WAL usage: 8 records, 2 full page images, 18091 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.852 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.num_exp_sub" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 64 hits, 0 reads, 0 dirtied WAL usage: 9 records, 0 full page images, 2358 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.853 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.num_exp_div" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 49 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 290 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.854 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.num_exp_mul" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 53 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 1308 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.863 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.num_result" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 37 hits, 0 reads, 0 dirtied WAL usage: 6 records, 0 full page images, 974 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.890 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.quad_poly_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 473 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 858 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.926 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.quad_box_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 216 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 858 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.956 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.quad_box_tbl_ord_seq1" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 154 hits, 0 reads, 0 dirtied WAL usage: 6 records, 0 full page images, 4461 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.958 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.quad_box_tbl_ord_seq2" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 48 hits, 0 reads, 0 dirtied WAL usage: 6 records, 0 full page images, 3425 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.960 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.timestamp_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 86 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 687 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.961 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.timestamptz_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 17 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 703 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.962 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.ramp" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 31 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 1142 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:42.988 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.quad_point_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 185 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 199 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:42.990 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.slow_emp4000" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 40 hits, 0 reads, 0 dirtied WAL usage: 1 records, 0 full page images, 76 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.008 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.fast_emp4000" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 60 hits, 0 reads, 0 dirtied WAL usage: 1 records, 0 full page images, 76 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.012 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.array_index_op_test" avg read rate: 0.000 MB/s, avg write rate: 1.562 MB/s buffer usage: 159 hits, 0 reads, 1 dirtied WAL usage: 20 records, 1 full page images, 16946 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.030 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.kd_point_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 98 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 199 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.051 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.radix_text_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 116 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 2962 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.058 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_partitioned_fk_2_1" violates foreign key constraint "fk_partitioned_fk_a_b_fkey" 2025-07-03 22:06:43.058 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(1600, 601) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:43.058 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk ATTACH PARTITION fk_partitioned_fk_2 FOR VALUES IN (1600); 2025-07-03 22:06:43.072 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot attach table "fk_partitioned_pk_6" as a partition because it is referenced by foreign key "fk_partitioned_fk_6_a_fkey" 2025-07-03 22:06:43.072 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_6 ATTACH PARTITION fk_partitioned_pk_6 FOR VALUES IN (1); 2025-07-03 22:06:43.090 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.dupindexcols" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 104 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 208 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.110 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot ALTER TABLE "fk_partitioned_pk_61" because it is being used by active queries in this session 2025-07-03 22:06:43.110 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_partitioned_fk_6 ATTACH PARTITION fk_partitioned_pk_6 FOR VALUES IN (1); 2025-07-03 22:06:43.118 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.bt_i4_heap": index scans: 0 pages: 35 removed, 45 remain, 80 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15183, which was 13 XIDs old when operation ended new relfrozenxid: 7074, which is 93 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 45 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 13.905 MB/s buffer usage: 230 hits, 0 reads, 49 dirtied WAL usage: 53 records, 51 full page images, 413708 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.121 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "other_partitioned_fk_1" violates foreign key constraint "other_partitioned_fk_a_b_fkey" 2025-07-03 22:06:43.121 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a, b)=(2048, 1) is not present in table "fk_notpartitioned_pk". 2025-07-03 22:06:43.121 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table other_partitioned_fk add foreign key (a, b) references fk_notpartitioned_pk(a, b); 2025-07-03 22:06:43.128 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.bt_i4_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 71 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 152 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.178 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.bt_name_heap": index scans: 0 pages: 44 removed, 124 remain, 168 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15200, which was 11 XIDs old when operation ended new relfrozenxid: 7138, which is 129 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 124 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 20.337 MB/s buffer usage: 415 hits, 0 reads, 128 dirtied WAL usage: 132 records, 130 full page images, 1060660 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.04 s 2025-07-03 22:06:43.205 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.bt_name_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 150 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 268 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.230 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.bt_txt_heap": index scans: 0 pages: 42 removed, 54 remain, 96 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15211, which was 7 XIDs old when operation ended new relfrozenxid: 7199, which is 181 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 54 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 18.281 MB/s buffer usage: 269 hits, 0 reads, 58 dirtied WAL usage: 62 records, 60 full page images, 486500 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.234 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-07-03 22:06:43.234 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id_abc)=(5) is not present in table "parted_self_fk". 2025-07-03 22:06:43.234 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO parted_self_fk VALUES (4, 5); 2025-07-03 22:06:43.236 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_1" on table "parted_self_fk" 2025-07-03 22:06:43.236 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id)=(1) is still referenced from table "parted_self_fk". 2025-07-03 22:06:43.236 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 1 RETURNING *; 2025-07-03 22:06:43.256 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "part2_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-07-03 22:06:43.256 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id_abc)=(9) is not present in table "parted_self_fk". 2025-07-03 22:06:43.256 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO part2_self_fk VALUES (16, 9); 2025-07-03 22:06:43.258 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_5" on table "part2_self_fk" 2025-07-03 22:06:43.258 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id)=(2) is still referenced from table "part2_self_fk". 2025-07-03 22:06:43.258 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 2 RETURNING *; 2025-07-03 22:06:43.264 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "part2_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey" 2025-07-03 22:06:43.264 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id_abc)=(9) is not present in table "parted_self_fk". 2025-07-03 22:06:43.264 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO parted_self_fk VALUES (16, 9); 2025-07-03 22:06:43.266 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "part1_self_fk" violates foreign key constraint "parted_self_fk_id_abc_fkey_1" on table "parted_self_fk" 2025-07-03 22:06:43.266 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id)=(3) is still referenced from table "parted_self_fk". 2025-07-03 22:06:43.266 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM parted_self_fk WHERE id = 3 RETURNING *; 2025-07-03 22:06:43.269 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.bt_txt_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 84 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 870 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:43.297 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.bt_f8_heap": index scans: 0 pages: 41 removed, 55 remain, 96 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15226, which was 6 XIDs old when operation ended new relfrozenxid: 7273, which is 224 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 55 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 17.166 MB/s buffer usage: 273 hits, 0 reads, 59 dirtied WAL usage: 63 records, 61 full page images, 494588 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.305 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.bt_f8_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 81 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 214 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.355 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_class": index scans: 1 pages: 0 removed, 162 remain, 162 scanned (100.00% of total), 0 eagerly scanned tuples: 907 removed, 1416 remain, 0 are dead but not yet removable removable cutoff: 15233, which was 2 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 2 pages from table (1.23% of total) had 11 tuples frozen visibility map: 153 pages set all-visible, 80 pages set all-frozen (0 were all-visible) index scan needed: 148 pages from table (91.36% of total) had 4310 dead item identifiers removed index "pg_class_oid_index": pages: 14 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_class_relname_nsp_index": pages: 33 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "pg_class_tblspc_relfilenode_index": pages: 21 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 1.598 MB/s buffer usage: 592 hits, 0 reads, 10 dirtied WAL usage: 437 records, 11 full page images, 90223 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.04 s 2025-07-03 22:06:43.416 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_class" avg read rate: 0.000 MB/s, avg write rate: 0.256 MB/s buffer usage: 661 hits, 0 reads, 2 dirtied WAL usage: 99 records, 2 full page images, 37416 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.06 s 2025-07-03 22:06:43.431 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.array_op_test" avg read rate: 0.000 MB/s, avg write rate: 0.521 MB/s buffer usage: 68 hits, 0 reads, 1 dirtied WAL usage: 19 records, 0 full page images, 9587 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.447 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.hash_i4_heap": index scans: 1 pages: 34 removed, 46 remain, 80 scanned (100.00% of total), 0 eagerly scanned tuples: 2 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15239, which was 1 XIDs old when operation ended new relfrozenxid: 7079, which is 61 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 2 pages from table (2.50% of total) had 450 tuples frozen visibility map: 46 pages set all-visible, 2 pages set all-frozen (0 were all-visible) index scan needed: 2 pages from table (2.50% of total) had 2 dead item identifiers removed index "hash_i4_index": pages: 66 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 27.385 MB/s buffer usage: 274 hits, 0 reads, 53 dirtied WAL usage: 62 records, 55 full page images, 432087 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.469 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.hash_i4_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 84 hits, 0 reads, 0 dirtied WAL usage: 6 records, 0 full page images, 1464 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.494 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_1_a_fkey" of relation "fk_part_1" 2025-07-03 22:06:43.494 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_1 drop constraint fk_part_1_a_fkey; 2025-07-03 22:06:43.505 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.hash_name_heap": index scans: 0 pages: 44 removed, 124 remain, 168 scanned (100.00% of total), 0 eagerly scanned tuples: 1 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15241, which was 2 XIDs old when operation ended new relfrozenxid: 7148, which is 130 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 1 pages from table (0.60% of total) had 80 tuples frozen visibility map: 123 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan bypassed: 1 pages from table (0.60% of total) have 1 dead item identifiers avg read rate: 0.000 MB/s, avg write rate: 28.451 MB/s buffer usage: 418 hits, 0 reads, 128 dirtied WAL usage: 132 records, 130 full page images, 1060657 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:43.518 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.hash_name_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 154 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 1682 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.539 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.hash_txt_heap": index scans: 1 pages: 41 removed, 55 remain, 96 scanned (100.00% of total), 0 eagerly scanned tuples: 2 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15243, which was 2 XIDs old when operation ended new relfrozenxid: 7233, which is 184 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 2 pages from table (2.08% of total) had 368 tuples frozen visibility map: 55 pages set all-visible, 2 pages set all-frozen (0 were all-visible) index scan needed: 2 pages from table (2.08% of total) had 2 dead item identifiers removed index "hash_txt_index": pages: 66 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 23.862 MB/s buffer usage: 312 hits, 0 reads, 62 dirtied WAL usage: 71 records, 64 full page images, 513941 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.555 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_23_a_fkey" of relation "fk_part_23" 2025-07-03 22:06:43.555 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_23 drop constraint fk_part_23_a_fkey; 2025-07-03 22:06:43.557 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_23_a_fkey" of relation "fk_part_23_2" 2025-07-03 22:06:43.557 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_23_2 drop constraint fk_part_23_a_fkey; 2025-07-03 22:06:43.563 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.hash_txt_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 85 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 2517 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.591 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.hash_f8_heap": index scans: 1 pages: 41 removed, 55 remain, 96 scanned (100.00% of total), 0 eagerly scanned tuples: 2 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15249, which was 1 XIDs old when operation ended new relfrozenxid: 7277, which is 228 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 1 pages from table (1.04% of total) had 183 tuples frozen visibility map: 55 pages set all-visible, 1 pages set all-frozen (0 were all-visible) index scan needed: 1 pages from table (1.04% of total) had 2 dead item identifiers removed index "hash_f8_index": pages: 66 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "hash_f8_index_1": pages: 30 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "hash_f8_index_2": pages: 41 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "hash_f8_index_3": pages: 27 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 24.611 MB/s, avg write rate: 19.174 MB/s buffer usage: 402 hits, 86 reads, 67 dirtied WAL usage: 74 records, 69 full page images, 543678 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.594 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_4" 2025-07-03 22:06:43.594 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_4 drop constraint fk_part_a_fkey; 2025-07-03 22:06:43.617 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.hash_f8_heap" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 113 hits, 0 reads, 0 dirtied WAL usage: 7 records, 0 full page images, 3018 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.619 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.agg_data_2k": index scans: 0 pages: 7 removed, 9 remain, 16 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 2000 remain, 0 are dead but not yet removable removable cutoff: 15254, which was 1 XIDs old when operation ended new relfrozenxid: 7964, which is 290 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 9 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 30.728 MB/s buffer usage: 66 hits, 0 reads, 4 dirtied WAL usage: 17 records, 6 full page images, 50279 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.620 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.agg_data_2k" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 28 hits, 0 reads, 0 dirtied WAL usage: 3 records, 0 full page images, 732 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.643 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.agg_data_20k": index scans: 0 pages: 39 removed, 89 remain, 128 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 20000 remain, 0 are dead but not yet removable removable cutoff: 15256, which was 1 XIDs old when operation ended new relfrozenxid: 7966, which is 292 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 89 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed avg read rate: 0.000 MB/s, avg write rate: 1.359 MB/s buffer usage: 354 hits, 0 reads, 4 dirtied WAL usage: 97 records, 6 full page images, 54999 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.652 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.agg_data_20k" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 104 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 158 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.654 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.btree_tall_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 50 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 1621 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.667 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_56" 2025-07-03 22:06:43.667 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_56 drop constraint fk_part_a_fkey; 2025-07-03 22:06:43.667 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_part_a_fkey" of relation "fk_part_56_5" 2025-07-03 22:06:43.667 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart0.fk_part_56_5 drop constraint fk_part_a_fkey; 2025-07-03 22:06:43.690 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_part_1_1" violates foreign key constraint "fk_part_a_fkey" 2025-07-03 22:06:43.690 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pkey". 2025-07-03 22:06:43.690 UTC client backend[25221] pg_regress/foreign_key STATEMENT: insert into fkpart1.fk_part values (1); 2025-07-03 22:06:43.691 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.delete_test_table": index scans: 0 pages: 0 removed, 589 remain, 9 scanned (1.53% of total), 0 eagerly scanned tuples: 0 removed, 11 remain, 0 are dead but not yet removable removable cutoff: 15258, which was 8 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 8 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "delete_test_table_pkey": pages: 491 in total, 0 newly deleted, 482 currently deleted, 482 reusable avg read rate: 48.278 MB/s, avg write rate: 0.638 MB/s buffer usage: 814 hits, 227 reads, 3 dirtied WAL usage: 13 records, 3 full page images, 25525 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:43.692 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pkey" violates foreign key constraint "fk_part_a_fkey" on table "fk_part" 2025-07-03 22:06:43.692 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_part". 2025-07-03 22:06:43.692 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from fkpart1.pkey where a = 1; 2025-07-03 22:06:43.696 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_part_1_2" violates foreign key constraint "fk_part_a_fkey" 2025-07-03 22:06:43.696 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(2) is not present in table "pkey". 2025-07-03 22:06:43.696 UTC client backend[25221] pg_regress/foreign_key STATEMENT: insert into fkpart1.fk_part_1 values (2); 2025-07-03 22:06:43.700 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.delete_test_table" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 645 hits, 0 reads, 0 dirtied WAL usage: 10 records, 0 full page images, 2413 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.701 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pkey" violates foreign key constraint "fk_part_a_fkey" on table "fk_part_1" 2025-07-03 22:06:43.701 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk_part_1". 2025-07-03 22:06:43.701 UTC client backend[25221] pg_regress/foreign_key STATEMENT: delete from fkpart1.pkey where a = 1; 2025-07-03 22:06:43.726 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.spgist_point_tbl": index scans: 1 pages: 0 removed, 128 remain, 128 scanned (100.00% of total), 0 eagerly scanned tuples: 15005 removed, 5001 remain, 0 are dead but not yet removable removable cutoff: 15272, which was 2 XIDs old when operation ended new relfrozenxid: 8232, which is 14 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 128 pages set all-visible, 63 pages set all-frozen (0 were all-visible) index scan needed: 128 pages from table (100.00% of total) had 15009 dead item identifiers removed index "spgist_point_idx": pages: 137 in total, 1 newly deleted, 1 currently deleted, 1 reusable avg read rate: 0.000 MB/s, avg write rate: 1.222 MB/s buffer usage: 565 hits, 0 reads, 4 dirtied WAL usage: 653 records, 4 full page images, 180617 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:43.729 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fkey" of relation "fk_part_1" 2025-07-03 22:06:43.729 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1 drop constraint fkey; 2025-07-03 22:06:43.732 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.spgist_point_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 162 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 858 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.734 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "my_fkey" of relation "fk_part_1_1" 2025-07-03 22:06:43.734 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1_1 drop constraint my_fkey; 2025-07-03 22:06:43.738 UTC client backend[25221] pg_regress/foreign_key ERROR: constraint "my_fkey" of relation "fk_part_1_1" does not exist 2025-07-03 22:06:43.738 UTC client backend[25221] pg_regress/foreign_key STATEMENT: alter table fkpart2.fk_part_1_1 drop constraint my_fkey; 2025-07-03 22:06:43.826 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.gist_point_tbl": index scans: 1 pages: 96 removed, 32 remain, 128 scanned (100.00% of total), 0 eagerly scanned tuples: 17500 removed, 2500 remain, 0 are dead but not yet removable removable cutoff: 15276, which was 9 XIDs old when operation ended new relfrozenxid: 8277, which is 45 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 128 pages set all-visible, 96 pages set all-frozen (0 were all-visible) index scan needed: 128 pages from table (100.00% of total) had 17500 dead item identifiers removed index "gist_pointidx": pages: 164 in total, 81 newly deleted, 81 currently deleted, 0 reusable avg read rate: 13.646 MB/s, avg write rate: 13.729 MB/s buffer usage: 609 hits, 164 reads, 165 dirtied WAL usage: 634 records, 3 full page images, 164522 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.01 s, elapsed: 0.09 s 2025-07-03 22:06:43.828 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.gist_point_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 64 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 152 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.898 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk1" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.898 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-07-03 22:06:43.898 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (1); 2025-07-03 22:06:43.900 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.900 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1000) is not present in table "pk". 2025-07-03 22:06:43.900 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (1000); 2025-07-03 22:06:43.904 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.904 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(2000) is not present in table "pk". 2025-07-03 22:06:43.904 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (2000); 2025-07-03 22:06:43.905 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk2" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.905 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(3000) is not present in table "pk". 2025-07-03 22:06:43.905 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (3000); 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk3" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4000) is not present in table "pk". 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (4000); 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk3" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4500) is not present in table "pk". 2025-07-03 22:06:43.906 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT into fk VALUES (4500); 2025-07-03 22:06:43.910 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk1" violates foreign key constraint "fk_a_fkey_1" on table "fk" 2025-07-03 22:06:43.910 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk". 2025-07-03 22:06:43.910 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 1; 2025-07-03 22:06:43.911 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk2" violates foreign key constraint "fk_a_fkey_2" on table "fk" 2025-07-03 22:06:43.911 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "fk". 2025-07-03 22:06:43.911 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 1000; 2025-07-03 22:06:43.912 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk3" violates foreign key constraint "fk_a_fkey_3" on table "fk" 2025-07-03 22:06:43.912 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "fk". 2025-07-03 22:06:43.912 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 2000; 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk4" violates foreign key constraint "fk_a_fkey_4" on table "fk" 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(3000) is still referenced from table "fk". 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 3000; 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk51" violates foreign key constraint "fk_a_fkey_6" on table "fk" 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4000) is still referenced from table "fk". 2025-07-03 22:06:43.913 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 4000; 2025-07-03 22:06:43.914 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk52" violates foreign key constraint "fk_a_fkey_7" on table "fk" 2025-07-03 22:06:43.914 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4500) is still referenced from table "fk". 2025-07-03 22:06:43.914 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 4500; 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk1" violates foreign key constraint "fk_a_fkey_1" on table "fk" 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "fk". 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 2 WHERE a = 1; 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk2" violates foreign key constraint "fk_a_fkey_2" on table "fk" 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "fk". 2025-07-03 22:06:43.915 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 1002 WHERE a = 1000; 2025-07-03 22:06:43.916 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk3" violates foreign key constraint "fk_a_fkey_3" on table "fk" 2025-07-03 22:06:43.916 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "fk". 2025-07-03 22:06:43.916 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 2002 WHERE a = 2000; 2025-07-03 22:06:43.917 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk4" violates foreign key constraint "fk_a_fkey_4" on table "fk" 2025-07-03 22:06:43.917 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(3000) is still referenced from table "fk". 2025-07-03 22:06:43.917 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 3002 WHERE a = 3000; 2025-07-03 22:06:43.919 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk51" violates foreign key constraint "fk_a_fkey_6" on table "fk" 2025-07-03 22:06:43.919 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4000) is still referenced from table "fk". 2025-07-03 22:06:43.919 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 4002 WHERE a = 4000; 2025-07-03 22:06:43.920 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk52" violates foreign key constraint "fk_a_fkey_7" on table "fk" 2025-07-03 22:06:43.920 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(4500) is still referenced from table "fk". 2025-07-03 22:06:43.920 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 4502 WHERE a = 4500; 2025-07-03 22:06:43.922 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_proc" avg read rate: 0.000 MB/s, avg write rate: 0.416 MB/s buffer usage: 504 hits, 0 reads, 5 dirtied WAL usage: 105 records, 2 full page images, 54250 bytes, 0 buffers full system usage: CPU: user: 0.03 s, system: 0.00 s, elapsed: 0.09 s 2025-07-03 22:06:43.941 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.brin_test": index scans: 0 pages: 0 removed, 45 remain, 45 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15329, which was 12 XIDs old when operation ended new relfrozenxid: 9747, which is 1507 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 45 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "brin_test_a_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "brin_test_b_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.425 MB/s buffer usage: 170 hits, 0 reads, 1 dirtied WAL usage: 48 records, 1 full page images, 11716 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.953 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.brin_test" avg read rate: 0.000 MB/s, avg write rate: 0.651 MB/s buffer usage: 111 hits, 0 reads, 1 dirtied WAL usage: 8 records, 0 full page images, 2910 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:43.962 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.spgist_box_tbl": index scans: 0 pages: 0 removed, 34 remain, 34 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 4000 remain, 0 are dead but not yet removable removable cutoff: 15344, which was 0 XIDs old when operation ended new relfrozenxid: 9248, which is 1008 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 34 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "spgist_box_idx": pages: 39 in total, 2 newly deleted, 2 currently deleted, 2 reusable avg read rate: 0.000 MB/s, avg write rate: 14.510 MB/s buffer usage: 149 hits, 0 reads, 7 dirtied WAL usage: 58 records, 7 full page images, 60859 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.964 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.spgist_box_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 62 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 858 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:43.974 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.spgist_text_tbl": index scans: 0 pages: 0 removed, 180 remain, 180 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 11100 remain, 0 are dead but not yet removable removable cutoff: 15344, which was 3 XIDs old when operation ended new relfrozenxid: 9344, which is 1104 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 180 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "spgist_text_idx": pages: 55 in total, 1 newly deleted, 1 currently deleted, 1 reusable avg read rate: 0.000 MB/s, avg write rate: 5.021 MB/s buffer usage: 454 hits, 0 reads, 6 dirtied WAL usage: 202 records, 6 full page images, 61578 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:44.095 UTC client backend[25221] pg_regress/foreign_key ERROR: removing partition "droppk_d" violates foreign key constraint "dropfk_a_fkey_5" 2025-07-03 22:06:44.095 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(2000) is still referenced from table "dropfk". 2025-07-03 22:06:44.095 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk_d; 2025-07-03 22:06:44.096 UTC client backend[25221] pg_regress/foreign_key ERROR: removing partition "droppk2_d" violates foreign key constraint "dropfk_a_fkey_4" 2025-07-03 22:06:44.096 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1500) is still referenced from table "dropfk". 2025-07-03 22:06:44.096 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk2 DETACH PARTITION droppk2_d; 2025-07-03 22:06:44.099 UTC client backend[25221] pg_regress/foreign_key ERROR: removing partition "droppk1" violates foreign key constraint "dropfk_a_fkey_1" 2025-07-03 22:06:44.099 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is still referenced from table "dropfk". 2025-07-03 22:06:44.099 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk1; 2025-07-03 22:06:44.100 UTC client backend[25221] pg_regress/foreign_key ERROR: removing partition "droppk2" violates foreign key constraint "dropfk_a_fkey_2" 2025-07-03 22:06:44.100 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "dropfk". 2025-07-03 22:06:44.100 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk DETACH PARTITION droppk2; 2025-07-03 22:06:44.103 UTC client backend[25221] pg_regress/foreign_key ERROR: removing partition "droppk21" violates foreign key constraint "dropfk_a_fkey_3" 2025-07-03 22:06:44.103 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1000) is still referenced from table "dropfk". 2025-07-03 22:06:44.103 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE droppk2 DETACH PARTITION droppk21; 2025-07-03 22:06:44.106 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk_d because other objects depend on it 2025-07-03 22:06:44.106 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk_d 2025-07-03 22:06:44.106 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.106 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk_d; 2025-07-03 22:06:44.111 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.spgist_text_tbl" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 214 hits, 0 reads, 0 dirtied WAL usage: 4 records, 0 full page images, 2267 bytes, 0 buffers full system usage: CPU: user: 0.04 s, system: 0.00 s, elapsed: 0.13 s 2025-07-03 22:06:44.111 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk2_d because other objects depend on it 2025-07-03 22:06:44.111 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2_d 2025-07-03 22:06:44.111 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.111 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2_d; 2025-07-03 22:06:44.113 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk1 because other objects depend on it 2025-07-03 22:06:44.113 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk1 2025-07-03 22:06:44.113 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.113 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk1; 2025-07-03 22:06:44.115 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk2 because other objects depend on it 2025-07-03 22:06:44.115 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2 2025-07-03 22:06:44.115 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.115 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2; 2025-07-03 22:06:44.116 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk21 because other objects depend on it 2025-07-03 22:06:44.116 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk21 2025-07-03 22:06:44.116 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.116 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk21; 2025-07-03 22:06:44.121 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk_d because other objects depend on it 2025-07-03 22:06:44.121 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk_d 2025-07-03 22:06:44.121 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.121 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk_d; 2025-07-03 22:06:44.125 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk2_d because other objects depend on it 2025-07-03 22:06:44.125 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2_d 2025-07-03 22:06:44.125 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.125 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2_d; 2025-07-03 22:06:44.126 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.brintest_multi": index scans: 0 pages: 0 removed, 35 remain, 35 scanned (100.00% of total), 0 eagerly scanned tuples: 132 removed, 132 remain, 0 are dead but not yet removable removable cutoff: 15363, which was 11 XIDs old when operation ended new relfrozenxid: 10324, which is 31 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 35 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "brinidx_multi": pages: 7 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 515 hits, 0 reads, 0 dirtied WAL usage: 74 records, 0 full page images, 6133 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:44.128 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk1 because other objects depend on it 2025-07-03 22:06:44.128 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk1 2025-07-03 22:06:44.128 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.128 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk1; 2025-07-03 22:06:44.139 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop table droppk2 because other objects depend on it 2025-07-03 22:06:44.139 UTC client backend[25221] pg_regress/foreign_key DETAIL: constraint dropfk_a_fkey on table dropfk depends on table droppk2 2025-07-03 22:06:44.139 UTC client backend[25221] pg_regress/foreign_key HINT: Use DROP ... CASCADE to drop the dependent objects too. 2025-07-03 22:06:44.139 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DROP TABLE droppk2; 2025-07-03 22:06:44.157 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.brintest_multi" avg read rate: 0.000 MB/s, avg write rate: 0.756 MB/s buffer usage: 770 hits, 0 reads, 3 dirtied WAL usage: 41 records, 0 full page images, 23342 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:44.183 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.brintest_bloom": index scans: 0 pages: 0 removed, 58 remain, 58 scanned (100.00% of total), 0 eagerly scanned tuples: 235 removed, 130 remain, 0 are dead but not yet removable removable cutoff: 15384, which was 1 XIDs old when operation ended new relfrozenxid: 10311, which is 13 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 58 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "brinidx_bloom": pages: 10 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 366 hits, 0 reads, 0 dirtied WAL usage: 119 records, 0 full page images, 8933 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:44.198 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.brintest_bloom" avg read rate: 0.000 MB/s, avg write rate: 1.042 MB/s buffer usage: 309 hits, 0 reads, 2 dirtied WAL usage: 47 records, 0 full page images, 26115 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:44.201 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.brin_test_bloom": index scans: 0 pages: 0 removed, 45 remain, 45 scanned (100.00% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15385, which was 2 XIDs old when operation ended new relfrozenxid: 10317, which is 1 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 45 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "brin_test_bloom_a_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "brin_test_bloom_b_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 3.302 MB/s buffer usage: 164 hits, 0 reads, 1 dirtied WAL usage: 48 records, 1 full page images, 11716 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:44.235 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.brin_test_bloom" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 92 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 816 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:44.236 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.public.brin_test_multi": index scans: 0 pages: 0 removed, 45 remain, 1 scanned (2.22% of total), 0 eagerly scanned tuples: 0 removed, 10000 remain, 0 are dead but not yet removable removable cutoff: 15397, which was 1 XIDs old when operation ended frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 0 pages set all-visible, 0 pages set all-frozen (0 were all-visible) index scan not needed: 0 pages from table (0.00% of total) had 0 dead item identifiers removed index "brin_test_multi_a_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable index "brin_test_multi_b_idx": pages: 3 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 70 hits, 0 reads, 0 dirtied WAL usage: 2 records, 0 full page images, 606 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:44.250 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk4" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:44.250 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(50) is not present in table "pk". 2025-07-03 22:06:44.250 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk ATTACH PARTITION fk4 FOR VALUES IN (50); 2025-07-03 22:06:44.257 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.brin_test_multi" avg read rate: 0.000 MB/s, avg write rate: 0.372 MB/s buffer usage: 101 hits, 0 reads, 1 dirtied WAL usage: 8 records, 0 full page images, 2910 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:44.278 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:44.278 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-07-03 22:06:44.278 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk VALUES (1); 2025-07-03 22:06:44.280 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk" violates foreign key constraint "fk_a_fkey" 2025-07-03 22:06:44.280 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(1) is not present in table "pk". 2025-07-03 22:06:44.280 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:44.285 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_catalog.pg_depend": index scans: 1 pages: 0 removed, 134 remain, 134 scanned (100.00% of total), 0 eagerly scanned tuples: 4734 removed, 6679 remain, 0 are dead but not yet removable removable cutoff: 15405, which was 6 XIDs old when operation ended new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 4 pages from table (2.99% of total) had 45 tuples frozen visibility map: 120 pages set all-visible, 28 pages set all-frozen (0 were all-visible) index scan needed: 118 pages from table (88.06% of total) had 13598 dead item identifiers removed index "pg_depend_depender_index": pages: 153 in total, 2 newly deleted, 12 currently deleted, 10 reusable index "pg_depend_reference_index": pages: 95 in total, 4 newly deleted, 4 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 4.504 MB/s buffer usage: 757 hits, 0 reads, 16 dirtied WAL usage: 522 records, 15 full page images, 161340 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.02 s 2025-07-03 22:06:44.321 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.pg_catalog.pg_depend" avg read rate: 0.000 MB/s, avg write rate: 0.217 MB/s buffer usage: 247 hits, 0 reads, 1 dirtied WAL usage: 22 records, 1 full page images, 14838 bytes, 0 buffers full system usage: CPU: user: 0.01 s, system: 0.00 s, elapsed: 0.03 s 2025-07-03 22:06:44.322 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.rtest_t1" avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s buffer usage: 30 hits, 0 reads, 0 dirtied WAL usage: 5 records, 0 full page images, 812 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:44.335 UTC autovacuum worker[25621] LOG: automatic analyze of table "regression.public.test_tsvector" avg read rate: 0.000 MB/s, avg write rate: 1.674 MB/s buffer usage: 124 hits, 0 reads, 3 dirtied WAL usage: 21 records, 3 full page images, 31792 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.01 s 2025-07-03 22:06:44.337 UTC autovacuum worker[25621] LOG: automatic vacuum of table "regression.pg_toast.pg_toast_2619": index scans: 1 pages: 0 removed, 26 remain, 26 scanned (100.00% of total), 0 eagerly scanned tuples: 68 removed, 33 remain, 2 are dead but not yet removable removable cutoff: 15422, which was 3 XIDs old when operation ended new relfrozenxid: 13105, which is 12305 XIDs ahead of previous value new relminmxid: 3, which is 2 MXIDs ahead of previous value frozen: 0 pages from table (0.00% of total) had 0 tuples frozen visibility map: 24 pages set all-visible, 17 pages set all-frozen (0 were all-visible) index scan needed: 22 pages from table (84.62% of total) had 85 dead item identifiers removed index "pg_toast_2619_index": pages: 2 in total, 0 newly deleted, 0 currently deleted, 0 reusable avg read rate: 0.000 MB/s, avg write rate: 25.448 MB/s buffer usage: 98 hits, 0 reads, 2 dirtied WAL usage: 70 records, 3 full page images, 29263 bytes, 0 buffers full system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-07-03 22:06:44.402 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot alter constraint "ref_f1_f2_fkey" on relation "ref22" 2025-07-03 22:06:44.402 UTC client backend[25221] pg_regress/foreign_key DETAIL: Constraint "ref_f1_f2_fkey" is derived from constraint "ref_f1_f2_fkey" of relation "ref". 2025-07-03 22:06:44.402 UTC client backend[25221] pg_regress/foreign_key HINT: You may alter the constraint it derives from instead. 2025-07-03 22:06:44.402 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE ref22 ALTER CONSTRAINT ref_f1_f2_fkey DEFERRABLE INITIALLY IMMEDIATE; 2025-07-03 22:06:44.479 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot alter constraint "ref_f1_f2_fkey_1" on relation "ref" 2025-07-03 22:06:44.479 UTC client backend[25221] pg_regress/foreign_key DETAIL: Constraint "ref_f1_f2_fkey_1" is derived from constraint "ref_f1_f2_fkey" of relation "ref". 2025-07-03 22:06:44.479 UTC client backend[25221] pg_regress/foreign_key HINT: You may alter the constraint it derives from instead. 2025-07-03 22:06:44.479 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE ref ALTER CONSTRAINT ref_f1_f2_fkey_1 DEFERRABLE INITIALLY DEFERRED; 2025-07-03 22:06:44.815 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk11" violates RESTRICT setting of foreign key constraint "fk_a_fkey_2" on table "fk" 2025-07-03 22:06:44.815 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(20) is referenced from table "fk". 2025-07-03 22:06:44.815 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM pk WHERE a = 20; 2025-07-03 22:06:44.816 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "pk" violates RESTRICT setting of foreign key constraint "fk_a_fkey" on table "fk" 2025-07-03 22:06:44.816 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (a)=(30) is referenced from table "fk". 2025-07-03 22:06:44.816 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE pk SET a = 90 WHERE a = 30; 2025-07-03 22:06:44.845 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot ALTER TABLE "tbl2_p1" because it has pending trigger events 2025-07-03 22:06:44.845 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fkpart8.tbl2 DROP CONSTRAINT tbl2_f1_fkey; 2025-07-03 22:06:44.942 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "tbl1" violates foreign key constraint "tbl2_f1_fkey" on table "tbl2" 2025-07-03 22:06:44.942 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(0) is still referenced from table "tbl2". 2025-07-03 22:06:44.942 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:44.948 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl4_f1_fkey" on table "tbl4" 2025-07-03 22:06:44.948 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl4". 2025-07-03 22:06:44.948 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:44.970 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl5_f1_fkey" on table "tbl5" 2025-07-03 22:06:44.970 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl5". 2025-07-03 22:06:44.970 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fkpart10.tbl3 SET f1 = f1 * -3; 2025-07-03 22:06:44.978 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "tbl3" violates foreign key constraint "tbl4_f1_fkey" on table "tbl4" 2025-07-03 22:06:44.978 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (f1)=(-2) is still referenced from table "tbl4". 2025-07-03 22:06:44.978 UTC client backend[25221] pg_regress/foreign_key STATEMENT: COMMIT; 2025-07-03 22:06:45.092 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot move tuple across partitions when a non-root ancestor of the source partition is directly referenced in a foreign key 2025-07-03 22:06:45.092 UTC client backend[25221] pg_regress/foreign_key DETAIL: A foreign key points to ancestor "pk1" but not the root ancestor "pk". 2025-07-03 22:06:45.092 UTC client backend[25221] pg_regress/foreign_key HINT: Consider defining the foreign key on table "pk". 2025-07-03 22:06:45.092 UTC client backend[25221] pg_regress/foreign_key STATEMENT: UPDATE fkpart11.pk SET a = a - 1; 2025-07-03 22:06:45.290 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_r_2_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey" 2025-07-03 22:06:45.290 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (p_id, p_jd)=(2, 1) is not present in table "fk_p". 2025-07-03 22:06:45.290 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_r VALUES (2, 2, 1); 2025-07-03 22:06:45.322 UTC client backend[25221] pg_regress/foreign_key ERROR: insert or update on table "fk_r_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey" 2025-07-03 22:06:45.322 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (p_id, p_jd)=(1, 2) is not present in table "fk_p". 2025-07-03 22:06:45.322 UTC client backend[25221] pg_regress/foreign_key STATEMENT: INSERT INTO fk_r_1 (id, p_id, p_jd) VALUES (2, 1, 2); 2025-07-03 22:06:45.324 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_p_1_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey_7" on table "fk_r_1" 2025-07-03 22:06:45.324 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id, jd)=(1, 1) is still referenced from table "fk_r_1". 2025-07-03 22:06:45.324 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM fk_p; 2025-07-03 22:06:45.382 UTC client backend[25221] pg_regress/foreign_key ERROR: update or delete on table "fk_p_1_1" violates foreign key constraint "fk_r_p_id_p_jd_fkey_2" on table "fk_r" 2025-07-03 22:06:45.382 UTC client backend[25221] pg_regress/foreign_key DETAIL: Key (id, jd)=(1, 1) is still referenced from table "fk_r". 2025-07-03 22:06:45.382 UTC client backend[25221] pg_regress/foreign_key STATEMENT: DELETE FROM fk_p; 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey" of relation "fk_r_1" 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r_1 DROP CONSTRAINT fk_r_p_id_p_jd_fkey; 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey_1" of relation "fk_r" 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r DROP CONSTRAINT fk_r_p_id_p_jd_fkey_1; 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key ERROR: cannot drop inherited constraint "fk_r_p_id_p_jd_fkey" of relation "fk_r_2" 2025-07-03 22:06:45.396 UTC client backend[25221] pg_regress/foreign_key STATEMENT: ALTER TABLE fk_r_2 DROP CONSTRAINT fk_r_p_id_p_jd_fkey; 2025-07-03 22:06:45.447 UTC client backend[25221] pg_regress/foreign_key LOG: disconnection: session time: 0:00:09.356 user=postgres database=regression host=[local] 2025-07-03 22:06:45.700 UTC not initialized[26024] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.701 UTC client backend[26024] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.701 UTC client backend[26024] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/json_encoding 2025-07-03 22:06:45.706 UTC not initialized[26026] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.707 UTC client backend[26026] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.707 UTC client backend[26026] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonb 2025-07-03 22:06:45.712 UTC not initialized[26027] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.714 UTC client backend[26027] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.714 UTC client backend[26027] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/json 2025-07-03 22:06:45.716 UTC not initialized[26029] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.717 UTC client backend[26029] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.717 UTC client backend[26029] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson_jsontable 2025-07-03 22:06:45.723 UTC not initialized[26033] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.725 UTC not initialized[26031] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.726 UTC client backend[26033] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.726 UTC client backend[26033] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson_queryfuncs 2025-07-03 22:06:45.726 UTC client backend[26031] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.726 UTC client backend[26031] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonb_jsonpath 2025-07-03 22:06:45.728 UTC not initialized[26030] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.728 UTC not initialized[26034] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.729 UTC client backend[26030] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.729 UTC client backend[26030] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonpath_encoding 2025-07-03 22:06:45.730 UTC client backend[26034] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.730 UTC client backend[26034] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/sqljson 2025-07-03 22:06:45.734 UTC not initialized[26036] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:45.735 UTC client backend[26036] [unknown] LOG: connection authenticated: user="postgres" method=trust (/tmp/cirrus-ci-build/src/test/regress/tmp_check/data/pg_hba.conf:117) 2025-07-03 22:06:45.735 UTC client backend[26036] [unknown] LOG: connection authorized: user=postgres database=regression application_name=pg_regress/jsonpath 2025-07-03 22:06:45.792 UTC client backend[26027] pg_regress/json LOG: connection ready: setup total=95.529 ms, fork=11.682 ms, authentication=0.381 ms 2025-07-03 22:06:45.806 UTC client backend[26024] pg_regress/json_encoding LOG: connection ready: setup total=114.819 ms, fork=8.224 ms, authentication=0.386 ms 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json DETAIL: Token "'" is invalid. 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: '... 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json STATEMENT: SELECT $$''$$::json; 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json DETAIL: Token ""abc" is invalid. 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: "abc 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '"abc'::json; 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json DETAIL: Character with value 0x0a must be escaped. 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: "abc 2025-07-03 22:06:45.807 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '"abc def"'::json; 2025-07-03 22:06:45.808 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.808 UTC client backend[26027] pg_regress/json DETAIL: Escape sequence "\v" is invalid. 2025-07-03 22:06:45.808 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: "\v... 2025-07-03 22:06:45.808 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '"\v"'::json; 2025-07-03 22:06:45.809 UTC client backend[26029] pg_regress/sqljson_jsontable LOG: connection ready: setup total=110.762 ms, fork=17.172 ms, authentication=0.391 ms 2025-07-03 22:06:45.810 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: syntax error at or near "(" at character 18 2025-07-03 22:06:45.810 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT JSON_TABLE('[]', '$'); 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 72 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') DEFAULT 1 ON ERROR); 2025-07-03 22:06:45.811 UTC client backend[26031] pg_regress/jsonb_jsonpath LOG: connection ready: setup total=109.400 ms, fork=19.807 ms, authentication=0.407 ms 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 72 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-07-03 22:06:45.811 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') NULL ON ERROR); 2025-07-03 22:06:45.816 UTC client backend[26034] pg_regress/sqljson LOG: connection ready: setup total=107.839 ms, fork=20.323 ms, authentication=0.400 ms 2025-07-03 22:06:45.817 UTC client backend[26034] pg_regress/sqljson ERROR: syntax error at or near ")" at character 13 2025-07-03 22:06:45.817 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON(); 2025-07-03 22:06:45.817 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.817 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') ERROR ON ERROR); 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: js2 at character 63 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' as js2 COLUMNS (js2 int path '$')); 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: syntax error at or near ")" at character 45 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(NULL, '$' COLUMNS ()); 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: JSON_TABLE function has 1 columns available but 2 columns specified 2025-07-03 22:06:45.818 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE (NULL::jsonb, '$' COLUMNS (v1 timestamp)) AS f (v1, v2); 2025-07-03 22:06:45.819 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: js2 at character 74 2025-07-03 22:06:45.819 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' COLUMNS (js2 int path '$', js2 int path '$')); 2025-07-03 22:06:45.819 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.819 UTC client backend[26027] pg_regress/json DETAIL: Token "01" is invalid. 2025-07-03 22:06:45.819 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 01 2025-07-03 22:06:45.819 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '01'::json; 2025-07-03 22:06:45.820 UTC client backend[26026] pg_regress/jsonb LOG: connection ready: setup total=126.626 ms, fork=11.423 ms, authentication=0.378 ms 2025-07-03 22:06:45.822 UTC client backend[26030] pg_regress/jsonpath_encoding LOG: connection ready: setup total=122.459 ms, fork=27.245 ms, authentication=0.378 ms 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json DETAIL: Token "1f2" is invalid. 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 1f2 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '1f2'::json; 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json DETAIL: Token "0.x1" is invalid. 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 0.x1 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '0.x1'::json; 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json DETAIL: Token "1.3ex100" is invalid. 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 1.3ex100 2025-07-03 22:06:45.824 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '1.3ex100'::json; 2025-07-03 22:06:45.825 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.825 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.825 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u" 2025-07-03 22:06:45.825 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u"'::json; 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u00" 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u00"'::json; 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u000g... 2025-07-03 22:06:45.826 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u000g"'::json; 2025-07-03 22:06:45.826 UTC client backend[26034] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 28 2025-07-03 22:06:45.826 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON('{ "a" : 1 } ' FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json DETAIL: Expected JSON value, but found "]". 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: [1,2,] 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '[1,2,]'::json; 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: [1,2 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '[1,2'::json; 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: [1,[2] 2025-07-03 22:06:45.826 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '[1,[2]'::json; 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json DETAIL: Expected ":", but found "}". 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc"} 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc"}'::json; 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json DETAIL: Expected string or "}", but found "1". 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {1... 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{1:"abc"}'::json; 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json DETAIL: Expected ":", but found ",". 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc",... 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc",1}'::json; 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json DETAIL: Token "=" is invalid. 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc"=... 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc"=1}'::json; 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json DETAIL: Expected JSON value, but found ":". 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc"::... 2025-07-03 22:06:45.827 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc"::1}'::json; 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json DETAIL: Expected "," or "}", but found ":". 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc":1:... 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc":1:2}'::json; 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json DETAIL: Expected string, but found "3". 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: {"abc":1,3... 2025-07-03 22:06:45.828 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{"abc":1,3}'::json; 2025-07-03 22:06:45.829 UTC client backend[26027] pg_regress/json ERROR: stack depth limit exceeded 2025-07-03 22:06:45.829 UTC client backend[26027] pg_regress/json HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-07-03 22:06:45.829 UTC client backend[26027] pg_regress/json STATEMENT: SELECT repeat('[', 10000)::json; 2025-07-03 22:06:45.829 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8 2025-07-03 22:06:45.829 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u"'::jsonpath; 2025-07-03 22:06:45.830 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8 2025-07-03 22:06:45.830 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u00"'::jsonpath; 2025-07-03 22:06:45.831 UTC client backend[26027] pg_regress/json ERROR: stack depth limit exceeded 2025-07-03 22:06:45.831 UTC client backend[26027] pg_regress/json HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-07-03 22:06:45.831 UTC client backend[26027] pg_regress/json STATEMENT: SELECT repeat('{"a":', 10000)::json; 2025-07-03 22:06:45.832 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8 2025-07-03 22:06:45.832 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u000g"'::jsonpath; 2025-07-03 22:06:45.832 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-07-03 22:06:45.832 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.832 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '"\u0000"'::jsonpath; 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '"\ud83d\ud83d"'::jsonpath; 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '"\ude04\ud83d"'::jsonpath; 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.833 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '"\ud83dX"'::jsonpath; 2025-07-03 22:06:45.834 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.834 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.834 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '"\ude04X"'::jsonpath; 2025-07-03 22:06:45.834 UTC client backend[26034] pg_regress/sqljson ERROR: cannot use non-string types with WITH UNIQUE KEYS clause at character 8 2025-07-03 22:06:45.834 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON(' 1 '::json WITH UNIQUE KEYS); 2025-07-03 22:06:45.834 UTC client backend[26034] pg_regress/sqljson ERROR: cannot cast type integer to json at character 13 2025-07-03 22:06:45.834 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON(123); 2025-07-03 22:06:45.835 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:45.835 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON('{"a": 1, "a": 2}' WITH UNIQUE KEYS); 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83d\ud83d... 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ud83d\ud83d" }' -> 'a'; 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ude04\ud83d" }' -> 'a'; 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83dX... 2025-07-03 22:06:45.835 UTC client backend[26024] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ud83dX" }' -> 'a'; 2025-07-03 22:06:45.837 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.837 UTC client backend[26027] pg_regress/json DETAIL: Expected end of input, but found "false". 2025-07-03 22:06:45.837 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: true false 2025-07-03 22:06:45.837 UTC client backend[26027] pg_regress/json STATEMENT: SELECT 'true false'::json; 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json DETAIL: Expected end of input, but found ",". 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: true,... 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json STATEMENT: SELECT 'true, false'::json; 2025-07-03 22:06:45.838 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-07-03 22:06:45.838 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.838 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '"null \u0000 escape"'::jsonpath as not_unescaped; 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json DETAIL: Token "truf" is invalid. 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: truf 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json STATEMENT: SELECT 'truf'::json; 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json DETAIL: Token "trues" is invalid. 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: trues 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json STATEMENT: SELECT 'trues'::json; 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 2025-07-03 22:06:45.838 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ''::json; 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u"'::jsonpath; 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 1: 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ' '::json; 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u00"'::jsonpath; 2025-07-03 22:06:45.839 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json 2025-07-03 22:06:45.839 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.839 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-07-03 22:06:45.839 UTC client backend[26024] pg_regress/json_encoding STATEMENT: select json '{ "a": "\ude04X" }' -> 'a'; 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u000g"'::jsonpath; 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.839 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: SELECT '$."\u0000"'::jsonpath; 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json DETAIL: Expected JSON value, but found ",". 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 3: "two":,... 2025-07-03 22:06:45.839 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{ "one": 1, "two":,"two", -- ERROR extraneous comma before field "two" "three": true}'::json; 2025-07-03 22:06:45.840 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.840 UTC client backend[26027] pg_regress/json DETAIL: Expected JSON value, but found "}". 2025-07-03 22:06:45.840 UTC client backend[26027] pg_regress/json CONTEXT: JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":} 2025-07-03 22:06:45.840 UTC client backend[26027] pg_regress/json STATEMENT: SELECT '{ "one": 1, "two":"two", "averyveryveryveryveryveryveryveryveryverylongfieldname":}'::json; 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '$."\ud83d\ud83d"'::jsonpath; 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '$."\ude04\ud83d"'::jsonpath; 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '$."\ud83dX"'::jsonpath; 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: invalid input syntax for type jsonpath at character 8 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.841 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '$."\ude04X"'::jsonpath; 2025-07-03 22:06:45.843 UTC client backend[26030] pg_regress/jsonpath_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-07-03 22:06:45.843 UTC client backend[26030] pg_regress/jsonpath_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.843 UTC client backend[26030] pg_regress/jsonpath_encoding STATEMENT: select '$."null \u0000 escape"'::jsonpath as not_unescaped; 2025-07-03 22:06:45.844 UTC client backend[26024] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence 2025-07-03 22:06:45.844 UTC client backend[26024] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.844 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-07-03 22:06:45.844 UTC client backend[26024] pg_regress/json_encoding STATEMENT: select json '{ "a": "null \u0000 escape" }' ->> 'a' as fails; 2025-07-03 22:06:45.844 UTC client backend[26034] pg_regress/sqljson ERROR: syntax error at or near ")" at character 20 2025-07-03 22:06:45.844 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SCALAR(); 2025-07-03 22:06:45.845 UTC client backend[26033] pg_regress/sqljson_queryfuncs LOG: connection ready: setup total=139.365 ms, fork=13.533 ms, authentication=0.366 ms 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u" 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u"'::jsonb; 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u00" 2025-07-03 22:06:45.845 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u00"'::jsonb; 2025-07-03 22:06:45.846 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.846 UTC client backend[26024] pg_regress/json_encoding DETAIL: "\u" must be followed by four hexadecimal digits. 2025-07-03 22:06:45.846 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u000g... 2025-07-03 22:06:45.846 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u000g"'::jsonb; 2025-07-03 22:06:45.847 UTC client backend[26030] pg_regress/jsonpath_encoding LOG: disconnection: session time: 0:00:00.119 user=postgres database=regression host=[local] 2025-07-03 22:06:45.849 UTC client backend[26024] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 8 2025-07-03 22:06:45.849 UTC client backend[26024] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.849 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: "\u0000... 2025-07-03 22:06:45.849 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT '"\u0000"'::jsonb; 2025-07-03 22:06:45.852 UTC client backend[26036] pg_regress/jsonpath LOG: connection ready: setup total=139.644 ms, fork=14.558 ms, authentication=0.467 ms 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode high surrogate must not follow a high surrogate. 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83d\ud83d... 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ud83d\ud83d" }' -> 'a'; 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-07-03 22:06:45.853 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ude04\ud83d" }' -> 'a'; 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ud83dX... 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ud83dX" }' -> 'a'; 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding ERROR: invalid input syntax for type json at character 14 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding DETAIL: Unicode low surrogate must follow a high surrogate. 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "\ude04... 2025-07-03 22:06:45.854 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "\ude04X" }' -> 'a'; 2025-07-03 22:06:45.856 UTC client backend[26024] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 14 2025-07-03 22:06:45.856 UTC client backend[26024] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.856 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-07-03 22:06:45.856 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "null \u0000 escape" }' as fails; 2025-07-03 22:06:45.857 UTC client backend[26036] pg_regress/jsonpath ERROR: invalid input syntax for type jsonpath: "" at character 8 2025-07-03 22:06:45.857 UTC client backend[26036] pg_regress/jsonpath STATEMENT: select ''::jsonpath; 2025-07-03 22:06:45.858 UTC client backend[26034] pg_regress/sqljson ERROR: syntax error at or near ")" at character 23 2025-07-03 22:06:45.858 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE(); 2025-07-03 22:06:45.861 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.861 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_EXISTS(jsonb '1', 'strict $.a' ERROR ON ERROR); 2025-07-03 22:06:45.865 UTC client backend[26034] pg_regress/sqljson ERROR: cannot use type jsonb in RETURNING clause of JSON_SERIALIZE() 2025-07-03 22:06:45.865 UTC client backend[26034] pg_regress/sqljson HINT: Try returning a string type or bytea. 2025-07-03 22:06:45.865 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING jsonb); 2025-07-03 22:06:45.866 UTC client backend[26024] pg_regress/json_encoding ERROR: unsupported Unicode escape sequence at character 14 2025-07-03 22:06:45.866 UTC client backend[26024] pg_regress/json_encoding DETAIL: \u0000 cannot be converted to text. 2025-07-03 22:06:45.866 UTC client backend[26024] pg_regress/json_encoding CONTEXT: JSON data, line 1: { "a": "null \u0000... 2025-07-03 22:06:45.866 UTC client backend[26024] pg_regress/json_encoding STATEMENT: SELECT jsonb '{ "a": "null \u0000 escape" }' ->> 'a' as fails; 2025-07-03 22:06:45.871 UTC client backend[26034] pg_regress/sqljson ERROR: cannot set JSON encoding for non-bytea output types at character 35 2025-07-03 22:06:45.871 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.871 UTC client backend[26034] pg_regress/sqljson ERROR: unrecognized JSON encoding: invalid_encoding at character 56 2025-07-03 22:06:45.871 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING); 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson ERROR: unsupported JSON encoding at character 36 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF16); 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson ERROR: unsupported JSON encoding at character 36 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF32); 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson ERROR: cannot use non-string types with explicit FORMAT JSON clause at character 37 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON); 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 37 2025-07-03 22:06:45.874 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.876 UTC client backend[26034] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 38 2025-07-03 22:06:45.876 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.877 UTC client backend[26034] pg_regress/sqljson ERROR: JSON ENCODING clause is only allowed for bytea input type at character 39 2025-07-03 22:06:45.877 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('foo': NULL::jsonb FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.878 UTC client backend[26034] pg_regress/sqljson ERROR: null value not allowed for object key 2025-07-03 22:06:45.878 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(NULL: 1); 2025-07-03 22:06:45.880 UTC client backend[26024] pg_regress/json_encoding LOG: disconnection: session time: 0:00:00.180 user=postgres database=regression host=[local] 2025-07-03 22:06:45.887 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-07-03 22:06:45.887 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'strict $[1]'); 2025-07-03 22:06:45.888 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of integer range 2025-07-03 22:06:45.888 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'lax $[10000000000000000]'); 2025-07-03 22:06:45.891 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of integer range 2025-07-03 22:06:45.891 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1]', 'strict $[10000000000000000]'); 2025-07-03 22:06:45.894 UTC client backend[26034] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:45.894 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(json '[1]': 123); 2025-07-03 22:06:45.894 UTC client backend[26034] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:45.894 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(ARRAY[1,2,3]: 'aaa'); 2025-07-03 22:06:45.904 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.904 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_exists('[{"a": 1}, {"a": 2}, 3]', 'strict $[*].a', silent => false); 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "2" 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '3': 1, repeat('x', 1000): 1, 2: repeat('a', 100) WITH UNIQUE); 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL WITH UNIQUE); 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:45.905 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE); 2025-07-03 22:06:45.906 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.23" 2025-07-03 22:06:45.906 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"1.23"', '$' RETURNING int ERROR ON ERROR); 2025-07-03 22:06:45.906 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.906 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $.a'); 2025-07-03 22:06:45.906 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard member accessor can only be applied to an object 2025-07-03 22:06:45.906 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $.*'); 2025-07-03 22:06:45.907 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.907 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.a'); 2025-07-03 22:06:45.907 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:45.907 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL NULL ON NULL WITH UNIQUE RETURNING jsonb); 2025-07-03 22:06:45.907 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:45.907 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE RETURNING jsonb); 2025-07-03 22:06:45.908 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:45.908 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 NULL ON NULL WITH UNIQUE); 2025-07-03 22:06:45.908 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: JSON object does not contain key "a" 2025-07-03 22:06:45.908 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', 'strict $.a'); 2025-07-03 22:06:45.908 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:45.908 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE); 2025-07-03 22:06:45.909 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:45.909 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE RETURNING jsonb); 2025-07-03 22:06:45.913 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-07-03 22:06:45.913 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING char(2) ERROR ON ERROR); 2025-07-03 22:06:45.913 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array accessor can only be applied to an array 2025-07-03 22:06:45.913 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $[1]'); 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard array accessor can only be applied to an array 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', 'strict $[*]'); 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $[1]'); 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is not a single numeric value 2025-07-03 22:06:45.914 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $["a"]'); 2025-07-03 22:06:45.920 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-07-03 22:06:45.920 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[12, {"a": 13}, {"b": 14}]', 'lax $[0 to 10 / 0].a'); 2025-07-03 22:06:45.924 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.924 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3]', 'strict $[*].a'); 2025-07-03 22:06:45.925 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is out of bounds 2025-07-03 22:06:45.925 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $[last]'); 2025-07-03 22:06:45.928 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type 2025-07-03 22:06:45.928 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: value for domain jsonb_test_domain violates check constraint "jsonb_test_domain_check" 2025-07-03 22:06:45.928 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '{"d1": "H"}', '$' COLUMNS (js1 jsonb_test_domain PATH '$.a2' DEFAULT 'foo'::jsonb_test_domain ON EMPTY)); 2025-07-03 22:06:45.932 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath array subscript is not a single numeric value 2025-07-03 22:06:45.932 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3]', '$[last ? (@.type() == "string")]'); 2025-07-03 22:06:45.935 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: could not find jsonpath variable "value" 2025-07-03 22:06:45.935 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)'); 2025-07-03 22:06:45.935 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: "vars" argument is not an object 2025-07-03 22:06:45.935 UTC client backend[26031] pg_regress/jsonb_jsonpath DETAIL: Jsonpath parameters should be encoded as key-value pairs of "vars" object. 2025-07-03 22:06:45.935 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '1'); 2025-07-03 22:06:45.935 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "aaa" 2025-07-03 22:06:45.935 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int ERROR ON ERROR); 2025-07-03 22:06:45.936 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: "vars" argument is not an object 2025-07-03 22:06:45.936 UTC client backend[26031] pg_regress/jsonb_jsonpath DETAIL: Jsonpath parameters should be encoded as key-value pairs of "vars" object. 2025-07-03 22:06:45.936 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '[{"value" : 13}]'); 2025-07-03 22:06:45.936 UTC client backend[26036] pg_regress/jsonpath ERROR: LAST is allowed only in array subscripts at character 8 2025-07-03 22:06:45.936 UTC client backend[26036] pg_regress/jsonpath STATEMENT: select 'last'::jsonpath; 2025-07-03 22:06:45.937 UTC client backend[26036] pg_regress/jsonpath ERROR: LAST is allowed only in array subscripts at character 8 2025-07-03 22:06:45.937 UTC client backend[26036] pg_regress/jsonpath STATEMENT: select '$ ? (last > 0)'::jsonpath; 2025-07-03 22:06:45.937 UTC client backend[26034] pg_regress/sqljson ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:45.937 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('happy'::mood: '123'::jsonb); 2025-07-03 22:06:45.941 UTC client backend[26036] pg_regress/jsonpath ERROR: trailing junk after numeric literal at or near "1.t" of jsonpath input at character 8 2025-07-03 22:06:45.941 UTC client backend[26036] pg_regress/jsonpath STATEMENT: select '1.type()'::jsonpath; 2025-07-03 22:06:45.943 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.943 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "'" is invalid. 2025-07-03 22:06:45.943 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: '... 2025-07-03 22:06:45.943 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT $$''$$::jsonb; 2025-07-03 22:06:45.944 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.944 UTC client backend[26026] pg_regress/jsonb DETAIL: Token ""abc" is invalid. 2025-07-03 22:06:45.944 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: "abc 2025-07-03 22:06:45.944 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '"abc'::jsonb; 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb DETAIL: Character with value 0x0a must be escaped. 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: "abc 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '"abc def"'::jsonb; 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb DETAIL: Escape sequence "\v" is invalid. 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: "\v... 2025-07-03 22:06:45.945 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '"\v"'::jsonb; 2025-07-03 22:06:45.947 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.947 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "01" is invalid. 2025-07-03 22:06:45.947 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 01 2025-07-03 22:06:45.947 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '01'::jsonb; TRAP: failed Assert("v->type == jpiAnd || v->type == jpiOr || v->type == jpiEqual || v->type == jpiNotEqual || v->type == jpiLess || v->type == jpiGreater || v->type == jpiLessOrEqual || v->type == jpiGreaterOrEqual || v->type == jpiAdd || v->type == jpiSub || v->type == jpiMul || v->type == jpiDiv || v->type == jpiMod || v->type == jpiStartsWith || v->type == jpiDecimal"), File: "jsonpath.c", Line: 1265, PID: 26036 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "1f2" is invalid. 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 1f2 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '1f2'::jsonb; 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "0.x1" is invalid. 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 0.x1 2025-07-03 22:06:45.950 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '0.x1'::jsonb; /lib/x86_64-linux-gnu/libasan.so.8(+0x51f31)[0x7f12dcc51f31] postgres: postgres regression [local] SELECT(ExceptionalCondition+0xe6)[0x55e74edbedd0] postgres: postgres regression [local] SELECT(jspGetLeftArg+0x65)[0x55e74ebde680] postgres: postgres regression [local] SELECT(+0xfe6d1f)[0x55e74ebdfd1f] postgres: postgres regression [local] SELECT(+0xfe7014)[0x55e74ebe0014] postgres: postgres regression [local] SELECT(+0xfe7156)[0x55e74ebe0156] postgres: postgres regression [local] SELECT(jsonpath_out+0x4f)[0x55e74ebe026d] postgres: postgres regression [local] SELECT(FunctionCall1Coll+0x1a9)[0x55e74edd4929] postgres: postgres regression [local] SELECT(OutputFunctionCall+0x11)[0x55e74edd8766] postgres: postgres regression [local] SELECT(+0x467848)[0x55e74e060848] postgres: postgres regression [local] SELECT(+0x96410e)[0x55e74e55d10e] postgres: postgres regression [local] SELECT(standard_ExecutorRun+0x3e6)[0x55e74e55ef2a] postgres: postgres regression [local] SELECT(ExecutorRun+0x1c)[0x55e74e55ef8a] postgres: postgres regression [local] SELECT(+0xea36bd)[0x55e74ea9c6bd] postgres: postgres regression [local] SELECT(PortalRun+0x6a5)[0x55e74eaa04a1] postgres: postgres regression [local] SELECT(+0xe9e335)[0x55e74ea97335] postgres: postgres regression [local] SELECT(PostgresMain+0x1109)[0x55e74ea9b5ff] postgres: postgres regression [local] SELECT(BackendMain+0x11b)[0x55e74ea8d242] postgres: postgres regression [local] SELECT(postmaster_child_launch+0x23e)[0x55e74e8cff44] postgres: postgres regression [local] SELECT(+0xcdcf62)[0x55e74e8d5f62] postgres: postgres regression [local] SELECT(+0xcdffed)[0x55e74e8d8fed] postgres: postgres regression [local] SELECT(PostmasterMain+0x1c41)[0x55e74e8db137] postgres: postgres regression [local] SELECT(main+0x2a2)[0x55e74e66d4f4] /lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7f12dbb7824a] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7f12dbb78305] postgres: postgres regression [local] SELECT(_start+0x21)[0x55e74e032451] 2025-07-03 22:06:45.953 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.953 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "1.3ex100" is invalid. 2025-07-03 22:06:45.953 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 1.3ex100 2025-07-03 22:06:45.953 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '1.3ex100'::jsonb; 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected JSON value, but found "]". 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,2,] 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '[1,2,]'::jsonb; 2025-07-03 22:06:45.955 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (NULL) to the RETURNING type 2025-07-03 22:06:45.955 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: domain sqljsonb_int_not_null does not allow null values 2025-07-03 22:06:45.955 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null); 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,2 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '[1,2'::jsonb; 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: [1,[2] 2025-07-03 22:06:45.955 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '[1,[2]'::jsonb; 2025-07-03 22:06:45.955 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-07-03 22:06:45.955 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null ERROR ON ERROR); 2025-07-03 22:06:45.956 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-07-03 22:06:45.956 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null DEFAULT 2 ON EMPTY ERROR ON ERROR); 2025-07-03 22:06:45.956 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.956 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected ":", but found "}". 2025-07-03 22:06:45.956 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"} 2025-07-03 22:06:45.956 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc"}'::jsonb; 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected string or "}", but found "1". 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {1... 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{1:"abc"}'::jsonb; 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected ":", but found ",". 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc",... 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc",1}'::jsonb; 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "=" is invalid. 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"=... 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc"=1}'::jsonb; 2025-07-03 22:06:45.957 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: domain sqljsonb_int_not_null does not allow null values 2025-07-03 22:06:45.957 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', '$.a' RETURNING sqljsonb_int_not_null DEFAULT NULL ON EMPTY ERROR ON ERROR); 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected JSON value, but found ":". 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc"::... 2025-07-03 22:06:45.957 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc"::1}'::jsonb; 2025-07-03 22:06:45.958 UTC client backend[26034] pg_regress/sqljson ERROR: cannot set JSON encoding for non-bytea output types at character 34 2025-07-03 22:06:45.958 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING UTF8); 2025-07-03 22:06:45.958 UTC client backend[26034] pg_regress/sqljson ERROR: unrecognized JSON encoding: invalid_encoding at character 55 2025-07-03 22:06:45.958 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING); 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected "," or "}", but found ":". 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc":1:... 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc":1:2}'::jsonb; 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected string, but found "3". 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: {"abc":1,3... 2025-07-03 22:06:45.959 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{"abc":1,3}'::jsonb; 2025-07-03 22:06:45.960 UTC client backend[26026] pg_regress/jsonb ERROR: stack depth limit exceeded 2025-07-03 22:06:45.960 UTC client backend[26026] pg_regress/jsonb HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-07-03 22:06:45.960 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT repeat('[', 10000)::jsonb; 2025-07-03 22:06:45.963 UTC client backend[26034] pg_regress/sqljson ERROR: unsupported JSON encoding at character 35 2025-07-03 22:06:45.963 UTC client backend[26034] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-07-03 22:06:45.963 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF16); 2025-07-03 22:06:45.964 UTC client backend[26034] pg_regress/sqljson ERROR: unsupported JSON encoding at character 35 2025-07-03 22:06:45.964 UTC client backend[26034] pg_regress/sqljson HINT: Only UTF8 JSON encoding is supported. 2025-07-03 22:06:45.964 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF32); 2025-07-03 22:06:45.964 UTC client backend[26026] pg_regress/jsonb ERROR: stack depth limit exceeded 2025-07-03 22:06:45.964 UTC client backend[26026] pg_regress/jsonb HINT: Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate. 2025-07-03 22:06:45.964 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT repeat('{"a":', 10000)::jsonb; 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected end of input, but found "false". 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: true false 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT 'true false'::jsonb; 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected end of input, but found ",". 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: true,... 2025-07-03 22:06:45.968 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT 'true, false'::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "truf" is invalid. 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: truf 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT 'truf'::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: Token "trues" is invalid. 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: trues 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT 'trues'::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ''::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: The input string ended unexpectedly. 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 1: 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ' '::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected JSON value, but found ",". 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 3: "two":,... 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{ "one": 1, "two":,"two", -- ERROR extraneous comma before field "two" "three": true}'::jsonb; 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type json at character 8 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb DETAIL: Expected JSON value, but found "}". 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb CONTEXT: JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":} 2025-07-03 22:06:45.969 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT '{ "one": 1, "two":"two", "averyveryveryveryveryveryveryveryveryverylongfieldname":}'::jsonb; 2025-07-03 22:06:45.977 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value for domain rgb violates check constraint "rgb_check" 2025-07-03 22:06:45.977 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE('"purple"'::jsonb, 'lax $[*]' RETURNING rgb ERROR ON ERROR); 2025-07-03 22:06:45.977 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-07-03 22:06:45.977 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[]', '$' ERROR ON ERROR); 2025-07-03 22:06:45.980 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-07-03 22:06:45.980 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '{}', '$' ERROR ON ERROR); 2025-07-03 22:06:45.983 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:45.983 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'strict $.a' ERROR ON ERROR); 2025-07-03 22:06:45.984 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:45.984 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY ERROR ON ERROR); 2025-07-03 22:06:45.984 UTC client backend[26034] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-07-03 22:06:45.984 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT FROM (VALUES (1)) foo(i)); 2025-07-03 22:06:45.985 UTC client backend[26034] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-07-03 22:06:45.985 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT i, i FROM (VALUES (1)) foo(i)); 2025-07-03 22:06:45.985 UTC client backend[26034] pg_regress/sqljson ERROR: subquery must return only one column at character 8 2025-07-03 22:06:45.985 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(SELECT * FROM (VALUES (1, 2)) foo(i, j)); 2025-07-03 22:06:45.985 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:45.985 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY DEFAULT '3' ON ERROR); 2025-07-03 22:06:45.986 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_VALUE must return single scalar item 2025-07-03 22:06:45.986 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[1,2]', '$[*]' ERROR ON ERROR); 2025-07-03 22:06:45.991 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: " " 2025-07-03 22:06:45.991 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '[" "]', '$[*]' RETURNING int ERROR ON ERROR); 2025-07-03 22:06:45.993 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: cannot specify FORMAT JSON in RETURNING clause of JSON_VALUE() at character 55 2025-07-03 22:06:45.993 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING int FORMAT JSON); 2025-07-03 22:06:45.993 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: returning pseudo-types is not supported in SQL/JSON functions 2025-07-03 22:06:45.993 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING record); 2025-07-03 22:06:45.996 UTC client backend[26034] pg_regress/sqljson ERROR: null value not allowed for object key 2025-07-03 22:06:45.996 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(NULL: 1); 2025-07-03 22:06:45.996 UTC client backend[26034] pg_regress/sqljson ERROR: field name must not be null 2025-07-03 22:06:45.996 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(NULL: 1 RETURNING jsonb); 2025-07-03 22:06:46.000 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:46.000 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(k: v WITH UNIQUE KEYS) FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v); 2025-07-03 22:06:46.000 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:46.000 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(k: v ABSENT ON NULL WITH UNIQUE KEYS) FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v); 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '1 / $'); 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '1 / $ + 2'); 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: division by zero 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('0', '-(3 + 1 % $)'); 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: right operand of jsonpath operator + is not a single numeric value 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$ + "2"'); 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: right operand of jsonpath operator * is not a single numeric value 2025-07-03 22:06:46.002 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1, 2]', '3 * $'); 2025-07-03 22:06:46.003 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: operand of unary jsonpath operator - is not a numeric value 2025-07-03 22:06:46.003 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"a"', '-$'); 2025-07-03 22:06:46.003 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: operand of unary jsonpath operator + is not a numeric value 2025-07-03 22:06:46.003 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,"2",3]', '+$'); 2025-07-03 22:06:46.003 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:46.003 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(k: v WITH UNIQUE KEYS RETURNING jsonb) FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v); 2025-07-03 22:06:46.004 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value 2025-07-03 22:06:46.004 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(k: v ABSENT ON NULL WITH UNIQUE KEYS RETURNING jsonb) FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v); 2025-07-03 22:06:46.005 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "0" 2025-07-03 22:06:46.005 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(mod(i,100): (i)::text FORMAT JSON WITH UNIQUE) FROM generate_series(0, 199) i; 2025-07-03 22:06:46.006 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.234" 2025-07-03 22:06:46.006 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: select json_value('{"a": 1.234}', '$.a' returning int error on error); 2025-07-03 22:06:46.006 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "1.234" 2025-07-03 22:06:46.006 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: select json_value('{"a": "1.234"}', '$.a' returning int error on error); 2025-07-03 22:06:46.012 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: left operand of jsonpath operator * is not a single numeric value 2025-07-03 22:06:46.012 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{"a": [1, 2]}', 'lax $.a * 3'); 2025-07-03 22:06:46.013 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath wildcard member accessor can only be applied to an object 2025-07-03 22:06:46.013 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,2,3,{"b": [3,4,5]}]', 'strict $.*'); 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type json 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Token "aaa" is invalid. 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs CONTEXT: JSON data, line 1: aaa 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' OMIT QUOTES ERROR ON ERROR); 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type json 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Token "aaa" is invalid. 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs CONTEXT: JSON data, line 1: aaa 2025-07-03 22:06:46.019 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING json OMIT QUOTES ERROR ON ERROR); 2025-07-03 22:06:46.020 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(3) 2025-07-03 22:06:46.020 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING char(3) ERROR ON ERROR); 2025-07-03 22:06:46.024 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8 2025-07-03 22:06:46.024 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1]', '$' WITH WRAPPER OMIT QUOTES); 2025-07-03 22:06:46.024 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8 2025-07-03 22:06:46.024 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1]', '$' WITH CONDITIONAL WRAPPER OMIT QUOTES); 2025-07-03 22:06:46.026 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: expected JSON array 2025-07-03 22:06:46.026 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb'{"rec": "{1,2,3}"}', '$.rec' returning int[] keep quotes error on error); 2025-07-03 22:06:46.031 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .size() can only be applied to an array 2025-07-03 22:06:46.031 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[1,null,true,"11",[],[1],[1,2,3],{},{"a":1,"b":2}]', 'strict $[*].size()'); 2025-07-03 22:06:46.033 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-07-03 22:06:46.033 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{},1]', '$[*].keyvalue()'); 2025-07-03 22:06:46.034 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: malformed range literal: ""[1,2]"" 2025-07-03 22:06:46.034 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Missing left parenthesis or bracket. 2025-07-03 22:06:46.034 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb'{"rec": "[1,2]"}', '$.rec' returning int4range keep quotes error on error); 2025-07-03 22:06:46.039 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-07-03 22:06:46.039 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue()'); 2025-07-03 22:06:46.040 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .keyvalue() can only be applied to an object 2025-07-03 22:06:46.040 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue().a'); 2025-07-03 22:06:46.040 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-07-03 22:06:46.040 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.double()'); 2025-07-03 22:06:46.041 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-07-03 22:06:46.041 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.double()'); 2025-07-03 22:06:46.045 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-07-03 22:06:46.045 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.double()'); 2025-07-03 22:06:46.045 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .double() can only be applied to a string or numeric value 2025-07-03 22:06:46.045 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.double()'); 2025-07-03 22:06:46.046 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .double() is invalid for type double precision 2025-07-03 22:06:46.046 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.double()'); 2025-07-03 22:06:46.046 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .double() is invalid for type double precision 2025-07-03 22:06:46.046 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.double()'); 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.double()'); 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.double()'); 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.double()'); 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .double() 2025-07-03 22:06:46.047 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.double()'); 2025-07-03 22:06:46.048 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .abs() can only be applied to a numeric value 2025-07-03 22:06:46.048 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.abs()'); 2025-07-03 22:06:46.052 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:46.052 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT to_json(a) AS a, JSON_OBJECTAGG(k : v WITH UNIQUE KEYS) OVER (ORDER BY k) FROM (VALUES (1,1), (1,2), (2,2)) a(k,v); 2025-07-03 22:06:46.053 UTC client backend[26034] pg_regress/sqljson ERROR: duplicate JSON object key value: "1" 2025-07-03 22:06:46.053 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT to_json(a) AS a, JSON_OBJECTAGG(k : v ABSENT ON NULL WITH UNIQUE KEYS) OVER (ORDER BY k) FROM (VALUES (1,1), (1,null), (2,2)) a(k,v); 2025-07-03 22:06:46.055 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .floor() can only be applied to a numeric value 2025-07-03 22:06:46.055 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.floor()'); 2025-07-03 22:06:46.055 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ceiling() can only be applied to a numeric value 2025-07-03 22:06:46.055 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.2"', '$.ceiling()'); 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY); 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY NULL ON ERROR); 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.058 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY ARRAY ON ERROR); 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY OBJECT ON ERROR); 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY ERROR ON ERROR); 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: JSON path expression in JSON_QUERY must return single item when no wrapper is requested 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs HINT: Use the WITH WRAPPER clause to wrap SQL/JSON items into an array. 2025-07-03 22:06:46.059 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1,2]', '$[*]' ERROR ON ERROR); 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.datetime()'); 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.datetime()'); 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-07-03 22:06:46.062 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.datetime()'); 2025-07-03 22:06:46.063 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-07-03 22:06:46.063 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.datetime()'); 2025-07-03 22:06:46.063 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .datetime() can only be applied to a string 2025-07-03 22:06:46.063 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.datetime()'); 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: datetime format is not recognized: "bogus" 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath HINT: Use a datetime template argument to specify the input data format. 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.datetime()'); 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: invalid datetime format separator: "a" 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34"', '$.datetime("aaa")'); 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: invalid value "aa" for "HH24" 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath DETAIL: Value must be an integer. 2025-07-03 22:06:46.065 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"aaaa"', '$.datetime("HH24")'); 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: expected JSON array 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR); 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: expected JSON array 2025-07-03 22:06:46.066 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"[3,4]"', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR); 2025-07-03 22:06:46.066 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: trailing characters remain in input string after datetime format 2025-07-03 22:06:46.066 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy")'); 2025-07-03 22:06:46.066 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: trailing characters remain in input string after datetime format 2025-07-03 22:06:46.066 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy").type()'); 2025-07-03 22:06:46.067 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type smallint: ""123.1"" 2025-07-03 22:06:46.067 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 error on error); 2025-07-03 22:06:46.067 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: ""123.1"" 2025-07-03 22:06:46.067 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int4 error on error); 2025-07-03 22:06:46.068 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type bigint: ""123.1"" 2025-07-03 22:06:46.068 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int8 error on error); 2025-07-03 22:06:46.071 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type boolean: ""123.1"" 2025-07-03 22:06:46.071 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING bool error on error); 2025-07-03 22:06:46.071 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type numeric: ""123.1"" 2025-07-03 22:06:46.071 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING numeric error on error); 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: unmatched format character "T" 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017t12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")'); 2025-07-03 22:06:46.076 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type real: ""123.1"" 2025-07-03 22:06:46.076 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING real error on error); 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: unmatched format character "T" 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"10-03-2017 12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")'); 2025-07-03 22:06:46.076 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type double precision: ""123.1"" 2025-07-03 22:06:46.076 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING float8 error on error); 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.bigint()'); 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-07-03 22:06:46.076 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.bigint()'); 2025-07-03 22:06:46.077 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type smallint: "123.1" 2025-07-03 22:06:46.077 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 omit quotes error on error); 2025-07-03 22:06:46.077 UTC client backend[26027] pg_regress/json ERROR: cannot call json_object_keys on a scalar 2025-07-03 22:06:46.077 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object_keys(test_json) FROM test_json WHERE json_type = 'scalar'; 2025-07-03 22:06:46.077 UTC client backend[26027] pg_regress/json ERROR: cannot call json_object_keys on an array 2025-07-03 22:06:46.077 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object_keys(test_json) FROM test_json WHERE json_type = 'array'; 2025-07-03 22:06:46.077 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-07-03 22:06:46.077 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.bigint()'); 2025-07-03 22:06:46.078 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .bigint() can only be applied to a string or numeric value 2025-07-03 22:06:46.078 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.bigint()'); 2025-07-03 22:06:46.078 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.078 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.bigint()'); 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.bigint()'); 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.bigint()'); 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.bigint()'); 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.bigint()'); 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.079 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.bigint()'); 2025-07-03 22:06:46.080 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.080 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.bigint()'); 2025-07-03 22:06:46.080 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: returning pseudo-types is not supported in SQL/JSON functions 2025-07-03 22:06:46.080 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING anyarray EMPTY OBJECT ON ERROR); 2025-07-03 22:06:46.082 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.082 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345678901234567890', '$.bigint()'); 2025-07-03 22:06:46.083 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint 2025-07-03 22:06:46.083 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12345678901234567890"', '$.bigint()'); 2025-07-03 22:06:46.084 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-07-03 22:06:46.084 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.boolean()'); 2025-07-03 22:06:46.085 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-07-03 22:06:46.085 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.boolean()'); 2025-07-03 22:06:46.085 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value 2025-07-03 22:06:46.085 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.boolean()'); 2025-07-03 22:06:46.094 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.094 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.boolean()'); 2025-07-03 22:06:46.094 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.094 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.boolean()'); 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.boolean()'); 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.boolean()'); 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.boolean()'); 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.095 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.boolean()'); 2025-07-03 22:06:46.096 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.096 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.boolean()'); 2025-07-03 22:06:46.096 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.096 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.boolean()'); 2025-07-03 22:06:46.097 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "100" of jsonpath item method .boolean() is invalid for type boolean 2025-07-03 22:06:46.097 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"100"', '$.boolean()'); 2025-07-03 22:06:46.097 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: cannot call populate_composite on a scalar 2025-07-03 22:06:46.097 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb'{"rec": "(abc,42,01.02.2003)"}', '$.rec' returning comp_abc keep quotes error on error); 2025-07-03 22:06:46.110 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "a" 2025-07-03 22:06:46.110 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[{"a": "a", "b": "foo", "t": "aaa", "js": [1, "2", {}], "jb": {"x": [1, "2", {}]}}, {"a": 2}]', '$[0]' RETURNING sqljsonb_rec ERROR ON ERROR); 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.date()'); 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.date()'); 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-07-03 22:06:46.115 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1', '$.date()'); 2025-07-03 22:06:46.116 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-07-03 22:06:46.116 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.date()'); 2025-07-03 22:06:46.117 UTC client backend[26034] pg_regress/sqljson ERROR: cannot use type integer in IS JSON predicate 2025-07-03 22:06:46.117 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT NULL::int IS JSON; 2025-07-03 22:06:46.117 UTC client backend[26034] pg_regress/sqljson ERROR: invalid byte sequence for encoding "UTF8": 0x00 2025-07-03 22:06:46.117 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT bytea '\x00' IS JSON; 2025-07-03 22:06:46.120 UTC client backend[26027] pg_regress/json ERROR: cannot get array length of a non-array 2025-07-03 22:06:46.120 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_array_length('{"f1":1,"f2":[5,6]}'); 2025-07-03 22:06:46.120 UTC client backend[26027] pg_regress/json ERROR: cannot get array length of a scalar 2025-07-03 22:06:46.120 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_array_length('4'); 2025-07-03 22:06:46.125 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .date() can only be applied to a string 2025-07-03 22:06:46.125 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.date()'); 2025-07-03 22:06:46.125 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "bogus" 2025-07-03 22:06:46.125 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"bogus"', '$.date()'); 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "12:34:56" 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56"', '$.date()'); 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: date format is not recognized: "12:34:56 +05:30" 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12:34:56 +05:30"', '$.date()'); 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to date without time zone usage 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-07-03 22:06:46.128 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.date()'); 2025-07-03 22:06:46.129 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: syntax error at or near "2" of jsonpath input at character 41 2025-07-03 22:06:46.129 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15"', '$.date(2)'); 2025-07-03 22:06:46.129 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-07-03 22:06:46.129 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.decimal()'); 2025-07-03 22:06:46.134 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-07-03 22:06:46.134 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.decimal()'); 2025-07-03 22:06:46.135 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: syntax error at or near "{" of jsonpath input 2025-07-03 22:06:46.135 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[{"a": 1, "b": "foo", "t": "aaa", "js": [1, "2", {}], "jb": {"x": [1, "2", {}]}}, {"a": 2}]', '$[0]' RETURNING jsonpath ERROR ON ERROR); 2025-07-03 22:06:46.136 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-07-03 22:06:46.136 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.decimal()'); 2025-07-03 22:06:46.136 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid input syntax for type integer: "a" 2025-07-03 22:06:46.136 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '[1,2,null,"a"]', '$[*]' RETURNING int[] WITH WRAPPER ERROR ON ERROR); 2025-07-03 22:06:46.138 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON EMPTY expression (NULL) to the RETURNING type 2025-07-03 22:06:46.138 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: domain sqljsonb_int_not_null does not allow null values 2025-07-03 22:06:46.138 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null); 2025-07-03 22:06:46.139 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: no SQL/JSON item found for specified path 2025-07-03 22:06:46.139 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null ERROR ON EMPTY ERROR ON ERROR); 2025-07-03 22:06:46.141 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: only one FOR ORDINALITY column is allowed at character 69 2025-07-03 22:06:46.141 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (id FOR ORDINALITY, id2 FOR ORDINALITY, a int PATH '$.a' ERROR ON EMPTY)) jt; 2025-07-03 22:06:46.143 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .decimal() can only be applied to a string or numeric value 2025-07-03 22:06:46.143 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.decimal()'); 2025-07-03 22:06:46.144 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid input syntax for type integer: "err" 2025-07-03 22:06:46.144 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM (VALUES ('1'), ('"err"')) vals(js) LEFT OUTER JOIN JSON_TABLE(vals.js::jsonb, '$' COLUMNS (a int PATH '$' ERROR ON ERROR)) jt ON true; 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .decimal() is invalid for type numeric 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.decimal()'); 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.decimal()'); 2025-07-03 22:06:46.145 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid input syntax for type integer: "err" 2025-07-03 22:06:46.145 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM (VALUES ('1'), ('"err"')) vals(js) LEFT OUTER JOIN JSON_TABLE(vals.js::jsonb, '$' COLUMNS (a int PATH '$' ERROR ON ERROR)) jt ON true; 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-07-03 22:06:46.145 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.decimal()'); 2025-07-03 22:06:46.146 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-07-03 22:06:46.146 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.decimal()'); 2025-07-03 22:06:46.146 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .decimal() 2025-07-03 22:06:46.146 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.decimal()'); 2025-07-03 22:06:46.146 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-07-03 22:06:46.146 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING varchar(2)); 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECT('a': JSON_OBJECT('b': 1 RETURNING varchar(2))); 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAY(JSON_ARRAY('{ "a" : 123 }' RETURNING varchar(2))); 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-07-03 22:06:46.147 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_ARRAYAGG(('111' || i)::bytea FORMAT JSON NULL ON NULL RETURNING varchar(2)) FROM generate_series(1,1) i; 2025-07-03 22:06:46.148 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character varying(2) 2025-07-03 22:06:46.148 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_OBJECTAGG(i: ('111' || i)::bytea FORMAT JSON WITH UNIQUE RETURNING varchar(2)) FROM generate_series(1, 1) i; 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(6, 2)'); 2025-07-03 22:06:46.155 UTC client backend[26034] pg_regress/sqljson ERROR: value too long for type character(2) 2025-07-03 22:06:46.155 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('123' RETURNING sqljson_char2); 2025-07-03 22:06:46.155 UTC client backend[26034] pg_regress/sqljson ERROR: value for domain sqljson_char2 violates check constraint "sqljson_char2_check" 2025-07-03 22:06:46.155 UTC client backend[26034] pg_regress/sqljson STATEMENT: SELECT JSON_SERIALIZE('12' RETURNING sqljson_char2); 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(4, 6)'); 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision 0 must be between 1 and 1000 2025-07-03 22:06:46.155 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(0, 6)'); 2025-07-03 22:06:46.156 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision 1001 must be between 1 and 1000 2025-07-03 22:06:46.156 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345.678', '$.decimal(1001, 6)'); 2025-07-03 22:06:46.156 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: no SQL/JSON item found for specified path of column "a" 2025-07-03 22:06:46.156 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int PATH '$.a' ERROR ON EMPTY)) jt; 2025-07-03 22:06:46.156 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: jsonpath member accessor can only be applied to an object 2025-07-03 22:06:46.156 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int PATH 'strict $.a' ERROR ON ERROR) ERROR ON ERROR) jt; 2025-07-03 22:06:46.156 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NUMERIC precision -6 must be between 1 and 1000 2025-07-03 22:06:46.156 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(-6, +2)'); 2025-07-03 22:06:46.157 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: no SQL/JSON item found for specified path of column "a" 2025-07-03 22:06:46.157 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int PATH 'lax $.a' ERROR ON EMPTY) ERROR ON ERROR) jt; 2025-07-03 22:06:46.163 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NUMERIC scale -1001 must be between -1000 and 1000 2025-07-03 22:06:46.163 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(6, -1001)'); 2025-07-03 22:06:46.164 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NUMERIC scale 1001 must be between -1000 and 1000 2025-07-03 22:06:46.164 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234.5678', '$.decimal(6, 1001)'); 2025-07-03 22:06:46.165 UTC client backend[26026] pg_regress/jsonb ERROR: cannot call jsonb_object_keys on a scalar 2025-07-03 22:06:46.165 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'scalar'; 2025-07-03 22:06:46.165 UTC client backend[26026] pg_regress/jsonb ERROR: cannot call jsonb_object_keys on an array 2025-07-03 22:06:46.165 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'array'; 2025-07-03 22:06:46.167 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.167 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type smallint: "false" 2025-07-03 22:06:46.167 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int2 EXISTS PATH '$.a')); 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type bigint: "false" 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int8 EXISTS PATH '$.a')); 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: precision of jsonpath item method .decimal() is out of range for type integer 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12.3', '$.decimal(12345678901,1)'); 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: scale of jsonpath item method .decimal() is out of range for type integer 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12.3', '$.decimal(1,12345678901)'); 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-07-03 22:06:46.168 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.integer()'); 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: invalid input syntax for type real: "false" 2025-07-03 22:06:46.168 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a float4 EXISTS PATH '$.a')); 2025-07-03 22:06:46.169 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.169 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: value too long for type character(3) 2025-07-03 22:06:46.169 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a')); 2025-07-03 22:06:46.169 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: value too long for type character(3) 2025-07-03 22:06:46.169 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a' ERROR ON ERROR)); 2025-07-03 22:06:46.175 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-07-03 22:06:46.175 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.integer()'); 2025-07-03 22:06:46.175 UTC client backend[26034] pg_regress/sqljson LOG: disconnection: session time: 0:00:00.447 user=postgres database=regression host=[local] 2025-07-03 22:06:46.176 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-07-03 22:06:46.176 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.integer()'); 2025-07-03 22:06:46.176 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .integer() can only be applied to a string or numeric value 2025-07-03 22:06:46.176 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.integer()'); 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23"', '$.integer()'); 2025-07-03 22:06:46.177 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.177 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-07-03 22:06:46.177 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT a, a::bool FROM JSON_TABLE(jsonb '{"a":1}', '$' COLUMNS (a dint4_0 EXISTS PATH '$.b')); 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.integer()'); 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.177 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1e1000', '$.integer()'); 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "nan" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.integer()'); 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "NaN" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.integer()'); 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "inf" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.integer()'); 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "-inf" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.178 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.integer()'); 2025-07-03 22:06:46.180 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345678901" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.180 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('12345678901', '$.integer()'); 2025-07-03 22:06:46.181 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "12345678901" of jsonpath item method .integer() is invalid for type integer 2025-07-03 22:06:46.181 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"12345678901"', '$.integer()'); 2025-07-03 22:06:46.184 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-07-03 22:06:46.184 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT a, a::bool FROM JSON_TABLE(jsonb '{"a":1}', '$' COLUMNS (a dint4_0 EXISTS PATH '$.b' ERROR ON ERROR)); 2025-07-03 22:06:46.185 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: could not coerce ON ERROR expression (FALSE) to the RETURNING type 2025-07-03 22:06:46.185 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: value for domain dint4_0 violates check constraint "dint4_0_check" 2025-07-03 22:06:46.185 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT a, a::bool FROM JSON_TABLE(jsonb '{"a":1}', '$' COLUMNS (a dint4_0 EXISTS PATH '$.b' FALSE ON ERROR)); 2025-07-03 22:06:46.185 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-07-03 22:06:46.185 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.number()'); 2025-07-03 22:06:46.185 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-07-03 22:06:46.185 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.number()'); 2025-07-03 22:06:46.188 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-07-03 22:06:46.188 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.number()'); 2025-07-03 22:06:46.195 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .number() can only be applied to a string or numeric value 2025-07-03 22:06:46.195 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.number()'); 2025-07-03 22:06:46.196 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 56 2025-07-03 22:06:46.196 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '"world"', '$' COLUMNS (item text PATH '$' WITH WRAPPER OMIT QUOTES)); 2025-07-03 22:06:46.199 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: argument "1.23aaa" of jsonpath item method .number() is invalid for type numeric 2025-07-03 22:06:46.199 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"1.23aaa"', '$.number()'); 2025-07-03 22:06:46.199 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-07-03 22:06:46.199 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"nan"', '$.number()'); 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"NaN"', '$.number()'); 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"inf"', '$.number()'); 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: NaN or Infinity is not allowed for jsonpath item method .number() 2025-07-03 22:06:46.200 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"-inf"', '$.number()'); 2025-07-03 22:06:46.205 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: only string constants are supported in JSON_TABLE path specification at character 46 2025-07-03 22:06:46.205 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '{"a": 123}', '$' || '.' || 'a' COLUMNS (foo int)); 2025-07-03 22:06:46.206 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: JSON path expression for column "b" must return single item when no wrapper is requested 2025-07-03 22:06:46.206 UTC client backend[26029] pg_regress/sqljson_jsontable HINT: Use the WITH WRAPPER clause to wrap SQL/JSON items into an array. 2025-07-03 22:06:46.206 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE('{"a": [{"b": "1"}, {"b": "2"}]}', '$' COLUMNS (b json path '$.a[*].b' ERROR ON ERROR)); 2025-07-03 22:06:46.206 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: a at character 90 2025-07-03 22:06:46.206 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE( jsonb '[]', '$' AS a COLUMNS ( b int, NESTED PATH '$' AS a COLUMNS ( c int ) ) ) jt; 2025-07-03 22:06:46.206 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-07-03 22:06:46.206 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.string()'); 2025-07-03 22:06:46.207 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-07-03 22:06:46.207 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.string()'); 2025-07-03 22:06:46.207 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value 2025-07-03 22:06:46.207 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.string()'); 2025-07-03 22:06:46.207 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: b at character 85 2025-07-03 22:06:46.207 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE( jsonb '[]', '$' COLUMNS ( b int, NESTED PATH '$' AS b COLUMNS ( c int ) ) ) jt; 2025-07-03 22:06:46.207 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: duplicate JSON_TABLE column or path name: a at character 156 2025-07-03 22:06:46.207 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE( jsonb '[]', '$' COLUMNS ( NESTED PATH '$' AS a COLUMNS ( b int ), NESTED PATH '$' COLUMNS ( NESTED PATH '$' AS a COLUMNS ( c int ) ) ) ) jt; 2025-07-03 22:06:46.216 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamptz to timestamp without time zone usage 2025-07-03 22:06:46.216 UTC client backend[26031] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-07-03 22:06:46.216 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56 +5:30"', '$.timestamp().string()'); 2025-07-03 22:06:46.219 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: cannot convert value from timestamp to timestamptz without time zone usage 2025-07-03 22:06:46.219 UTC client backend[26031] pg_regress/jsonb_jsonpath HINT: Use *_tz() function for time zone support. 2025-07-03 22:06:46.219 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz().string()'); 2025-07-03 22:06:46.227 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type timestamp: "[100,200,false]" 2025-07-03 22:06:46.227 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_record(row('x',3,'2012-12-31 15:30:56')::jpop,'{"c":[100,200,false],"x":43.2}') q; 2025-07-03 22:06:46.228 UTC client backend[26027] pg_regress/json ERROR: domain js_int_not_null does not allow null values 2025-07-03 22:06:46.228 UTC client backend[26027] pg_regress/json STATEMENT: SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"x": 43.2}') q; 2025-07-03 22:06:46.228 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.228 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.ltrim()'); 2025-07-03 22:06:46.228 UTC client backend[26027] pg_regress/json ERROR: domain js_int_not_null does not allow null values 2025-07-03 22:06:46.228 UTC client backend[26027] pg_regress/json STATEMENT: SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"i": null}') q; 2025-07-03 22:06:46.234 UTC client backend[26026] pg_regress/jsonb ERROR: cannot get array length of a non-array 2025-07-03 22:06:46.234 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_array_length('{"f1":1,"f2":[5,6]}'); 2025-07-03 22:06:46.234 UTC client backend[26026] pg_regress/jsonb ERROR: cannot get array length of a scalar 2025-07-03 22:06:46.234 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_array_length('4'); 2025-07-03 22:06:46.235 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.235 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.ltrim()'); 2025-07-03 22:06:46.236 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.236 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.ltrim()'); 2025-07-03 22:06:46.237 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.237 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.ltrim()'); 2025-07-03 22:06:46.238 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.238 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.ltrim()'); 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.ltrim()'); 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.ltrim().type()'); 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .ltrim() can only be applied to a string 2025-07-03 22:06:46.239 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[2, true]', '$.ltrim()'); 2025-07-03 22:06:46.239 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.239 UTC client backend[26027] pg_regress/json HINT: See the value of key "ia". 2025-07-03 22:06:46.239 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": 123}') q; 2025-07-03 22:06:46.240 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.240 UTC client backend[26027] pg_regress/json HINT: See the array element [1] of key "ia". 2025-07-03 22:06:46.240 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], 2]}') q; 2025-07-03 22:06:46.242 UTC client backend[26027] pg_regress/json ERROR: malformed JSON array 2025-07-03 22:06:46.242 UTC client backend[26027] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.242 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], [2, 3]]}') q; 2025-07-03 22:06:46.243 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.243 UTC client backend[26027] pg_regress/json HINT: See the value of key "ia1". 2025-07-03 22:06:46.243 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia1 FROM json_populate_record(NULL::jsrec, '{"ia1": 123}') q; 2025-07-03 22:06:46.247 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.247 UTC client backend[26027] pg_regress/json HINT: See the value of key "ia1d". 2025-07-03 22:06:46.247 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": 123}') q; 2025-07-03 22:06:46.247 UTC client backend[26027] pg_regress/json ERROR: value for domain js_int_array_1d violates check constraint "js_int_array_1d_check" 2025-07-03 22:06:46.247 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": [1, "2", null, 4]}') q; 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.lower()'); 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.lower()'); 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.249 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.lower()'); 2025-07-03 22:06:46.250 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.250 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.lower()'); 2025-07-03 22:06:46.250 UTC client backend[26027] pg_regress/json ERROR: malformed JSON array 2025-07-03 22:06:46.250 UTC client backend[26027] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.250 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], [3]]}') q; 2025-07-03 22:06:46.251 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.251 UTC client backend[26027] pg_regress/json HINT: See the array element [1] of key "ia2". 2025-07-03 22:06:46.251 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], 3, 4]}') q; 2025-07-03 22:06:46.251 UTC client backend[26027] pg_regress/json ERROR: value for domain js_int_array_2d violates check constraint "js_int_array_2d_check" 2025-07-03 22:06:46.251 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia2d FROM json_populate_record(NULL::jsrec, '{"ia2d": [[1, "2"], [null, 4]]}') q; 2025-07-03 22:06:46.252 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.252 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.lower()'); 2025-07-03 22:06:46.252 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.252 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.lower()'); 2025-07-03 22:06:46.255 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.255 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.lower().type()'); 2025-07-03 22:06:46.256 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .lower() can only be applied to a string 2025-07-03 22:06:46.256 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[2, true]', '$.lower()'); 2025-07-03 22:06:46.257 UTC client backend[26027] pg_regress/json ERROR: malformed JSON array 2025-07-03 22:06:46.257 UTC client backend[26027] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.257 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ia3 FROM json_populate_record(NULL::jsrec, '{"ia3": [ [[1, 2], [3, 4]], [[5, 6], [7, 8], [9, 10]] ]}') q; 2025-07-03 22:06:46.260 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.260 UTC client backend[26027] pg_regress/json HINT: See the value of key "ta". 2025-07-03 22:06:46.260 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": 123}') q; 2025-07-03 22:06:46.261 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.261 UTC client backend[26027] pg_regress/json HINT: See the array element [1] of key "ta". 2025-07-03 22:06:46.261 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q; 2025-07-03 22:06:46.263 UTC client backend[26027] pg_regress/json ERROR: value too long for type character(10) 2025-07-03 22:06:46.263 UTC client backend[26027] pg_regress/json STATEMENT: SELECT c FROM json_populate_record(NULL::jsrec, '{"c": "aaaaaaaaaaaaa"}') q; 2025-07-03 22:06:46.263 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.263 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.upper()'); 2025-07-03 22:06:46.264 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.264 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.upper()'); 2025-07-03 22:06:46.264 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.264 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.upper()'); 2025-07-03 22:06:46.265 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.265 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.upper()'); 2025-07-03 22:06:46.267 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.267 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.upper()'); 2025-07-03 22:06:46.267 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.267 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.upper()'); 2025-07-03 22:06:46.268 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.268 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.upper().type()'); 2025-07-03 22:06:46.268 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .upper() can only be applied to a string 2025-07-03 22:06:46.268 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[2, true]', '$.upper()'); 2025-07-03 22:06:46.269 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.269 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.initcap()'); 2025-07-03 22:06:46.272 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.272 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[]', 'strict $.initcap()'); 2025-07-03 22:06:46.272 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.272 UTC client backend[26027] pg_regress/json HINT: See the value of key "ca". 2025-07-03 22:06:46.272 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": 123}') q; 2025-07-03 22:06:46.272 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.272 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('{}', '$.initcap()'); 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1.23', '$.initcap()'); 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.initcap()'); 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.273 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('true', '$.initcap()'); 2025-07-03 22:06:46.274 UTC client backend[26027] pg_regress/json ERROR: value too long for type character(10) 2025-07-03 22:06:46.274 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q; 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('1234', '$.initcap().type()'); 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .initcap() can only be applied to a string 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('[2, true]', '$.initcap()'); 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath ERROR: jsonpath item method .replace() can only be applied to a string 2025-07-03 22:06:46.274 UTC client backend[26031] pg_regress/jsonb_jsonpath STATEMENT: select jsonb_path_query('null', '$.replace("x", "bye")'); 2025-07-03 22:06:46.275 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.275 UTC client backend[26027] pg_regress/json HINT: See the array element [1] of key "ca". 2025-07-03 22:06:46.275 UTC client backend[26027] pg_regress/json STATEMENT: SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q; TRAP: failed Assert("v->type == jpiAnd || v->type == jpiOr || v->type == jpiEqual || v->type == jpiNotEqual || v->type == jpiLess || v->type == jpiGreater || v->type == jpiLessOrEqual || v->type == jpiGreaterOrEqual || v->type == jpiAdd || v->type == jpiSub || v->type == jpiMul || v->type == jpiDiv || v->type == jpiMod || v->type == jpiStartsWith || v->type == jpiDecimal"), File: "jsonpath.c", Line: 1265, PID: 26031 /lib/x86_64-linux-gnu/libasan.so.8(+0x51f31)[0x7f12dcc51f31] postgres: postgres regression [local] SELECT(ExceptionalCondition+0xe6)[0x55e74edbedd0] postgres: postgres regression [local] SELECT(jspGetLeftArg+0x65)[0x55e74ebde680] postgres: postgres regression [local] SELECT(+0xfeb8fa)[0x55e74ebe48fa] postgres: postgres regression [local] SELECT(+0xff010a)[0x55e74ebe910a] postgres: postgres regression [local] SELECT(+0xff4c4a)[0x55e74ebedc4a] postgres: postgres regression [local] SELECT(+0xff4d0b)[0x55e74ebedd0b] postgres: postgres regression [local] SELECT(+0xff012c)[0x55e74ebe912c] postgres: postgres regression [local] SELECT(+0xff0201)[0x55e74ebe9201] postgres: postgres regression [local] SELECT(+0xff1c2a)[0x55e74ebeac2a] postgres: postgres regression [local] SELECT(+0xfed34c)[0x55e74ebe634c] postgres: postgres regression [local] SELECT(+0xff0201)[0x55e74ebe9201] postgres: postgres regression [local] SELECT(+0xff0542)[0x55e74ebe9542] postgres: postgres regression [local] SELECT(+0xff7509)[0x55e74ebf0509] postgres: postgres regression [local] SELECT(jsonb_path_query+0xe)[0x55e74ebf06ea] postgres: postgres regression [local] SELECT(ExecMakeFunctionResultSet+0x80d)[0x55e74e57c918] postgres: postgres regression [local] SELECT(+0xa0509c)[0x55e74e5fe09c] postgres: postgres regression [local] SELECT(+0xa052fd)[0x55e74e5fe2fd] postgres: postgres regression [local] SELECT(+0x97bdc6)[0x55e74e574dc6] postgres: postgres regression [local] SELECT(+0x963e99)[0x55e74e55ce99] postgres: postgres regression [local] SELECT(+0x964082)[0x55e74e55d082] postgres: postgres regression [local] SELECT(standard_ExecutorRun+0x3e6)[0x55e74e55ef2a] postgres: postgres regression [local] SELECT(ExecutorRun+0x1c)[0x55e74e55ef8a] postgres: postgres regression [local] SELECT(+0xea36bd)[0x55e74ea9c6bd] postgres: postgres regression [local] SELECT(PortalRun+0x6a5)[0x55e74eaa04a1] postgres: postgres regression [local] SELECT(+0xe9e335)[0x55e74ea97335] postgres: postgres regression [local] SELECT(PostgresMain+0x1109)[0x55e74ea9b5ff] postgres: postgres regression [local] SELECT(BackendMain+0x11b)[0x55e74ea8d242] postgres: postgres regression [local] SELECT(postmaster_child_launch+0x23e)[0x55e74e8cff44] postgres: postgres regression [local] SELECT(+0xcdcf62)[0x55e74e8d5f62] postgres: postgres regression [local] SELECT(+0xcdffed)[0x55e74e8d8fed] postgres: postgres regression [local] SELECT(PostmasterMain+0x1c41)[0x55e74e8db137] postgres: postgres regression [local] SELECT(main+0x2a2)[0x55e74e66d4f4] /lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7f12dbb7824a] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7f12dbb78305] postgres: postgres regression [local] SELECT(_start+0x21)[0x55e74e032451] 2025-07-03 22:06:46.286 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.286 UTC client backend[26027] pg_regress/json HINT: See the value of key "jsa". 2025-07-03 22:06:46.286 UTC client backend[26027] pg_regress/json STATEMENT: SELECT jsa FROM json_populate_record(NULL::jsrec, '{"jsa": 123}') q; 2025-07-03 22:06:46.297 UTC client backend[26027] pg_regress/json ERROR: cannot call populate_composite on a scalar 2025-07-03 22:06:46.297 UTC client backend[26027] pg_regress/json STATEMENT: SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": 123}') q; 2025-07-03 22:06:46.298 UTC client backend[26027] pg_regress/json ERROR: cannot call populate_composite on an array 2025-07-03 22:06:46.298 UTC client backend[26027] pg_regress/json STATEMENT: SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": [1, 2]}') q; 2025-07-03 22:06:46.301 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.301 UTC client backend[26027] pg_regress/json HINT: See the value of key "reca". 2025-07-03 22:06:46.301 UTC client backend[26027] pg_regress/json STATEMENT: SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": 123}') q; 2025-07-03 22:06:46.301 UTC client backend[26027] pg_regress/json ERROR: cannot call populate_composite on a scalar 2025-07-03 22:06:46.301 UTC client backend[26027] pg_regress/json STATEMENT: SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": [1, 2]}') q; 2025-07-03 22:06:46.306 UTC client backend[26027] pg_regress/json ERROR: could not determine row type for result of json_populate_record 2025-07-03 22:06:46.306 UTC client backend[26027] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.306 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_populate_record(null::record, '{"x": 0, "y": 1}'); 2025-07-03 22:06:46.308 UTC client backend[26027] pg_regress/json ERROR: value for domain j_ordered_pair violates check constraint "j_ordered_pair_check" 2025-07-03 22:06:46.308 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_populate_record(row(1,2)::j_ordered_pair, '{"x": 1, "y": 0}'); 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: syntax error at or near "empty" at character 79 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on empty)); 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior at character 57 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause. 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int) NULL ON ERROR); 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON EMPTY behavior for column "a" at character 56 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only ERROR, NULL, or DEFAULT expression is allowed in ON EMPTY for scalar columns. 2025-07-03 22:06:46.309 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int true on empty)); 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior for column "a" at character 68 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for formatted columns. 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int omit quotes true on error)); 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable ERROR: invalid ON ERROR behavior for column "a" at character 63 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable DETAIL: Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for EXISTS columns. 2025-07-03 22:06:46.310 UTC client backend[26029] pg_regress/sqljson_jsontable STATEMENT: SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on error)); 2025-07-03 22:06:46.312 UTC client backend[26027] pg_regress/json ERROR: invalid input syntax for type timestamp: "[100,200,300]" 2025-07-03 22:06:46.312 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_recordset(row('def',99,null)::jpop,'[{"c":[100,200,300],"x":43.2},{"a":{"z":true},"b":3,"c":"2012-01-20 10:42:53"}]') q; 2025-07-03 22:06:46.313 UTC client backend[26026] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-07-03 22:06:46.313 UTC client backend[26026] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.313 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{a,b,c}'::text[]); 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]); 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('a', 'b', 'c'); 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-07-03 22:06:46.314 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(NULL, 'a'); 2025-07-03 22:06:46.315 UTC client backend[26026] pg_regress/jsonb ERROR: argument list must have even number of elements 2025-07-03 22:06:46.315 UTC client backend[26026] pg_regress/jsonb HINT: The arguments of jsonb_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.315 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(VARIADIC '{a,b,c}'::text[]); 2025-07-03 22:06:46.315 UTC client backend[26026] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-07-03 22:06:46.315 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(VARIADIC ARRAY[NULL, 'a']::text[]); 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb ERROR: argument 1: key must not be null 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(null,2); 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r; 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.317 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object(json '{"a":1,"b":2}', 3); 2025-07-03 22:06:46.318 UTC client backend[26026] pg_regress/jsonb ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.318 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_build_object('{1,2,3}'::int[], 3); 2025-07-03 22:06:46.318 UTC client backend[26026] pg_regress/jsonb ERROR: field name must not be null 2025-07-03 22:06:46.318 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object_agg(NULL, '{"a":1}'); 2025-07-03 22:06:46.319 UTC client backend[26027] pg_regress/json ERROR: could not determine row type for result of json_populate_recordset 2025-07-03 22:06:46.319 UTC client backend[26027] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.319 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_populate_recordset(null::record, '[{"x": 0, "y": 1}]'); 2025-07-03 22:06:46.327 UTC client backend[26027] pg_regress/json ERROR: could not determine row type for result of json_populate_recordset 2025-07-03 22:06:46.327 UTC client backend[26027] pg_regress/json HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.327 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_populate_recordset(null::record, '[]'); 2025-07-03 22:06:46.331 UTC client backend[26027] pg_regress/json ERROR: value for domain j_ordered_pair violates check constraint "j_ordered_pair_check" 2025-07-03 22:06:46.331 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_populate_recordset(row(1,2)::j_ordered_pair, '[{"x": 1, "y": 0}]'); 2025-07-03 22:06:46.334 UTC client backend[26027] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.334 UTC client backend[26027] pg_regress/json DETAIL: Returned row contains 1 attribute, but query expects 2. 2025-07-03 22:06:46.334 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_recordset(row(0::int,0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_recordset(row(0::int,0::int,0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-07-03 22:06:46.335 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.351 UTC client backend[26026] pg_regress/jsonb ERROR: field name must not be null 2025-07-03 22:06:46.351 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object_agg(name, type) FROM foo; 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb ERROR: array must have even number of elements 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{a,b,c}'); 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb ERROR: array must have two columns 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{a},{b}}'); 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb ERROR: array must have two columns 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{a,b,c},{b,c,d}}'); 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb ERROR: wrong number of array subscripts 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{{a,b},{c,d}},{{b,c},{d,e}}}'); 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb ERROR: wrong number of array subscripts 2025-07-03 22:06:46.353 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_object('{{a,1},{b,2},{3,NULL},{"d e f","a b c"}}', '{{a,1},{b,2},{3,NULL},{"d e f","a b c"}}'); 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb ERROR: mismatched array dimensions 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}'); 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb ERROR: mismatched array dimensions 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}'); 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb ERROR: null value not allowed for object key 2025-07-03 22:06:46.354 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}'); 2025-07-03 22:06:46.376 UTC client backend[26029] pg_regress/sqljson_jsontable LOG: disconnection: session time: 0:00:00.660 user=postgres database=regression host=[local] 2025-07-03 22:06:46.406 UTC client backend[26027] pg_regress/json ERROR: argument list must have even number of elements 2025-07-03 22:06:46.406 UTC client backend[26027] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.406 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object('{a,b,c}'::text[]); 2025-07-03 22:06:46.406 UTC client backend[26027] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.406 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]); 2025-07-03 22:06:46.411 UTC client backend[26027] pg_regress/json ERROR: argument list must have even number of elements 2025-07-03 22:06:46.411 UTC client backend[26027] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.411 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object('a', 'b', 'c'); 2025-07-03 22:06:46.411 UTC client backend[26027] pg_regress/json ERROR: null value not allowed for object key 2025-07-03 22:06:46.411 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(NULL, 'a'); 2025-07-03 22:06:46.412 UTC client backend[26027] pg_regress/json ERROR: argument list must have even number of elements 2025-07-03 22:06:46.412 UTC client backend[26027] pg_regress/json HINT: The arguments of json_build_object() must consist of alternating keys and values. 2025-07-03 22:06:46.412 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(VARIADIC '{a,b,c}'::text[]); 2025-07-03 22:06:46.413 UTC client backend[26027] pg_regress/json ERROR: null value not allowed for object key 2025-07-03 22:06:46.413 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(VARIADIC ARRAY[NULL, 'a']::text[]); 2025-07-03 22:06:46.414 UTC client backend[26027] pg_regress/json ERROR: null value not allowed for object key 2025-07-03 22:06:46.414 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(null,2); 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r; 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object(json '{"a":1,"b":2}', 3); 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json ERROR: key value must be scalar, not array, composite, or json 2025-07-03 22:06:46.415 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_build_object('{1,2,3}'::int[], 3); 2025-07-03 22:06:46.434 UTC client backend[26027] pg_regress/json ERROR: null value not allowed for object key 2025-07-03 22:06:46.434 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object_agg(name, type) FROM foo; 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json ERROR: array must have even number of elements 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object('{a,b,c}'); 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json ERROR: array must have two columns 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object('{{a},{b}}'); 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json ERROR: array must have two columns 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object('{{a,b,c},{b,c,d}}'); 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json ERROR: wrong number of array subscripts 2025-07-03 22:06:46.436 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object('{{{a,b},{c,d}},{{b,c},{d,e}}}'); 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json ERROR: wrong number of array subscripts 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json STATEMENT: SELECT json_object('{{a,1},{b,2},{3,NULL},{"d e f","a b c"}}', '{{a,1},{b,2},{3,NULL},{"d e f","a b c"}}'); 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json ERROR: mismatched array dimensions 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json STATEMENT: select json_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}'); 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json ERROR: mismatched array dimensions 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json STATEMENT: select json_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}'); 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json ERROR: null value not allowed for object key 2025-07-03 22:06:46.437 UTC client backend[26027] pg_regress/json STATEMENT: select json_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}'); 2025-07-03 22:06:46.438 UTC client backend[26027] pg_regress/json ERROR: duplicate JSON object key value: "0" 2025-07-03 22:06:46.438 UTC client backend[26027] pg_regress/json STATEMENT: select json_object_agg_unique(mod(i,100), i) from generate_series(0, 199) i; 2025-07-03 22:06:46.441 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.441 UTC client backend[26027] pg_regress/json HINT: See the value of key "ia". 2025-07-03 22:06:46.441 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_to_record('{"ia": 123}') as x(ia _int4); 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json ERROR: expected JSON array 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json HINT: See the array element [1] of key "ia". 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_to_record('{"ia": [[1], 2]}') as x(ia _int4); 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json ERROR: malformed JSON array 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.442 UTC client backend[26027] pg_regress/json STATEMENT: select * from json_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4); 2025-07-03 22:06:46.446 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type timestamp: "[100, 200, false]" 2025-07-03 22:06:46.446 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT * FROM jsonb_populate_record(row('x',3,'2012-12-31 15:30:56')::jbpop,'{"c":[100,200,false],"x":43.2}') q; 2025-07-03 22:06:46.455 UTC client backend[26026] pg_regress/jsonb ERROR: domain jsb_int_not_null does not allow null values 2025-07-03 22:06:46.455 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"x": 43.2}') q; 2025-07-03 22:06:46.459 UTC client backend[26026] pg_regress/jsonb ERROR: domain jsb_int_not_null does not allow null values 2025-07-03 22:06:46.459 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"i": null}') q; 2025-07-03 22:06:46.463 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.463 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ia". 2025-07-03 22:06:46.463 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": 123}') q; 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb HINT: See the array element [1] of key "ia". 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], 2]}') q; 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb ERROR: malformed JSON array 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.464 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], [2, 3]]}') q; 2025-07-03 22:06:46.468 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.468 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ia1". 2025-07-03 22:06:46.468 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia1 FROM jsonb_populate_record(NULL::jsbrec, '{"ia1": 123}') q; 2025-07-03 22:06:46.470 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.470 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ia1d". 2025-07-03 22:06:46.470 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": 123}') q; 2025-07-03 22:06:46.472 UTC client backend[26026] pg_regress/jsonb ERROR: value for domain jsb_int_array_1d violates check constraint "jsb_int_array_1d_check" 2025-07-03 22:06:46.472 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": [1, "2", null, 4]}') q; 2025-07-03 22:06:46.476 UTC client backend[26026] pg_regress/jsonb ERROR: malformed JSON array 2025-07-03 22:06:46.476 UTC client backend[26026] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.476 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], [3]]}') q; 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json ERROR: wrong flag in flag array: "" 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json STATEMENT: select json_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::json, '""'); 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json ERROR: wrong flag type, only arrays and scalars are allowed 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json STATEMENT: select json_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::json, '{}'); 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json ERROR: flag array element is not a string 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json STATEMENT: select json_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::json, 'null'); 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json ERROR: flag array element is not a string 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json HINT: Possible values are: "string", "numeric", "boolean", "key", and "all". 2025-07-03 22:06:46.481 UTC client backend[26027] pg_regress/json STATEMENT: select json_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::json, '["all", null]'); 2025-07-03 22:06:46.483 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.483 UTC client backend[26026] pg_regress/jsonb HINT: See the array element [1] of key "ia2". 2025-07-03 22:06:46.483 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], 3, 4]}') q; 2025-07-03 22:06:46.484 UTC client backend[26026] pg_regress/jsonb ERROR: value for domain jsb_int_array_2d violates check constraint "jsb_int_array_2d_check" 2025-07-03 22:06:46.484 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia2d FROM jsonb_populate_record(NULL::jsbrec, '{"ia2d": [[1, "2"], [null, 4]]}') q; 2025-07-03 22:06:46.495 UTC client backend[26026] pg_regress/jsonb ERROR: malformed JSON array 2025-07-03 22:06:46.495 UTC client backend[26026] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.495 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ia3 FROM jsonb_populate_record(NULL::jsbrec, '{"ia3": [ [[1, 2], [3, 4]], [[5, 6], [7, 8], [9, 10]] ]}') q; 2025-07-03 22:06:46.496 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.496 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ta". 2025-07-03 22:06:46.496 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": 123}') q; 2025-07-03 22:06:46.504 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.504 UTC client backend[26026] pg_regress/jsonb HINT: See the array element [1] of key "ta". 2025-07-03 22:06:46.504 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q; 2025-07-03 22:06:46.505 UTC client backend[26026] pg_regress/jsonb ERROR: value too long for type character(10) 2025-07-03 22:06:46.505 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT c FROM jsonb_populate_record(NULL::jsbrec, '{"c": "aaaaaaaaaaaaa"}') q; 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ca". 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": 123}') q; 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb ERROR: value too long for type character(10) 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q; 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb HINT: See the array element [1] of key "ca". 2025-07-03 22:06:46.506 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q; 2025-07-03 22:06:46.516 UTC client backend[26027] pg_regress/json LOG: disconnection: session time: 0:00:00.808 user=postgres database=regression host=[local] 2025-07-03 22:06:46.525 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.525 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "jsa". 2025-07-03 22:06:46.525 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsa FROM jsonb_populate_record(NULL::jsbrec, '{"jsa": 123}') q; 2025-07-03 22:06:46.527 UTC client backend[26026] pg_regress/jsonb ERROR: cannot call populate_composite on a scalar 2025-07-03 22:06:46.527 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": 123}') q; 2025-07-03 22:06:46.528 UTC client backend[26026] pg_regress/jsonb ERROR: cannot call populate_composite on an array 2025-07-03 22:06:46.528 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": [1, 2]}') q; 2025-07-03 22:06:46.529 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.529 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "reca". 2025-07-03 22:06:46.529 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": 123}') q; 2025-07-03 22:06:46.529 UTC client backend[26026] pg_regress/jsonb ERROR: cannot call populate_composite on a scalar 2025-07-03 22:06:46.529 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": [1, 2]}') q; 2025-07-03 22:06:46.540 UTC client backend[26026] pg_regress/jsonb ERROR: value too long for type character(2) 2025-07-03 22:06:46.540 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_char2, '{"a": "aaa"}') q; 2025-07-03 22:06:46.544 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint1" 2025-07-03 22:06:46.544 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains (, 1, [1, 2]). 2025-07-03 22:06:46.544 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('', 1); 2025-07-03 22:06:46.545 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-07-03 22:06:46.545 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains (1, 1, [1, 2]). 2025-07-03 22:06:46.545 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('1', 1); 2025-07-03 22:06:46.551 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-07-03 22:06:46.551 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ([], null, [1, 2]). 2025-07-03 22:06:46.551 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('[]'); 2025-07-03 22:06:46.552 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.552 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "a". 2025-07-03 22:06:46.552 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_ia, '{"a": 43.2}') q; 2025-07-03 22:06:46.552 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2" 2025-07-03 22:06:46.552 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"b": 1}, 1, [1, 2]). 2025-07-03 22:06:46.552 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"b": 1}', 1); 2025-07-03 22:06:46.553 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint3" 2025-07-03 22:06:46.553 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"a": 1}, 1, [1, 2]). 2025-07-03 22:06:46.553 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"a": 1}', 1); 2025-07-03 22:06:46.554 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint4" 2025-07-03 22:06:46.554 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Failing row contains ({"a": 10}, 1, [1, 2]). 2025-07-03 22:06:46.554 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: INSERT INTO test_jsonb_constraints VALUES ('{"a": 10}', 1); 2025-07-03 22:06:46.554 UTC client backend[26026] pg_regress/jsonb ERROR: malformed JSON array 2025-07-03 22:06:46.554 UTC client backend[26026] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.554 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_ia2, '{"a": [[1], [2, 3]]}') q; 2025-07-03 22:06:46.564 UTC client backend[26026] pg_regress/jsonb ERROR: domain jsb_i_not_null does not allow null values 2025-07-03 22:06:46.564 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_i_not_null_rec, '{"a": null}') q; 2025-07-03 22:06:46.568 UTC client backend[26026] pg_regress/jsonb ERROR: value for domain jsb_i_gt_1 violates check constraint "jsb_i_gt_1_check" 2025-07-03 22:06:46.568 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_record(NULL::jsb_i_gt_1_rec, '{"a": 1}') q; 2025-07-03 22:06:46.595 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.595 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time()')); 2025-07-03 22:06:46.596 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.596 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date()')); 2025-07-03 22:06:46.597 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.597 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time_tz()')); 2025-07-03 22:06:46.597 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.597 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp()')); 2025-07-03 22:06:46.597 UTC client backend[26026] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_record 2025-07-03 22:06:46.597 UTC client backend[26026] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.597 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_record(null::record, '{"x": 0, "y": 1}'); 2025-07-03 22:06:46.598 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.598 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp_tz()')); 2025-07-03 22:06:46.598 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.598 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time_tz())')); 2025-07-03 22:06:46.600 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.600 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time())')); 2025-07-03 22:06:46.600 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.600 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time())')); 2025-07-03 22:06:46.601 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.601 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time_tz())')); 2025-07-03 22:06:46.601 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.601 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.timestamp_tz())')); 2025-07-03 22:06:46.601 UTC client backend[26026] pg_regress/jsonb ERROR: value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check" 2025-07-03 22:06:46.601 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_record(row(1,2)::jb_ordered_pair, '{"x": 1, "y": 0}'); 2025-07-03 22:06:46.602 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.602 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.timestamp_tz())')); 2025-07-03 22:06:46.602 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.602 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.datetime("HH:MI TZH"))')); 2025-07-03 22:06:46.603 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.603 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.datetime("HH:MI TZH"))')); 2025-07-03 22:06:46.604 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.604 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI TZH"))')); 2025-07-03 22:06:46.604 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.604 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI"))')); 2025-07-03 22:06:46.605 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.605 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI TZH"))')); 2025-07-03 22:06:46.614 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.614 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI"))')); 2025-07-03 22:06:46.614 UTC client backend[26026] pg_regress/jsonb ERROR: invalid input syntax for type timestamp: "[100, 200, 300]" 2025-07-03 22:06:46.614 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT * FROM jsonb_populate_recordset(row('def',99,NULL)::jbpop,'[{"c":[100,200,300],"x":43.2},{"a":{"z":true},"b":3,"c":"2012-01-20 10:42:53"}]') q; 2025-07-03 22:06:46.615 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.615 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '12:34'::timetz AS x)); 2025-07-03 22:06:46.616 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.616 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '1234'::int AS x)); 2025-07-03 22:06:46.616 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.616 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp(2) < $.timestamp(3))')); 2025-07-03 22:06:46.618 UTC client backend[26026] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_recordset 2025-07-03 22:06:46.618 UTC client backend[26026] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.618 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(null::record, '[{"x": 0, "y": 1}]'); 2025-07-03 22:06:46.620 UTC client backend[26026] pg_regress/jsonb ERROR: could not determine row type for result of jsonb_populate_recordset 2025-07-03 22:06:46.620 UTC client backend[26026] pg_regress/jsonb HINT: Provide a non-null record argument, or call the function in the FROM clause using a column definition list. 2025-07-03 22:06:46.620 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(null::record, '[]'); 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb ERROR: value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check" 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb STATEMENT: SELECT jsonb_populate_recordset(row(1,2)::jb_ordered_pair, '[{"x": 1, "y": 0}]'); 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb DETAIL: Returned row contains 1 attribute, but query expects 2. 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-07-03 22:06:46.624 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(0::int,0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb DETAIL: Returned row contains 3 attributes, but query expects 2. 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(0::int,0::int,0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.625 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.625 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime())')); 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb ERROR: function return row and query-specified return row do not match 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb DETAIL: Returned type integer at ordinal position 1, but query expects text. 2025-07-03 22:06:46.625 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text); 2025-07-03 22:06:46.626 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.626 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime("HH:MI TZH"))')); 2025-07-03 22:06:46.630 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.630 UTC client backend[26026] pg_regress/jsonb HINT: See the value of key "ia". 2025-07-03 22:06:46.630 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": 123}') as x(ia _int4); 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb ERROR: expected JSON array 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb HINT: See the array element [1] of key "ia". 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": [[1], 2]}') as x(ia _int4); 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb ERROR: malformed JSON array 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb DETAIL: Multidimensional arrays must have sub-arrays with matching dimensions. 2025-07-03 22:06:46.632 UTC client backend[26026] pg_regress/jsonb STATEMENT: select * from jsonb_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4); 2025-07-03 22:06:46.636 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.636 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime("HH:MI TZH") < $.datetime("YY-MM-DD HH:MI"))')); 2025-07-03 22:06:46.648 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.648 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() < $x' PASSING '12:34'::timetz AS x)); 2025-07-03 22:06:46.657 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.657 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() ? (@ == $x)' PASSING '12:34'::time AS x)); 2025-07-03 22:06:46.665 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.665 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$[1, $.a ? (@.datetime() == $x)]' PASSING '12:34'::time AS x)); 2025-07-03 22:06:46.668 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.668 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$[1, 0 to $.a ? (@.datetime() == $x)]' PASSING '12:34'::time AS x)); 2025-07-03 22:06:46.674 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: functions in index expression must be marked IMMUTABLE 2025-07-03 22:06:46.674 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: CREATE INDEX ON test_jsonb_mutability (JSON_VALUE(js, '$' DEFAULT random()::int ON ERROR)); 2025-07-03 22:06:46.682 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: DEFAULT expression must not return a set at character 50 2025-07-03 22:06:46.682 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT ret_setint() ON ERROR) FROM test_jsonb_mutability; 2025-07-03 22:06:46.684 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: DEFAULT expression must not contain column references at character 50 2025-07-03 22:06:46.684 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT b + 1 ON ERROR) FROM test_jsonb_mutability; 2025-07-03 22:06:46.684 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50 2025-07-03 22:06:46.684 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT sum(1) over() ON ERROR) FROM test_jsonb_mutability; 2025-07-03 22:06:46.685 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50 2025-07-03 22:06:46.685 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(js, '$' RETURNING int DEFAULT (SELECT 1) ON ERROR) FROM test_jsonb_mutability; 2025-07-03 22:06:46.740 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type 2025-07-03 22:06:46.740 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: value for domain queryfuncs_test_domain violates check constraint "queryfuncs_test_domain_check" 2025-07-03 22:06:46.740 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '{"d1": "H"}', '$.a2' RETURNING queryfuncs_test_domain DEFAULT 'foo'::queryfuncs_test_domain ON EMPTY); 2025-07-03 22:06:46.743 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55 2025-07-03 22:06:46.743 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int DEFAULT (SELECT '"1"')::jsonb ON ERROR); 2025-07-03 22:06:46.744 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 73 2025-07-03 22:06:46.744 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING queryfuncs_test_domain DEFAULT (select '"1"')::queryfuncs_test_domain ON ERROR); 2025-07-03 22:06:46.744 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55 2025-07-03 22:06:46.744 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int DEFAULT (SELECT 1)::oid::int ON ERROR); 2025-07-03 22:06:46.745 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57 2025-07-03 22:06:46.745 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int[] DEFAULT (SELECT '{1}')::oid[]::int[] ON ERROR); 2025-07-03 22:06:46.745 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57 2025-07-03 22:06:46.745 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING int[] DEFAULT (SELECT '{1}')::text COLLATE "C" ON ERROR); 2025-07-03 22:06:46.756 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 62 2025-07-03 22:06:46.756 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY('"a"', '$.a' RETURNING someparent DEFAULT (SELECT '(1)')::somechild::someparent ON ERROR); 2025-07-03 22:06:46.778 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: syntax error at or near " " of jsonpath input 2025-07-03 22:06:46.778 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '{"a": 123}', 'error' || ' ' || 'error'); 2025-07-03 22:06:46.799 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "xyz" 2025-07-03 22:06:46.799 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$xyz' PASSING 1 AS xy); 2025-07-03 22:06:46.799 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "xy" 2025-07-03 22:06:46.799 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$xy' PASSING 1 AS xyz); 2025-07-03 22:06:46.800 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not find jsonpath variable "Xyz" 2025-07-03 22:06:46.800 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb 'null', '$Xyz' PASSING 1 AS Xyz); 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 35 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for JSON_EXISTS(). 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_EXISTS(jsonb '1', '$' DEFAULT 1 ON ERROR); 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 34 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, NULL, or DEFAULT expression is allowed in ON ERROR for JSON_VALUE(). 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1', '$' EMPTY ON ERROR); 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: invalid ON ERROR behavior at character 34 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for JSON_QUERY(). 2025-07-03 22:06:46.802 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '1', '$' TRUE ON ERROR); 2025-07-03 22:06:46.806 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-07-03 22:06:46.806 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR); 2025-07-03 22:06:46.807 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-07-03 22:06:46.807 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR); 2025-07-03 22:06:46.815 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-07-03 22:06:46.815 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR); 2025-07-03 22:06:46.816 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: value too long for type character(2) 2025-07-03 22:06:46.816 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR); 2025-07-03 22:06:46.826 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: bit string too long for type bit varying(3) 2025-07-03 22:06:46.826 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3 DEFAULT '111111' ON ERROR); 2025-07-03 22:06:46.827 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: could not coerce ON ERROR expression (DEFAULT) to the RETURNING type 2025-07-03 22:06:46.827 UTC client backend[26033] pg_regress/sqljson_queryfuncs DETAIL: value for domain queryfuncs_d_varbit3 violates check constraint "queryfuncs_d_varbit3_check" 2025-07-03 22:06:46.827 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3 DEFAULT '01' ON ERROR); 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: bit string length 3 does not match type bit(2) 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"111"', '$' RETURNING bit(2) ERROR ON ERROR); 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: cannot cast behavior expression of type integer to bit at character 63 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs HINT: You will need to explicitly cast the expression to type bit. 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '1234', '$' RETURNING bit(3) DEFAULT 1 ON ERROR); 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs ERROR: bit string length 4 does not match type bit(3) 2025-07-03 22:06:46.828 UTC client backend[26033] pg_regress/sqljson_queryfuncs STATEMENT: SELECT JSON_VALUE(jsonb '"111"', '$.a' RETURNING bit(3) DEFAULT '1111' ON EMPTY); 2025-07-03 22:06:46.837 UTC client backend[26033] pg_regress/sqljson_queryfuncs LOG: disconnection: session time: 0:00:01.117 user=postgres database=regression host=[local] 2025-07-03 22:06:47.494 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 2 is null 2025-07-03 22:06:47.494 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('{"n":null, "a":1, "b":[1,2], "c":{"1":2}, "d":{"1":[2,3]}}'::jsonb, '{d,NULL,0}', '[1,2,3]'); 2025-07-03 22:06:47.495 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 2 is null 2025-07-03 22:06:47.495 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('{"n":null, "a":1, "b":[1,2], "c":{"1":2}, "d":{"1":[2,3]}}'::jsonb, '{d,NULL,0}', '{"1": 2}'); 2025-07-03 22:06:47.498 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 2 is not an integer: "-1e" 2025-07-03 22:06:47.498 UTC client backend[26026] pg_regress/jsonb STATEMENT: select '{"n":null, "a":1, "b":[1,2], "c":{"1":2}, "d":{"1":[2,3]}}'::jsonb #- '{b,-1e}'; 2025-07-03 22:06:47.498 UTC client backend[26026] pg_regress/jsonb ERROR: cannot delete from scalar 2025-07-03 22:06:47.498 UTC client backend[26026] pg_regress/jsonb STATEMENT: select '"a"'::jsonb - 'a'; 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb ERROR: cannot delete from scalar 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb STATEMENT: select '"a"'::jsonb - 1; 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb ERROR: cannot delete from object using integer index 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb STATEMENT: select '{}'::jsonb - 1; 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb ERROR: cannot delete path in scalar 2025-07-03 22:06:47.499 UTC client backend[26026] pg_regress/jsonb STATEMENT: select '"a"'::jsonb #- '{a}'; 2025-07-03 22:06:47.500 UTC client backend[26026] pg_regress/jsonb ERROR: cannot set path in scalar 2025-07-03 22:06:47.500 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('"a"','{a}','"b"'); 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 2 is not an integer: "non_integer" 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": [1, 2, 3]}', '{a, non_integer}', '"new_value"'); 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 3 is not an integer: "non_integer" 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, non_integer}', '"new_value"'); 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 3 is null 2025-07-03 22:06:47.513 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, NULL}', '"new_value"'); 2025-07-03 22:06:47.514 UTC client backend[26026] pg_regress/jsonb ERROR: null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception" 2025-07-03 22:06:47.514 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, null); 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb ERROR: null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception" 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, 'no_such_treatment'); 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb ERROR: JSON value must not be null 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb DETAIL: Exception was raised because null_value_treatment is "raise_exception". 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb HINT: To avoid, either change the null_value_treatment argument or ensure that an SQL NULL is not passed. 2025-07-03 22:06:47.515 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, null_value_treatment => 'raise_exception') as raise_exception; 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb HINT: Try using the function jsonb_set to replace key value. 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"'); 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb HINT: Try using the function jsonb_set to replace key value. 2025-07-03 22:06:47.521 UTC client backend[26026] pg_regress/jsonb STATEMENT: select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"', true); 2025-07-03 22:06:47.526 UTC client backend[26026] pg_regress/jsonb ERROR: subscript type numeric is not supported at character 34 2025-07-03 22:06:47.526 UTC client backend[26026] pg_regress/jsonb HINT: jsonb subscript must be coercible to either integer or text. 2025-07-03 22:06:47.526 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1.0]; 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 32 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('{"a": 1}'::jsonb)['a':'b']; 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 36 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1:2]; 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 35 2025-07-03 22:06:47.537 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[:2]; 2025-07-03 22:06:47.538 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript does not support slices at character 34 2025-07-03 22:06:47.538 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[1:]; 2025-07-03 22:06:47.538 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript does not support slices 2025-07-03 22:06:47.538 UTC client backend[26026] pg_regress/jsonb STATEMENT: select ('[1, "2", null]'::jsonb)[:]; 2025-07-03 22:06:47.556 UTC client backend[26026] pg_regress/jsonb ERROR: jsonb subscript in assignment must not be null 2025-07-03 22:06:47.556 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[NULL] = '1'; 2025-07-03 22:06:47.562 UTC client backend[26026] pg_regress/jsonb ERROR: path element at position 1 is out of range: -8 2025-07-03 22:06:47.562 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[-8] = '1'; 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a']['b'] = '1'; 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.598 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a']['b']['c'] = '1'; 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0] = '1'; 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0]['c'] = '1'; 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.599 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json['a'][0][0] = '1'; 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[0] = '1'; 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb ERROR: cannot replace existing key 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb DETAIL: The path assumes key is a composite object, but it is a scalar value. 2025-07-03 22:06:47.600 UTC client backend[26026] pg_regress/jsonb STATEMENT: update test_jsonb_subscript set test_json[0][0] = '1'; 2025-07-03 22:06:47.603 UTC postmaster[14495] LOG: client backend (PID 26036) was terminated by signal 6: Aborted 2025-07-03 22:06:47.603 UTC postmaster[14495] DETAIL: Failed process was running: select '$.replace("hello","bye")'::jsonpath; 2025-07-03 22:06:47.603 UTC postmaster[14495] LOG: terminating any other active server processes 2025-07-03 22:06:47.984 UTC not initialized[26213] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:47.984 UTC client backend[26213] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:47.994 UTC not initialized[26215] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:47.994 UTC client backend[26215] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:47.995 UTC not initialized[26217] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.003 UTC client backend[26217] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.009 UTC not initialized[26218] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.009 UTC client backend[26218] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.014 UTC not initialized[26219] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.014 UTC client backend[26219] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.017 UTC not initialized[26220] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.017 UTC client backend[26220] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.024 UTC not initialized[26221] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.024 UTC client backend[26221] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.032 UTC not initialized[26222] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.033 UTC client backend[26222] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.034 UTC not initialized[26224] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.035 UTC client backend[26224] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.035 UTC not initialized[26225] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.040 UTC client backend[26225] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.046 UTC not initialized[26223] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.046 UTC client backend[26223] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.060 UTC not initialized[26226] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.060 UTC client backend[26226] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.064 UTC not initialized[26227] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.064 UTC client backend[26227] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.065 UTC not initialized[26229] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.065 UTC client backend[26229] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.069 UTC not initialized[26233] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.069 UTC client backend[26233] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.071 UTC not initialized[26234] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.071 UTC client backend[26234] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.087 UTC not initialized[26235] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.087 UTC client backend[26235] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.095 UTC not initialized[26236] [unknown] LOG: connection received: host=[local] 2025-07-03 22:06:48.095 UTC client backend[26236] [unknown] FATAL: the database system is in recovery mode 2025-07-03 22:06:48.340 UTC postmaster[14495] LOG: shutting down because "restart_after_crash" is off 2025-07-03 22:06:48.395 UTC postmaster[14495] LOG: database system is shut down