2025-02-01 03:24:44.455 UTC postmaster[25306] LOG:  starting PostgreSQL 18devel on x86_64-linux, compiled by gcc-12.2.0, 64-bit
2025-02-01 03:24:44.455 UTC postmaster[25306] LOG:  listening on Unix socket "/tmp/pg_regress-Oplk9r/.s.PGSQL.40052"
2025-02-01 03:24:44.475 UTC startup[25316] LOG:  database system was shut down at 2025-02-01 03:24:44 UTC
2025-02-01 03:24:44.478 UTC postmaster[25306] LOG:  database system is ready to accept connections
2025-02-01 03:24:45.216 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "" at character 8
2025-02-01 03:24:45.216 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Missing left parenthesis or bracket.
2025-02-01 03:24:45.216 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select ''::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "-[a,z)" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Missing left parenthesis or bracket.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '-[a,z)'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "[a,z) - " at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '[a,z) - '::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(",a)" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Unexpected end of input.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(",a)'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(,,a)" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Too many commas.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(,,a)'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(),a)" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Missing comma after lower bound.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(),a)'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(a,))" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(a,))'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(],a)" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Missing comma after lower bound.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(],a)'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  malformed range literal: "(a,])" at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes DETAIL:  Junk after right parenthesis or bracket.
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '(a,])'::textrange;
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2025-02-01 03:24:45.219 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '[z,a]'::textrange;
2025-02-01 03:24:45.222 UTC client backend[25490] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "G/0" at character 32
2025-02-01 03:24:45.222 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('G/0');
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "-1/0" at character 32
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('-1/0');
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: " 0/12345678" at character 32
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES (' 0/12345678');
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "ABCD/" at character 32
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('ABCD/');
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn ERROR:  invalid input syntax for type pg_lsn: "/ABCD" at character 32
2025-02-01 03:24:45.223 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  INSERT INTO PG_LSN_TBL VALUES ('/ABCD');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "34.5" at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('34.5');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  value "1000000000000" is out of range for type integer at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('1000000000000');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "asdf" at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('asdf');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "     " at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('     ');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "   asdf   " at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('   asdf   ');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "- 1234" at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('- 1234');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "123       5" at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('123       5');
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "" at character 34
2025-02-01 03:24:45.226 UTC client backend[25496] pg_regress/int4 STATEMENT:  INSERT INTO INT4_TBL(f1) VALUES ('');
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "34.5" at character 34
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('34.5');
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 ERROR:  value "100000" is out of range for type smallint at character 34
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('100000');
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "asdf" at character 34
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('asdf');
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "    " at character 34
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('    ');
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "- 1234" at character 34
2025-02-01 03:24:45.230 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('- 1234');
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "4 444" at character 34
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('4 444');
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "123 dt" at character 34
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('123 dt');
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "" at character 34
2025-02-01 03:24:45.231 UTC client backend[25497] pg_regress/int2 STATEMENT:  INSERT INTO INT2_TBL(f1) VALUES ('');
2025-02-01 03:24:45.232 UTC client backend[25497] pg_regress/int2 ERROR:  table "f" has 1 columns available but 2 columns specified
2025-02-01 03:24:45.232 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT * FROM INT2_TBL AS f(a, b);
2025-02-01 03:24:45.233 UTC client backend[25497] pg_regress/int2 ERROR:  table "s" has 1 columns available but 2 columns specified
2025-02-01 03:24:45.233 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT * FROM (TABLE int2_tbl) AS s (a, b);
2025-02-01 03:24:45.234 UTC client backend[25495] pg_regress/text ERROR:  function length(integer) does not exist at character 8
2025-02-01 03:24:45.234 UTC client backend[25495] pg_regress/text HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:45.234 UTC client backend[25495] pg_regress/text STATEMENT:  select length(42);
2025-02-01 03:24:45.236 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "test" at character 13
2025-02-01 03:24:45.236 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'test' AS error;
2025-02-01 03:24:45.236 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "foo" at character 13
2025-02-01 03:24:45.236 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'foo' AS error;
2025-02-01 03:24:45.238 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "yeah" at character 13
2025-02-01 03:24:45.238 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'yeah' AS error;
2025-02-01 03:24:45.240 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "nay" at character 13
2025-02-01 03:24:45.240 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'nay' AS error;
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "o" at character 13
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'o' AS error;
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "on_" at character 13
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'on_' AS error;
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "off_" at character 13
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool 'off_' AS error;
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "11" at character 13
2025-02-01 03:24:45.241 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool '11' AS error;
2025-02-01 03:24:45.242 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "000" at character 13
2025-02-01 03:24:45.242 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool '000' AS error;
2025-02-01 03:24:45.242 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "" at character 13
2025-02-01 03:24:45.242 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT bool '' AS error;
2025-02-01 03:24:45.242 UTC client backend[25490] pg_regress/pg_lsn ERROR:  pg_lsn out of range
2025-02-01 03:24:45.242 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  SELECT 'FFFFFFFF/FFFFFFFE'::pg_lsn + 2::numeric;
2025-02-01 03:24:45.244 UTC client backend[25490] pg_regress/pg_lsn ERROR:  pg_lsn out of range
2025-02-01 03:24:45.244 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  SELECT '0/1'::pg_lsn - 2::numeric;
2025-02-01 03:24:45.246 UTC client backend[25490] pg_regress/pg_lsn ERROR:  cannot add NaN to pg_lsn
2025-02-01 03:24:45.246 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  SELECT '0/16AE7F7'::pg_lsn + 'NaN'::numeric;
2025-02-01 03:24:45.246 UTC client backend[25490] pg_regress/pg_lsn ERROR:  cannot subtract NaN from pg_lsn
2025-02-01 03:24:45.246 UTC client backend[25490] pg_regress/pg_lsn STATEMENT:  SELECT '0/16AE7F7'::pg_lsn - 'NaN'::numeric;
2025-02-01 03:24:45.246 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "foo.boo[]"
2025-02-01 03:24:45.246 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('foo.boo[]');
2025-02-01 03:24:45.246 UTC client backend[25503] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "31:12:" at character 8
2025-02-01 03:24:45.246 UTC client backend[25503] pg_regress/txid STATEMENT:  select '31:12:'::txid_snapshot;
2025-02-01 03:24:45.247 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "      " at character 34
2025-02-01 03:24:45.247 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('      ');
2025-02-01 03:24:45.249 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: " "
2025-02-01 03:24:45.249 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident(' ');
2025-02-01 03:24:45.249 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "xxx" at character 34
2025-02-01 03:24:45.249 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('xxx');
2025-02-01 03:24:45.249 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: " .aaa"
2025-02-01 03:24:45.249 UTC client backend[25494] pg_regress/name DETAIL:  No valid identifier before ".".
2025-02-01 03:24:45.249 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident(' .aaa');
2025-02-01 03:24:45.249 UTC client backend[25508] pg_regress/int8 ERROR:  value "3908203590239580293850293850329485" is out of range for type bigint at character 34
2025-02-01 03:24:45.249 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('3908203590239580293850293850329485');
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: " aaa . "
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name DETAIL:  No valid identifier after ".".
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident(' aaa . ');
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 ERROR:  value "-1204982019841029840928340329840934" is out of range for type bigint at character 34
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('-1204982019841029840928340329840934');
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "aaa.a%b"
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('aaa.a%b');
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "- 123" at character 34
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('- 123');
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "X
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
2025-02-01 03:24:45.250 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident(E'X\rXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX');
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "  345     5" at character 34
2025-02-01 03:24:45.250 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('  345     5');
2025-02-01 03:24:45.251 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "" at character 34
2025-02-01 03:24:45.251 UTC client backend[25508] pg_regress/int8 STATEMENT:  INSERT INTO INT8_TBL(q1) VALUES ('');
2025-02-01 03:24:45.257 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "  tru e "
2025-02-01 03:24:45.257 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT '  tru e '::text::boolean AS invalid;
2025-02-01 03:24:45.258 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: ""
2025-02-01 03:24:45.258 UTC client backend[25500] pg_regress/boolean STATEMENT:  SELECT ''::text::boolean AS invalid;
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc ERROR:  operator does not exist: ||// at character 16
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regoper('||//');
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc ERROR:  operator does not exist: ++(int4,int4) at character 20
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regoperator('++(int4,int4)');
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc ERROR:  function "know" does not exist at character 16
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regproc('know');
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc ERROR:  function "absinthe(numeric)" does not exist at character 21
2025-02-01 03:24:45.258 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regprocedure('absinthe(numeric)');
2025-02-01 03:24:45.259 UTC client backend[25495] pg_regress/text ERROR:  operator does not exist: integer || numeric at character 10
2025-02-01 03:24:45.259 UTC client backend[25495] pg_regress/text HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:45.259 UTC client backend[25495] pg_regress/text STATEMENT:  select 3 || 4.0;
2025-02-01 03:24:45.259 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: ""c".X XXXXXXXXXX"
2025-02-01 03:24:45.259 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident(E'"c".X XXXX\002XXXXXX');
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "1020"
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('1020');
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "10.20"
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('10.20');
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "."
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name DETAIL:  No valid identifier before ".".
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('.');
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: ".1020"
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name DETAIL:  No valid identifier before ".".
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('.1020');
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name ERROR:  string is not a valid identifier: "xxx.1020"
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name DETAIL:  No valid identifier after ".".
2025-02-01 03:24:45.260 UTC client backend[25494] pg_regress/name STATEMENT:  SELECT parse_ident('xxx.1020');
2025-02-01 03:24:45.260 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.260 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 * int2 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.261 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.261 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 * int4 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.262 UTC client backend[25495] pg_regress/text ERROR:  VARIADIC argument must be an array at character 32
2025-02-01 03:24:45.262 UTC client backend[25495] pg_regress/text STATEMENT:  select concat_ws(',', variadic 10);
2025-02-01 03:24:45.262 UTC client backend[25497] pg_regress/int2 ERROR:  smallint out of range
2025-02-01 03:24:45.262 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 * int2 '2' AS x FROM INT2_TBL i;
2025-02-01 03:24:45.262 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.262 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 + int2 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text ERROR:  too few arguments for format()
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text STATEMENT:  select format('Hello %s %s', 'World');
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text ERROR:  too few arguments for format()
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text STATEMENT:  select format('Hello %s');
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "0:1:" at character 8
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid STATEMENT:  select '0:1:'::txid_snapshot;
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text ERROR:  unrecognized format() type specifier "x"
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text HINT:  For a single "%" use "%%".
2025-02-01 03:24:45.263 UTC client backend[25495] pg_regress/text STATEMENT:  select format('Hello %x', 20);
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "12:13:0" at character 8
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid STATEMENT:  select '12:13:0'::txid_snapshot;
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8
2025-02-01 03:24:45.263 UTC client backend[25503] pg_regress/txid STATEMENT:  select '12:16:14,13'::txid_snapshot;
2025-02-01 03:24:45.264 UTC client backend[25495] pg_regress/text ERROR:  null values cannot be formatted as an SQL identifier
2025-02-01 03:24:45.264 UTC client backend[25495] pg_regress/text STATEMENT:  select format('INSERT INTO %I VALUES(%L,%L)', NULL, 10, 'Hello');
2025-02-01 03:24:45.265 UTC client backend[25507] pg_regress/varchar ERROR:  value too long for type character varying(1)
2025-02-01 03:24:45.265 UTC client backend[25507] pg_regress/varchar STATEMENT:  INSERT INTO VARCHAR_TBL (f1) VALUES ('cd');
2025-02-01 03:24:45.265 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.265 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 + int4 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.266 UTC client backend[25497] pg_regress/int2 ERROR:  smallint out of range
2025-02-01 03:24:45.266 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 + int2 '2' AS x FROM INT2_TBL i;
2025-02-01 03:24:45.266 UTC client backend[25509] pg_regress/float4 ERROR:  "10e70" is out of range for type real at character 36
2025-02-01 03:24:45.266 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70');
2025-02-01 03:24:45.266 UTC client backend[25509] pg_regress/float4 ERROR:  "-10e70" is out of range for type real at character 36
2025-02-01 03:24:45.266 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70');
2025-02-01 03:24:45.266 UTC client backend[25506] pg_regress/enum ERROR:  invalid input value for enum rainbow: "mauve" at character 8
2025-02-01 03:24:45.266 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT 'mauve'::rainbow;
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 ERROR:  "10e-70" is out of range for type real at character 36
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70');
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 ERROR:  "-10e-70" is out of range for type real at character 36
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70');
2025-02-01 03:24:45.267 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.267 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 - int2 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 ERROR:  value out of range: overflow
2025-02-01 03:24:45.267 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e70'::float8);
2025-02-01 03:24:45.268 UTC client backend[25497] pg_regress/int2 ERROR:  smallint out of range
2025-02-01 03:24:45.268 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT i.f1, i.f1 - int2 '2' AS x FROM INT2_TBL i;
2025-02-01 03:24:45.269 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.269 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT i.f1, i.f1 - int4 '2' AS x FROM INT4_TBL i;
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 ERROR:  value out of range: overflow
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e70'::float8);
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "    " at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('    ');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "asdfasd" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('asdfasd');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "99asdfasd" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('99asdfasd');
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 ERROR:  value out of range: underflow
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-70'::float8);
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "5    d" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('5    d');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "    5d" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('    5d');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: "5    5" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('5    5');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  invalid input syntax for type oid: " - 500" at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES (' - 500');
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  value "32958209582039852935" is out of range for type oid at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('32958209582039852935');
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 ERROR:  value out of range: underflow
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-70'::float8);
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid ERROR:  value "-23582358720398502385" is out of range for type oid at character 33
2025-02-01 03:24:45.271 UTC client backend[25504] pg_regress/oid STATEMENT:  INSERT INTO OID_TBL(f1) VALUES ('-23582358720398502385');
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 ERROR:  "10e400" is out of range for type real at character 36
2025-02-01 03:24:45.271 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e400');
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 ERROR:  "-10e400" is out of range for type real at character 36
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e400');
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 ERROR:  "10e-400" is out of range for type real at character 36
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('10e-400');
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 ERROR:  "-10e-400" is out of range for type real at character 36
2025-02-01 03:24:45.272 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('-10e-400');
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "" at character 36
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('');
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "       " at character 36
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('       ');
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "xyz" at character 36
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('xyz');
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "5.0.0" at character 36
2025-02-01 03:24:45.273 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5.0.0');
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "5 . 0" at character 36
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5 . 0');
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "5.   0" at character 36
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('5.   0');
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "     - 3.0" at character 36
2025-02-01 03:24:45.274 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('     - 3.0');
2025-02-01 03:24:45.275 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "123            5" at character 36
2025-02-01 03:24:45.275 UTC client backend[25509] pg_regress/float4 STATEMENT:  INSERT INTO FLOAT4_TBL(f1) VALUES ('123            5');
2025-02-01 03:24:45.281 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "N A N" at character 8
2025-02-01 03:24:45.281 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT 'N A N'::float4;
2025-02-01 03:24:45.282 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: "NaN x" at character 8
2025-02-01 03:24:45.282 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT 'NaN x'::float4;
2025-02-01 03:24:45.282 UTC client backend[25509] pg_regress/float4 ERROR:  invalid input syntax for type real: " INFINITY    x" at character 8
2025-02-01 03:24:45.282 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT ' INFINITY    x'::float4;
2025-02-01 03:24:45.283 UTC client backend[25510] pg_regress/bit ERROR:  bit string length 2 does not match type bit(11)
2025-02-01 03:24:45.283 UTC client backend[25510] pg_regress/bit STATEMENT:  INSERT INTO BIT_TABLE VALUES (B'10');
2025-02-01 03:24:45.284 UTC client backend[25500] pg_regress/boolean ERROR:  invalid input syntax for type boolean: "XXX" at character 43
2025-02-01 03:24:45.284 UTC client backend[25500] pg_regress/boolean STATEMENT:  INSERT INTO BOOLTBL2 (f1)
	   VALUES (bool 'XXX');
2025-02-01 03:24:45.284 UTC client backend[25510] pg_regress/bit ERROR:  bit string length 12 does not match type bit(11)
2025-02-01 03:24:45.284 UTC client backend[25510] pg_regress/bit STATEMENT:  INSERT INTO BIT_TABLE VALUES (B'101011111010');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  relation "pg_classes" does not exist at character 17
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regclass('pg_classes');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  type "int3" does not exist at character 16
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regtype('int3');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  operator does not exist: ng_catalog.||/ at character 16
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regoper('ng_catalog.||/');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  operator does not exist: ng_catalog.+(int4,int4) at character 20
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regoperator('ng_catalog.+(int4,int4)');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  function "ng_catalog.now" does not exist at character 16
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regproc('ng_catalog.now');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  function "ng_catalog.abs(numeric)" does not exist at character 21
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regprocedure('ng_catalog.abs(numeric)');
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc ERROR:  relation "ng_catalog.pg_class" does not exist at character 17
2025-02-01 03:24:45.284 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regclass('ng_catalog.pg_class');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  schema "ng_catalog" does not exist at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regtype('ng_catalog.int4');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  collation "ng_catalog.POSIX" for encoding "UTF8" does not exist at character 21
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regcollation('ng_catalog."POSIX"');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  role "regress_regrole_test" does not exist at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regrole('regress_regrole_test');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  role "regress_regrole_test" does not exist at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regrole('"regress_regrole_test"');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  role "nonexistent" does not exist at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regrole('Nonexistent');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  role "Nonexistent" does not exist at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regrole('"Nonexistent"');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  invalid name syntax at character 16
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regrole('foo.bar');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  schema "nonexistent" does not exist at character 21
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regnamespace('Nonexistent');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  schema "Nonexistent" does not exist at character 21
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regnamespace('"Nonexistent"');
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc ERROR:  invalid name syntax at character 21
2025-02-01 03:24:45.285 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT regnamespace('foo.bar');
2025-02-01 03:24:45.286 UTC client backend[25510] pg_regress/bit ERROR:  bit string too long for type bit varying(11)
2025-02-01 03:24:45.286 UTC client backend[25510] pg_regress/bit STATEMENT:  INSERT INTO VARBIT_TABLE VALUES (B'101011111010');
2025-02-01 03:24:45.286 UTC client backend[25502] pg_regress/char ERROR:  value too long for type character(1)
2025-02-01 03:24:45.286 UTC client backend[25502] pg_regress/char STATEMENT:  INSERT INTO CHAR_TBL (f1) VALUES ('cd');
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 * (-1)::int4;
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 / (-1)::int4;
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 * (-1)::int2;
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.288 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT (-2147483648)::int4 / (-1)::int2;
2025-02-01 03:24:45.289 UTC client backend[25502] pg_regress/char ERROR:  value too long for type character(4)
2025-02-01 03:24:45.289 UTC client backend[25502] pg_regress/char STATEMENT:  INSERT INTO CHAR_TBL (f1) VALUES ('abcde');
2025-02-01 03:24:45.290 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.290 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT gcd((-2147483648)::int4, 0::int4);
2025-02-01 03:24:45.290 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.290 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT gcd((-2147483648)::int4, (-2147483648)::int4);
2025-02-01 03:24:45.291 UTC client backend[25497] pg_regress/int2 ERROR:  smallint out of range
2025-02-01 03:24:45.291 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT (-32768)::int2 * (-1)::int2;
2025-02-01 03:24:45.291 UTC client backend[25497] pg_regress/int2 ERROR:  smallint out of range
2025-02-01 03:24:45.291 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT (-32768)::int2 / (-1)::int2;
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0b" at character 13
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0b';
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0o" at character 13
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0o';
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "0x" at character 13
2025-02-01 03:24:45.292 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0x';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "0b1000000000000000" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0b1000000000000000';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "0o100000" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0o100000';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "0x8000" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '0x8000';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "-0b1000000000000001" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '-0b1000000000000001';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "-0o100001" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '-0o100001';
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 ERROR:  value "-0x8001" is out of range for type smallint at character 13
2025-02-01 03:24:45.293 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '-0x8001';
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "_100" at character 13
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '_100';
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "100_" at character 13
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '100_';
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 ERROR:  invalid input syntax for type smallint: "10__000" at character 13
2025-02-01 03:24:45.294 UTC client backend[25497] pg_regress/int2 STATEMENT:  SELECT int2 '10__000';
2025-02-01 03:24:45.294 UTC client backend[25495] pg_regress/text ERROR:  too few arguments for format()
2025-02-01 03:24:45.294 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%1$s %4$s', 1, 2, 3);
2025-02-01 03:24:45.294 UTC client backend[25495] pg_regress/text ERROR:  too few arguments for format()
2025-02-01 03:24:45.294 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%1$s %13$s', 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12);
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text ERROR:  format specifies argument 0, but arguments are numbered from 1
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%0$s', 'Hello');
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text ERROR:  format specifies argument 0, but arguments are numbered from 1
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%*0$s', 'Hello');
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text ERROR:  unterminated format() type specifier
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text HINT:  For a single "%" use "%%".
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%1$', 1);
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text ERROR:  unterminated format() type specifier
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text HINT:  For a single "%" use "%%".
2025-02-01 03:24:45.295 UTC client backend[25495] pg_regress/text STATEMENT:  select format('%1$1', 1);
2025-02-01 03:24:45.297 UTC client backend[25510] pg_regress/bit ERROR:  " " is not a valid binary digit at character 8
2025-02-01 03:24:45.297 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT b' 0';
2025-02-01 03:24:45.298 UTC client backend[25512] pg_regress/float8 ERROR:  "10e400" is out of range for type double precision at character 8
2025-02-01 03:24:45.298 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '10e400'::float8;
2025-02-01 03:24:45.299 UTC client backend[25512] pg_regress/float8 ERROR:  "-10e400" is out of range for type double precision at character 8
2025-02-01 03:24:45.299 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '-10e400'::float8;
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 ERROR:  "10e-400" is out of range for type double precision at character 8
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '10e-400'::float8;
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 ERROR:  "-10e-400" is out of range for type double precision at character 8
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '-10e-400'::float8;
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "" at character 36
2025-02-01 03:24:45.300 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('');
2025-02-01 03:24:45.300 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11111111-1111-1111-1111-111111111111F" at character 38
2025-02-01 03:24:45.300 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111F');
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "{11111111-1111-1111-1111-11111111111}" at character 38
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('{11111111-1111-1111-1111-11111111111}');
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "111-11111-1111-1111-1111-111111111111" at character 38
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('111-11111-1111-1111-1111-111111111111');
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "{22222222-2222-2222-2222-222222222222 " at character 38
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('{22222222-2222-2222-2222-222222222222 ');
2025-02-01 03:24:45.301 UTC client backend[25503] pg_regress/txid ERROR:  invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 22
2025-02-01 03:24:45.301 UTC client backend[25503] pg_regress/txid STATEMENT:  SELECT txid_snapshot '1:9223372036854775808:3';
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11111111-1111-1111-G111-111111111111" at character 38
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-G111-111111111111');
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid ERROR:  invalid input syntax for type uuid: "11+11111-1111-1111-1111-111111111111" at character 38
2025-02-01 03:24:45.301 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11+11111-1111-1111-1111-111111111111');
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit ERROR:  " " is not a valid binary digit at character 8
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT b'0 ';
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit ERROR:  " " is not a valid hexadecimal digit at character 8
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT x' 0';
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit ERROR:  " " is not a valid hexadecimal digit at character 8
2025-02-01 03:24:45.302 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT x'0 ';
2025-02-01 03:24:45.303 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.303 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT q1, q2, q1 * q2 AS multiply FROM INT8_TBL;
2025-02-01 03:24:45.305 UTC client backend[25509] pg_regress/float4 ERROR:  division by zero
2025-02-01 03:24:45.305 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT f.f1 / '0.0' from FLOAT4_TBL f;
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "     " at character 36
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('     ');
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "xyz" at character 36
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('xyz');
2025-02-01 03:24:45.307 UTC client backend[25498] pg_regress/money ERROR:  value "123456789012345678" is out of range for type money at character 8
2025-02-01 03:24:45.307 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '123456789012345678'::money;
2025-02-01 03:24:45.307 UTC client backend[25498] pg_regress/money ERROR:  value "9223372036854775807" is out of range for type money at character 8
2025-02-01 03:24:45.307 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '9223372036854775807'::money;
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5.0.0" at character 36
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5.0.0');
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5 . 0" at character 36
2025-02-01 03:24:45.307 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5 . 0');
2025-02-01 03:24:45.309 UTC client backend[25507] pg_regress/varchar ERROR:  value too long for type character varying(4)
2025-02-01 03:24:45.309 UTC client backend[25507] pg_regress/varchar STATEMENT:  INSERT INTO VARCHAR_TBL (f1) VALUES ('abcde');
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "5.   0" at character 36
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('5.   0');
2025-02-01 03:24:45.311 UTC client backend[25498] pg_regress/money ERROR:  value "-123456789012345678" is out of range for type money at character 8
2025-02-01 03:24:45.311 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-123456789012345678'::money;
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "    - 3" at character 36
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('    - 3');
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "123           5" at character 36
2025-02-01 03:24:45.311 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('123           5');
2025-02-01 03:24:45.311 UTC client backend[25498] pg_regress/money ERROR:  value "-9223372036854775808" is out of range for type money at character 8
2025-02-01 03:24:45.311 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-9223372036854775808'::money;
2025-02-01 03:24:45.312 UTC client backend[25509] pg_regress/float4 ERROR:  smallint out of range
2025-02-01 03:24:45.312 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '32767.6'::float4::int2;
2025-02-01 03:24:45.313 UTC client backend[25509] pg_regress/float4 ERROR:  smallint out of range
2025-02-01 03:24:45.313 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '-32768.6'::float4::int2;
2025-02-01 03:24:45.314 UTC client backend[25509] pg_regress/float4 ERROR:  integer out of range
2025-02-01 03:24:45.314 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '2147483647'::float4::int4;
2025-02-01 03:24:45.314 UTC client backend[25509] pg_regress/float4 ERROR:  integer out of range
2025-02-01 03:24:45.314 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '-2147483900'::float4::int4;
2025-02-01 03:24:45.315 UTC client backend[25509] pg_regress/float4 ERROR:  bigint out of range
2025-02-01 03:24:45.315 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '9223372036854775807'::float4::int8;
2025-02-01 03:24:45.315 UTC client backend[25509] pg_regress/float4 ERROR:  bigint out of range
2025-02-01 03:24:45.315 UTC client backend[25509] pg_regress/float4 STATEMENT:  SELECT '-9223380000000000000'::float4::int8;
2025-02-01 03:24:45.316 UTC client backend[25498] pg_regress/money ERROR:  value "-92233720368547758.09" is out of range for type money at character 8
2025-02-01 03:24:45.316 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-92233720368547758.09'::money;
2025-02-01 03:24:45.316 UTC client backend[25498] pg_regress/money ERROR:  value "92233720368547758.08" is out of range for type money at character 8
2025-02-01 03:24:45.316 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '92233720368547758.08'::money;
2025-02-01 03:24:45.317 UTC client backend[25498] pg_regress/money ERROR:  value "-92233720368547758.085" is out of range for type money at character 8
2025-02-01 03:24:45.317 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-92233720368547758.085'::money;
2025-02-01 03:24:45.317 UTC client backend[25498] pg_regress/money ERROR:  value "92233720368547758.075" is out of range for type money at character 8
2025-02-01 03:24:45.317 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '92233720368547758.075'::money;
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum ERROR:  invalid enum label "plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto"
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum DETAIL:  Labels must be 63 bytes or less.
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE
	  'plutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutoplutopluto';
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum ERROR:  "zeus" is not an existing enum label
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE 'pluto' AFTER 'zeus';
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum ERROR:  enum label "mercury" already exists
2025-02-01 03:24:45.317 UTC client backend[25506] pg_regress/enum STATEMENT:  ALTER TYPE planets ADD VALUE 'mercury';
2025-02-01 03:24:45.318 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.318 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT lcm((-2147483648)::int4, 1::int4);
2025-02-01 03:24:45.319 UTC client backend[25496] pg_regress/int4 ERROR:  integer out of range
2025-02-01 03:24:45.319 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT lcm(2147483647::int4, 2147483646::int4);
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc ERROR:  syntax error at or near "type" at character 11
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc CONTEXT:  invalid type name "incorrect type name syntax"
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('incorrect type name syntax', 'regtype');
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc ERROR:  invalid NUMERIC type modifier
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('numeric(1,2,3)', 'regtype');
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc ERROR:  improper qualified name (too many dotted names): way.too.many.names
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('way.too.many.names', 'regtype');
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc ERROR:  cross-database references are not implemented: no_such_catalog.schema.name
2025-02-01 03:24:45.321 UTC client backend[25492] pg_regress/regproc STATEMENT:  SELECT * FROM pg_input_error_info('no_such_catalog.schema.name', 'regtype');
2025-02-01 03:24:45.322 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "N A N" at character 8
2025-02-01 03:24:45.322 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT 'N A N'::float8;
2025-02-01 03:24:45.323 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: "NaN x" at character 8
2025-02-01 03:24:45.323 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT 'NaN x'::float8;
2025-02-01 03:24:45.323 UTC client backend[25512] pg_regress/float8 ERROR:  invalid input syntax for type double precision: " INFINITY    x" at character 8
2025-02-01 03:24:45.323 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT ' INFINITY    x'::float8;
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0b" at character 13
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0b';
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0o" at character 13
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0o';
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "0x" at character 13
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0x';
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 ERROR:  value "0b10000000000000000000000000000000" is out of range for type integer at character 13
2025-02-01 03:24:45.331 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0b10000000000000000000000000000000';
2025-02-01 03:24:45.332 UTC client backend[25489] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:45.332 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select numrange(2.0, 1.0);
2025-02-01 03:24:45.332 UTC client backend[25496] pg_regress/int4 ERROR:  value "0o20000000000" is out of range for type integer at character 13
2025-02-01 03:24:45.332 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0o20000000000';
2025-02-01 03:24:45.333 UTC client backend[25496] pg_regress/int4 ERROR:  value "0x80000000" is out of range for type integer at character 13
2025-02-01 03:24:45.333 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '0x80000000';
2025-02-01 03:24:45.333 UTC client backend[25496] pg_regress/int4 ERROR:  value "-0b10000000000000000000000000000001" is out of range for type integer at character 13
2025-02-01 03:24:45.333 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '-0b10000000000000000000000000000001';
2025-02-01 03:24:45.334 UTC client backend[25496] pg_regress/int4 ERROR:  value "-0o20000000001" is out of range for type integer at character 13
2025-02-01 03:24:45.334 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '-0o20000000001';
2025-02-01 03:24:45.334 UTC client backend[25496] pg_regress/int4 ERROR:  value "-0x80000001" is out of range for type integer at character 13
2025-02-01 03:24:45.334 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '-0x80000001';
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "_100" at character 13
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '_100';
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "100_" at character 13
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '100_';
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 ERROR:  invalid input syntax for type integer: "100__000" at character 13
2025-02-01 03:24:45.341 UTC client backend[25496] pg_regress/int4 STATEMENT:  SELECT int4 '100__000';
2025-02-01 03:24:45.343 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.343 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '92233720368547758.07'::money + '0.01'::money;
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-92233720368547758.08'::money - '0.01'::money;
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '92233720368547758.07'::money * 2::float8;
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.344 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '-1'::money / 1.175494e-38::float4;
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '92233720368547758.07'::money * 2::int4;
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money ERROR:  division by zero
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '1'::money / 0::int2;
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '42'::money * 'inf'::float8;
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '42'::money * '-inf'::float8;
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money ERROR:  money out of range
2025-02-01 03:24:45.345 UTC client backend[25498] pg_regress/money STATEMENT:  SELECT '42'::money * 'nan'::float4;
2025-02-01 03:24:45.350 UTC client backend[25489] pg_regress/rangetypes ERROR:  result of range union would not be contiguous
2025-02-01 03:24:45.350 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select numrange(1.0, 2.0) + numrange(2.5, 3.0);
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 ERROR:  value "-9223372036854775809" is out of range for type bigint at character 8
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775809'::int8;
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 ERROR:  value "9223372036854775808" is out of range for type bigint at character 8
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775808'::int8;
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 STATEMENT:  select -('-9223372036854775808'::int8);
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 STATEMENT:  select 0::int8 - '-9223372036854775808'::int8;
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.353 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '9223372036854775800'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 + '-9223372036854775800'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 - '-9223372036854775800'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '9223372036854775800'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '9223372036854775800'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  division by zero
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 / '0'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  division by zero
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 % '0'::int8;
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.354 UTC client backend[25508] pg_regress/int8 STATEMENT:  select abs('-9223372036854775808'::int8);
2025-02-01 03:24:45.356 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.356 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '100'::int4;
2025-02-01 03:24:45.357 UTC client backend[25505] pg_regress/uuid ERROR:  duplicate key value violates unique constraint "guid1_unique_btree"
2025-02-01 03:24:45.357 UTC client backend[25505] pg_regress/uuid DETAIL:  Key (guid_field)=(11111111-1111-1111-1111-111111111111) already exists.
2025-02-01 03:24:45.357 UTC client backend[25505] pg_regress/uuid STATEMENT:  INSERT INTO guid1(guid_field) VALUES('11111111-1111-1111-1111-111111111111');
2025-02-01 03:24:45.360 UTC client backend[25512] pg_regress/float8 ERROR:  zero raised to a negative power is undefined
2025-02-01 03:24:45.360 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT power(float8 '0', float8 '-inf');
2025-02-01 03:24:45.360 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.360 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '100'::int4;
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '100'::int4;
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '100'::int4 + '9223372036854775800'::int8;
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-100'::int4 - '9223372036854775800'::int8;
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.361 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '100'::int4 * '9223372036854775800'::int8;
2025-02-01 03:24:45.365 UTC client backend[25512] pg_regress/float8 ERROR:  a negative number raised to a non-integer power yields a complex result
2025-02-01 03:24:45.365 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT power(float8 '-inf', float8 '3.5');
2025-02-01 03:24:45.367 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.367 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 + '100'::int2;
2025-02-01 03:24:45.367 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.367 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775800'::int8 - '100'::int2;
2025-02-01 03:24:45.368 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.368 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '9223372036854775800'::int8 * '100'::int2;
2025-02-01 03:24:45.368 UTC client backend[25508] pg_regress/int8 ERROR:  division by zero
2025-02-01 03:24:45.368 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-9223372036854775808'::int8 / '0'::int2;
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '100'::int2 + '9223372036854775800'::int8;
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '-100'::int2 - '9223372036854775800'::int8;
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '100'::int2 * '9223372036854775800'::int8;
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 ERROR:  division by zero
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 STATEMENT:  select '100'::int2 / '0'::int8;
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 ERROR:  integer out of range
2025-02-01 03:24:45.369 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS int4) FROM int8_tbl WHERE q2 <> 456;
2025-02-01 03:24:45.371 UTC client backend[25508] pg_regress/int8 ERROR:  smallint out of range
2025-02-01 03:24:45.371 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS int2) FROM int8_tbl WHERE q2 <> 456;
2025-02-01 03:24:45.375 UTC client backend[25512] pg_regress/float8 ERROR:  value out of range: overflow
2025-02-01 03:24:45.375 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT f.f1 * '1e200' from FLOAT8_TBL f;
2025-02-01 03:24:45.375 UTC client backend[25512] pg_regress/float8 ERROR:  value out of range: overflow
2025-02-01 03:24:45.375 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT f.f1 ^ '1e200' from FLOAT8_TBL f;
2025-02-01 03:24:45.375 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.375 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT CAST('922337203685477580700.0'::float8 AS int8);
2025-02-01 03:24:45.375 UTC client backend[25508] pg_regress/int8 ERROR:  OID out of range
2025-02-01 03:24:45.375 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT CAST(q1 AS oid) FROM INT8_TBL;
2025-02-01 03:24:45.376 UTC client backend[25512] pg_regress/float8 ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.376 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 = '0.0' ;
2025-02-01 03:24:45.376 UTC client backend[25512] pg_regress/float8 ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.376 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT ln(f.f1) from FLOAT8_TBL f where f.f1 < '0.0' ;
2025-02-01 03:24:45.377 UTC client backend[25512] pg_regress/float8 ERROR:  value out of range: underflow
2025-02-01 03:24:45.377 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT exp(f.f1) from FLOAT8_TBL f;
2025-02-01 03:24:45.377 UTC client backend[25512] pg_regress/float8 ERROR:  division by zero
2025-02-01 03:24:45.377 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT f.f1 / '0.0' from FLOAT8_TBL f;
2025-02-01 03:24:45.378 UTC client backend[25508] pg_regress/int8 ERROR:  step size cannot equal zero
2025-02-01 03:24:45.378 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT * FROM generate_series('+4567890123456789'::int8, '+4567890123456799'::int8, 0);
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int8;
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int8;
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int4;
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.379 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int4;
2025-02-01 03:24:45.380 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.380 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 * (-1)::int2;
2025-02-01 03:24:45.380 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.380 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT (-9223372036854775808)::int8 / (-1)::int2;
2025-02-01 03:24:45.382 UTC client backend[25512] pg_regress/float8 ERROR:  input is out of range
2025-02-01 03:24:45.382 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT acosh(float8 '-infinity');
2025-02-01 03:24:45.383 UTC client backend[25512] pg_regress/float8 ERROR:  input is out of range
2025-02-01 03:24:45.383 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT atanh(float8 'infinity');
2025-02-01 03:24:45.383 UTC client backend[25512] pg_regress/float8 ERROR:  input is out of range
2025-02-01 03:24:45.383 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT atanh(float8 '-infinity');
2025-02-01 03:24:45.383 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.383 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT gcd((-9223372036854775808)::int8, 0::int8);
2025-02-01 03:24:45.383 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.383 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT gcd((-9223372036854775808)::int8, (-9223372036854775808)::int8);
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT lcm((-9223372036854775808)::int8, 1::int8);
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 ERROR:  bigint out of range
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT lcm(9223372036854775807::int8, 9223372036854775806::int8);
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0b" at character 13
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0b';
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0o" at character 13
2025-02-01 03:24:45.387 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0o';
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "0x" at character 13
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0x';
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 ERROR:  value "0b1000000000000000000000000000000000000000000000000000000000000000" is out of range for type bigint at character 13
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0b1000000000000000000000000000000000000000000000000000000000000000';
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 ERROR:  value "0o1000000000000000000000" is out of range for type bigint at character 13
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0o1000000000000000000000';
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 ERROR:  value "0x8000000000000000" is out of range for type bigint at character 13
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '0x8000000000000000';
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 ERROR:  value "-0b1000000000000000000000000000000000000000000000000000000000000001" is out of range for type bigint at character 13
2025-02-01 03:24:45.391 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '-0b1000000000000000000000000000000000000000000000000000000000000001';
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 ERROR:  value "-0o1000000000000000000001" is out of range for type bigint at character 13
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '-0o1000000000000000000001';
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 ERROR:  value "-0x8000000000000001" is out of range for type bigint at character 13
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '-0x8000000000000001';
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "_100" at character 13
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '_100';
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "100_" at character 13
2025-02-01 03:24:45.392 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '100_';
2025-02-01 03:24:45.393 UTC client backend[25508] pg_regress/int8 ERROR:  invalid input syntax for type bigint: "100__000" at character 13
2025-02-01 03:24:45.393 UTC client backend[25508] pg_regress/int8 STATEMENT:  SELECT int8 '100__000';
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 ERROR:  "10e400" is out of range for type double precision at character 36
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('10e400');
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 ERROR:  "-10e400" is out of range for type double precision at character 36
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e400');
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 ERROR:  "10e-400" is out of range for type double precision at character 36
2025-02-01 03:24:45.396 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('10e-400');
2025-02-01 03:24:45.397 UTC client backend[25512] pg_regress/float8 ERROR:  "-10e-400" is out of range for type double precision at character 36
2025-02-01 03:24:45.397 UTC client backend[25512] pg_regress/float8 STATEMENT:  INSERT INTO FLOAT8_TBL(f1) VALUES ('-10e-400');
2025-02-01 03:24:45.404 UTC client backend[25512] pg_regress/float8 ERROR:  smallint out of range
2025-02-01 03:24:45.404 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '32767.6'::float8::int2;
2025-02-01 03:24:45.404 UTC client backend[25512] pg_regress/float8 ERROR:  smallint out of range
2025-02-01 03:24:45.404 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '-32768.6'::float8::int2;
2025-02-01 03:24:45.406 UTC client backend[25512] pg_regress/float8 ERROR:  integer out of range
2025-02-01 03:24:45.406 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '2147483647.6'::float8::int4;
2025-02-01 03:24:45.407 UTC client backend[25512] pg_regress/float8 ERROR:  integer out of range
2025-02-01 03:24:45.407 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '-2147483648.6'::float8::int4;
2025-02-01 03:24:45.408 UTC client backend[25512] pg_regress/float8 ERROR:  bigint out of range
2025-02-01 03:24:45.408 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '9223372036854775807'::float8::int8;
2025-02-01 03:24:45.409 UTC client backend[25512] pg_regress/float8 ERROR:  bigint out of range
2025-02-01 03:24:45.409 UTC client backend[25512] pg_regress/float8 STATEMENT:  SELECT '-9223372036854780000'::float8::int8;
2025-02-01 03:24:45.416 UTC client backend[25506] pg_regress/enum ERROR:  value for domain rgb violates check constraint "rgb_check"
2025-02-01 03:24:45.416 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT 'purple'::rgb;
2025-02-01 03:24:45.417 UTC client backend[25506] pg_regress/enum ERROR:  value for domain rgb violates check constraint "rgb_check"
2025-02-01 03:24:45.417 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT 'purple'::rainbow::rgb;
2025-02-01 03:24:45.420 UTC client backend[25512] pg_regress/float8 ERROR:  type "no_such_type" does not exist at character 69
2025-02-01 03:24:45.420 UTC client backend[25512] pg_regress/float8 STATEMENT:  create type xfloat8 (input = xfloat8in, output = xfloat8out, like = no_such_type);
2025-02-01 03:24:45.444 UTC client backend[25510] pg_regress/bit ERROR:  negative substring length not allowed
2025-02-01 03:24:45.444 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT SUBSTRING('01010101'::bit(8) FROM -10 FOR -2147483646) AS "error";
2025-02-01 03:24:45.444 UTC client backend[25510] pg_regress/bit ERROR:  negative substring length not allowed
2025-02-01 03:24:45.444 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT SUBSTRING('01010101'::varbit FROM -10 FOR -2147483646) AS "error";
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit ERROR:  cannot AND bit strings of different sizes
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit STATEMENT:  select B'001' & B'10';
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit ERROR:  cannot OR bit strings of different sizes
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit STATEMENT:  select B'0111' | B'011';
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit ERROR:  cannot XOR bit strings of different sizes
2025-02-01 03:24:45.459 UTC client backend[25510] pg_regress/bit STATEMENT:  select B'0010' # B'011101';
2025-02-01 03:24:45.466 UTC client backend[25506] pg_regress/enum ERROR:  insert or update on table "enumtest_child" violates foreign key constraint "enumtest_child_parent_fkey"
2025-02-01 03:24:45.466 UTC client backend[25506] pg_regress/enum DETAIL:  Key (parent)=(blue) is not present in table "enumtest_parent".
2025-02-01 03:24:45.466 UTC client backend[25506] pg_regress/enum STATEMENT:  INSERT INTO enumtest_child VALUES ('blue');
2025-02-01 03:24:45.467 UTC client backend[25506] pg_regress/enum ERROR:  update or delete on table "enumtest_parent" violates foreign key constraint "enumtest_child_parent_fkey" on table "enumtest_child"
2025-02-01 03:24:45.467 UTC client backend[25506] pg_regress/enum DETAIL:  Key (id)=(red) is still referenced from table "enumtest_child".
2025-02-01 03:24:45.467 UTC client backend[25506] pg_regress/enum STATEMENT:  DELETE FROM enumtest_parent;
2025-02-01 03:24:45.469 UTC client backend[25506] pg_regress/enum ERROR:  foreign key constraint "enumtest_bogus_child_parent_fkey" cannot be implemented
2025-02-01 03:24:45.469 UTC client backend[25506] 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-02-01 03:24:45.469 UTC client backend[25506] pg_regress/enum STATEMENT:  CREATE TABLE enumtest_bogus_child(parent bogus REFERENCES enumtest_parent);
2025-02-01 03:24:45.473 UTC client backend[25506] pg_regress/enum ERROR:  "red" is not an existing enum label
2025-02-01 03:24:45.473 UTC client backend[25506] pg_regress/enum STATEMENT:  ALTER TYPE rainbow RENAME VALUE 'red' TO 'crimson';
2025-02-01 03:24:45.473 UTC client backend[25506] pg_regress/enum ERROR:  enum label "green" already exists
2025-02-01 03:24:45.473 UTC client backend[25506] pg_regress/enum STATEMENT:  ALTER TYPE rainbow RENAME VALUE 'blue' TO 'green';
2025-02-01 03:24:45.474 UTC client backend[25506] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus at character 8
2025-02-01 03:24:45.474 UTC client backend[25506] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2025-02-01 03:24:45.474 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT 'new'::bogus;
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT enum_last(null::bogus);
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum ERROR:  unsafe use of new value "new" of enum type bogus
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2025-02-01 03:24:45.476 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT enum_range(null::bogus);
2025-02-01 03:24:45.479 UTC client backend[25506] pg_regress/enum ERROR:  unsafe use of new value "bad" of enum type bogon at character 8
2025-02-01 03:24:45.479 UTC client backend[25506] pg_regress/enum HINT:  New enum values must be committed before they can be used.
2025-02-01 03:24:45.479 UTC client backend[25506] pg_regress/enum STATEMENT:  SELECT 'bad'::bogon;
2025-02-01 03:24:45.502 UTC client backend[25510] pg_regress/bit ERROR:  bit index 16 out of valid range (0..15)
2025-02-01 03:24:45.502 UTC client backend[25510] pg_regress/bit STATEMENT:  SELECT set_bit(B'0101011000100100', 16, 1);
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'inf'::numeric / '0';
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '-inf'::numeric / '0';
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '0'::numeric / '0';
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'inf'::numeric % '0';
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '-inf'::numeric % '0';
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.566 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '0'::numeric % '0';
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT div('inf'::numeric, '0');
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT div('-inf'::numeric, '0');
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.567 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT div('0'::numeric, '0');
2025-02-01 03:24:45.568 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take square root of a negative number
2025-02-01 03:24:45.568 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT sqrt('-1'::numeric);
2025-02-01 03:24:45.568 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take square root of a negative number
2025-02-01 03:24:45.568 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT sqrt('-inf'::numeric);
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT ln('0'::numeric);
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT ln('-1'::numeric);
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT ln('-inf'::numeric);
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.569 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('0'::numeric, '10');
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('10'::numeric, '0');
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('-inf'::numeric, '10');
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('10'::numeric, '-inf');
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.570 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('inf'::numeric, '0');
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('inf'::numeric, '-inf');
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT log('-inf'::numeric, 'inf');
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT power('0'::numeric, '-1');
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2025-02-01 03:24:45.571 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT power('0'::numeric, '-inf');
2025-02-01 03:24:45.575 UTC client backend[25513] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2025-02-01 03:24:45.575 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT power('-2'::numeric, '3.3');
2025-02-01 03:24:45.575 UTC client backend[25513] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2025-02-01 03:24:45.575 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT power('-2'::numeric, '-1.5');
2025-02-01 03:24:45.576 UTC client backend[25513] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2025-02-01 03:24:45.576 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT power('-inf'::numeric, '4.5');
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 must round to an absolute value less than 1.
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (3, '1.0');
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 must round to an absolute value less than 1.
2025-02-01 03:24:45.587 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (6, '0.99995');
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 cannot hold an infinite value.
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (10, 'Inf');
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 4, scale 4 cannot hold an infinite value.
2025-02-01 03:24:45.588 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO fract_only VALUES (11, '-Inf');
2025-02-01 03:24:45.589 UTC client backend[25513] pg_regress/numeric ERROR:  bigint out of range
2025-02-01 03:24:45.589 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT (-9223372036854775808.5)::int8;
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric ERROR:  bigint out of range
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 9223372036854775807.5::int8;
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric ERROR:  integer out of range
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT (-2147483648.5)::int4;
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric ERROR:  integer out of range
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 2147483647.5::int4;
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric ERROR:  smallint out of range
2025-02-01 03:24:45.590 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT (-32768.5)::int2;
2025-02-01 03:24:45.591 UTC client backend[25513] pg_regress/numeric ERROR:  smallint out of range
2025-02-01 03:24:45.591 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 32767.5::int2;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert NaN to smallint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int2;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to smallint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int2;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to smallint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int2;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert NaN to integer
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int4;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to integer
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int4;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to integer
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int4;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert NaN to bigint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'NaN'::numeric::int8;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to bigint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT 'Infinity'::numeric::int8;
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert infinity to bigint
2025-02-01 03:24:45.593 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT '-Infinity'::numeric::int8;
2025-02-01 03:24:45.600 UTC client backend[25513] pg_regress/numeric ERROR:  value overflows numeric format
2025-02-01 03:24:45.600 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT round(5.5e131071, -131072);
2025-02-01 03:24:45.604 UTC client backend[25513] pg_regress/numeric ERROR:  count must be greater than zero
2025-02-01 03:24:45.604 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0, 3.0, 4.0, 0);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  count must be greater than zero
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0, 3.0, 4.0, -5);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  lower bound cannot equal upper bound
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(3.5, 3.0, 3.0, 888);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  count must be greater than zero
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, 0);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  count must be greater than zero
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(5.0::float8, 3.0::float8, 4.0::float8, -5);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  lower bound cannot equal upper bound
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(3.5::float8, 3.0::float8, 3.0::float8, 888);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  operand, lower bound, and upper bound cannot be NaN
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket('NaN', 3.0, 4.0, 888);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  operand, lower bound, and upper bound cannot be NaN
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, 'NaN', 4.0::float8, 888);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(2.0, 3.0, '-inf', 888);
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.605 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, '-inf', 4.0::float8, 888);
2025-02-01 03:24:45.619 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.619 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::numeric, 'Infinity'::numeric, 5, 10);
2025-02-01 03:24:45.619 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.619 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::numeric, 5, '-Infinity'::numeric, 20);
2025-02-01 03:24:45.620 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.620 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::float8, 'Infinity'::float8, 5, 10);
2025-02-01 03:24:45.620 UTC client backend[25513] pg_regress/numeric ERROR:  lower and upper bounds must be finite
2025-02-01 03:24:45.620 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0.0::float8, 5, '-Infinity'::float8, 20);
2025-02-01 03:24:45.624 UTC client backend[25513] pg_regress/numeric ERROR:  integer out of range
2025-02-01 03:24:45.624 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(1::float8, 0, 1, 2147483647);
2025-02-01 03:24:45.624 UTC client backend[25513] pg_regress/numeric ERROR:  integer out of range
2025-02-01 03:24:45.624 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT width_bucket(0::float8, 1, 0, 2147483647);
2025-02-01 03:24:45.667 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.667 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('viv', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('DCCCD', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('XIXL', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('MCCM', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('MMMM', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('VV', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('IL', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('VIX', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('LXC', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('DCM', 'RN');
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.668 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('MMMDCM', 'RN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('CLXC', 'RN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  "RN" is incompatible with other formats
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric DETAIL:  "RN" may only be used together with "FM".
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('CM', 'MIRN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  cannot use "RN" twice
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('CM', 'RNRN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('qiv', 'RN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: " "
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number('', 'RN');
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric ERROR:  invalid Roman numeral
2025-02-01 03:24:45.669 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT to_number(' ', 'RN');
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "     " at character 40
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('     ');
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "   1234   %" at character 40
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('   1234   %');
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "xyz" at character 40
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('xyz');
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "- 1234" at character 40
2025-02-01 03:24:45.678 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('- 1234');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "5 . 0" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('5 . 0');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "5. 0   " at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('5. 0   ');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: " N aN " at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES (' N aN ');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "+NaN" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('+NaN');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "-NaN" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('-NaN');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "+ infinity" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('+ infinity');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "_123" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('_123');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123_" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123_');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "12__34" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('12__34');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123_.456" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123_.456');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "123._456" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('123._456');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e_34" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e_34');
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e34_" at character 40
2025-02-01 03:24:45.679 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e34_');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "1.2e3__4" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('1.2e3__4');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0b1112" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0b1112');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0c1112" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0c1112');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0o12345678" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0o12345678');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x1eg" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x1eg');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x12.34" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x12.34');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x__1234" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x__1234');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x1234_" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x1234_');
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric ERROR:  invalid input syntax for type numeric: "0x12__34" at character 40
2025-02-01 03:24:45.680 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_input_test(n1) VALUES ('0x12__34');
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale -6 cannot hold an infinite value.
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millions) VALUES ('inf');
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale -6 must round to an absolute value less than 10^9.
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millions) VALUES (999500000);
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale -3 must round to an absolute value less than 10^6.
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (thousands) VALUES (999500);
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale 0 must round to an absolute value less than 10^3.
2025-02-01 03:24:45.723 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (units) VALUES (999.5);
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale 3 must round to an absolute value less than 1.
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (thousandths) VALUES (0.9995);
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric ERROR:  numeric field overflow
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric DETAIL:  A field with precision 3, scale 6 must round to an absolute value less than 10^-3.
2025-02-01 03:24:45.724 UTC client backend[25513] pg_regress/numeric STATEMENT:  INSERT INTO num_typemod_test (millionths) VALUES (0.0009995);
2025-02-01 03:24:45.750 UTC client backend[25513] pg_regress/numeric ERROR:  value overflows numeric format
2025-02-01 03:24:45.750 UTC client backend[25513] pg_regress/numeric STATEMENT:  select 10.0 ^ 2147483647 as overflows;
2025-02-01 03:24:45.750 UTC client backend[25513] pg_regress/numeric ERROR:  value overflows numeric format
2025-02-01 03:24:45.750 UTC client backend[25513] pg_regress/numeric STATEMENT:  select 117743296169.0 ^ 1000000000 as overflows;
2025-02-01 03:24:45.757 UTC client backend[25513] pg_regress/numeric ERROR:  zero raised to a negative power is undefined
2025-02-01 03:24:45.757 UTC client backend[25513] pg_regress/numeric STATEMENT:  select 0.0 ^ (-12.34);
2025-02-01 03:24:45.757 UTC client backend[25513] pg_regress/numeric ERROR:  a negative number raised to a non-integer power yields a complex result
2025-02-01 03:24:45.757 UTC client backend[25513] pg_regress/numeric STATEMENT:  select (-12.34) ^ 1.2;
2025-02-01 03:24:45.761 UTC client backend[25513] pg_regress/numeric ERROR:  step size cannot equal zero
2025-02-01 03:24:45.761 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series(-100::numeric, 100::numeric, 0::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  step size cannot be NaN
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series(-100::numeric, 100::numeric, 'nan'::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  start value cannot be NaN
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series('nan'::numeric, 100::numeric, 10::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  stop value cannot be NaN
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, 'nan'::numeric, 10::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  start value cannot be infinity
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series('inf'::numeric, 'inf'::numeric, 10::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  stop value cannot be infinity
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, 'inf'::numeric, 10::numeric);
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric ERROR:  step size cannot be infinity
2025-02-01 03:24:45.762 UTC client backend[25513] pg_regress/numeric STATEMENT:  select * from generate_series(0::numeric, '42'::numeric, '-inf'::numeric);
2025-02-01 03:24:45.763 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.763 UTC client backend[25513] pg_regress/numeric STATEMENT:  select ln(-12.34);
2025-02-01 03:24:45.763 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.763 UTC client backend[25513] pg_regress/numeric STATEMENT:  select ln(0.0);
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric CONTEXT:  SQL function "log" statement 1
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(-12.34);
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric CONTEXT:  SQL function "log" statement 1
2025-02-01 03:24:45.765 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(0.0);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(-12.34, 56.78);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(-12.34, -56.78);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of a negative number
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(12.34, -56.78);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(0.0, 12.34);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  cannot take logarithm of zero
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(12.34, 0.0);
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric ERROR:  division by zero
2025-02-01 03:24:45.767 UTC client backend[25513] pg_regress/numeric STATEMENT:  select log(1.0, 12.34);
2025-02-01 03:24:45.839 UTC client backend[25513] pg_regress/numeric LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp25513.0", size 1400000
2025-02-01 03:24:45.839 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT SUM(9999::numeric) FROM generate_series(1, 100000);
2025-02-01 03:24:45.902 UTC client backend[25513] pg_regress/numeric LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp25513.1", size 1400000
2025-02-01 03:24:45.902 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT SUM((-9999)::numeric) FROM generate_series(1, 100000);
2025-02-01 03:24:46.089 UTC client backend[25513] pg_regress/numeric ERROR:  value overflows numeric format
2025-02-01 03:24:46.089 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT lcm(9999 * (10::numeric)^131068 + (10::numeric^131068 - 1), 2);
2025-02-01 03:24:46.092 UTC client backend[25513] pg_regress/numeric ERROR:  value overflows numeric format
2025-02-01 03:24:46.092 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT factorial(100000);
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric ERROR:  factorial of a negative number is undefined
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT factorial(-4);
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric ERROR:  pg_lsn out of range
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT pg_lsn(-1::numeric);
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric ERROR:  pg_lsn out of range
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT pg_lsn(18446744073709551616::numeric);
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric ERROR:  cannot convert NaN to pg_lsn
2025-02-01 03:24:46.093 UTC client backend[25513] pg_regress/numeric STATEMENT:  SELECT pg_lsn('NaN'::numeric);
2025-02-01 03:24:46.153 UTC client backend[25489] pg_regress/rangetypes ERROR:  conflicting key value violates exclusion constraint "test_range_excl_room_during_excl"
2025-02-01 03:24:46.153 UTC client backend[25489] 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-02-01 03:24:46.153 UTC client backend[25489] 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-02-01 03:24:46.153 UTC client backend[25489] pg_regress/rangetypes ERROR:  conflicting key value violates exclusion constraint "test_range_excl_speaker_during_excl"
2025-02-01 03:24:46.153 UTC client backend[25489] 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-02-01 03:24:46.153 UTC client backend[25489] 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-02-01 03:24:46.156 UTC client backend[25489] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2025-02-01 03:24:46.156 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '[2010-01-01 01:00:00 -08, 2010-01-01 02:00:00 -05)'::tstzrange;
2025-02-01 03:24:46.156 UTC client backend[25489] pg_regress/rangetypes ERROR:  function float4mi(double precision, double precision) does not exist
2025-02-01 03:24:46.156 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create type bogus_float8range as range (subtype=float8, subtype_diff=float4mi);
2025-02-01 03:24:46.167 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot drop type mydomain because other objects depend on it
2025-02-01 03:24:46.167 UTC client backend[25489] pg_regress/rangetypes DETAIL:  type mydomainrange depends on type mydomain
2025-02-01 03:24:46.167 UTC client backend[25489] pg_regress/rangetypes HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:46.167 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  drop domain mydomain;
2025-02-01 03:24:46.170 UTC client backend[25489] pg_regress/rangetypes ERROR:  value for domain restrictedrange violates check constraint "restrictedrange_check"
2025-02-01 03:24:46.170 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select '[4,50)'::restrictedrange @> 7;
2025-02-01 03:24:46.178 UTC client backend[25489] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:46.178 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select textrange1('a','Z') @> 'b'::text;
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes ERROR:  function anyarray_anyrange_func(integer[], numrange) does not exist at character 8
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select anyarray_anyrange_func(ARRAY[1,2], numrange(10,20));
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function bogus_func(anyelement)
	  returns anyrange as 'select int4range(1,10)' language sql;
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:46.183 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function bogus_func(int)
	  returns anyrange as 'select int4range(1,10)' language sql;
2025-02-01 03:24:46.188 UTC client backend[25489] pg_regress/rangetypes ERROR:  function rangetypes_sql(numrange, integer[]) does not exist at character 8
2025-02-01 03:24:46.188 UTC client backend[25489] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:46.188 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select rangetypes_sql(numrange(1,10), ARRAY[2,20]);
2025-02-01 03:24:46.189 UTC client backend[25489] pg_regress/rangetypes ERROR:  function anycompatiblearray_anycompatiblerange_func(numeric[], int4range) does not exist at character 8
2025-02-01 03:24:46.189 UTC client backend[25489] pg_regress/rangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:46.189 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select anycompatiblearray_anycompatiblerange_func(ARRAY[1.1,2], int4range(10,20));
2025-02-01 03:24:46.190 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.190 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:24:46.190 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function bogus_func(anycompatible)
	  returns anycompatiblerange as 'select int4range(1,10)' language sql;
2025-02-01 03:24:46.209 UTC client backend[25489] pg_regress/rangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:46.209 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  select arrayrange(ARRAY[2,1], ARRAY[1,2]);
2025-02-01 03:24:46.217 UTC client backend[25489] pg_regress/rangetypes ERROR:  composite type two_ints cannot be made a member of itself
2025-02-01 03:24:46.217 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  alter type two_ints add attribute c two_ints_range;
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function outparam_fail(i anyelement, out r anyrange, out t text)
	  as $$ select '[1,10]', 'foo' $$ language sql;
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function inoutparam_fail(inout i anyelement, out r anyrange)
	  as $$ select $1, '[1,10]' $$ language sql;
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:46.231 UTC client backend[25489] pg_regress/rangetypes STATEMENT:  create function table_fail(i anyelement) returns table(i anyelement, r anyrange)
	  as $$ select $1, '[1,10]' $$ language sql;
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "123    08:00:2b:01:02:03" at character 8
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '123    08:00:2b:01:02:03'::macaddr8;
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03  123" at character 8
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03  123'::macaddr8;
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "123    08:00:2b:01:02:03:04:05" at character 8
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '123    08:00:2b:01:02:03:04:05'::macaddr8;
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05  123" at character 8
2025-02-01 03:24:46.523 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03:04:05  123'::macaddr8;
2025-02-01 03:24:46.524 UTC client backend[25884] pg_regress/inet ERROR:  table "inet_tbl" does not exist
2025-02-01 03:24:46.524 UTC client backend[25884] pg_regress/inet STATEMENT:  DROP TABLE INET_TBL;
2025-02-01 03:24:46.532 UTC client backend[25885] pg_regress/macaddr ERROR:  invalid input syntax for type macaddr: "0800:2b01:0203" at character 37
2025-02-01 03:24:46.532 UTC client backend[25885] pg_regress/macaddr STATEMENT:  INSERT INTO macaddr_data VALUES (8, '0800:2b01:0203');
2025-02-01 03:24:46.532 UTC client backend[25885] pg_regress/macaddr ERROR:  invalid input syntax for type macaddr: "not even close" at character 37
2025-02-01 03:24:46.532 UTC client backend[25885] pg_regress/macaddr STATEMENT:  INSERT INTO macaddr_data VALUES (9, 'not even close');
2025-02-01 03:24:46.532 UTC client backend[25890] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 America/New_York" at character 32
2025-02-01 03:24:46.532 UTC client backend[25890] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York');
2025-02-01 03:24:46.532 UTC client backend[25890] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 m2" at character 32
2025-02-01 03:24:46.532 UTC client backend[25890] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2');
2025-02-01 03:24:46.533 UTC client backend[25880] pg_regress/point ERROR:  invalid input syntax for type point: "asdfasdf" at character 35
2025-02-01 03:24:46.533 UTC client backend[25880] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('asdfasdf');
2025-02-01 03:24:46.533 UTC client backend[25890] pg_regress/timetz ERROR:  invalid input syntax for type time with time zone: "15:36:39 MSK m2" at character 32
2025-02-01 03:24:46.533 UTC client backend[25890] pg_regress/timetz STATEMENT:  INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2');
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "123abc" at character 8
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 123abc;
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0x0o" at character 8
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0x0o;
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.a" at character 8
2025-02-01 03:24:46.533 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0.a;
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0a" at character 8
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0.0a;
2025-02-01 03:24:46.534 UTC client backend[25880] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0 10.0)" at character 35
2025-02-01 03:24:46.534 UTC client backend[25880] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0 10.0)');
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near ".0a" at character 8
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT .0a;
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e1a" at character 8
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0.0e1a;
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e" at character 8
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0.0e;
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0.0e+" at character 8
2025-02-01 03:24:46.534 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0.0e+a;
2025-02-01 03:24:46.534 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "1997-02-29" at character 30
2025-02-01 03:24:46.534 UTC client backend[25893] pg_regress/date STATEMENT:  INSERT INTO DATE_TBL VALUES ('1997-02-29');
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after parameter at or near "$1a" at character 22
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  PREPARE p1 AS SELECT $1a;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  parameter number too large at or near "$2147483648" at character 22
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  PREPARE p1 AS SELECT $2147483648;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  invalid binary integer at or near "0b" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0b;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1b" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1b;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0b0x" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0b0x;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  invalid octal integer at or near "0o" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0o;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1o" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1o;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0o0x" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0o0x;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  invalid hexadecimal integer at or near "0x" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0x;
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1x" at character 8
2025-02-01 03:24:46.535 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1x;
2025-02-01 03:24:46.537 UTC client backend[25877] pg_regress/time ERROR:  invalid input syntax for type time: "15:36:39 America/New_York" at character 30
2025-02-01 03:24:46.537 UTC client backend[25877] pg_regress/time STATEMENT:  INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York');
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz ERROR:  date/time field value out of range: "24:00:00.01 PDT" at character 8
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT '24:00:00.01 PDT'::timetz;
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz ERROR:  date/time field value out of range: "23:59:60.01 PDT" at character 8
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT '23:59:60.01 PDT'::timetz;
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz ERROR:  date/time field value out of range: "24:01:00 PDT" at character 8
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT '24:01:00 PDT'::timetz;
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz ERROR:  date/time field value out of range: "25:00:00 PDT" at character 8
2025-02-01 03:24:46.538 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT '25:00:00 PDT'::timetz;
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time ERROR:  date/time field value out of range: "24:00:00.01" at character 8
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT '24:00:00.01'::time;
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time ERROR:  date/time field value out of range: "23:59:60.01" at character 8
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT '23:59:60.01'::time;
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time ERROR:  date/time field value out of range: "24:01:00" at character 8
2025-02-01 03:24:46.538 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT '24:01:00'::time;
2025-02-01 03:24:46.539 UTC client backend[25877] pg_regress/time ERROR:  date/time field value out of range: "25:00:00" at character 8
2025-02-01 03:24:46.539 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT '25:00:00'::time;
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0, 10.0) x" at character 35
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 10.0) x');
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point ERROR:  invalid input syntax for type point: "(10.0,10.0" at character 35
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0,10.0');
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point ERROR:  "1e+500" is out of range for type double precision at character 35
2025-02-01 03:24:46.539 UTC client backend[25880] pg_regress/point STATEMENT:  INSERT INTO POINT_TBL(f1) VALUES ('(10.0, 1e+500)');
2025-02-01 03:24:46.541 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "0x0y" at character 8
2025-02-01 03:24:46.541 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 0x0y;
2025-02-01 03:24:46.542 UTC client backend[25890] pg_regress/timetz ERROR:  operator does not exist: time with time zone + time with time zone at character 11
2025-02-01 03:24:46.542 UTC client backend[25890] pg_regress/timetz HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:46.542 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT f1 + time with time zone '00:01' AS "Illegal" FROM TIMETZ_TBL;
2025-02-01 03:24:46.542 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "1/8/1999" at character 13
2025-02-01 03:24:46.542 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.542 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1/8/1999';
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "1/18/1999" at character 13
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1/18/1999';
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "18/1/1999" at character 13
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.543 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '18/1/1999';
2025-02-01 03:24:46.543 UTC client backend[25877] pg_regress/time ERROR:  operator is not unique: time without time zone + time without time zone at character 11
2025-02-01 03:24:46.543 UTC client backend[25877] pg_regress/time HINT:  Could not choose a best candidate operator. You might need to add explicit type casts.
2025-02-01 03:24:46.543 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL;
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01:02:03:04:05:06:07" at character 8
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01:02:03:04:05:06:07'::macaddr8;
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box ERROR:  invalid input syntax for type box: "(2.3, 4.5)" at character 34
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(2.3, 4.5)');
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08-00-2b-01-02-03-04-05-06-07" at character 8
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08-00-2b-01-02-03-04-05-06-07'::macaddr8;
2025-02-01 03:24:46.543 UTC client backend[25894] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "0.0" at character 37
2025-02-01 03:24:46.543 UTC client backend[25894] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('0.0');
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box ERROR:  invalid input syntax for type box: "[1, 2, 3, 4)" at character 34
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('[1, 2, 3, 4)');
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b:01020304050607" at character 8
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08002b:01020304050607'::macaddr8;
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b01020304050607" at character 8
2025-02-01 03:24:46.543 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08002b01020304050607'::macaddr8;
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box ERROR:  invalid input syntax for type box: "(1, 2, 3, 4]" at character 34
2025-02-01 03:24:46.543 UTC client backend[25891] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4]');
2025-02-01 03:24:46.543 UTC client backend[25887] pg_regress/strings ERROR:  syntax error at or near "' - third line'" at character 75
2025-02-01 03:24:46.543 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT 'first line'
	' - next line' /* this comment is not allowed here */
	' - third line'
		AS "Illegal comment within continuation";
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0.0 0.0" at character 37
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0.0 0.0');
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0,1,2)" at character 37
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2)');
2025-02-01 03:24:46.544 UTC client backend[25891] pg_regress/box ERROR:  invalid input syntax for type box: "(1, 2, 3, 4) x" at character 34
2025-02-01 03:24:46.544 UTC client backend[25891] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('(1, 2, 3, 4) x');
2025-02-01 03:24:46.544 UTC client backend[25891] pg_regress/box ERROR:  invalid input syntax for type box: "asdfasdf(ad" at character 34
2025-02-01 03:24:46.544 UTC client backend[25891] pg_regress/box STATEMENT:  INSERT INTO BOX_TBL (f1) VALUES ('asdfasdf(ad');
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "(0,1,2,3" at character 37
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('(0,1,2,3');
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape at character 18
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings HINT:  Unicode escapes must be \XXXX or \+XXXXXX.
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \061';
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon ERROR:  invalid input syntax for type polygon: "asdf" at character 37
2025-02-01 03:24:46.544 UTC client backend[25894] pg_regress/polygon STATEMENT:  INSERT INTO POLYGON_TBL(f1) VALUES ('asdf');
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape at character 18
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings HINT:  Unicode escapes must be \XXXX or \+XXXXXX.
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+0061';
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  UESCAPE must be followed by a simple string literal at or near "+" at character 33
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE +;
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape character at or near "'+'" at character 33
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE '+';
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99';
2025-02-01 03:24:46.544 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "0z002b0102030405" at character 8
2025-02-01 03:24:46.544 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '0z002b0102030405'::macaddr8;
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99xy';
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2025-02-01 03:24:46.544 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99\\';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 23
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \db99\0061';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at character 26
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+00db99\+000061';
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "January 8, 99 BC" at character 13
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date 'January 8, 99 BC';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape value at character 18
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+2FFFFF';
2025-02-01 03:24:46.545 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08002b010203xyza" at character 8
2025-02-01 03:24:46.545 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08002b010203xyza'::macaddr8;
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape at character 17
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings HINT:  Unicode escapes must be \uXXXX or \UXXXXXXXX.
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \u061';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape at character 17
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings HINT:  Unicode escapes must be \uXXXX or \UXXXXXXXX.
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \U0061';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "'" at character 23
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "x" at character 23
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99xy';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\" at character 23
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99\\';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\u0061" at character 23
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \udb99\u0061';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair at or near "\U00000061" at character 27
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \U0000db99\U00000061';
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape value at or near "\U002FFFFF" at character 17
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'wrong: \U002FFFFF';
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08-Jan-99" at character 13
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.545 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08-Jan-99';
2025-02-01 03:24:46.545 UTC client backend[25890] pg_regress/timetz ERROR:  unit "day" not supported for type time with time zone
2025-02-01 03:24:46.545 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT EXTRACT(DAY         FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04');
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.545 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'d\0061t\+000061' AS U&"d\0061t\+000061";
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'d!0061t\+000061' UESCAPE '!' AS U&"d*0061t\+000061" UESCAPE '*';
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&' \' UESCAPE '!' AS "tricky";
2025-02-01 03:24:46.546 UTC client backend[25890] pg_regress/timetz ERROR:  unit "fortnight" not recognized for type time with time zone
2025-02-01 03:24:46.546 UTC client backend[25890] pg_regress/timetz STATEMENT:  SELECT EXTRACT(FORTNIGHT   FROM TIME WITH TIME ZONE '2020-05-26 13:30:25.575401-04');
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "Jan-08-99" at character 13
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date 'Jan-08-99';
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \061';
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: \+0061';
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  unsafe use of string constant with Unicode escapes at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings DETAIL:  String constants with Unicode escapes cannot be used when "standard_conforming_strings" is off.
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT U&'wrong: +0061' UESCAPE '+';
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2025-02-01 03:24:46.546 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8
2025-02-01 03:24:46.546 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00-2b:01:02:03:04:05'::macaddr8;
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2025-02-01 03:24:46.546 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2025-02-01 03:24:46.546 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00-2b:01:02:03:04:05" at character 8
2025-02-01 03:24:46.546 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00-2b:01:02:03:04:05'::macaddr8;
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  invalid hexadecimal data: odd number of digits at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'\\xDeAdBeE'::bytea;
2025-02-01 03:24:46.546 UTC client backend[25883] pg_regress/numerology ERROR:  column "_100" does not exist at character 8
2025-02-01 03:24:46.546 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT _100;
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings ERROR:  invalid hexadecimal digit: "x" at character 8
2025-02-01 03:24:46.546 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'\\xDeAdBeEx'::bytea;
2025-02-01 03:24:46.546 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "100_" at character 8
2025-02-01 03:24:46.546 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 100_;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "100__000" at character 8
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 100__000;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  syntax error at or near ".5" at character 14
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT _1_000.5;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000_" at character 8
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1_000_.5;
2025-02-01 03:24:46.547 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8
2025-02-01 03:24:46.547 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01.02:03:04:05'::macaddr8;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000._5" at character 8
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1_000._5;
2025-02-01 03:24:46.547 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "08:00:2b:01.02:03:04:05" at character 8
2025-02-01 03:24:46.547 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  SELECT '08:00:2b:01.02:03:04:05'::macaddr8;
2025-02-01 03:24:46.547 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08 Jan 99" at character 13
2025-02-01 03:24:46.547 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.547 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08 Jan 99';
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000.5_" at character 8
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1_000.5_;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after numeric literal at or near "1_000.5e_1" at character 8
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  SELECT 1_000.5e_1;
2025-02-01 03:24:46.547 UTC client backend[25887] pg_regress/strings ERROR:  invalid input syntax for type bytea at character 8
2025-02-01 03:24:46.547 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT E'De\\678dBeEf'::bytea;
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology ERROR:  trailing junk after parameter at or near "$0_1" at character 22
2025-02-01 03:24:46.547 UTC client backend[25883] pg_regress/numerology STATEMENT:  PREPARE p1 AS SELECT $0_1;
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "Jan 08 99" at character 13
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date 'Jan 08 99';
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08-01-99" at character 13
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.548 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08-01-99';
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08-01-1999" at character 13
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08-01-1999';
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "01-08-99" at character 13
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '01-08-99';
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "01-08-1999" at character 13
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.549 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '01-08-1999';
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08 01 99" at character 13
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08 01 99';
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "08 01 1999" at character 13
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '08 01 1999';
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "01 08 99" at character 13
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '01 08 99';
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "01 08 1999" at character 13
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.550 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '01 08 1999';
2025-02-01 03:24:46.556 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "1/18/1999" at character 13
2025-02-01 03:24:46.556 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.556 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1/18/1999';
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "{}" at character 30
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{}');
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "{0" at character 30
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0');
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet ERROR:  invalid cidr value: "192.168.1.2/30" at character 37
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226');
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(-100,0),-100>" at character 32
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(-100,0),-100>');
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0}" at character 30
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0}');
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(100,200),10" at character 32
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10');
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet ERROR:  invalid input syntax for type cidr: "1234::1234::1234" at character 37
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4');
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle ERROR:  invalid input syntax for type circle: "<(100,200),10> x" at character 32
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('<(100,200),10> x');
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0,1" at character 30
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1');
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle ERROR:  invalid input syntax for type circle: "1abc,3,5" at character 32
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('1abc,3,5');
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle ERROR:  invalid input syntax for type circle: "(3,(1,2),3)" at character 32
2025-02-01 03:24:46.557 UTC client backend[25886] pg_regress/circle STATEMENT:  INSERT INTO CIRCLE_TBL VALUES ('(3,(1,2),3)');
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet ERROR:  invalid cidr value: "192.168.1.2/30" at character 42
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2025-02-01 03:24:46.557 UTC client backend[25884] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226');
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line ERROR:  invalid line specification: A and B cannot both be zero at character 30
2025-02-01 03:24:46.557 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1}');
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "{0,0,1} x" at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('{0,0,1} x');
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "(3asdf,2 ,3,4r2)" at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('(3asdf,2 ,3,4r2)');
2025-02-01 03:24:46.558 UTC client backend[25884] pg_regress/inet ERROR:  invalid cidr value: "ffff:ffff:ffff:ffff::/24" at character 42
2025-02-01 03:24:46.558 UTC client backend[25884] pg_regress/inet DETAIL:  Value has bits set to right of mask.
2025-02-01 03:24:46.558 UTC client backend[25884] pg_regress/inet STATEMENT:  INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226');
2025-02-01 03:24:46.558 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-Jan-08" at character 13
2025-02-01 03:24:46.558 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.558 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-Jan-08';
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "[1,2,3, 4" at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[1,2,3, 4');
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "[(,2),(3,4)]" at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(,2),(3,4)]');
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid input syntax for type line: "[(1,2),(3,4)" at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(1,2),(3,4)');
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line ERROR:  invalid line specification: must be two distinct points at character 30
2025-02-01 03:24:46.558 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES ('[(1,2),(1,2)]');
2025-02-01 03:24:46.559 UTC client backend[25878] pg_regress/line ERROR:  invalid line specification: must be two distinct points
2025-02-01 03:24:46.559 UTC client backend[25878] pg_regress/line STATEMENT:  INSERT INTO LINE_TBL VALUES (line(point '(1,0)', point '(1,0)'));
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99 Jan 08" at character 13
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.559 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 Jan 08';
2025-02-01 03:24:46.561 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99 08 Jan" at character 13
2025-02-01 03:24:46.561 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 08 Jan';
2025-02-01 03:24:46.561 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-01-08" at character 13
2025-02-01 03:24:46.561 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.561 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-01-08';
2025-02-01 03:24:46.565 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-08-01" at character 13
2025-02-01 03:24:46.565 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.565 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-08-01';
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99 01 08" at character 13
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 01 08';
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99 08 01" at character 13
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.566 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 08 01';
2025-02-01 03:24:46.567 UTC client backend[25877] pg_regress/time ERROR:  unit "day" not supported for type time without time zone
2025-02-01 03:24:46.567 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT EXTRACT(DAY         FROM TIME '2020-05-26 13:30:25.575401');
2025-02-01 03:24:46.567 UTC client backend[25877] pg_regress/time ERROR:  unit "fortnight" not recognized for type time without time zone
2025-02-01 03:24:46.567 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT EXTRACT(FORTNIGHT   FROM TIME '2020-05-26 13:30:25.575401');
2025-02-01 03:24:46.568 UTC client backend[25877] pg_regress/time ERROR:  unit "timezone" not supported for type time without time zone
2025-02-01 03:24:46.568 UTC client backend[25877] pg_regress/time STATEMENT:  SELECT EXTRACT(TIMEZONE    FROM TIME '2020-05-26 13:30:25.575401');
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "(3asdf,2 ,3,4r2)" at character 30
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('(3asdf,2 ,3,4r2)');
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[1,2,3, 4" at character 30
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[1,2,3, 4');
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[(,2),(3,4)]" at character 30
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[(,2),(3,4)]');
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg ERROR:  invalid input syntax for type lseg: "[(1,2),(3,4)" at character 30
2025-02-01 03:24:46.572 UTC client backend[25892] pg_regress/lseg STATEMENT:  INSERT INTO LSEG_TBL VALUES ('[(1,2),(3,4)');
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path ERROR:  invalid input syntax for type path: "[]" at character 30
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[]');
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path ERROR:  invalid input syntax for type path: "[(,2),(3,4)]" at character 30
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[(,2),(3,4)]');
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path ERROR:  invalid input syntax for type path: "[(1,2),(3,4)" at character 30
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('[(1,2),(3,4)');
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path ERROR:  invalid input syntax for type path: "(1,2,3,4" at character 30
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('(1,2,3,4');
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path ERROR:  invalid input syntax for type path: "(1,2),(3,4)]" at character 30
2025-02-01 03:24:46.574 UTC client backend[25881] pg_regress/path STATEMENT:  INSERT INTO PATH_TBL VALUES ('(1,2),(3,4)]');
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "18/1/1999" at character 13
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '18/1/1999';
2025-02-01 03:24:46.580 UTC client backend[25889] pg_regress/macaddr8 ERROR:  invalid input syntax for type macaddr8: "not even close" at character 38
2025-02-01 03:24:46.580 UTC client backend[25889] pg_regress/macaddr8 STATEMENT:  INSERT INTO macaddr8_data VALUES (9, 'not even close');
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-Jan-08" at character 13
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.580 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-Jan-08';
2025-02-01 03:24:46.581 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99-08-Jan" at character 13
2025-02-01 03:24:46.581 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-08-Jan';
2025-02-01 03:24:46.585 UTC client backend[25887] pg_regress/strings ERROR:  negative substring length not allowed
2025-02-01 03:24:46.585 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT SUBSTRING('string' FROM -10 FOR -2147483646) AS "error";
2025-02-01 03:24:46.592 UTC client backend[25887] pg_regress/strings ERROR:  SQL regular expression may not contain more than two escape-double-quote separators
2025-02-01 03:24:46.592 UTC client backend[25887] pg_regress/strings CONTEXT:  SQL function "substring" statement 1
2025-02-01 03:24:46.592 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT SUBSTRING('abcdefg' SIMILAR 'a*#"%#"g*#"x' ESCAPE '#') AS "error";
2025-02-01 03:24:46.592 UTC client backend[25884] pg_regress/inet ERROR:  invalid mask length: 33
2025-02-01 03:24:46.592 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT set_masklen(inet(text(i)), 33) FROM INET_TBL;
2025-02-01 03:24:46.593 UTC client backend[25884] pg_regress/inet ERROR:  invalid mask length: 33
2025-02-01 03:24:46.593 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT set_masklen(cidr(text(c)), 33) FROM INET_TBL;
2025-02-01 03:24:46.599 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "1999-08-Jan" at character 13
2025-02-01 03:24:46.599 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '1999-08-Jan';
2025-02-01 03:24:46.599 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99 Jan 08" at character 13
2025-02-01 03:24:46.599 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 Jan 08';
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date ERROR:  invalid input syntax for type date: "99 08 Jan" at character 13
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 08 Jan';
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-01-08" at character 13
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-01-08';
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99-08-01" at character 13
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.600 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99-08-01';
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99 01 08" at character 13
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 01 08';
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date ERROR:  date/time field value out of range: "99 08 01" at character 13
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:46.601 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '99 08 01';
2025-02-01 03:24:46.602 UTC client backend[25893] pg_regress/date ERROR:  date out of range: "4714-11-23 BC" at character 13
2025-02-01 03:24:46.602 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '4714-11-23 BC';
2025-02-01 03:24:46.602 UTC client backend[25887] pg_regress/strings ERROR:  invalid escape string
2025-02-01 03:24:46.602 UTC client backend[25887] pg_regress/strings HINT:  Escape string must be empty or one character.
2025-02-01 03:24:46.602 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT 'abcdefg' SIMILAR TO '_bcd#%' ESCAPE '##' AS error;
2025-02-01 03:24:46.602 UTC client backend[25893] pg_regress/date ERROR:  date out of range: "5874898-01-01" at character 13
2025-02-01 03:24:46.602 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT date '5874898-01-01';
2025-02-01 03:24:46.604 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "badly formatted interval" at character 39
2025-02-01 03:24:46.604 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL (f1) VALUES ('badly formatted interval');
2025-02-01 03:24:46.604 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "@ 30 eons ago" at character 39
2025-02-01 03:24:46.604 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL (f1) VALUES ('@ 30 eons ago');
2025-02-01 03:24:46.605 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "" at character 8
2025-02-01 03:24:46.605 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Missing left brace.
2025-02-01 03:24:46.605 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select ''::textmultirange;
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{,}" at character 8
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected range start.
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{,}'::textmultirange;
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(,)}." at character 8
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Junk after closing right brace.
2025-02-01 03:24:46.606 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(,)}.'::textmultirange;
2025-02-01 03:24:46.607 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression option: "z"
2025-02-01 03:24:46.607 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_replace('AAA aaa', 'A+', 'Z', 'z');
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{[a,c),}" at character 8
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected range start.
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{[a,c),}'::textmultirange;
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{,[a,c)}" at character 8
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected range start.
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{,[a,c)}'::textmultirange;
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{-[a,z)}" at character 8
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected range start.
2025-02-01 03:24:46.607 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{-[a,z)}'::textmultirange;
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{[a,z) - }" at character 8
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{[a,z) - }'::textmultirange;
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(",a)}" at character 8
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Unexpected end of input.
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(",a)}'::textmultirange;
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed range literal: "(,,a)" at character 8
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Too many commas.
2025-02-01 03:24:46.608 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(,,a)}'::textmultirange;
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed range literal: "()" at character 8
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Missing comma after lower bound.
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(),a)}'::textmultirange;
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(a,))}" at character 8
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(a,))}'::textmultirange;
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed range literal: "(]" at character 8
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Missing comma after lower bound.
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(],a)}'::textmultirange;
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes ERROR:  malformed multirange literal: "{(a,])}" at character 8
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Expected comma or end of multirange.
2025-02-01 03:24:46.609 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{(a,])}'::textmultirange;
2025-02-01 03:24:46.610 UTC client backend[25897] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound at character 8
2025-02-01 03:24:46.610 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{[z,a]}'::textmultirange;
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "start": -1
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', -1, 0, 'i');
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "n": -1
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', 1, -1, 'i');
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression option: "1"
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings HINT:  If you meant to use regexp_replace() with a start parameter, cast the fourth argument to integer explicitly.
2025-02-01 03:24:46.612 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_replace('A PostgreSQL function', 'a|e|i|o|u', 'X', '1');
2025-02-01 03:24:46.613 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2025-02-01 03:24:46.613 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_count('123123123123', '123', 0);
2025-02-01 03:24:46.613 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "start": -3
2025-02-01 03:24:46.613 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_count('123123123123', '123', -3);
2025-02-01 03:24:46.614 UTC client backend[25887] pg_regress/strings ERROR:  regexp_like() does not support the "global" option
2025-02-01 03:24:46.614 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_like('abc', 'a.c', 'g');
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 0, 1);
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "n": 0
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 0);
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "endoption": -1
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, -1);
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "endoption": 2
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 2);
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings ERROR:  regexp_instr() does not support the "global" option
2025-02-01 03:24:46.631 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, 'g');
2025-02-01 03:24:46.632 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "subexpr": -1
2025-02-01 03:24:46.632 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_instr('abcabcabc', 'a.c', 1, 1, 0, '', -1);
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date ERROR:  unit "microseconds" not supported for type date
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(MICROSECONDS  FROM DATE '2020-08-11');
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date ERROR:  unit "milliseconds" not supported for type date
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(MILLISECONDS  FROM DATE '2020-08-11');
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date ERROR:  unit "second" not supported for type date
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(SECOND        FROM DATE '2020-08-11');
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date ERROR:  unit "minute" not supported for type date
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(MINUTE        FROM DATE '2020-08-11');
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date ERROR:  unit "hour" not supported for type date
2025-02-01 03:24:46.632 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(HOUR          FROM DATE '2020-08-11');
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date ERROR:  unit "timezone" not supported for type date
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE      FROM DATE '2020-08-11');
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date ERROR:  unit "timezone_m" not supported for type date
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE_M    FROM DATE '2020-08-11');
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date ERROR:  unit "timezone_h" not supported for type date
2025-02-01 03:24:46.635 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(TIMEZONE_H    FROM DATE '2020-08-11');
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "start": 0
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 0, 1);
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "n": 0
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 0);
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings ERROR:  regexp_substr() does not support the "global" option
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, 'g');
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings ERROR:  invalid value for parameter "subexpr": -1
2025-02-01 03:24:46.643 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_substr('abcabcabc', 'a.c', 1, 1, '', -1);
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  unit "microsec" not recognized for type date
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT EXTRACT(MICROSEC  FROM DATE 'infinity');
2025-02-01 03:24:46.652 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression option: "z"
2025-02-01 03:24:46.652 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque)$re$, 'gz');
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  date field value out of range: 0-07-15
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  select make_date(0, 7, 15);
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  date field value out of range: 2013-02-30
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  select make_date(2013, 2, 30);
2025-02-01 03:24:46.652 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression: parentheses () not balanced
2025-02-01 03:24:46.652 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(barbeque$re$);
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  date field value out of range: 2013-13-01
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  select make_date(2013, 13, 1);
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  date field value out of range: 2013-11--1
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  select make_date(2013, 11, -1);
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date ERROR:  date field value out of range: -2147483648-01-01
2025-02-01 03:24:46.652 UTC client backend[25893] pg_regress/date STATEMENT:  SELECT make_date(-2147483648, 1, 1);
2025-02-01 03:24:46.653 UTC client backend[25893] pg_regress/date ERROR:  time field value out of range: 10:55:100.1
2025-02-01 03:24:46.653 UTC client backend[25893] pg_regress/date STATEMENT:  select make_time(10, 55, 100.1);
2025-02-01 03:24:46.653 UTC client backend[25893] pg_regress/date ERROR:  time field value out of range: 24:00:2.1
2025-02-01 03:24:46.653 UTC client backend[25893] pg_regress/date STATEMENT:  select make_time(24, 0, 2.1);
2025-02-01 03:24:46.656 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression: invalid repetition count(s)
2025-02-01 03:24:46.656 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_matches('foobarbequebaz', $re$(bar)(beque){2,1}$re$);
2025-02-01 03:24:46.659 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression option: "z"
2025-02-01 03:24:46.659 UTC client backend[25887] 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-02-01 03:24:46.659 UTC client backend[25887] pg_regress/strings ERROR:  invalid regular expression option: "z"
2025-02-01 03:24:46.659 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'iz');
2025-02-01 03:24:46.660 UTC client backend[25887] pg_regress/strings ERROR:  regexp_split_to_table() does not support the "global" option
2025-02-01 03:24:46.660 UTC client backend[25887] 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-02-01 03:24:46.660 UTC client backend[25887] pg_regress/strings ERROR:  regexp_split_to_array() does not support the "global" option
2025-02-01 03:24:46.660 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT regexp_split_to_array('thE QUick bROWn FOx jUMPs ovEr The lazy dOG', 'e', 'g');
2025-02-01 03:24:46.677 UTC client backend[25884] pg_regress/inet ERROR:  result is out of range
2025-02-01 03:24:46.677 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT '127.0.0.1'::inet + 10000000000;
2025-02-01 03:24:46.678 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.678 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT -('-2147483648 months'::interval);
2025-02-01 03:24:46.679 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.679 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT -('-2147483648 days'::interval);
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet ERROR:  result is out of range
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT '127.0.0.1'::inet - 10000000000;
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet ERROR:  result is out of range
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT '126::1'::inet - '127::2'::inet;
2025-02-01 03:24:46.679 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.679 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT -('-9223372036854775808 us'::interval);
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet ERROR:  result is out of range
2025-02-01 03:24:46.679 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT '127::1'::inet - '126::2'::inet;
2025-02-01 03:24:46.683 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.683 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT -('-2147483647 months -2147483647 days -9223372036854775807 us'::interval);
2025-02-01 03:24:46.684 UTC client backend[25884] pg_regress/inet ERROR:  cannot merge addresses from different families
2025-02-01 03:24:46.684 UTC client backend[25884] pg_regress/inet STATEMENT:  SELECT inet_merge(c, i) FROM INET_TBL;
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483648 days" at character 42
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483648 days');
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 days" at character 42
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483649 days');
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range at character 42
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('2147483647 years');
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range at character 42
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval STATEMENT:  INSERT INTO INTERVAL_TBL_OF (f1) VALUES ('-2147483648 years');
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.688 UTC client backend[25888] pg_regress/interval STATEMENT:  select extract(epoch from '256 microseconds'::interval * (2^55)::float8);
2025-02-01 03:24:46.700 UTC client backend[25897] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:46.700 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select nummultirange(numrange(2.0, 1.0));
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '3000000 months'::interval * 1000;
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '3000000 months'::interval / 0.001;
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '3000000 days'::interval * 1000;
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '3000000 days'::interval / 0.001;
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '1 month 2146410 days'::interval * 1000.5002;
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.731 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '4611686018427387904 usec'::interval / 0.1;
2025-02-01 03:24:46.739 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.739 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_hours(interval '2147483647 days 24 hrs');
2025-02-01 03:24:46.739 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.739 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_days(interval '2147483647 months 30 days');
2025-02-01 03:24:46.740 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.740 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '2147483647 months 30 days');
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '-2147483648 months -30 days');
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '2147483647 months -30 days 1440 hrs');
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.741 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT justify_interval(interval '-2147483648 months 30 days -1440 hrs');
2025-02-01 03:24:46.742 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 second 2 seconds" at character 8
2025-02-01 03:24:46.742 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '1 second 2 seconds'::interval;
2025-02-01 03:24:46.742 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "10 milliseconds 20 milliseconds" at character 8
2025-02-01 03:24:46.742 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '10 milliseconds 20 milliseconds'::interval;
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "5.5 seconds 3 milliseconds" at character 8
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '5.5 seconds 3 milliseconds'::interval;
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1:20:05 5 microseconds" at character 8
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '1:20:05 5 microseconds'::interval;
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 day 1 day" at character 8
2025-02-01 03:24:46.743 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '1 day 1 day'::interval;
2025-02-01 03:24:46.747 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2025-02-01 03:24:46.747 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2' day to minute;
2025-02-01 03:24:46.751 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2025-02-01 03:24:46.751 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2' day to second;
2025-02-01 03:24:46.759 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2025-02-01 03:24:46.759 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2' hour to minute;
2025-02-01 03:24:46.759 UTC client backend[25887] pg_regress/strings ERROR:  negative substring length not allowed
2025-02-01 03:24:46.759 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT substr(f1, 5, -1) from toasttest;
2025-02-01 03:24:46.759 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2025-02-01 03:24:46.759 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2' hour to second;
2025-02-01 03:24:46.764 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2" at character 17
2025-02-01 03:24:46.764 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2' minute to second;
2025-02-01 03:24:46.765 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 11" at character 17
2025-02-01 03:24:46.765 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '123 11' day;
2025-02-01 03:24:46.765 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 11" at character 17
2025-02-01 03:24:46.765 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '123 11';
2025-02-01 03:24:46.767 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "123 2:03 -2:04" at character 17
2025-02-01 03:24:46.767 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '123 2:03 -2:04';
2025-02-01 03:24:46.768 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.345" at character 17
2025-02-01 03:24:46.768 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2.345' day to second(2);
2025-02-01 03:24:46.768 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.345" at character 17
2025-02-01 03:24:46.768 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2.345' hour to second(2);
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 2.3456" at character 17
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '1 2.3456' minute to second(2);
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range at character 17
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '2562047788:00:54.775807' second(2);
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range at character 17
2025-02-01 03:24:46.769 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-2562047788:00:54.775807' second(2);
2025-02-01 03:24:46.771 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "" at character 18
2025-02-01 03:24:46.771 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT  interval '';
2025-02-01 03:24:46.776 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "P.Y0M3DT4H5M6S" at character 17
2025-02-01 03:24:46.776 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P.Y0M3DT4H5M6S';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483648 years" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483648 years';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 years" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483649 years';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483648 months" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483648 months';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 months" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483649 months';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483648 days" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483648 days';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483649 days" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483649 days';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2562047789 hours" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2562047789 hours';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2562047789 hours" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2562047789 hours';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "153722867281 minutes" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '153722867281 minutes';
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-153722867281 minutes" at character 17
2025-02-01 03:24:46.782 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-153722867281 minutes';
2025-02-01 03:24:46.784 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036855 seconds" at character 17
2025-02-01 03:24:46.784 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036855 seconds';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036855 seconds" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036855 seconds';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036854777 millisecond" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036854777 millisecond';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854777 millisecond" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854777 millisecond';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775808 microsecond" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036854775808 microsecond';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775809 microsecond" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854775809 microsecond';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P2147483648" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P2147483648';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-2147483649" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-2147483649';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P1-2147483647-2147483647';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT2562047789" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT2562047789';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047789" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT-2562047789';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 weeks" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 weeks';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 weeks" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 weeks';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 decades" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 decades';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 decades" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 decades';
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 centuries" at character 17
2025-02-01 03:24:46.785 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 centuries';
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 centuries" at character 17
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 centuries';
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 millennium" at character 17
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 millennium';
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 millennium" at character 17
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 millennium';
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "1 week 2147483647 days" at character 17
2025-02-01 03:24:46.786 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '1 week 2147483647 days';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-1 week -2147483648 days" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-1 week -2147483648 days';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 1 week" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 days 1 week';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -1 week" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 days -1 week';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P1W2147483647D" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P1W2147483647D';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-1W-2147483648D" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-1W-2147483648D';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D1W" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P2147483647D1W';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-1W" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-1W';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "1 decade 2147483647 years" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '1 decade 2147483647 years';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "1 century 2147483647 years" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '1 century 2147483647 years';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "1 millennium 2147483647 years" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '1 millennium 2147483647 years';
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-1 decade -2147483648 years" at character 17
2025-02-01 03:24:46.787 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-1 decade -2147483648 years';
2025-02-01 03:24:46.788 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-1 century -2147483648 years" at character 17
2025-02-01 03:24:46.788 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-1 century -2147483648 years';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-1 millennium -2147483648 years" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-1 millennium -2147483648 years';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 decade" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 decade';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 century" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 century';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 years 1 millennium" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 years 1 millennium';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 decade" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 decade';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 century" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 century';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 years -1 millennium" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 years -1 millennium';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 millennium 2147483647 months" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 millennium 2147483647 months';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 centuries 2147483647 months" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 centuries 2147483647 months';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 decades 2147483647 months" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 decades 2147483647 months';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 yrs 2147483647 months" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 yrs 2147483647 months';
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 millennium -2147483648 months" at character 17
2025-02-01 03:24:46.790 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 millennium -2147483648 months';
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 centuries -2147483648 months" at character 17
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 centuries -2147483648 months';
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 decades -2147483648 months" at character 17
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 decades -2147483648 months';
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 yrs -2147483648 months" at character 17
2025-02-01 03:24:46.791 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 yrs -2147483648 months';
2025-02-01 03:24:46.793 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 millennium" at character 17
2025-02-01 03:24:46.793 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 millennium';
2025-02-01 03:24:46.793 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 centuries" at character 17
2025-02-01 03:24:46.793 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 centuries';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 decades" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 decades';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 months 0.1 yrs" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 months 0.1 yrs';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 millennium" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 millennium';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 centuries" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 centuries';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 decades" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 decades';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -0.1 yrs" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months -0.1 yrs';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 months 2147483647 days" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 months 2147483647 days';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 months -2147483648 days" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 months -2147483648 days';
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 0.1 months" at character 17
2025-02-01 03:24:46.795 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 days 0.1 months';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -0.1 months" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 days -0.1 months';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.5 weeks 2147483647 days" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.5 weeks 2147483647 days';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.5 weeks -2147483648 days" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.5 weeks -2147483648 days';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2147483647 days 0.5 weeks" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2147483647 days 0.5 weeks';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days -0.5 weeks" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 days -0.5 weeks';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.01 months 9223372036854775807 microseconds" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.01 months 9223372036854775807 microseconds';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.01 months -9223372036854775808 microseconds" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.01 months -9223372036854775808 microseconds';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.01 months" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.01 months';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.01 months" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.01 months';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 weeks 9223372036854775807 microseconds" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 weeks 9223372036854775807 microseconds';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 weeks -9223372036854775808 microseconds" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 weeks -9223372036854775808 microseconds';
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.1 weeks" at character 17
2025-02-01 03:24:46.796 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.1 weeks';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.1 weeks" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.1 weeks';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 days 9223372036854775807 microseconds" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 days 9223372036854775807 microseconds';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-0.1 days -9223372036854775808 microseconds" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-0.1 days -9223372036854775808 microseconds';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "9223372036854775807 microseconds 0.1 days" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '9223372036854775807 microseconds 0.1 days';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds -0.1 days" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds -0.1 days';
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.1Y2147483647M" at character 17
2025-02-01 03:24:46.797 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.1Y2147483647M';
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-0.1Y-2147483648M" at character 17
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-0.1Y-2147483648M';
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P2147483647M0.1Y" at character 17
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P2147483647M0.1Y';
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648M-0.1Y" at character 17
2025-02-01 03:24:46.798 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-2147483648M-0.1Y';
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.1M2147483647D" at character 17
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.1M2147483647D';
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-0.1M-2147483648D" at character 17
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-0.1M-2147483648D';
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D0.1M" at character 17
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P2147483647D0.1M';
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-0.1M" at character 17
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-0.1M';
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.5W2147483647D" at character 17
2025-02-01 03:24:46.800 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.5W2147483647D';
2025-02-01 03:24:46.801 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-0.5W-2147483648D" at character 17
2025-02-01 03:24:46.801 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-0.5W-2147483648D';
2025-02-01 03:24:46.801 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P2147483647D0.5W" at character 17
2025-02-01 03:24:46.801 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P2147483647D0.5W';
2025-02-01 03:24:46.802 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-2147483648D-0.5W" at character 17
2025-02-01 03:24:46.802 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-2147483648D-0.5W';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.01MT2562047788H54.775807S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.01MT2562047788H54.775807S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-0.01MT-2562047788H-54.775808S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-0.01MT-2562047788H-54.775808S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.1DT2562047788H54.775807S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.1DT2562047788H54.775807S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P-0.1DT-2562047788H-54.775808S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P-0.1DT-2562047788H-54.775808S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788.1H54.775807S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT2562047788.1H54.775807S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047788.1H-54.775808S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT-2562047788.1H-54.775808S';
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788H0.1M54.775807S" at character 17
2025-02-01 03:24:46.803 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT2562047788H0.1M54.775807S';
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT-2562047788H-0.1M-54.775808S" at character 17
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT-2562047788H-0.1M-54.775808S';
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P0.1-2147483647-00" at character 17
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P0.1-2147483647-00';
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P00-0.1-2147483647" at character 17
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P00-0.1-2147483647';
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P00-0.01-00T2562047788:00:54.775807" at character 17
2025-02-01 03:24:46.804 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P00-0.01-00T2562047788:00:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "P00-00-0.1T2562047788:00:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'P00-00-0.1T2562047788:00:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788.1:00:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT2562047788.1:00:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "PT2562047788:01.:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval 'PT2562047788:01.:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 2562047788:0:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 2562047788:0:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "0.1 2562047788:0:54.775808 ago" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '0.1 2562047788:0:54.775808 ago';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2562047788.1:0:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2562047788.1:0:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "2562047788.1:0:54.775808 ago" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2562047788.1:0:54.775808 ago';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "2562047788:0.1:54.775807" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2562047788:0.1:54.775807';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "2562047788:0.1:54.775808 ago" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '2562047788:0.1:54.775808 ago';
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months ago" at character 17
2025-02-01 03:24:46.805 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months ago';
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 days ago" at character 17
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 days ago';
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-9223372036854775808 microseconds ago" at character 17
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-9223372036854775808 microseconds ago';
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval ERROR:  interval field value out of range: "-2147483648 months -2147483648 days -9223372036854775808 microseconds ago" at character 17
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval STATEMENT:  select interval '-2147483648 months -2147483648 days -9223372036854775808 microseconds ago';
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(years := 178956971);
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.806 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(years := -178956971);
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(years := 1, months := 2147483647);
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(years := -1, months := -2147483648);
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.809 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(weeks := 306783379);
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(weeks := -306783379);
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(weeks := 1, days := 2147483647);
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(weeks := -1, days := -2147483648);
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval ERROR:  value out of range: overflow
2025-02-01 03:24:46.810 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(secs := 1e308);
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(secs := 1e18);
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(secs := -1e18);
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(mins := 1, secs := 9223372036800.0);
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.811 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(mins := -1, secs := -9223372036800.0);
2025-02-01 03:24:46.820 UTC client backend[25888] pg_regress/interval ERROR:  integer out of range
2025-02-01 03:24:46.820 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(years := 'inf'::float::int);
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval ERROR:  integer out of range
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(months := 'NaN'::float::int);
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(secs := 'inf');
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.821 UTC client backend[25888] pg_regress/interval STATEMENT:  select make_interval(secs := 'NaN');
2025-02-01 03:24:46.824 UTC client backend[25888] pg_regress/interval ERROR:  unit "fortnight" not recognized for type interval
2025-02-01 03:24:46.824 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT EXTRACT(FORTNIGHT FROM INTERVAL '2 days');
2025-02-01 03:24:46.836 UTC client backend[25882] pg_regress/timestamp ERROR:  time zone "america/does_not_exist" not recognized at character 35
2025-02-01 03:24:46.836 UTC client backend[25882] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('19970710 173201 America/Does_not_exist');
2025-02-01 03:24:46.839 UTC client backend[25888] pg_regress/interval ERROR:  unit "timezone" not supported for type interval
2025-02-01 03:24:46.839 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT EXTRACT(TIMEZONE FROM INTERVAL '2 days');
2025-02-01 03:24:46.848 UTC client backend[25882] pg_regress/timestamp ERROR:  date/time field value out of range: "Feb 29 17:32:01 1997" at character 35
2025-02-01 03:24:46.848 UTC client backend[25882] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 29 17:32:01 1997');
2025-02-01 03:24:46.854 UTC client backend[25882] pg_regress/timestamp ERROR:  time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 35
2025-02-01 03:24:46.854 UTC client backend[25882] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 -0097');
2025-02-01 03:24:46.865 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 35
2025-02-01 03:24:46.865 UTC client backend[25882] pg_regress/timestamp STATEMENT:  INSERT INTO TIMESTAMP_TBL VALUES ('Feb 16 17:32:01 5097 BC');
2025-02-01 03:24:46.867 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamp out of range: "4714-11-23 23:59:59 BC" at character 8
2025-02-01 03:24:46.867 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT '4714-11-23 23:59:59 BC'::timestamp;
2025-02-01 03:24:46.867 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamp out of range: "294277-01-01 00:00:00" at character 8
2025-02-01 03:24:46.867 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT '294277-01-01 00:00:00'::timestamp;
2025-02-01 03:24:46.873 UTC client backend[25882] pg_regress/timestamp ERROR:  unit "ago" not recognized for type timestamp without time zone
2025-02-01 03:24:46.873 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT date_trunc( 'ago', timestamp 'infinity' ) AS invalid_trunc;
2025-02-01 03:24:46.885 UTC client backend[25896] pg_regress/timestamptz ERROR:  time zone "america/does_not_exist" not recognized at character 37
2025-02-01 03:24:46.885 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('19970710 173201 America/Does_not_exist');
2025-02-01 03:24:46.885 UTC client backend[25896] pg_regress/timestamptz ERROR:  time zone "America/Does_not_exist" not recognized
2025-02-01 03:24:46.885 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT '19970710 173201' AT TIME ZONE 'America/Does_not_exist';
2025-02-01 03:24:46.887 UTC client backend[25896] pg_regress/timestamptz ERROR:  invalid input syntax for type timestamp with time zone: "Jan 01 00:00:00 2024 LMT" at character 8
2025-02-01 03:24:46.887 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT 'Jan 01 00:00:00 2024 LMT'::timestamptz;
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' + interval '1 month 1 day 1 us';
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' + interval '-1 month -1 day -1 us';
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '2147483646 months 2147483646 days 9223372036854775806 us' - interval '-1 month -1 day -1 us';
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.895 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-2147483647 months -2147483647 days -9223372036854775807 us' - interval '1 month 1 day 1 us';
2025-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamps cannot be binned into intervals containing months or years
2025-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT date_bin('5 months'::interval, timestamp '2020-02-01 01:01:01', timestamp '2001-01-01');
2025-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamps cannot be binned into intervals containing months or years
2025-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT date_bin('5 years'::interval,  timestamp '2020-02-01 01:01:01', timestamp '2001-01-01');
2025-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp ERROR:  stride must be greater than zero
2025-02-01 03:24:46.897 UTC client backend[25882] 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-02-01 03:24:46.897 UTC client backend[25882] pg_regress/timestamp ERROR:  stride must be greater than zero
2025-02-01 03:24:46.897 UTC client backend[25882] 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-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select date_bin('15 minutes'::interval, timestamp '294276-12-30', timestamp '4000-12-20 BC');
2025-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select date_bin('200000000 days'::interval, '2024-02-01'::timestamp, '2024-01-01'::timestamp);
2025-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp ERROR:  timestamp out of range
2025-02-01 03:24:46.898 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamp, '4000-01-01 BC'::timestamp);
2025-02-01 03:24:46.905 UTC client backend[25887] pg_regress/strings ERROR:  negative substring length not allowed
2025-02-01 03:24:46.905 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT substr(f1, 5, -1) from toasttest;
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval ERROR:  cannot add infinite interval to time
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT time '11:27:42' + interval 'infinity';
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval ERROR:  cannot add infinite interval to time
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT time '11:27:42' + interval '-infinity';
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2025-02-01 03:24:46.908 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT time '11:27:42' - interval 'infinity';
2025-02-01 03:24:46.911 UTC client backend[25888] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2025-02-01 03:24:46.911 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT time '11:27:42' - interval '-infinity';
2025-02-01 03:24:46.912 UTC client backend[25888] pg_regress/interval ERROR:  cannot add infinite interval to time
2025-02-01 03:24:46.912 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' + interval 'infinity';
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval ERROR:  cannot add infinite interval to time
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' + interval '-infinity';
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' - interval 'infinity';
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval ERROR:  cannot subtract infinite interval from time
2025-02-01 03:24:46.913 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timetz '11:27:42' - interval '-infinity';
2025-02-01 03:24:46.916 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.916 UTC client backend[25882] pg_regress/timestamp STATEMENT:  SELECT timestamp '294276-12-31 23:59:59' - timestamp '1999-12-23 19:59:04.224192' AS overflows;
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT -interval '-2147483647 months -2147483647 days -9223372036854775807 us';
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval 'infinity' * 'nan';
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.918 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-infinity' * 'nan';
2025-02-01 03:24:46.919 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.919 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' * 2;
2025-02-01 03:24:46.919 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.919 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval 'infinity' * 0;
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-infinity' * 0;
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '0 days' * 'infinity'::float;
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.920 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '0 days' * '-infinity'::float;
2025-02-01 03:24:46.921 UTC client backend[25896] pg_regress/timestamptz ERROR:  date/time field value out of range: "Feb 29 17:32:01 1997" at character 37
2025-02-01 03:24:46.921 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 29 17:32:01 1997');
2025-02-01 03:24:46.921 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.921 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / 'infinity';
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / '-infinity';
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval 'infinity' / 'nan';
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.922 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / 'infinity';
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / '-infinity';
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-infinity' / 'nan';
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval ERROR:  interval out of range
2025-02-01 03:24:46.923 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT interval '-1073741824 months -1073741824 days -4611686018427387904 us' / 0.5;
2025-02-01 03:24:46.924 UTC client backend[25888] pg_regress/interval ERROR:  timestamps cannot be binned into infinite intervals
2025-02-01 03:24:46.924 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT date_bin('infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00');
2025-02-01 03:24:46.925 UTC client backend[25888] pg_regress/interval ERROR:  timestamps cannot be binned into infinite intervals
2025-02-01 03:24:46.925 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT date_bin('-infinity', timestamp '2001-02-16 20:38:40', timestamp '2001-02-16 20:05:00');
2025-02-01 03:24:46.926 UTC client backend[25888] pg_regress/interval ERROR:  unit "week" not supported for type interval
2025-02-01 03:24:46.926 UTC client backend[25888] pg_regress/interval DETAIL:  Months usually have fractional weeks.
2025-02-01 03:24:46.926 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT i AS interval, date_trunc('week', i)
	    FROM INFINITE_INTERVAL_TBL
	    WHERE NOT isfinite(i);
2025-02-01 03:24:46.929 UTC client backend[25896] pg_regress/timestamptz ERROR:  time zone displacement out of range: "Feb 16 17:32:01 -0097" at character 37
2025-02-01 03:24:46.929 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097');
2025-02-01 03:24:46.929 UTC client backend[25888] pg_regress/interval ERROR:  unit "ago" not recognized for type interval
2025-02-01 03:24:46.929 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT i AS interval, date_trunc('ago', i)
	    FROM INFINITE_INTERVAL_TBL
	    WHERE NOT isfinite(i);
2025-02-01 03:24:46.929 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp out of range: "Feb 16 17:32:01 5097 BC" at character 37
2025-02-01 03:24:46.929 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC');
2025-02-01 03:24:46.950 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2025-02-01 03:24:46.950 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamp);
2025-02-01 03:24:46.953 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2025-02-01 03:24:46.953 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamp);
2025-02-01 03:24:46.953 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2025-02-01 03:24:46.953 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '1995-08-06 12:12:12'::timestamptz);
2025-02-01 03:24:46.954 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2025-02-01 03:24:46.954 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '1995-08-06 12:12:12'::timestamptz);
2025-02-01 03:24:46.954 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2025-02-01 03:24:46.954 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '12:12:12'::time);
2025-02-01 03:24:46.955 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2025-02-01 03:24:46.955 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '12:12:12'::time);
2025-02-01 03:24:46.975 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp out of range: "4714-11-23 23:59:59+00 BC" at character 8
2025-02-01 03:24:46.975 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT '4714-11-23 23:59:59+00 BC'::timestamptz;
2025-02-01 03:24:46.975 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "infinity" must be finite
2025-02-01 03:24:46.975 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('infinity'::interval, '12:12:12'::timetz);
2025-02-01 03:24:46.975 UTC client backend[25888] pg_regress/interval ERROR:  interval time zone "-infinity" must be finite
2025-02-01 03:24:46.975 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT timezone('-infinity'::interval, '12:12:12'::timetz);
2025-02-01 03:24:46.976 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp out of range: "294277-01-01 00:00:00+00" at character 8
2025-02-01 03:24:46.976 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT '294277-01-01 00:00:00+00'::timestamptz;
2025-02-01 03:24:46.976 UTC client backend[25888] pg_regress/interval ERROR:  cannot convert infinite interval to time
2025-02-01 03:24:46.976 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT 'infinity'::interval::time;
2025-02-01 03:24:46.976 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp out of range: "294277-12-31 16:00:00-08" at character 8
2025-02-01 03:24:46.976 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT '294277-12-31 16:00:00-08'::timestamptz;
2025-02-01 03:24:46.976 UTC client backend[25888] pg_regress/interval ERROR:  cannot convert infinite interval to time
2025-02-01 03:24:46.976 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT '-infinity'::interval::time;
2025-02-01 03:24:46.977 UTC client backend[25882] pg_regress/timestamp ERROR:  date field value out of range: 0-07-15
2025-02-01 03:24:46.977 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select make_timestamp(0, 7, 15, 12, 30, 15);
2025-02-01 03:24:46.979 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "42 days 2 seconds ago ago" at character 17
2025-02-01 03:24:46.979 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL '42 days 2 seconds ago ago';
2025-02-01 03:24:46.979 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "2 minutes ago 5 days" at character 17
2025-02-01 03:24:46.979 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL '2 minutes ago 5 days';
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "hour 5 months" at character 17
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'hour 5 months';
2025-02-01 03:24:46.980 UTC client backend[25882] pg_regress/timestamp ERROR:  step size cannot equal zero
2025-02-01 03:24:46.980 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select * from generate_series('2020-01-01 00:00'::timestamp,
	                              '2020-01-02 03:00'::timestamp,
	                              '0 hour'::interval);
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "1 year months days 5 hours" at character 17
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL '1 year months days 5 hours';
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "now" at character 17
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'now';
2025-02-01 03:24:46.980 UTC client backend[25882] pg_regress/timestamp ERROR:  step size cannot be infinite
2025-02-01 03:24:46.980 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval 'infinity');
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "today" at character 17
2025-02-01 03:24:46.980 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'today';
2025-02-01 03:24:46.981 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "tomorrow" at character 17
2025-02-01 03:24:46.981 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'tomorrow';
2025-02-01 03:24:46.982 UTC client backend[25882] pg_regress/timestamp ERROR:  step size cannot be infinite
2025-02-01 03:24:46.982 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select generate_series(timestamp '1995-08-06 12:12:12', timestamp '1996-08-06 12:12:12', interval '-infinity');
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "allballs" at character 17
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'allballs';
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "epoch" at character 17
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'epoch';
2025-02-01 03:24:46.982 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.982 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select timestamp 'infinity' - timestamp 'infinity';
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "yesterday" at character 17
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'yesterday';
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "infinity years" at character 17
2025-02-01 03:24:46.982 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'infinity years';
2025-02-01 03:24:46.983 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "infinity ago" at character 17
2025-02-01 03:24:46.983 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL 'infinity ago';
2025-02-01 03:24:46.983 UTC client backend[25888] pg_regress/interval ERROR:  invalid input syntax for type interval: "+infinity -infinity" at character 17
2025-02-01 03:24:46.983 UTC client backend[25888] pg_regress/interval STATEMENT:  SELECT INTERVAL '+infinity -infinity';
2025-02-01 03:24:46.991 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.991 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select timestamp '-infinity' - timestamp '-infinity';
2025-02-01 03:24:46.994 UTC client backend[25887] pg_regress/strings ERROR:  field position must not be zero
2025-02-01 03:24:46.994 UTC client backend[25887] pg_regress/strings STATEMENT:  select split_part('joeuser@mydatabase','@',0) AS "an error";
2025-02-01 03:24:46.994 UTC client backend[25896] pg_regress/timestamptz ERROR:  unit "ago" not recognized for type timestamp with time zone
2025-02-01 03:24:46.994 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT date_trunc( 'ago', timestamp with time zone 'infinity' ) AS invalid_trunc;
2025-02-01 03:24:46.995 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.995 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select age(timestamp 'infinity', timestamp 'infinity');
2025-02-01 03:24:46.996 UTC client backend[25882] pg_regress/timestamp ERROR:  interval out of range
2025-02-01 03:24:46.996 UTC client backend[25882] pg_regress/timestamp STATEMENT:  select age(timestamp '-infinity', timestamp '-infinity');
2025-02-01 03:24:47.002 UTC client backend[25896] pg_regress/timestamptz ERROR:  unit "ago" not recognized for type timestamp with time zone
2025-02-01 03:24:47.002 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT date_trunc('ago', timestamp with time zone 'infinity', 'GMT') AS invalid_zone_trunc;
2025-02-01 03:24:47.004 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamps cannot be binned into intervals containing months or years
2025-02-01 03:24:47.004 UTC client backend[25896] 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-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamps cannot be binned into intervals containing months or years
2025-02-01 03:24:47.005 UTC client backend[25896] 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-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz ERROR:  stride must be greater than zero
2025-02-01 03:24:47.005 UTC client backend[25896] 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-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz ERROR:  stride must be greater than zero
2025-02-01 03:24:47.005 UTC client backend[25896] 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-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select date_bin('15 minutes'::interval, timestamptz '294276-12-30', timestamptz '4000-12-20 BC');
2025-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.005 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select date_bin('200000000 days'::interval, '2024-02-01'::timestamptz, '2024-01-01'::timestamptz);
2025-02-01 03:24:47.006 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp out of range
2025-02-01 03:24:47.006 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select date_bin('365000 days'::interval, '4400-01-01 BC'::timestamptz, '4000-01-01 BC'::timestamptz);
2025-02-01 03:24:47.015 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.015 UTC client backend[25896] 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-02-01 03:24:47.020 UTC client backend[25887] pg_regress/strings ERROR:  index 99 out of valid range, 0..71
2025-02-01 03:24:47.020 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT get_bit('\x1234567890abcdef00'::bytea, 99);
2025-02-01 03:24:47.021 UTC client backend[25887] pg_regress/strings ERROR:  index 99 out of valid range, 0..71
2025-02-01 03:24:47.021 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT set_bit('\x1234567890abcdef00'::bytea, 99, 0);
2025-02-01 03:24:47.023 UTC client backend[25887] pg_regress/strings ERROR:  index 99 out of valid range, 0..8
2025-02-01 03:24:47.023 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT get_byte('\x1234567890abcdef00'::bytea, 99);
2025-02-01 03:24:47.024 UTC client backend[25887] pg_regress/strings ERROR:  index 99 out of valid range, 0..8
2025-02-01 03:24:47.024 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT set_byte('\x1234567890abcdef00'::bytea, 99, 11);
2025-02-01 03:24:47.027 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 8
2025-02-01 03:24:47.027 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.027 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 24
2025-02-01 03:24:47.027 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 42
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 62
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 80
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings WARNING:  nonstandard use of \\ in a string literal at character 98
2025-02-01 03:24:47.028 UTC client backend[25887] pg_regress/strings HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:24:47.047 UTC client backend[25887] pg_regress/strings ERROR:  null character not permitted
2025-02-01 03:24:47.047 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT chr(0);
2025-02-01 03:24:47.049 UTC client backend[25887] pg_regress/strings ERROR:  negative substring length not allowed
2025-02-01 03:24:47.049 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT SUBSTRING('string'::bytea FROM -10 FOR -2147483646) AS "error";
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \db99');
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \db99\0061');
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2025-02-01 03:24:47.055 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \+00db99\+000061');
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode code point: 2FFFFF
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \+2FFFFF');
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \udb99\u0061');
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode surrogate pair
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \U0000db99\U00000061');
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode code point: 2FFFFF
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \U002FFFFF');
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings ERROR:  invalid Unicode escape
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings HINT:  Unicode escapes must be \XXXX, \+XXXXXX, \uXXXX, or \UXXXXXXXX.
2025-02-01 03:24:47.057 UTC client backend[25887] pg_regress/strings STATEMENT:  SELECT unistr('wrong: \xyz');
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz ERROR:  invalid input syntax for type numeric time zone: "2"
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz HINT:  Numeric time zones must have "-" or "+" as first character.
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(1973, 07, 15, 08, 15, 55.33, '2');
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz ERROR:  numeric time zone "+16" out of range
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '+16');
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz ERROR:  numeric time zone "-16" out of range
2025-02-01 03:24:47.062 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(2014, 12, 10, 10, 10, 10, '-16');
2025-02-01 03:24:47.069 UTC client backend[25896] pg_regress/timestamptz ERROR:  time zone "Nehwon/Lankhmar" not recognized
2025-02-01 03:24:47.069 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT make_timestamptz(1910, 12, 24, 0, 0, 0, 'Nehwon/Lankhmar');
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz ERROR:  step size cannot equal zero
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select * from generate_series('2020-01-01 00:00'::timestamptz,
	                              '2020-01-02 03:00'::timestamptz,
	                              '0 hour'::interval);
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz ERROR:  step size cannot be infinite
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval 'infinity');
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz ERROR:  step size cannot be infinite
2025-02-01 03:24:47.071 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  select generate_series(timestamptz '1995-08-06 12:12:12', timestamptz '1996-08-06 12:12:12', interval '-infinity');
2025-02-01 03:24:47.096 UTC client backend[25896] pg_regress/timestamptz ERROR:  timestamp cannot be NaN
2025-02-01 03:24:47.096 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT to_timestamp('NaN'::float);
2025-02-01 03:24:47.105 UTC client backend[25897] pg_regress/multirangetypes ERROR:  value for domain restrictedmultirange violates check constraint "restrictedmultirange_check"
2025-02-01 03:24:47.105 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select '{[4,50)}'::restrictedmultirange @> 7;
2025-02-01 03:24:47.107 UTC client backend[25897] pg_regress/multirangetypes ERROR:  type "intmultirange" already exists
2025-02-01 03:24:47.107 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Failed while creating a multirange type for type "intrange".
2025-02-01 03:24:47.107 UTC client backend[25897] pg_regress/multirangetypes HINT:  You can manually specify a multirange type name using the "multirange_type_name" attribute.
2025-02-01 03:24:47.107 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create type intrange as range(subtype=int);
2025-02-01 03:24:47.108 UTC client backend[25897] pg_regress/multirangetypes ERROR:  type "intr_multirange" already exists
2025-02-01 03:24:47.108 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  Failed while creating a multirange type for type "intr".
2025-02-01 03:24:47.108 UTC client backend[25897] pg_regress/multirangetypes HINT:  You can manually specify a multirange type name using the "multirange_type_name" attribute.
2025-02-01 03:24:47.108 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create type intr as range(subtype=int);
2025-02-01 03:24:47.109 UTC client backend[25897] pg_regress/multirangetypes ERROR:  type "int4" already exists
2025-02-01 03:24:47.109 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create type textrange1 as range(subtype=text, multirange_type_name=int, collation="C");
2025-02-01 03:24:47.119 UTC client backend[25897] pg_regress/multirangetypes ERROR:  function multirange_of_text(textrange2) does not exist at character 8
2025-02-01 03:24:47.119 UTC client backend[25897] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.119 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select multirange_of_text(textrange2('a','Z'));
2025-02-01 03:24:47.119 UTC client backend[25897] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:47.119 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select multirange_of_text(textrange1('a','Z')) @> 'b'::text;
2025-02-01 03:24:47.120 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.120 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT timestamptz 'infinity' - timestamptz 'infinity';
2025-02-01 03:24:47.122 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.122 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT timestamptz '-infinity' - timestamptz '-infinity';
2025-02-01 03:24:47.123 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.123 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT age(timestamptz 'infinity', timestamptz 'infinity');
2025-02-01 03:24:47.123 UTC client backend[25896] pg_regress/timestamptz ERROR:  interval out of range
2025-02-01 03:24:47.123 UTC client backend[25896] pg_regress/timestamptz STATEMENT:  SELECT age(timestamptz '-infinity', timestamptz '-infinity');
2025-02-01 03:24:47.125 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot alter multirange type multitextrange1
2025-02-01 03:24:47.125 UTC client backend[25897] pg_regress/multirangetypes HINT:  You can alter type textrange1, which will alter the multirange type as well.
2025-02-01 03:24:47.125 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  alter type multitextrange1 owner to regress_multirange_owner;
2025-02-01 03:24:47.126 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot set privileges of multirange types
2025-02-01 03:24:47.126 UTC client backend[25897] pg_regress/multirangetypes HINT:  Set the privileges of the range type instead.
2025-02-01 03:24:47.126 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  revoke usage on type multitextrange1 from public;
2025-02-01 03:24:47.167 UTC client backend[25897] pg_regress/multirangetypes ERROR:  permission denied for type multitextrange1
2025-02-01 03:24:47.167 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create temp table test2(f1 multitextrange1[]);
2025-02-01 03:24:47.170 UTC client backend[25897] pg_regress/multirangetypes ERROR:  function anyarray_anymultirange_func(integer[], nummultirange) does not exist at character 8
2025-02-01 03:24:47.170 UTC client backend[25897] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.170 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select anyarray_anymultirange_func(ARRAY[1,2], nummultirange(numrange(10,20)));
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create function bogus_func(anyelement)
	  returns anymultirange as 'select int4multirange(int4range(1,10))' language sql;
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:47.171 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create function bogus_func(int)
	  returns anymultirange as 'select int4multirange(int4range(1,10))' language sql;
2025-02-01 03:24:47.172 UTC client backend[25897] pg_regress/multirangetypes ERROR:  function multirangetypes_sql(nummultirange, integer[]) does not exist at character 8
2025-02-01 03:24:47.172 UTC client backend[25897] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.172 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select multirangetypes_sql(nummultirange(numrange(1,10)), ARRAY[2,20]);
2025-02-01 03:24:47.175 UTC client backend[25897] pg_regress/multirangetypes ERROR:  function anycompatiblearray_anycompatiblemultirange_func(numeric[], int4multirange) does not exist at character 8
2025-02-01 03:24:47.175 UTC client backend[25897] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.175 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select anycompatiblearray_anycompatiblemultirange_func(ARRAY[1.1,2], multirange(int4range(10,20)));
2025-02-01 03:24:47.176 UTC client backend[25897] pg_regress/multirangetypes ERROR:  function anycompatiblerange_anycompatiblemultirange_func(numrange, int4multirange) does not exist at character 8
2025-02-01 03:24:47.176 UTC client backend[25897] pg_regress/multirangetypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.176 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select anycompatiblerange_anycompatiblemultirange_func(numrange(1,2), multirange(int4range(10,20)));
2025-02-01 03:24:47.177 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.177 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:24:47.177 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create function bogus_func(anycompatible)
	  returns anycompatiblerange as 'select int4range(1,10)' language sql;
2025-02-01 03:24:47.180 UTC client backend[25897] pg_regress/multirangetypes ERROR:  range lower bound must be less than or equal to range upper bound
2025-02-01 03:24:47.180 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  select arraymultirange(arrayrange(ARRAY[2,1], ARRAY[1,2]));
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:47.193 UTC client backend[25897] 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-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes STATEMENT:  create function mr_inoutparam_fail(inout i anyelement, out r anymultirange)
	  as $$ select $1, '[1,10]' $$ language sql;
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes ERROR:  cannot determine result data type
2025-02-01 03:24:47.193 UTC client backend[25897] pg_regress/multirangetypes DETAIL:  A result of type anymultirange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:24:47.193 UTC client backend[25897] 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-02-01 03:24:47.398 UTC client backend[26064] pg_regress/tstypes ERROR:  syntax error in tsvector: "'' '1' '2'" at character 8
2025-02-01 03:24:47.398 UTC client backend[26064] pg_regress/tstypes STATEMENT:  SELECT $$'' '1' '2'$$::tsvector;
2025-02-01 03:24:47.417 UTC client backend[26062] pg_regress/regex ERROR:  regexp_match() does not support the "global" option
2025-02-01 03:24:47.417 UTC client backend[26062] pg_regress/regex HINT:  Use the regexp_matches function instead.
2025-02-01 03:24:47.417 UTC client backend[26062] pg_regress/regex STATEMENT:  select regexp_match('abc', 'Bd', 'ig');
2025-02-01 03:24:47.428 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "27/12/2001 04:05:06.789-08" at character 33
2025-02-01 03:24:47.428 UTC client backend[26069] pg_regress/horology HINT:  Perhaps you need a different "DateStyle" setting.
2025-02-01 03:24:47.428 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp with time zone '27/12/2001 04:05:06.789-08';
2025-02-01 03:24:47.434 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type time with time zone: "T040506.789 America/Los_Angeles" at character 28
2025-02-01 03:24:47.434 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT time with time zone 'T040506.789 America/Los_Angeles';
2025-02-01 03:24:47.434 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type xid: "" at character 8
2025-02-01 03:24:47.434 UTC client backend[26076] pg_regress/xid STATEMENT:  select ''::xid;
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type xid: "asdf" at character 8
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid STATEMENT:  select 'asdf'::xid;
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type xid8: "" at character 8
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid STATEMENT:  select ''::xid8;
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type xid8: "asdf" at character 8
2025-02-01 03:24:47.435 UTC client backend[26076] pg_regress/xid STATEMENT:  select 'asdf'::xid8;
2025-02-01 03:24:47.439 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.439 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT
	    pg_catalog.pg_set_relation_stats(
	        relation => 0::Oid,
	        relpages => 17::integer,
	        reltuples => 400.0::real,
	        relallvisible => 4::integer);
2025-02-01 03:24:47.439 UTC client backend[26074] pg_regress/unicode ERROR:  invalid normalization form: def
2025-02-01 03:24:47.439 UTC client backend[26074] pg_regress/unicode STATEMENT:  SELECT "normalize"('abc', 'def');
2025-02-01 03:24:47.441 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type time: "T04" at character 31
2025-02-01 03:24:47.441 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT time without time zone 'T04';
2025-02-01 03:24:47.442 UTC client backend[26074] pg_regress/unicode ERROR:  invalid normalization form: def
2025-02-01 03:24:47.442 UTC client backend[26074] pg_regress/unicode STATEMENT:  SELECT is_normalized('abc', 'def');
2025-02-01 03:24:47.444 UTC client backend[26076] pg_regress/xid ERROR:  operator does not exist: xid < xid at character 17
2025-02-01 03:24:47.444 UTC client backend[26076] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.444 UTC client backend[26076] pg_regress/xid STATEMENT:  select '1'::xid < '2'::xid;
2025-02-01 03:24:47.447 UTC client backend[26076] pg_regress/xid ERROR:  operator does not exist: xid <= xid at character 17
2025-02-01 03:24:47.447 UTC client backend[26076] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.447 UTC client backend[26076] pg_regress/xid STATEMENT:  select '1'::xid <= '2'::xid;
2025-02-01 03:24:47.448 UTC client backend[26076] pg_regress/xid ERROR:  operator does not exist: xid > xid at character 17
2025-02-01 03:24:47.448 UTC client backend[26076] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.448 UTC client backend[26076] pg_regress/xid STATEMENT:  select '1'::xid > '2'::xid;
2025-02-01 03:24:47.450 UTC client backend[26076] pg_regress/xid ERROR:  operator does not exist: xid >= xid at character 17
2025-02-01 03:24:47.450 UTC client backend[26076] pg_regress/xid HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.450 UTC client backend[26076] pg_regress/xid STATEMENT:  select '1'::xid >= '2'::xid;
2025-02-01 03:24:47.450 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type time with time zone: "T04+08" at character 28
2025-02-01 03:24:47.450 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT time with time zone 'T04+08';
2025-02-01 03:24:47.451 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06  J J J" at character 13
2025-02-01 03:24:47.451 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '1995-08-06  J J J';
2025-02-01 03:24:47.451 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "J J 1520447" at character 13
2025-02-01 03:24:47.451 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date 'J J 1520447';
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "Y2001M12D27H04M05S06.789+08" at character 33
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp with time zone 'Y2001M12D27H04M05S06.789+08';
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "Y2001M12D27H04MM05S06.789-08" at character 33
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp with time zone 'Y2001M12D27H04MM05S06.789-08';
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 epoch" at character 13
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 epoch';
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 infinity" at character 13
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 infinity';
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "1995-08-06 -infinity" at character 13
2025-02-01 03:24:47.455 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '1995-08-06 -infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "today infinity" at character 13
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date 'today infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type date: "-infinity infinity" at character 13
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '-infinity infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 epoch" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 epoch';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 infinity" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "1995-08-06 -infinity" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp '1995-08-06 -infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "epoch 01:01:01" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp 'epoch 01:01:01';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "infinity 01:01:01" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp 'infinity 01:01:01';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "-infinity 01:01:01" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp '-infinity 01:01:01';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "now epoch" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp 'now epoch';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp: "-infinity infinity" at character 18
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp '-infinity infinity';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 epoch" at character 20
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 epoch';
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 infinity" at character 20
2025-02-01 03:24:47.456 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 infinity';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "1995-08-06 -infinity" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz '1995-08-06 -infinity';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "epoch 01:01:01" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz 'epoch 01:01:01';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "infinity 01:01:01" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz 'infinity 01:01:01';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "-infinity 01:01:01" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz '-infinity 01:01:01';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "now epoch" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz 'now epoch';
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology ERROR:  invalid input syntax for type timestamp with time zone: "-infinity infinity" at character 20
2025-02-01 03:24:47.457 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamptz '-infinity infinity';
2025-02-01 03:24:47.459 UTC client backend[26073] pg_regress/expressions WARNING:  TIME(7) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:24:47.460 UTC client backend[26069] pg_regress/horology ERROR:  operator does not exist: date - time with time zone at character 26
2025-02-01 03:24:47.460 UTC client backend[26069] pg_regress/horology HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.460 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT date '1991-02-03' - time with time zone '04:05:06 UTC' AS "Subtract Time UTC";
2025-02-01 03:24:47.460 UTC client backend[26073] pg_regress/expressions WARNING:  TIMESTAMP(7) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:24:47.460 UTC client backend[26073] pg_regress/expressions WARNING:  TIME(7) precision reduced to maximum allowed, 6
2025-02-01 03:24:47.460 UTC client backend[26073] pg_regress/expressions WARNING:  TIMESTAMP(7) precision reduced to maximum allowed, 6
2025-02-01 03:24:47.461 UTC client backend[26077] pg_regress/geometry ERROR:  value out of range: underflow
2025-02-01 03:24:47.461 UTC client backend[26077] 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-02-01 03:24:47.462 UTC client backend[26069] pg_regress/horology ERROR:  timestamp out of range
2025-02-01 03:24:47.462 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range";
2025-02-01 03:24:47.462 UTC client backend[26069] pg_regress/horology ERROR:  timestamp out of range
2025-02-01 03:24:47.462 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp without time zone '294276-12-31 23:59:59' + interval '9223372036854775807 microseconds' AS "out of range";
2025-02-01 03:24:47.464 UTC client backend[26077] pg_regress/geometry ERROR:  value out of range: overflow
2025-02-01 03:24:47.464 UTC client backend[26077] 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-02-01 03:24:47.466 UTC client backend[26077] pg_regress/geometry ERROR:  division by zero
2025-02-01 03:24:47.466 UTC client backend[26077] 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-02-01 03:24:47.475 UTC client backend[26069] pg_regress/horology ERROR:  timestamp out of range
2025-02-01 03:24:47.475 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range";
2025-02-01 03:24:47.479 UTC client backend[26069] pg_regress/horology ERROR:  timestamp out of range
2025-02-01 03:24:47.479 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT timestamp with time zone '294276-12-31 23:59:59 UTC' + interval '9223372036854775807 microseconds' AS "out of range";
2025-02-01 03:24:47.490 UTC client backend[26069] pg_regress/horology ERROR:  cannot cast type time with time zone to interval at character 8
2025-02-01 03:24:47.490 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT CAST(time with time zone '01:02-08' AS interval) AS "+00:01";
2025-02-01 03:24:47.490 UTC client backend[26069] pg_regress/horology ERROR:  cannot cast type interval to time with time zone at character 8
2025-02-01 03:24:47.490 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT CAST(interval '02:03' AS time with time zone) AS "02:03:00-08";
2025-02-01 03:24:47.515 UTC client backend[26064] pg_regress/tstypes ERROR:  lexeme array may not contain nulls
2025-02-01 03:24:47.515 UTC client backend[26064] pg_regress/tstypes STATEMENT:  SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', NULL]);
2025-02-01 03:24:47.515 UTC client backend[26064] pg_regress/tstypes ERROR:  lexeme array may not contain empty strings
2025-02-01 03:24:47.515 UTC client backend[26064] pg_regress/tstypes STATEMENT:  SELECT array_to_tsvector(ARRAY['base','hidden','rebel','spaceship', '']);
2025-02-01 03:24:47.520 UTC client backend[26064] pg_regress/tstypes ERROR:  weight array may not contain nulls
2025-02-01 03:24:47.520 UTC client backend[26064] pg_regress/tstypes STATEMENT:  SELECT ts_filter('base hidden rebel spaceship strike'::tsvector, '{a,b,NULL}');
2025-02-01 03:24:47.524 UTC client backend[26077] pg_regress/geometry ERROR:  operator does not exist: lseg # point at character 23
2025-02-01 03:24:47.524 UTC client backend[26077] pg_regress/geometry HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.524 UTC client backend[26077] pg_regress/geometry STATEMENT:  SELECT p.f1, l.s, l.s # p.f1 AS intersection
	   FROM LSEG_TBL l, POINT_TBL p;
2025-02-01 03:24:47.536 UTC client backend[26068] pg_regress/stats_import ERROR:  cannot modify statistics for relation "testseq"
2025-02-01 03:24:47.536 UTC client backend[26068] pg_regress/stats_import DETAIL:  This operation is not supported for sequences.
2025-02-01 03:24:47.536 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT
	    pg_catalog.pg_clear_relation_stats(
	        'stats_import.testseq'::regclass);
2025-02-01 03:24:47.537 UTC client backend[26068] pg_regress/stats_import ERROR:  cannot modify statistics for relation "testview"
2025-02-01 03:24:47.537 UTC client backend[26068] pg_regress/stats_import DETAIL:  This operation is not supported for views.
2025-02-01 03:24:47.537 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT
	    pg_catalog.pg_clear_relation_stats(
	        'stats_import.testview'::regclass);
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => '0'::oid,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_clear_attribute_stats(
	    relation => '0'::oid,
	    attname => 'id'::name,
	    inherited => false::boolean);
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import ERROR:  "relation" cannot be NULL
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => NULL::oid,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import ERROR:  cannot modify statistics on system column "xmin"
2025-02-01 03:24:47.540 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'xmin'::name,
	    inherited => false::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import ERROR:  column "nope" of relation "test" does not exist
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'nope'::name,
	    inherited => false::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import ERROR:  cannot clear statistics on system column "ctid"
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_clear_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'ctid'::name,
	    inherited => false::boolean);
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import ERROR:  column "nope" of relation "test" does not exist
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_clear_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'nope'::name,
	    inherited => false::boolean);
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import ERROR:  "attname" cannot be NULL
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => NULL::name,
	    inherited => false::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import ERROR:  "inherited" cannot be NULL
2025-02-01 03:24:47.541 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => NULL::boolean,
	    null_frac => 0.1::real,
	    avg_width => 2::integer,
	    n_distinct => 0.3::real);
2025-02-01 03:24:47.542 UTC client backend[26068] pg_regress/stats_import ERROR:  "most_common_vals" must be specified when "most_common_freqs" is specified
2025-02-01 03:24:47.542 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_freqs => '{0.1,0.2,0.3}'::real[]
	    );
2025-02-01 03:24:47.542 UTC client backend[26068] pg_regress/stats_import ERROR:  "most_common_freqs" must be specified when "most_common_vals" is specified
2025-02-01 03:24:47.542 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_vals => '{1,2,3}'::text
	    );
2025-02-01 03:24:47.543 UTC client backend[26068] pg_regress/stats_import ERROR:  invalid input syntax for type integer: "2023-09-30"
2025-02-01 03:24:47.543 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_vals => '{2023-09-30,2024-10-31,3}'::text,
	    most_common_freqs => '{0.2,0.1}'::real[]
	    );
2025-02-01 03:24:47.543 UTC client backend[26068] pg_regress/stats_import ERROR:  invalid input syntax for type integer: "four"
2025-02-01 03:24:47.543 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_vals => '{2,four,3}'::text,
	    most_common_freqs => '{0.3,0.25,0.05}'::real[]
	    );
2025-02-01 03:24:47.555 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait flush-all
2025-02-01 03:24:47.560 UTC client backend[26068] pg_regress/stats_import ERROR:  "histogram_bounds" array cannot contain NULL values
2025-02-01 03:24:47.560 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    histogram_bounds => '{1,NULL,3,4}'::text
	    );
2025-02-01 03:24:47.574 UTC client backend[26068] pg_regress/stats_import ERROR:  unable to determine element type of attribute "id"
2025-02-01 03:24:47.574 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST.
2025-02-01 03:24:47.574 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_elems => '{1,3}'::text,
	    most_common_elem_freqs => '{0.3,0.2,0.2,0.3,0.0}'::real[]
	    );
2025-02-01 03:24:47.575 UTC client backend[26068] pg_regress/stats_import ERROR:  "most_common_elem_freqs" must be specified when "most_common_elems" is specified
2025-02-01 03:24:47.575 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'tags'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_elems => '{one,two}'::text
	    );
2025-02-01 03:24:47.583 UTC client backend[26068] pg_regress/stats_import ERROR:  "most_common_elems" must be specified when "most_common_elem_freqs" is specified
2025-02-01 03:24:47.583 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'tags'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_elem_freqs => '{0.3,0.2,0.2,0.3}'::real[]
	    );
2025-02-01 03:24:47.588 UTC client backend[26077] pg_regress/geometry ERROR:  open path cannot be converted to polygon
2025-02-01 03:24:47.588 UTC client backend[26077] pg_regress/geometry STATEMENT:  SELECT f1, f1::polygon FROM PATH_TBL WHERE isopen(f1);
2025-02-01 03:24:47.591 UTC client backend[26073] pg_regress/expressions ERROR:  operator does not exist: point = box at character 23
2025-02-01 03:24:47.591 UTC client backend[26073] pg_regress/expressions HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:47.591 UTC client backend[26073] pg_regress/expressions STATEMENT:  select '(0,0)'::point in ('(0,0,0,0)'::box, point(0,0));
2025-02-01 03:24:47.595 UTC client backend[26077] pg_regress/geometry ERROR:  division by zero
2025-02-01 03:24:47.595 UTC client backend[26077] 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-02-01 03:24:47.598 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "31:12:" at character 8
2025-02-01 03:24:47.598 UTC client backend[26076] pg_regress/xid STATEMENT:  select '31:12:'::pg_snapshot;
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "0:1:" at character 8
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid STATEMENT:  select '0:1:'::pg_snapshot;
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "12:13:0" at character 8
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid STATEMENT:  select '12:13:0'::pg_snapshot;
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "12:16:14,13" at character 8
2025-02-01 03:24:47.599 UTC client backend[26076] pg_regress/xid STATEMENT:  select '12:16:14,13'::pg_snapshot;
2025-02-01 03:24:47.599 UTC client backend[26068] pg_regress/stats_import ERROR:  unable to determine element type of attribute "id"
2025-02-01 03:24:47.599 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST.
2025-02-01 03:24:47.599 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    elem_count_histogram => '{1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}'::real[]
	    );
2025-02-01 03:24:47.600 UTC client backend[26068] pg_regress/stats_import ERROR:  "elem_count_histogram" array cannot contain NULL values
2025-02-01 03:24:47.600 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'tags'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    elem_count_histogram => '{1,1,NULL,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}'::real[]
	    );
2025-02-01 03:24:47.610 UTC client backend[26068] pg_regress/stats_import ERROR:  attribute "id" is not a range type
2025-02-01 03:24:47.610 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM.
2025-02-01 03:24:47.610 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    range_empty_frac => 0.5::real,
	    range_length_histogram => '{399,499,Infinity}'::text
	    );
2025-02-01 03:24:47.611 UTC client backend[26068] pg_regress/stats_import ERROR:  "range_empty_frac" must be specified when "range_length_histogram" is specified
2025-02-01 03:24:47.611 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'arange'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    range_length_histogram => '{399,499,Infinity}'::text
	    );
2025-02-01 03:24:47.612 UTC client backend[26068] pg_regress/stats_import ERROR:  "range_length_histogram" must be specified when "range_empty_frac" is specified
2025-02-01 03:24:47.612 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'arange'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    range_empty_frac => 0.5::real
	    );
2025-02-01 03:24:47.616 UTC client backend[26076] pg_regress/xid ERROR:  invalid input syntax for type pg_snapshot: "1:9223372036854775808:3" at character 20
2025-02-01 03:24:47.616 UTC client backend[26076] pg_regress/xid STATEMENT:  SELECT pg_snapshot '1:9223372036854775808:3';
2025-02-01 03:24:47.617 UTC client backend[26068] pg_regress/stats_import ERROR:  attribute "id" is not a range type
2025-02-01 03:24:47.617 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM.
2025-02-01 03:24:47.617 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'id'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    range_bounds_histogram => '{"[-1,1)","[0,4)","[1,4)","[1,100)"}'::text
	    );
2025-02-01 03:24:47.624 UTC client backend[26068] pg_regress/stats_import ERROR:  unable to determine element type of attribute "arange"
2025-02-01 03:24:47.624 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST.
2025-02-01 03:24:47.624 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_set_attribute_stats(
	    relation => 'stats_import.test'::regclass,
	    attname => 'arange'::name,
	    inherited => false::boolean,
	    null_frac => 0.5::real,
	    avg_width => 2::integer,
	    n_distinct => -0.1::real,
	    most_common_vals => '{"[2,3)","[1,2)","[3,4)"}'::text,
	    most_common_freqs => '{0.3,0.25,0.05}'::real[],
	    histogram_bounds => '{"[1,2)","[2,3)","[3,4)","[4,5)"}'::text,
	    correlation => 1.1::real,
	    most_common_elems => '{3,1}'::text,
	    most_common_elem_freqs => '{0.3,0.2,0.2,0.3,0.0}'::real[],
	    range_empty_frac => -0.5::real,
	    range_length_histogram => '{399,499,Infinity}'::text,
	    range_bounds_histogram => '{"[-1,1)","[0,4)","[1,4)","[1,100)"}'::text
	    );
2025-02-01 03:24:47.639 UTC client backend[26068] pg_regress/stats_import ERROR:  name at variadic position 5 is NULL
2025-02-01 03:24:47.639 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_restore_relation_stats(
	        'relation', '0'::oid::regclass,
	        'version', 150000::integer,
	        NULL, '17'::integer,
	        'reltuples', 400::real,
	        'relallvisible', 4::integer);
2025-02-01 03:24:47.639 UTC client backend[26068] pg_regress/stats_import ERROR:  name at variadic position 5 has type "integer", expected type "text"
2025-02-01 03:24:47.639 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_restore_relation_stats(
	        'relation', '0'::oid::regclass,
	        'version', 150000::integer,
	        17, '17'::integer,
	        'reltuples', 400::real,
	        'relallvisible', 4::integer);
2025-02-01 03:24:47.643 UTC client backend[26068] pg_regress/stats_import ERROR:  variadic arguments must be name/value pairs
2025-02-01 03:24:47.643 UTC client backend[26068] pg_regress/stats_import HINT:  Provide an even number of variadic arguments that can be divided into pairs.
2025-02-01 03:24:47.643 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_restore_relation_stats(
	        'relation', '0'::oid::regclass,
	        'version', 150000::integer,
	        'relpages', '17'::integer,
	        'reltuples', 400::real,
	        'relallvisible');
2025-02-01 03:24:47.643 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.643 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_restore_relation_stats(
	        'relation', '0'::oid::regclass,
	        'version', 150000::integer,
	        'relpages', '17'::integer,
	        'reltuples', 400::real,
	        'relallvisible', 4::integer);
2025-02-01 03:24:47.650 UTC client backend[26068] pg_regress/stats_import WARNING:  unrecognized argument name: "nope"
2025-02-01 03:24:47.650 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.650 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_restore_relation_stats(
	        'relation', '0'::oid::regclass,
	        'version', 150000::integer,
	        'relpages', '17'::integer,
	        'reltuples', 400::real,
	        'nope', 4::integer);
2025-02-01 03:24:47.650 UTC client backend[26068] pg_regress/stats_import WARNING:  argument "relpages" has type "text", expected type "integer"
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import ERROR:  could not open relation with OID 0
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_restore_attribute_stats(
	    'relation', '0'::oid::regclass,
	    'attname', 'id'::name,
	    'inherited', false::boolean,
	    'version', 150000::integer,
	    'null_frac', 0.1::real,
	    'avg_width', 2::integer,
	    'n_distinct', 0.3::real);
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import ERROR:  "relation" cannot be NULL
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_restore_attribute_stats(
	    'relation', NULL::oid,
	    'attname', 'id'::name,
	    'inherited', false::boolean,
	    'version', 150000::integer,
	    'null_frac', 0.1::real,
	    'avg_width', 2::integer,
	    'n_distinct', 0.3::real);
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import ERROR:  "attname" cannot be NULL
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_restore_attribute_stats(
	    'relation', 'stats_import.test'::regclass,
	    'attname', NULL::name,
	    'inherited', false::boolean,
	    'version', 150000::integer,
	    'null_frac', 0.1::real,
	    'avg_width', 2::integer,
	    'n_distinct', 0.3::real);
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import ERROR:  column "nope" of relation "test" does not exist
2025-02-01 03:24:47.665 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_restore_attribute_stats(
	    'relation', 'stats_import.test'::regclass,
	    'attname', 'nope'::name,
	    'inherited', false::boolean,
	    'version', 150000::integer,
	    'null_frac', 0.1::real,
	    'avg_width', 2::integer,
	    'n_distinct', 0.3::real);
2025-02-01 03:24:47.666 UTC client backend[26068] pg_regress/stats_import ERROR:  "inherited" cannot be NULL
2025-02-01 03:24:47.666 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT pg_catalog.pg_restore_attribute_stats(
	    'relation', 'stats_import.test'::regclass,
	    'attname', 'id'::name,
	    'inherited', NULL::boolean,
	    'version', 150000::integer,
	    'null_frac', 0.1::real,
	    'avg_width', 2::integer,
	    'n_distinct', 0.3::real);
2025-02-01 03:24:47.671 UTC client backend[26068] pg_regress/stats_import WARNING:  unrecognized argument name: "nope"
2025-02-01 03:24:47.681 UTC client backend[26068] pg_regress/stats_import WARNING:  "most_common_vals" must be specified when "most_common_freqs" is specified
2025-02-01 03:24:47.693 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 3939 buffers (24.0%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 2 recycled; write=0.124 s, sync=0.001 s, total=0.138 s; sync files=0, longest=0.000 s, average=0.000 s; distance=29531 kB, estimate=29531 kB; lsn=0/353F658, redo lsn=0/3461518
2025-02-01 03:24:47.695 UTC client backend[26068] pg_regress/stats_import WARNING:  "most_common_freqs" must be specified when "most_common_vals" is specified
2025-02-01 03:24:47.707 UTC client backend[26068] pg_regress/stats_import WARNING:  argument "most_common_freqs" has type "double precision[]", expected type "real[]"
2025-02-01 03:24:47.707 UTC client backend[26068] pg_regress/stats_import WARNING:  "most_common_freqs" must be specified when "most_common_vals" is specified
2025-02-01 03:24:47.719 UTC client backend[26068] pg_regress/stats_import WARNING:  invalid input syntax for type integer: "four"
2025-02-01 03:24:47.741 UTC client backend[26068] pg_regress/stats_import WARNING:  "histogram_bounds" array cannot contain NULL values
2025-02-01 03:24:47.750 UTC client backend[26068] pg_regress/stats_import WARNING:  "elem_count_histogram" array cannot contain NULL values
2025-02-01 03:24:47.764 UTC client backend[26077] pg_regress/geometry ERROR:  must request at least 2 points
2025-02-01 03:24:47.764 UTC client backend[26077] pg_regress/geometry STATEMENT:  SELECT f1, polygon(1, f1) FROM CIRCLE_TBL WHERE f1 >= '<(0,0),1>';
2025-02-01 03:24:47.764 UTC client backend[26077] pg_regress/geometry ERROR:  cannot convert circle with radius zero to polygon
2025-02-01 03:24:47.764 UTC client backend[26077] pg_regress/geometry STATEMENT:  SELECT f1, polygon(10, f1) FROM CIRCLE_TBL WHERE f1 < '<(0,0),1>';
2025-02-01 03:24:47.765 UTC client backend[26068] pg_regress/stats_import WARNING:  attribute "id" is not a range type
2025-02-01 03:24:47.765 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM.
2025-02-01 03:24:47.781 UTC client backend[26068] pg_regress/stats_import WARNING:  "range_empty_frac" must be specified when "range_length_histogram" is specified
2025-02-01 03:24:47.786 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:24:47.787 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 54 buffers (0.3%), wrote 2 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=908 kB, estimate=26668 kB; lsn=0/35446D8, redo lsn=0/3544680
2025-02-01 03:24:47.788 UTC client backend[26068] pg_regress/stats_import WARNING:  "range_length_histogram" must be specified when "range_empty_frac" is specified
2025-02-01 03:24:47.795 UTC client backend[26077] pg_regress/geometry ERROR:  value out of range: overflow
2025-02-01 03:24:47.795 UTC client backend[26077] 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-02-01 03:24:47.795 UTC client backend[26077] pg_regress/geometry ERROR:  division by zero
2025-02-01 03:24:47.795 UTC client backend[26077] 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-02-01 03:24:47.798 UTC client backend[26069] pg_regress/horology ERROR:  date out of range for timestamp
2025-02-01 03:24:47.798 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT '2202020-10-05'::date::timestamp;
2025-02-01 03:24:47.799 UTC client backend[26069] pg_regress/horology ERROR:  date out of range for timestamp
2025-02-01 03:24:47.799 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT '2202020-10-05'::date::timestamptz;
2025-02-01 03:24:47.800 UTC client backend[26068] pg_regress/stats_import WARNING:  attribute "id" is not a range type
2025-02-01 03:24:47.800 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_RANGE_LENGTH_HISTOGRAM or STATISTIC_KIND_BOUNDS_HISTOGRAM.
2025-02-01 03:24:47.807 UTC client backend[26069] pg_regress/horology ERROR:  date out of range for timestamp
2025-02-01 03:24:47.807 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT '4714-11-24 BC'::date::timestamptz;
2025-02-01 03:24:47.823 UTC client backend[26068] pg_regress/stats_import WARNING:  unable to determine element type of attribute "arange"
2025-02-01 03:24:47.823 UTC client backend[26068] pg_regress/stats_import DETAIL:  Cannot set STATISTIC_KIND_MCELEM or STATISTIC_KIND_DECHIST.
2025-02-01 03:24:47.831 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "/Feb/16" for "Mon"
2025-02-01 03:24:47.831 UTC client backend[26069] pg_regress/horology DETAIL:  The given value did not match any of the allowed values for this field.
2025-02-01 03:24:47.831 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('97/Feb/16', 'YYMonDD');
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "JUNK" for "TZ"
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology DETAIL:  Time zone abbreviation is not recognized.
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 JUNK', 'YYYY-MM-DD HH12:MI TZ');
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology ERROR:  invalid value ".." for "TZ"
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.845 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 ...', 'YYYY-MM-DD HH12:MI TZ');
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "xy" for "OF"
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 +xyz', 'YYYY-MM-DD HH12:MI OF');
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "xy" for "OF"
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.847 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2011-12-18 11:38 +01:xyz', 'YYYY-MM-DD HH12:MI OF');
2025-02-01 03:24:47.853 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2018-11-02 12:34:56.123456789"
2025-02-01 03:24:47.853 UTC client backend[26069] 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-02-01 03:24:47.861 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "+" for "MON"
2025-02-01 03:24:47.861 UTC client backend[26069] pg_regress/horology DETAIL:  The given value did not match any of the allowed values for this field.
2025-02-01 03:24:47.861 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2000 + + JUN', 'YYYY  MON');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "x1" for "MM"
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2011 x12 x18', 'YYYYxMMxDD');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  invalid combination of date conventions
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology HINT:  Do not mix Gregorian and ISO week date conventions in a formatting template.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2005527', 'YYYYIWID');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  source string too short for "MM" formatting field
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  Field requires 2 characters, but only 1 remain.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology HINT:  If your source string is not fixed-width, try using the "FM" modifier.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('19971', 'YYYYMMDD');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "1)" for "MM"
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  Field requires 2 characters, but only 1 could be parsed.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology HINT:  If your source string is not fixed-width, try using the "FM" modifier.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('19971)24', 'YYYYMMDD');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "da" for "DD"
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('Friday 1-January-1999', 'DY DD MON YYYY');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "uary" for "YYYY"
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('Fri 1-January-1999', 'DY DD MON YYYY');
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology ERROR:  conflicting values for "Mon" field in formatting string
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology DETAIL:  This value contradicts a previous setting for the same field type.
2025-02-01 03:24:47.869 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('1997-11-Jan-16', 'YYYY-MM-Mon-DD');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  invalid value "xy" for "DD"
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be an integer.
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('199711xy', 'YYYYMMDD');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  value for "YYYY" in source string is out of range
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology DETAIL:  Value must be in the range -2147483648 to 2147483647.
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('10000000000', 'FMYYYY');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 25:00:00"
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 25:00:00', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 15:60:00"
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:60:00', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-06-13 15:50:60"
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:50:60', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology ERROR:  hour "15" is invalid for the 12-hour clock
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology HINT:  Use the 24-hour clock, or give an hour between 1 and 12.
2025-02-01 03:24:47.870 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-06-13 15:50:55', 'YYYY-MM-DD HH:MI:SS');
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-13-01 15:50:55"
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-13-01 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-02-30 15:50:55"
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2016-02-30 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-29 15:50:55"
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-29 15:50:55', 'YYYY-MM-DD HH24:MI:SS');
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-11 86400"
2025-02-01 03:24:47.871 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSS');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-11 86400"
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2015-02-11 86400', 'YYYY-MM-DD SSSSS');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  value for "Y,YYY" in source string is out of range
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('1000000000,999', 'Y,YYY');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "0.-2147483648"
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('0.-2147483648', 'SS.MS');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "613566758"
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('613566758', 'W');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2024 613566758 1"
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_timestamp('2024 613566758 1', 'YYYY WW D');
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-13-10"
2025-02-01 03:24:47.872 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2016-13-10', 'YYYY-MM-DD');
2025-02-01 03:24:47.873 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016-02-30"
2025-02-01 03:24:47.873 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2016-02-30', 'YYYY-MM-DD');
2025-02-01 03:24:47.875 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2015-02-29"
2025-02-01 03:24:47.875 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2015-02-29', 'YYYY-MM-DD');
2025-02-01 03:24:47.875 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2015 366"
2025-02-01 03:24:47.875 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2015 366', 'YYYY DDD');
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2016 367"
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2016 367', 'YYYY DDD');
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "100000000"
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('100000000', 'CC');
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "-100000000"
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('-100000000', 'CC');
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "-2147483648 01"
2025-02-01 03:24:47.876 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('-2147483648 01', 'CC YY');
2025-02-01 03:24:47.877 UTC client backend[26069] pg_regress/horology ERROR:  date/time field value out of range: "2147483647 01"
2025-02-01 03:24:47.877 UTC client backend[26069] pg_regress/horology STATEMENT:  SELECT to_date('2147483647 01', 'CC YY');
2025-02-01 03:24:47.890 UTC client backend[26068] pg_regress/stats_import ERROR:  syntax error at or near "SELECT" at character 8
2025-02-01 03:24:47.890 UTC client backend[26068] pg_regress/stats_import STATEMENT:  SELECT
	SELECT COUNT(*)
	FROM pg_catalog.pg_stats AS s
	WHERE s.schemaname = 'stats_import'
	AND s.tablename IN ('test_clone', 'is_odd_clone');
2025-02-01 03:24:48.080 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:24:48.082 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 74 buffers (0.5%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=413 kB, estimate=24043 kB; lsn=0/35ABD60, redo lsn=0/35ABD08
2025-02-01 03:24:48.291 UTC client backend[26062] pg_regress/regex ERROR:  invalid regular expression: regular expression is too complex
2025-02-01 03:24:48.291 UTC client backend[26062] pg_regress/regex STATEMENT:  select 'x' ~ repeat('x*y*z*', 1000);
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex ERROR:  invalid regular expression: invalid backreference number
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex STATEMENT:  select 'xyz' ~ 'x(\w)(?=\1)';
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex ERROR:  invalid regular expression: invalid backreference number
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex STATEMENT:  select 'xyz' ~ 'x(\w)(?=(\1))';
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex ERROR:  invalid regular expression: invalid escape \ sequence
2025-02-01 03:24:48.334 UTC client backend[26062] pg_regress/regex STATEMENT:  select 'a' ~ '\x7fffffff';
2025-02-01 03:24:49.119 UTC client backend[26420] pg_regress/insert ERROR:  null value in column "col2" of relation "inserttest" violates not-null constraint
2025-02-01 03:24:49.119 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (null, null, testing).
2025-02-01 03:24:49.119 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT, DEFAULT);
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert ERROR:  INSERT has more target columns than expressions at character 37
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (DEFAULT, DEFAULT);
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert ERROR:  INSERT has more target columns than expressions at character 37
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (col1, col2, col3) values (1, 2);
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert ERROR:  INSERT has more expressions than target columns at character 42
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (col1) values (1, 2);
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert ERROR:  INSERT has more expressions than target columns at character 48
2025-02-01 03:24:49.129 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (col1) values (DEFAULT, DEFAULT);
2025-02-01 03:24:49.136 UTC client backend[26419] pg_regress/copyencoding ERROR:  invalid byte sequence for encoding "EUC_JP": 0xe3 0x81
2025-02-01 03:24:49.136 UTC client backend[26419] pg_regress/copyencoding CONTEXT:  COPY copy_encoding_tab, line 1
2025-02-01 03:24:49.136 UTC client backend[26419] pg_regress/copyencoding STATEMENT:  COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/build/testrun/regress/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv, ENCODING 'EUC_JP');
2025-02-01 03:24:49.140 UTC client backend[26419] pg_regress/copyencoding ERROR:  invalid byte sequence for encoding "EUC_JP": 0xe3 0x81
2025-02-01 03:24:49.140 UTC client backend[26419] pg_regress/copyencoding CONTEXT:  COPY copy_encoding_tab, line 1
2025-02-01 03:24:49.140 UTC client backend[26419] pg_regress/copyencoding STATEMENT:  COPY copy_encoding_tab FROM '/tmp/cirrus-ci-build/build/testrun/regress/regress/results/copyencoding_utf8.csv' WITH (FORMAT csv);
2025-02-01 03:24:49.150 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.150 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (key) do nothing;
2025-02-01 03:24:49.150 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.150 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  explain (costs off) insert into insertconflicttest values(0, 'Crowberry') on conflict (fruit) do nothing;
2025-02-01 03:24:49.152 UTC client backend[26420] pg_regress/insert ERROR:  cannot set an array element to DEFAULT at character 32
2025-02-01 03:24:49.152 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (f2[1], f2[2]) values (1,default);
2025-02-01 03:24:49.152 UTC client backend[26420] pg_regress/insert ERROR:  cannot set a subfield to DEFAULT at character 33
2025-02-01 03:24:49.152 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttest (f3.if1, f3.if2) values (1,default);
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy ERROR:  end-of-copy marker is not alone on its line
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY copytest2, line 3
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy STATEMENT:  copy copytest2(test) from stdin;
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy ERROR:  end-of-copy marker is not alone on its line
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY copytest2, line 3
2025-02-01 03:24:49.153 UTC client backend[26425] pg_regress/copy STATEMENT:  copy copytest2(test) from stdin;
2025-02-01 03:24:49.170 UTC client backend[26427] pg_regress/copyselect ERROR:  cannot copy from view "v_test1"
2025-02-01 03:24:49.170 UTC client backend[26427] pg_regress/copyselect HINT:  Try the COPY (SELECT ...) TO variant.
2025-02-01 03:24:49.170 UTC client backend[26427] pg_regress/copyselect STATEMENT:  copy v_test1 to stdout;
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect ERROR:  COPY (SELECT INTO) is not supported
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect STATEMENT:  copy (select t into temp test3 from test1 where id=3) to stdout;
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect ERROR:  syntax error at or near "from" at character 28
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect STATEMENT:  copy (select * from test1) from stdin;
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect ERROR:  syntax error at or near "(" at character 28
2025-02-01 03:24:49.172 UTC client backend[26427] pg_regress/copyselect STATEMENT:  copy (select * from test1) (t,id) to stdout;
2025-02-01 03:24:49.173 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.173 UTC client backend[26435] 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-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2025-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2025-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'g') to stdout;
2025-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml ERROR:  COPY query must have a RETURNING clause
2025-02-01 03:24:49.176 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2025-02-01 03:24:49.177 UTC client backend[26427] pg_regress/copyselect ERROR:  cannot copy from view "v_test1"
2025-02-01 03:24:49.177 UTC client backend[26427] pg_regress/copyselect HINT:  Try the COPY (SELECT ...) TO variant.
2025-02-01 03:24:49.177 UTC client backend[26427] pg_regress/copyselect STATEMENT:  COPY  v_test1 TO STDOUT 
2025-02-01 03:24:49.178 UTC client backend[26435] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE requires inference specification or constraint name at character 52
2025-02-01 03:24:49.178 UTC client backend[26435] pg_regress/insert_conflict HINT:  For example, ON CONFLICT (column_name).
2025-02-01 03:24:49.178 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict do update set fruit = excluded.fruit;
2025-02-01 03:24:49.179 UTC client backend[26437] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2025-02-01 03:24:49.179 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.185 UTC client backend[26437] pg_regress/copydml ERROR:  DO ALSO rules are not supported for COPY
2025-02-01 03:24:49.185 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict ERROR:  invalid reference to FROM-clause entry for table "excluded" at character 117
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict DETAIL:  There is an entry for table "excluded", but it cannot be referenced from this part of the query.
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruit RETURNING excluded.fruit;
2025-02-01 03:24:49.187 UTC client backend[26437] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.187 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict ERROR:  column "keyy" does not exist at character 64
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the column "insertconflicttest.key" or the column "excluded.key".
2025-02-01 03:24:49.187 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (keyy) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict ERROR:  column excluded.fruitt does not exist at character 92
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the column "excluded.fruit".
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (1, 'Apple') on conflict (key) do update set fruit = excluded.fruitt;
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.188 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (4, 'Mango') on conflict (fruit, key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.189 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.189 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (5, 'Lemon') on conflict (fruit) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.189 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.189 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (6, 'Passionfruit') on conflict (lower(fruit)) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict ERROR:  invalid reference to FROM-clause entry for table "insertconflicttest" at character 106
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict HINT:  Perhaps you meant to reference the table alias "ict".
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest AS ict values (6, 'Passionfruit') on conflict (key) do update set fruit = insertconflicttest.fruit;
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict ERROR:  column "insertconflicttest" of relation "insertconflicttest" does not exist at character 90
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict HINT:  SET target columns cannot be qualified with the relation name.
2025-02-01 03:24:49.190 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (3, 'Kiwi') on conflict (key, fruit) do update set insertconflicttest.fruit = 'Mango';
2025-02-01 03:24:49.190 UTC client backend[26437] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.190 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.191 UTC client backend[26437] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2025-02-01 03:24:49.191 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (9, 'Banana') on conflict (key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.194 UTC client backend[26427] pg_regress/copyselect ERROR:  division by zero
2025-02-01 03:24:49.194 UTC client backend[26427] pg_regress/copyselect STATEMENT:  copy (select 1) to stdout; select 1/0;
2025-02-01 03:24:49.194 UTC client backend[26437] pg_regress/copydml ERROR:  DO ALSO rules are not supported for COPY
2025-02-01 03:24:49.194 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (10, 'Blueberry') on conflict (key, key, key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.194 UTC client backend[26427] pg_regress/copyselect ERROR:  division by zero
2025-02-01 03:24:49.194 UTC client backend[26427] pg_regress/copyselect STATEMENT:  select 1/0; copy (select 1) to stdout;
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.194 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (11, 'Cherry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.195 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.195 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (12, 'Date') on conflict (lower(fruit), key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.198 UTC client backend[26437] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.198 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2025-02-01 03:24:49.199 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.199 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (13, 'Grape') on conflict (key, fruit) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.200 UTC client backend[26437] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.200 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (update copydml_test set t = 'f') to stdout;
2025-02-01 03:24:49.203 UTC client backend[26437] pg_regress/copydml ERROR:  DO INSTEAD NOTHING rules are not supported for COPY
2025-02-01 03:24:49.203 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2025-02-01 03:24:49.203 UTC client backend[26437] pg_regress/copydml ERROR:  DO ALSO rules are not supported for COPY
2025-02-01 03:24:49.203 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (14, 'Raisin') on conflict (fruit, key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (15, 'Cranberry') on conflict (key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (16, 'Melon') on conflict (key, key, key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (17, 'Mulberry') on conflict (key, lower(fruit)) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.206 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (18, 'Pineapple') on conflict (lower(fruit), key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.207 UTC client backend[26437] pg_regress/copydml ERROR:  multi-statement DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.207 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2025-02-01 03:24:49.209 UTC client backend[26437] pg_regress/copydml ERROR:  conditional DO INSTEAD rules are not supported for COPY
2025-02-01 03:24:49.209 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (delete from copydml_test) to stdout;
2025-02-01 03:24:49.209 UTC client backend[26437] pg_regress/copydml ERROR:  COPY query must not be a utility command
2025-02-01 03:24:49.209 UTC client backend[26437] pg_regress/copydml STATEMENT:  copy (insert into copydml_test default values) to stdout;
2025-02-01 03:24:49.212 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.212 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (22, 'Apricot') on conflict (upper(fruit)) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.212 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.212 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (fruit) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.216 UTC client backend[26425] pg_regress/copy ERROR:  cannot perform COPY FREEZE on a partitioned table
2025-02-01 03:24:49.216 UTC client backend[26425] pg_regress/copy STATEMENT:  copy parted_copytest from '/tmp/cirrus-ci-build/build/testrun/regress/regress/results/parted_copytest.csv' (freeze);
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (27, 'Prune') on conflict (key, upper(fruit)) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (28, 'Redcurrant') on conflict (fruit, key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.222 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (29, 'Nectarine') on conflict (key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.229 UTC client backend[26435] pg_regress/insert_conflict ERROR:  duplicate key value violates unique constraint "fruit_index"
2025-02-01 03:24:49.229 UTC client backend[26435] pg_regress/insert_conflict DETAIL:  Key (fruit)=(Peach) already exists.
2025-02-01 03:24:49.229 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (26, 'Peach') on conflict (key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.237 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.237 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (key) do update set fruit = excluded.fruit;
2025-02-01 03:24:49.238 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.238 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into insertconflicttest values (23, 'Blackberry') on conflict (key) where fruit like '%berry' or fruit = 'consequential' do nothing;
2025-02-01 03:24:49.239 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.239 UTC client backend[26435] 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-02-01 03:24:49.245 UTC client backend[26420] pg_regress/insert ERROR:  cannot set an array element to DEFAULT at character 33
2025-02-01 03:24:49.245 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (1,default);
2025-02-01 03:24:49.245 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2025-02-01 03:24:49.245 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (0,2);
2025-02-01 03:24:49.246 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2025-02-01 03:24:49.246 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) values (3,4), (0,6);
2025-02-01 03:24:49.246 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_pos_ints violates check constraint "insert_pos_ints_check"
2025-02-01 03:24:49.246 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttesta (f2[1], f2[2]) select 0,8;
2025-02-01 03:24:49.250 UTC client backend[26420] pg_regress/insert ERROR:  cannot set a subfield to DEFAULT at character 34
2025-02-01 03:24:49.250 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,default);
2025-02-01 03:24:49.253 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2025-02-01 03:24:49.253 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,array[null]);
2025-02-01 03:24:49.254 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2025-02-01 03:24:49.254 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) values (1,'{null}'), (2,'{bar}');
2025-02-01 03:24:49.255 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2025-02-01 03:24:49.255 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttestb (f3.if1, f3.if2) select 3, '{null,quux}';
2025-02-01 03:24:49.275 UTC client backend[26435] pg_regress/insert_conflict ERROR:  column excluded.ctid does not exist at character 82
2025-02-01 03:24:49.275 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into syscolconflicttest values (1) on conflict (key) do update set data = excluded.ctid::text;
2025-02-01 03:24:49.302 UTC client backend[26425] pg_regress/copy ERROR:  cannot use "match" with HEADER in COPY TO
2025-02-01 03:24:49.302 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest to stdout with (header match);
2025-02-01 03:24:49.302 UTC client backend[26425] pg_regress/copy ERROR:  header requires a Boolean value or "match"
2025-02-01 03:24:49.302 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header wrong_choice);
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy ERROR:  column name mismatch in header line field 1: got "a", expected "c"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	c"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest (c, b, a) from stdin with (header match);
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy ERROR:  column name mismatch in header line field 3: got null value ("\N"), expected "c"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	\N"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy ERROR:  wrong number of fields in header line: got 2, expected 3
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy ERROR:  wrong number of fields in header line: got 4, expected 3
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	c	d"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy ERROR:  column name mismatch in header line field 3: got "d", expected "c"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	b	d"
2025-02-01 03:24:49.303 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy ERROR:  wrong number of fields in header line: got 3, expected 2
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	........pg.dropped.2........	c"
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest from stdin with (header match);
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy ERROR:  wrong number of fields in header line: got 3, expected 2
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy CONTEXT:  COPY header_copytest, line 1: "a	c	b"
2025-02-01 03:24:49.304 UTC client backend[26425] pg_regress/copy STATEMENT:  copy header_copytest (a, c) from stdin with (header match);
2025-02-01 03:24:49.309 UTC client backend[26425] pg_regress/copy ERROR:  value too long for type character varying(5)
2025-02-01 03:24:49.309 UTC client backend[26425] pg_regress/copy STATEMENT:  copy oversized_column_default (col2) from stdin;
2025-02-01 03:24:49.309 UTC client backend[26425] pg_regress/copy ERROR:  value too long for type character varying(5)
2025-02-01 03:24:49.309 UTC client backend[26425] pg_regress/copy STATEMENT:  copy oversized_column_default from stdin (default '');
2025-02-01 03:24:49.328 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_nnarray violates check constraint "insert_nnarray_check"
2025-02-01 03:24:49.328 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttesta (f1[1]) values (1);
2025-02-01 03:24:49.335 UTC client backend[26420] pg_regress/insert ERROR:  value for domain insert_test_domain violates check constraint "insert_test_domain_check"
2025-02-01 03:24:49.335 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into inserttestb (f1.if1) values (1);
2025-02-01 03:24:49.343 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2025-02-01 03:24:49.343 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 11).
2025-02-01 03:24:49.343 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 11);
2025-02-01 03:24:49.347 UTC client backend[26435] pg_regress/insert_conflict ERROR:  table reference "excluded" is ambiguous at character 76
2025-02-01 03:24:49.347 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into excluded values(1, '2') on conflict (key) do update set data = excluded.data RETURNING *;
2025-02-01 03:24:49.359 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2025-02-01 03:24:49.359 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (a, 11).
2025-02-01 03:24:49.359 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part1 values ('a', 11);
2025-02-01 03:24:49.360 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2025-02-01 03:24:49.360 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (b, 1).
2025-02-01 03:24:49.360 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part1 values ('b', 1);
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part4" violates partition constraint
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (b, 21).
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part4 values ('b', 21);
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part4" violates partition constraint
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (a, 10).
2025-02-01 03:24:49.362 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part4 values ('a', 10);
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (null, null).
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part1 values (null);
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part1" violates partition constraint
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (1, null).
2025-02-01 03:24:49.364 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part1 values (1);
2025-02-01 03:24:49.379 UTC client backend[26435] pg_regress/insert_conflict ERROR:  duplicate key value violates unique constraint "twoconstraints_f1_key"
2025-02-01 03:24:49.379 UTC client backend[26435] pg_regress/insert_conflict DETAIL:  Key (f1)=(1) already exists.
2025-02-01 03:24:49.379 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(1, '((2,2),(3,3))');
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict ERROR:  conflicting key value violates exclusion constraint "twoconstraints_f2_excl"
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict DETAIL:  Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)).
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(2, '((0,0),(1,2))');
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict ERROR:  conflicting key value violates exclusion constraint "twoconstraints_f2_excl"
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict DETAIL:  Key (f2)=((1,2),(0,0)) conflicts with existing key (f2)=((1,1),(0,0)).
2025-02-01 03:24:49.380 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into twoconstraints values(2, '((0,0),(1,2))')
	  on conflict on constraint twoconstraints_f1_key do nothing;
2025-02-01 03:24:49.386 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2025-02-01 03:24:49.386 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (cc, 1).
2025-02-01 03:24:49.386 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_aa_bb values ('cc', 1);
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (AAa, 1).
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_aa_bb values ('AAa', 1);
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_aa_bb" violates partition constraint
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (null, null).
2025-02-01 03:24:49.388 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_aa_bb values (null);
2025-02-01 03:24:49.402 UTC client backend[26435] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2025-02-01 03:24:49.402 UTC client backend[26435] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2025-02-01 03:24:49.402 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (4,1), (4,2) on conflict(f1) do update set f2 = 0;
2025-02-01 03:24:49.405 UTC client backend[26435] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2025-02-01 03:24:49.405 UTC client backend[26435] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2025-02-01 03:24:49.405 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (5,1), (5,2) on conflict(f1) do update set f2 = 0;
2025-02-01 03:24:49.406 UTC client backend[26435] pg_regress/insert_conflict ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2025-02-01 03:24:49.406 UTC client backend[26435] pg_regress/insert_conflict HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2025-02-01 03:24:49.406 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into selfconflict values (6,1), (6,2) on conflict(f1) do update set f2 = 0;
2025-02-01 03:24:49.418 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_default" violates partition constraint
2025-02-01 03:24:49.418 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (aa, 2).
2025-02-01 03:24:49.418 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_default values ('aa', 2);
2025-02-01 03:24:49.419 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_default" violates partition constraint
2025-02-01 03:24:49.419 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (null, 2).
2025-02-01 03:24:49.419 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_default values (null, 2);
2025-02-01 03:24:49.428 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.428 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into parted_conflict_test values (2, 'b') on conflict (b) do update set a = excluded.a;
2025-02-01 03:24:49.449 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_ee_ff1" violates partition constraint
2025-02-01 03:24:49.449 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (EE, 11).
2025-02-01 03:24:49.449 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_ee_ff1 values ('EE', 11);
2025-02-01 03:24:49.450 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_default_p2" violates partition constraint
2025-02-01 03:24:49.450 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (gg, 43).
2025-02-01 03:24:49.450 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_default_p2 values ('gg', 43);
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_ee_ff1" violates partition constraint
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (cc, 1).
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_ee_ff1 values ('cc', 1);
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "part_default" found for row
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (43).
2025-02-01 03:24:49.451 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_default values ('gg', 43);
2025-02-01 03:24:49.467 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2025-02-01 03:24:49.467 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 0).
2025-02-01 03:24:49.467 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 0);
2025-02-01 03:24:49.468 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2025-02-01 03:24:49.468 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, 20).
2025-02-01 03:24:49.468 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into range_parted values ('a', 20);
2025-02-01 03:24:49.471 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "range_parted" found for row
2025-02-01 03:24:49.471 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, (b + 0)) = (a, null).
2025-02-01 03:24:49.471 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into range_parted values ('a');
2025-02-01 03:24:49.473 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "part_def" violates partition constraint
2025-02-01 03:24:49.473 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (b, 10).
2025-02-01 03:24:49.473 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_def values ('b', 10);
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "part_ee_ff" found for row
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (0).
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into list_parted values ('EE', 0);
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "part_ee_ff" found for row
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (0).
2025-02-01 03:24:49.481 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into part_ee_ff values ('EE', 0);
2025-02-01 03:24:49.555 UTC client backend[26435] pg_regress/insert_conflict ERROR:  there is no unique or exclusion constraint matching the ON CONFLICT specification
2025-02-01 03:24:49.555 UTC client backend[26435] pg_regress/insert_conflict STATEMENT:  insert into parted_conflict_1 values (40, 'cuarenta')
	  on conflict (a) do update set b = excluded.b;
2025-02-01 03:24:49.565 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "hpart0" violates partition constraint
2025-02-01 03:24:49.565 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (11).
2025-02-01 03:24:49.565 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into hpart0 values(11);
2025-02-01 03:24:49.668 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted1" found for row
2025-02-01 03:24:49.668 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains ((b + 0)) = (5).
2025-02-01 03:24:49.668 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted (a, b) values (1, 5);
2025-02-01 03:24:49.677 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted11" violates check constraint "check_b"
2025-02-01 03:24:49.677 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (1, 4).
2025-02-01 03:24:49.677 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 2);
2025-02-01 03:24:49.678 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted1" violates partition constraint
2025-02-01 03:24:49.678 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (3, 2).
2025-02-01 03:24:49.678 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted1 (a, b) values (2, 3);
2025-02-01 03:24:49.683 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "lparted_nonullpart" found for row
2025-02-01 03:24:49.683 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (null).
2025-02-01 03:24:49.683 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into lparted_nonullpart values (1);
2025-02-01 03:24:49.717 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted5a" violates check constraint "check_b"
2025-02-01 03:24:49.717 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (1, 45, a).
2025-02-01 03:24:49.717 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'a');
2025-02-01 03:24:49.719 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted5a" violates partition constraint
2025-02-01 03:24:49.719 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (b, 1, 40).
2025-02-01 03:24:49.719 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted5 (a, b, c) values (1, 40, 'a');
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted_def" found for row
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a) = (70).
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (70, 100);
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted_def1" violates partition constraint
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (52, 50, null).
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted_def1 values (52, 50);
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mlparted_def2" violates partition constraint
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (34, 50, null).
2025-02-01 03:24:49.742 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted_def2 values (34, 50);
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted5_cd" found for row
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (c).
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'c', 1);
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted5" found for row
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (f).
2025-02-01 03:24:49.782 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'f', 1);
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted5_cd" found for row
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (c).
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'c', 1);
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mlparted5" found for row
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (c) = (f).
2025-02-01 03:24:49.823 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mlparted values (1, 45, 'f', 1);
2025-02-01 03:24:49.832 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "key_desc_1" found for row
2025-02-01 03:24:49.832 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into key_desc values (1, 1);
2025-02-01 03:24:49.833 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "key_desc_1" found for row
2025-02-01 03:24:49.833 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (b) = (1).
2025-02-01 03:24:49.833 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into key_desc values (1, 1);
2025-02-01 03:24:49.833 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "key_desc" found for row
2025-02-01 03:24:49.833 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into key_desc values (2, 1);
2025-02-01 03:24:49.836 UTC client backend[26420] pg_regress/insert ERROR:  every bound following MINVALUE must also be MINVALUE at character 75
2025-02-01 03:24:49.836 UTC client backend[26420] pg_regress/insert STATEMENT:  create table mcrparted0 partition of mcrparted for values from (minvalue, 0, 0) to (1, maxvalue, maxvalue);
2025-02-01 03:24:49.836 UTC client backend[26420] pg_regress/insert ERROR:  every bound following MAXVALUE must also be MAXVALUE at character 100
2025-02-01 03:24:49.836 UTC client backend[26420] pg_regress/insert STATEMENT:  create table mcrparted2 partition of mcrparted for values from (10, 6, minvalue) to (10, maxvalue, minvalue);
2025-02-01 03:24:49.837 UTC client backend[26420] pg_regress/insert ERROR:  every bound following MINVALUE must also be MINVALUE at character 79
2025-02-01 03:24:49.837 UTC client backend[26420] pg_regress/insert STATEMENT:  create table mcrparted4 partition of mcrparted for values from (21, minvalue, 0) to (30, 20, minvalue);
2025-02-01 03:24:49.842 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mcrparted" found for row
2025-02-01 03:24:49.842 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, abs(b), c) = (null, null, null).
2025-02-01 03:24:49.842 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mcrparted values (null, null, null);
2025-02-01 03:24:49.845 UTC client backend[26420] pg_regress/insert ERROR:  no partition of relation "mcrparted" found for row
2025-02-01 03:24:49.845 UTC client backend[26420] pg_regress/insert DETAIL:  Partition key of the failing row contains (a, abs(b), c) = (11, 1, -1).
2025-02-01 03:24:49.845 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mcrparted values (11, 1, -1);
2025-02-01 03:24:49.846 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mcrparted3" violates partition constraint
2025-02-01 03:24:49.846 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (11, 1, -1).
2025-02-01 03:24:49.846 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mcrparted3 values (11, 1, -1);
2025-02-01 03:24:49.849 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "mcrparted4" violates partition constraint
2025-02-01 03:24:49.849 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (30, 21, 20).
2025-02-01 03:24:49.849 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into mcrparted4 values (30, 21, 20);
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (2, hi there).
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into brtrigpartcon values (1, 'hi there');
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (2, hi there).
2025-02-01 03:24:49.855 UTC client backend[26420] pg_regress/insert STATEMENT:  insert into brtrigpartcon1 values (1, 'hi there');
2025-02-01 03:24:49.861 UTC client backend[26420] pg_regress/insert ERROR:  new row for relation "brtrigpartcon1" violates partition constraint
2025-02-01 03:24:49.861 UTC client backend[26420] pg_regress/insert DETAIL:  Failing row contains (a, b) = (2, hi there).
2025-02-01 03:24:49.861 UTC client backend[26420] pg_regress/insert STATEMENT:  with result as (insert into brtrigpartcon values (1, 'hi there') returning 1)
	  insert into inserttest3 (f3) select * from result;
2025-02-01 03:24:50.053 UTC client backend[26684] pg_regress/create_function_c ERROR:  could not access file "nosuchfile": No such file or directory
2025-02-01 03:24:50.053 UTC client backend[26684] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C
	    AS 'nosuchfile';
2025-02-01 03:24:50.056 UTC client backend[26684] pg_regress/create_function_c ERROR:  could not find function "nosuchsymbol" in file "/tmp/cirrus-ci-build/build/src/test/regress/regress.so"
2025-02-01 03:24:50.056 UTC client backend[26684] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE C
	    AS '/tmp/cirrus-ci-build/build/src/test/regress/regress.so', 'nosuchsymbol';
2025-02-01 03:24:50.056 UTC client backend[26677] pg_regress/create_type ERROR:  type "shell" already exists
2025-02-01 03:24:50.056 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TYPE shell;
2025-02-01 03:24:50.056 UTC client backend[26684] pg_regress/create_function_c ERROR:  there is no built-in function named "nosuch"
2025-02-01 03:24:50.056 UTC client backend[26684] pg_regress/create_function_c STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE internal
	    AS 'nosuch';
2025-02-01 03:24:50.057 UTC client backend[26677] pg_regress/create_type ERROR:  type "shell" does not exist
2025-02-01 03:24:50.057 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP TYPE shell;
2025-02-01 03:24:50.058 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.058 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE SEQUENCE schema_not_existing.seq;
2025-02-01 03:24:50.058 UTC client backend[26679] pg_regress/create_operator ERROR:  operator right argument type must be specified
2025-02-01 03:24:50.058 UTC client backend[26679] pg_regress/create_operator DETAIL:  Postfix operators are not supported.
2025-02-01 03:24:50.058 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #%# (
	   leftarg = int8,		-- fail, postfix is no longer supported
	   procedure = factorial
	);
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE TABLE schema_not_existing.tab (id int);
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION regress_create_schema_role
	  CREATE INDEX ON schema_not_existing.tab (id);
2025-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator ERROR:  operator does not exist: ###### integer
2025-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (NONE, int4) IS 'bad prefix';
2025-02-01 03:24:50.059 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.059 UTC client backend[26678] 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-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator ERROR:  postfix operators are not supported
2025-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (int4, NONE) IS 'bad postfix';
2025-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator ERROR:  operator does not exist: integer ###### bigint
2025-02-01 03:24:50.059 UTC client backend[26679] pg_regress/create_operator STATEMENT:  COMMENT ON OPERATOR ###### (int4, int8) IS 'bad infix';
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator ERROR:  operator does not exist: ###### integer
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (NONE, int4);
2025-02-01 03:24:50.060 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.060 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE SEQUENCE schema_not_existing.seq;
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator ERROR:  postfix operators are not supported
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (int4, NONE);
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator ERROR:  operator does not exist: integer ###### bigint
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator STATEMENT:  DROP OPERATOR ###### (int4, int8);
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator ERROR:  syntax error at or near "=>" at character 17
2025-02-01 03:24:50.060 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR => (
	   rightarg = int8,
	   procedure = factorial
	);
2025-02-01 03:24:50.060 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.060 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE TABLE schema_not_existing.tab (id int);
2025-02-01 03:24:50.061 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.061 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2025-02-01 03:24:50.061 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.061 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA AUTHORIZATION CURRENT_ROLE
	  CREATE INDEX ON schema_not_existing.tab (id);
2025-02-01 03:24:50.061 UTC client backend[26679] pg_regress/create_operator ERROR:  syntax error at or near ";" at character 14
2025-02-01 03:24:50.061 UTC client backend[26679] pg_regress/create_operator STATEMENT:  SELECT 10 !=-;
2025-02-01 03:24:50.061 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_create_schema_role)
2025-02-01 03:24:50.061 UTC client backend[26678] 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-02-01 03:24:50.062 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2025-02-01 03:24:50.062 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE SEQUENCE schema_not_existing.seq;
2025-02-01 03:24:50.062 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2025-02-01 03:24:50.062 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE TABLE schema_not_existing.tab (id int);
2025-02-01 03:24:50.063 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Internallength" not recognized at character 27
2025-02-01 03:24:50.063 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Input" not recognized at character 50
2025-02-01 03:24:50.063 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Output" not recognized at character 71
2025-02-01 03:24:50.063 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Alignment" not recognized at character 94
2025-02-01 03:24:50.063 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Default" not recognized at character 115
2025-02-01 03:24:50.063 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2025-02-01 03:24:50.063 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE VIEW schema_not_existing.view AS SELECT 1;
2025-02-01 03:24:50.063 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2025-02-01 03:24:50.063 UTC client backend[26678] pg_regress/create_schema STATEMENT:  CREATE SCHEMA regress_schema_1 AUTHORIZATION CURRENT_ROLE
	  CREATE INDEX ON schema_not_existing.tab (id);
2025-02-01 03:24:50.063 UTC client backend[26678] pg_regress/create_schema ERROR:  CREATE specifies a schema (schema_not_existing) different from the one being created (regress_schema_1)
2025-02-01 03:24:50.063 UTC client backend[26678] 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-02-01 03:24:50.067 UTC client backend[26677] pg_regress/create_type WARNING:  type attribute "Passedbyvalue" not recognized at character 132
2025-02-01 03:24:50.067 UTC client backend[26677] pg_regress/create_type ERROR:  type input function must be specified
2025-02-01 03:24:50.067 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (
		"Internallength" = 4,
		"Input" = int42_in,
		"Output" = int42_out,
		"Alignment" = int4,
		"Default" = 42,
		"Passedbyvalue"
	);
2025-02-01 03:24:50.067 UTC client backend[26677] pg_regress/create_type ERROR:  type input function array_in must return type bogus_type
2025-02-01 03:24:50.067 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (INPUT = array_in,
	    OUTPUT = array_out,
	    ELEMENT = int,
	    INTERNALLENGTH = 32);
2025-02-01 03:24:50.069 UTC client backend[26677] pg_regress/create_type ERROR:  type "bogus_type" does not exist
2025-02-01 03:24:50.069 UTC client backend[26677] 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-02-01 03:24:50.069 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TYPE bogus_type (INPUT = array_in,
	    OUTPUT = array_out,
	    ELEMENT = int,
	    INTERNALLENGTH = 32);
2025-02-01 03:24:50.070 UTC client backend[26686] pg_regress/create_table ERROR:  column "u" has pseudo-type unknown
2025-02-01 03:24:50.070 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE unknowntab (
		u unknown    -- fail
	);
2025-02-01 03:24:50.071 UTC client backend[26677] pg_regress/create_type ERROR:  type "bad" does not exist
2025-02-01 03:24:50.071 UTC client backend[26677] pg_regress/create_type STATEMENT:  COMMENT ON TYPE bad IS 'bad comment';
2025-02-01 03:24:50.071 UTC client backend[26677] pg_regress/create_type ERROR:  column "nope" of relation "default_test_row" does not exist
2025-02-01 03:24:50.071 UTC client backend[26677] pg_regress/create_type STATEMENT:  COMMENT ON COLUMN default_test_row.nope IS 'bad comment';
2025-02-01 03:24:50.072 UTC client backend[26677] pg_regress/create_type ERROR:  type "text_w_default" already exists
2025-02-01 03:24:50.072 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TYPE text_w_default;
2025-02-01 03:24:50.073 UTC client backend[26686] pg_regress/create_table ERROR:  column "u" has pseudo-type unknown
2025-02-01 03:24:50.073 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TYPE unknown_comptype AS (
		u unknown    -- fail
	);
2025-02-01 03:24:50.073 UTC client backend[26686] pg_regress/create_table ERROR:  unrecognized parameter "Fillfactor"
2025-02-01 03:24:50.073 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE tas_case WITH ("Fillfactor" = 10) AS SELECT 1 a;
2025-02-01 03:24:50.075 UTC client backend[26679] pg_regress/create_operator ERROR:  permission denied for schema schema_op1
2025-02-01 03:24:50.075 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR schema_op1.#*# (
	   rightarg = int8,
	   procedure = factorial
	);
2025-02-01 03:24:50.076 UTC client backend[26679] pg_regress/create_operator ERROR:  SETOF type not allowed for operator argument
2025-02-01 03:24:50.076 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = SETOF int8,
	   procedure = factorial
	);
2025-02-01 03:24:50.076 UTC client backend[26679] pg_regress/create_operator ERROR:  SETOF type not allowed for operator argument
2025-02-01 03:24:50.076 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   rightarg = SETOF int8,
	   procedure = factorial
	);
2025-02-01 03:24:50.077 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "invalid_att" not recognized
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type ERROR:  cannot drop function base_fn_in(cstring) because other objects depend on it
2025-02-01 03:24:50.079 UTC client backend[26677] 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-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP FUNCTION base_fn_in(cstring);
2025-02-01 03:24:50.079 UTC client backend[26679] pg_regress/create_operator ERROR:  operator argument types must be specified
2025-02-01 03:24:50.079 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #@%# (
	   procedure = factorial
	);
2025-02-01 03:24:50.079 UTC client backend[26679] pg_regress/create_operator ERROR:  operator function must be specified
2025-02-01 03:24:50.079 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #@%# (
	   rightarg = int8
	);
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type ERROR:  cannot drop function base_fn_out(base_type) because other objects depend on it
2025-02-01 03:24:50.079 UTC client backend[26677] 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-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP FUNCTION base_fn_out(base_type);
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type ERROR:  cannot drop type base_type because other objects depend on it
2025-02-01 03:24:50.079 UTC client backend[26677] 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-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.079 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP TYPE base_type;
2025-02-01 03:24:50.080 UTC client backend[26677] pg_regress/create_type ERROR:  invalid NUMERIC type modifier at character 30
2025-02-01 03:24:50.080 UTC client backend[26677] pg_regress/create_type STATEMENT:  CREATE TEMP TABLE mytab (foo widget(42,13,7));
2025-02-01 03:24:50.080 UTC client backend[26679] pg_regress/create_operator ERROR:  permission denied for type type_op3
2025-02-01 03:24:50.080 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = type_op3,
	   rightarg = int8,
	   procedure = fn_op3
	);
2025-02-01 03:24:50.083 UTC client backend[26677] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2025-02-01 03:24:50.083 UTC client backend[26677] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('(1,2)', 'widget');
2025-02-01 03:24:50.083 UTC client backend[26677] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2025-02-01 03:24:50.083 UTC client backend[26677] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('{"(1,2)"}', 'widget[]');
2025-02-01 03:24:50.084 UTC client backend[26677] pg_regress/create_type ERROR:  invalid input syntax for type widget: "(1,2)"
2025-02-01 03:24:50.084 UTC client backend[26677] pg_regress/create_type STATEMENT:  SELECT pg_input_is_valid('("(1,2)")', 'mytab');
2025-02-01 03:24:50.086 UTC client backend[26679] pg_regress/create_operator ERROR:  permission denied for type type_op4
2025-02-01 03:24:50.086 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = type_op4,
	   procedure = fn_op4
	);
2025-02-01 03:24:50.087 UTC client backend[26679] pg_regress/create_operator ERROR:  permission denied for function fn_op5
2025-02-01 03:24:50.087 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = int8,
	   procedure = fn_op5
	);
2025-02-01 03:24:50.092 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist at character 6
2025-02-01 03:24:50.092 UTC client backend[26692] pg_regress/create_procedure HINT:  No procedure matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:50.092 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL nonexistent();
2025-02-01 03:24:50.094 UTC client backend[26679] pg_regress/create_operator ERROR:  permission denied for type type_op6
2025-02-01 03:24:50.094 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR #*# (
	   leftarg = int8,
	   rightarg = int8,
	   procedure = fn_op6
	);
2025-02-01 03:24:50.094 UTC client backend[26679] pg_regress/create_operator ERROR:  operator cannot be its own negator
2025-02-01 03:24:50.094 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    negator = ===
	);
2025-02-01 03:24:50.095 UTC client backend[26692] pg_regress/create_procedure ERROR:  random() is not a procedure at character 6
2025-02-01 03:24:50.095 UTC client backend[26692] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2025-02-01 03:24:50.095 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL random();
2025-02-01 03:24:50.095 UTC client backend[26679] pg_regress/create_operator ERROR:  operator cannot be its own negator
2025-02-01 03:24:50.095 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR ===!!! (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4ne,
	    negator = ===!!!
	);
2025-02-01 03:24:50.095 UTC client backend[26677] pg_regress/create_type ERROR:  type "myvarchar" is only a shell
2025-02-01 03:24:50.095 UTC client backend[26677] pg_regress/create_type STATEMENT:  ALTER TYPE myvarchar SET (storage = extended);
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator ERROR:  commutator operator = is already the commutator of operator =
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    commutator = =
	);
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator ERROR:  negator operator <> is already the negator of operator =
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator STATEMENT:  CREATE OPERATOR === (
	    leftarg = integer,
	    rightarg = integer,
	    procedure = int4eq,
	    negator = <>
	);
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Leftarg" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Rightarg" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Procedure" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Commutator" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Negator" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Restrict" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Join" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Hashes" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator WARNING:  operator attribute "Merges" not recognized
2025-02-01 03:24:50.096 UTC client backend[26679] pg_regress/create_operator ERROR:  operator function must be specified
2025-02-01 03:24:50.096 UTC client backend[26679] 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-02-01 03:24:50.097 UTC client backend[26677] pg_regress/create_type ERROR:  cannot change type's storage to PLAIN
2025-02-01 03:24:50.097 UTC client backend[26677] pg_regress/create_type STATEMENT:  ALTER TYPE myvarchar SET (storage = plain);
2025-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type ERROR:  cannot drop function myvarcharsend(myvarchar) because other objects depend on it
2025-02-01 03:24:50.100 UTC client backend[26677] 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-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP FUNCTION myvarcharsend(myvarchar);
2025-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type ERROR:  cannot drop type myvarchar because other objects depend on it
2025-02-01 03:24:50.100 UTC client backend[26677] 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-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.100 UTC client backend[26677] pg_regress/create_type STATEMENT:  DROP TYPE myvarchar;
2025-02-01 03:24:50.111 UTC client backend[26686] pg_regress/create_table ERROR:  only temporary relations may be created in temporary schemas at character 23
2025-02-01 03:24:50.111 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE UNLOGGED TABLE pg_temp.unlogged3 (a int primary key);
2025-02-01 03:24:50.120 UTC client backend[26686] pg_regress/create_table ERROR:  cannot create temporary relation in non-temporary schema at character 19
2025-02-01 03:24:50.120 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TEMP TABLE public.temp_to_perm (a int primary key);
2025-02-01 03:24:50.126 UTC client backend[26686] pg_regress/create_table ERROR:  partitioned tables cannot be unlogged
2025-02-01 03:24:50.126 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE UNLOGGED TABLE unlogged1 (a int) PARTITION BY RANGE (a);
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table ERROR:  ALTER action SET LOGGED cannot be performed on relation "unlogged1"
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table DETAIL:  This operation is not supported for partitioned tables.
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table STATEMENT:  ALTER TABLE unlogged1 SET LOGGED;
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table ERROR:  ALTER action SET UNLOGGED cannot be performed on relation "unlogged1"
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table DETAIL:  This operation is not supported for partitioned tables.
2025-02-01 03:24:50.127 UTC client backend[26686] pg_regress/create_table STATEMENT:  ALTER TABLE unlogged1 SET UNLOGGED;
2025-02-01 03:24:50.144 UTC client backend[26686] pg_regress/create_table ERROR:  relation "as_select1" already exists
2025-02-01 03:24:50.144 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relkind = 'r';
2025-02-01 03:24:50.151 UTC client backend[26686] pg_regress/create_table ERROR:  relation "as_select1" already exists
2025-02-01 03:24:50.151 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE as_select1 AS EXECUTE select1;
2025-02-01 03:24:50.163 UTC client backend[26692] pg_regress/create_procedure ERROR:  ptest1(unknown) is a procedure at character 8
2025-02-01 03:24:50.163 UTC client backend[26692] pg_regress/create_procedure HINT:  To call a procedure, use CALL.
2025-02-01 03:24:50.163 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  SELECT ptest1('x');
2025-02-01 03:24:50.175 UTC client backend[26692] pg_regress/create_procedure ERROR:  CREATE TABLE is not yet supported in unquoted SQL function body
2025-02-01 03:24:50.175 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx()
	LANGUAGE SQL
	BEGIN ATOMIC
	  CREATE TABLE x (a int);
	END;
2025-02-01 03:24:50.187 UTC client backend[26692] pg_regress/create_procedure ERROR:  calling procedures with output arguments is not supported in SQL functions
2025-02-01 03:24:50.187 UTC client backend[26692] pg_regress/create_procedure CONTEXT:  SQL function "ptest4b"
2025-02-01 03:24:50.187 UTC client backend[26692] 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-02-01 03:24:50.213 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure ptest9(numeric) does not exist at character 6
2025-02-01 03:24:50.213 UTC client backend[26692] pg_regress/create_procedure HINT:  No procedure matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:50.213 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL ptest9(1./0.);
2025-02-01 03:24:50.250 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure name "ptest10" is not unique
2025-02-01 03:24:50.250 UTC client backend[26692] pg_regress/create_procedure HINT:  Specify the argument list to select the procedure unambiguously.
2025-02-01 03:24:50.250 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  drop procedure ptest10;
2025-02-01 03:24:50.250 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure name "ptest10" is not unique
2025-02-01 03:24:50.250 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  drop procedure ptest10(int, int, int);
2025-02-01 03:24:50.288 UTC client backend[26686] pg_regress/create_table ERROR:  syntax error at or near "OIDS" at character 29
2025-02-01 03:24:50.288 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH OIDS;
2025-02-01 03:24:50.289 UTC client backend[26686] pg_regress/create_table ERROR:  tables declared WITH OIDS are not supported
2025-02-01 03:24:50.289 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH (oids);
2025-02-01 03:24:50.289 UTC client backend[26686] pg_regress/create_table ERROR:  tables declared WITH OIDS are not supported
2025-02-01 03:24:50.289 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE withoid() WITH (oids = true);
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  version() is not a procedure at character 6
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL version();
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  sum(integer) is not a procedure at character 6
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure HINT:  To call a function, use SELECT.
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL sum(1);
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 40
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx() LANGUAGE SQL WINDOW AS $$ INSERT INTO cp_test VALUES (1, 'a') $$;
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 40
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx() LANGUAGE SQL STRICT AS $$ INSERT INTO cp_test VALUES (1, 'a') $$;
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  VARIADIC parameter must be the last parameter at character 43
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx(a VARIADIC int[], b OUT int) LANGUAGE SQL
	  AS $$ SELECT a[1] $$;
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure OUT parameters cannot appear after one with a default value at character 43
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CREATE PROCEDURE ptestx(a int DEFAULT 42, b OUT int) LANGUAGE SQL
	  AS $$ SELECT a $$;
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  invalid attribute in procedure definition at character 30
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE ptest1(text) STRICT;
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure ERROR:  ptest1(text) is not a function
2025-02-01 03:24:50.305 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  ALTER FUNCTION ptest1(text) VOLATILE;
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure ERROR:  cp_testfunc1(integer) is not a procedure
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE cp_testfunc1(int) VOLATILE;
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  ALTER PROCEDURE nonexistent() VOLATILE;
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure ERROR:  ptest1(text) is not a function
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  DROP FUNCTION ptest1(text);
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure ERROR:  cp_testfunc1(integer) is not a procedure
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  DROP PROCEDURE cp_testfunc1(int);
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure ERROR:  procedure nonexistent() does not exist
2025-02-01 03:24:50.306 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  DROP PROCEDURE nonexistent();
2025-02-01 03:24:50.312 UTC client backend[26692] pg_regress/create_procedure ERROR:  permission denied for procedure ptest1
2025-02-01 03:24:50.312 UTC client backend[26692] pg_regress/create_procedure STATEMENT:  CALL ptest1('a');
2025-02-01 03:24:50.312 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 51
2025-02-01 03:24:50.312 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_column (id int DEFAULT (id));
2025-02-01 03:24:50.329 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 51
2025-02-01 03:24:50.329 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_column (id int DEFAULT (bar.id));
2025-02-01 03:24:50.350 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 59
2025-02-01 03:24:50.350 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg_column (id int DEFAULT (avg(id)));
2025-02-01 03:24:50.351 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in DEFAULT expression at character 58
2025-02-01 03:24:50.351 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_non_column (a int DEFAULT (avg(non_existent)));
2025-02-01 03:24:50.352 UTC client backend[26686] pg_regress/create_table ERROR:  aggregate functions are not allowed in DEFAULT expressions at character 47
2025-02-01 03:24:50.352 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (avg(1)));
2025-02-01 03:24:50.353 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use subquery in DEFAULT expression at character 46
2025-02-01 03:24:50.353 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (select 1));
2025-02-01 03:24:50.354 UTC client backend[26686] pg_regress/create_table ERROR:  set-returning functions are not allowed in DEFAULT expressions at character 47
2025-02-01 03:24:50.354 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE default_expr_agg (a int DEFAULT (generate_series(1,3)));
2025-02-01 03:24:50.392 UTC client backend[26686] pg_regress/create_table ERROR:  cannot create partitioned table as inheritance child
2025-02-01 03:24:50.392 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) INHERITS (some_table) PARTITION BY LIST (a);
2025-02-01 03:24:50.395 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use "list" partition strategy with more than one column
2025-02-01 03:24:50.395 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a1 int,
		a2 int
	) PARTITION BY LIST (a1, a2);
2025-02-01 03:24:50.397 UTC client backend[26686] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition key expressions
2025-02-01 03:24:50.397 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (retset(a));
2025-02-01 03:24:50.399 UTC client backend[26686] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition key expressions
2025-02-01 03:24:50.399 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE ((avg(a)));
2025-02-01 03:24:50.401 UTC client backend[26686] pg_regress/create_table ERROR:  window functions are not allowed in partition key expressions
2025-02-01 03:24:50.401 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE ((avg(a) OVER (PARTITION BY b)));
2025-02-01 03:24:50.401 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use subquery in partition key expression
2025-02-01 03:24:50.401 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY LIST ((a LIKE (SELECT 1)));
2025-02-01 03:24:50.403 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use constant expression as partition key
2025-02-01 03:24:50.403 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE ((42));
2025-02-01 03:24:50.408 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use constant expression as partition key
2025-02-01 03:24:50.408 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (const_func());
2025-02-01 03:24:50.410 UTC client backend[26686] pg_regress/create_table ERROR:  unrecognized partitioning strategy "magic" at character 53
2025-02-01 03:24:50.410 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
	    a int
	) PARTITION BY MAGIC (a);
2025-02-01 03:24:50.411 UTC client backend[26686] pg_regress/create_table ERROR:  column "b" named in partition key does not exist at character 57
2025-02-01 03:24:50.411 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (b);
2025-02-01 03:24:50.416 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use system column "xmin" in partition key at character 57
2025-02-01 03:24:50.416 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (xmin);
2025-02-01 03:24:50.418 UTC client backend[26686] pg_regress/create_table ERROR:  partition key column 1 has pseudo-type record
2025-02-01 03:24:50.418 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE (((a, b)));
2025-02-01 03:24:50.419 UTC client backend[26686] pg_regress/create_table ERROR:  partition key column 2 has pseudo-type unknown
2025-02-01 03:24:50.419 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		b int
	) PARTITION BY RANGE (a, ('unknown'));
2025-02-01 03:24:50.428 UTC client backend[26686] pg_regress/create_table ERROR:  functions in partition key expression must be marked IMMUTABLE
2025-02-01 03:24:50.428 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int
	) PARTITION BY RANGE (immut_func(a));
2025-02-01 03:24:50.437 UTC client backend[26686] pg_regress/create_table ERROR:  data type point has no default operator class for access method "btree"
2025-02-01 03:24:50.437 UTC client backend[26686] pg_regress/create_table HINT:  You must specify a btree operator class or define a default btree operator class for the data type.
2025-02-01 03:24:50.437 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY LIST (a);
2025-02-01 03:24:50.438 UTC client backend[26686] pg_regress/create_table ERROR:  operator class "point_ops" does not exist for access method "btree"
2025-02-01 03:24:50.438 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY LIST (a point_ops);
2025-02-01 03:24:50.440 UTC client backend[26686] pg_regress/create_table ERROR:  data type point has no default operator class for access method "btree"
2025-02-01 03:24:50.440 UTC client backend[26686] pg_regress/create_table HINT:  You must specify a btree operator class or define a default btree operator class for the data type.
2025-02-01 03:24:50.440 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY RANGE (a);
2025-02-01 03:24:50.446 UTC client backend[26686] pg_regress/create_table ERROR:  operator class "point_ops" does not exist for access method "btree"
2025-02-01 03:24:50.446 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a point
	) PARTITION BY RANGE (a point_ops);
2025-02-01 03:24:50.451 UTC client backend[26686] pg_regress/create_table ERROR:  cannot add NO INHERIT constraint to partitioned table "partitioned"
2025-02-01 03:24:50.451 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE partitioned (
		a int,
		CONSTRAINT check_a CHECK (a > 0) NO INHERIT
	) PARTITION BY RANGE (a);
2025-02-01 03:24:50.463 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop function plusone(integer) because other objects depend on it
2025-02-01 03:24:50.463 UTC client backend[26686] pg_regress/create_table DETAIL:  table partitioned depends on function plusone(integer)
2025-02-01 03:24:50.463 UTC client backend[26686] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.463 UTC client backend[26686] pg_regress/create_table STATEMENT:  DROP FUNCTION plusone(int);
2025-02-01 03:24:50.471 UTC client backend[26686] pg_regress/create_table ERROR:  cannot inherit from partitioned table "partitioned2"
2025-02-01 03:24:50.471 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail () INHERITS (partitioned2);
2025-02-01 03:24:50.560 UTC client backend[26686] pg_regress/create_table ERROR:  no partition of relation "partitioned2" found for row
2025-02-01 03:24:50.560 UTC client backend[26686] pg_regress/create_table DETAIL:  Partition key of the failing row contains ((a + 1), substr(b, 1, 5)) = (2, hello).
2025-02-01 03:24:50.560 UTC client backend[26686] pg_regress/create_table STATEMENT:  INSERT INTO partitioned2 VALUES (1, 'hello');
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table STATEMENT:  alter table partitioned drop column a;
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop type intdom1 because other objects depend on it
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table DETAIL:  table partitioned depends on type intdom1
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.590 UTC client backend[26686] pg_regress/create_table STATEMENT:  drop domain intdom1;
2025-02-01 03:24:50.591 UTC client backend[26686] pg_regress/create_table ERROR:  relation "partitioned" does not exist at character 7
2025-02-01 03:24:50.591 UTC client backend[26686] pg_regress/create_table STATEMENT:  table partitioned;
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table STATEMENT:  alter table partitioned drop column a;
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop type intdom1 because other objects depend on it
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table DETAIL:  table partitioned depends on type intdom1
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:50.592 UTC client backend[26686] pg_regress/create_table STATEMENT:  drop domain intdom1;
2025-02-01 03:24:50.593 UTC client backend[26686] pg_regress/create_table ERROR:  relation "partitioned" does not exist at character 7
2025-02-01 03:24:50.593 UTC client backend[26686] pg_regress/create_table STATEMENT:  table partitioned;
2025-02-01 03:24:50.612 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2025-02-01 03:24:50.612 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename);
2025-02-01 03:24:50.613 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2025-02-01 03:24:50.613 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (somename.somename);
2025-02-01 03:24:50.613 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 75
2025-02-01 03:24:50.613 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (a);
2025-02-01 03:24:50.614 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 79
2025-02-01 03:24:50.614 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(a));
2025-02-01 03:24:50.615 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 79
2025-02-01 03:24:50.615 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(somename));
2025-02-01 03:24:50.616 UTC client backend[26686] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition bound at character 75
2025-02-01 03:24:50.616 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (sum(1));
2025-02-01 03:24:50.618 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use subquery in partition bound at character 75
2025-02-01 03:24:50.618 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((select 1));
2025-02-01 03:24:50.623 UTC client backend[26686] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition bound at character 75
2025-02-01 03:24:50.623 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN (generate_series(4, 6));
2025-02-01 03:24:50.624 UTC client backend[26686] pg_regress/create_table ERROR:  collations are not supported by type integer at character 81
2025-02-01 03:24:50.624 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF list_parted FOR VALUES IN ((1+1) collate "POSIX");
2025-02-01 03:24:50.627 UTC client backend[26686] pg_regress/create_table ERROR:  syntax error at or near ")" at character 64
2025-02-01 03:24:50.627 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES IN ();
2025-02-01 03:24:50.627 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a list partition at character 60
2025-02-01 03:24:50.627 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES FROM (1) TO (2);
2025-02-01 03:24:50.628 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a list partition at character 60
2025-02-01 03:24:50.628 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2025-02-01 03:24:50.637 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_default_part" conflicts with existing default partition "part_default" at character 57
2025-02-01 03:24:50.637 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF list_parted DEFAULT;
2025-02-01 03:24:50.638 UTC client backend[26686] pg_regress/create_table ERROR:  specified value cannot be cast to type boolean for column "a" at character 59
2025-02-01 03:24:50.638 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE bools_true PARTITION OF bools FOR VALUES IN (1);
2025-02-01 03:24:50.661 UTC client backend[26686] pg_regress/create_table ERROR:  partition "bigintp_10_2" would overlap partition "bigintp_10" at character 63
2025-02-01 03:24:50.661 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE bigintp_10_2 PARTITION OF bigintp FOR VALUES IN ('10');
2025-02-01 03:24:50.666 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2025-02-01 03:24:50.666 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (somename) TO ('2019-01-01');
2025-02-01 03:24:50.666 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2025-02-01 03:24:50.666 UTC client backend[26686] 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-02-01 03:24:50.671 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 80
2025-02-01 03:24:50.671 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE part_bogus_expr_fail PARTITION OF range_parted
	  FOR VALUES FROM (a) TO ('2019-01-01');
2025-02-01 03:24:50.677 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 84
2025-02-01 03:24:50.677 UTC client backend[26686] 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-02-01 03:24:50.678 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use column reference in partition bound expression at character 84
2025-02-01 03:24:50.678 UTC client backend[26686] 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-02-01 03:24:50.679 UTC client backend[26686] pg_regress/create_table ERROR:  aggregate functions are not allowed in partition bound at character 80
2025-02-01 03:24:50.679 UTC client backend[26686] 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-02-01 03:24:50.682 UTC client backend[26686] pg_regress/create_table ERROR:  cannot use subquery in partition bound at character 80
2025-02-01 03:24:50.682 UTC client backend[26686] 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-02-01 03:24:50.682 UTC client backend[26686] pg_regress/create_table ERROR:  set-returning functions are not allowed in partition bound at character 80
2025-02-01 03:24:50.682 UTC client backend[26686] 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-02-01 03:24:50.683 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2025-02-01 03:24:50.683 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES IN ('a');
2025-02-01 03:24:50.683 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2025-02-01 03:24:50.683 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2025-02-01 03:24:50.684 UTC client backend[26686] pg_regress/create_table ERROR:  FROM must specify exactly one value per partitioning column
2025-02-01 03:24:50.684 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a', 1) TO ('z');
2025-02-01 03:24:50.685 UTC client backend[26686] pg_regress/create_table ERROR:  TO must specify exactly one value per partitioning column
2025-02-01 03:24:50.685 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM ('a') TO ('z', 1);
2025-02-01 03:24:50.685 UTC client backend[26686] pg_regress/create_table ERROR:  cannot specify NULL in range bound
2025-02-01 03:24:50.685 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES FROM (null) TO (maxvalue);
2025-02-01 03:24:50.686 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a range partition at character 61
2025-02-01 03:24:50.686 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted FOR VALUES WITH (MODULUS 10, REMAINDER 1);
2025-02-01 03:24:50.692 UTC client backend[26686] pg_regress/create_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2025-02-01 03:24:50.692 UTC client backend[26686] pg_regress/create_table DETAIL:  The new modulus 25 is not divisible by 10, the modulus of existing partition "hpart_4".
2025-02-01 03:24:50.692 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 25, REMAINDER 3);
2025-02-01 03:24:50.695 UTC client backend[26686] pg_regress/create_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2025-02-01 03:24:50.695 UTC client backend[26686] pg_regress/create_table DETAIL:  The new modulus 150 is not a factor of 200, the modulus of existing partition "hpart_3".
2025-02-01 03:24:50.695 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 150, REMAINDER 3);
2025-02-01 03:24:50.696 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "hpart_4" at character 60
2025-02-01 03:24:50.696 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES WITH (MODULUS 100, REMAINDER 3);
2025-02-01 03:24:50.696 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a hash partition at character 60
2025-02-01 03:24:50.696 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES FROM ('a', 1) TO ('z');
2025-02-01 03:24:50.697 UTC client backend[26686] pg_regress/create_table ERROR:  invalid bound specification for a hash partition at character 60
2025-02-01 03:24:50.697 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted FOR VALUES IN (1000);
2025-02-01 03:24:50.699 UTC client backend[26686] pg_regress/create_table ERROR:  a hash-partitioned table may not have a default partition
2025-02-01 03:24:50.699 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF hash_parted DEFAULT;
2025-02-01 03:24:50.700 UTC client backend[26686] pg_regress/create_table ERROR:  "unparted" is not partitioned
2025-02-01 03:24:50.700 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF unparted FOR VALUES IN ('a');
2025-02-01 03:24:50.707 UTC client backend[26686] pg_regress/create_table ERROR:  "unparted" is not partitioned
2025-02-01 03:24:50.707 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF unparted FOR VALUES WITH (MODULUS 2, REMAINDER 1);
2025-02-01 03:24:50.711 UTC client backend[26686] pg_regress/create_table ERROR:  cannot create a permanent relation as partition of temporary relation "temp_parted"
2025-02-01 03:24:50.711 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF temp_parted FOR VALUES IN ('a');
2025-02-01 03:24:50.717 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part_null_z" at character 65
2025-02-01 03:24:50.717 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN (null);
2025-02-01 03:24:50.717 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part_ab" at character 65
2025-02-01 03:24:50.717 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('b', 'c');
2025-02-01 03:24:50.722 UTC client backend[26686] pg_regress/create_table ERROR:  updated partition constraint for default partition "list_parted2_def" would be violated by some row
2025-02-01 03:24:50.722 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF list_parted2 FOR VALUES IN ('W', 'X', 'Y');
2025-02-01 03:24:50.723 UTC client backend[26686] pg_regress/create_table ERROR:  empty range bound specified for partition "fail_part" at character 68
2025-02-01 03:24:50.723 UTC client backend[26686] pg_regress/create_table DETAIL:  Specified lower bound (1) is greater than or equal to upper bound (0).
2025-02-01 03:24:50.723 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (0);
2025-02-01 03:24:50.724 UTC client backend[26686] pg_regress/create_table ERROR:  empty range bound specified for partition "fail_part" at character 68
2025-02-01 03:24:50.724 UTC client backend[26686] pg_regress/create_table DETAIL:  Specified lower bound (1) is greater than or equal to upper bound (1).
2025-02-01 03:24:50.724 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (1) TO (1);
2025-02-01 03:24:50.726 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part0" at character 68
2025-02-01 03:24:50.726 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (minvalue) TO (2);
2025-02-01 03:24:50.731 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part0" at character 68
2025-02-01 03:24:50.731 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (-1) TO (1);
2025-02-01 03:24:50.732 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part1" at character 68
2025-02-01 03:24:50.732 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (9) TO (maxvalue);
2025-02-01 03:24:50.734 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part2" at character 76
2025-02-01 03:24:50.734 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (30);
2025-02-01 03:24:50.735 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part2" at character 76
2025-02-01 03:24:50.735 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (10) TO (50);
2025-02-01 03:24:50.744 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_default_part" conflicts with existing default partition "range2_default" at character 59
2025-02-01 03:24:50.744 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_default_part PARTITION OF range_parted2 DEFAULT;
2025-02-01 03:24:50.746 UTC client backend[26686] pg_regress/create_table ERROR:  updated partition constraint for default partition "range2_default" would be violated by some row
2025-02-01 03:24:50.746 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted2 FOR VALUES FROM (80) TO (90);
2025-02-01 03:24:50.749 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part00" at character 68
2025-02-01 03:24:50.749 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (0, minvalue) TO (0, 1);
2025-02-01 03:24:50.759 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part12" at character 71
2025-02-01 03:24:50.759 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, 10) TO (1, 20);
2025-02-01 03:24:50.763 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "part10" at character 68
2025-02-01 03:24:50.763 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF range_parted3 FOR VALUES FROM (1, minvalue) TO (1, maxvalue);
2025-02-01 03:24:50.810 UTC client backend[26686] pg_regress/create_table ERROR:  partition "fail_part" would overlap partition "h2part_4" at character 61
2025-02-01 03:24:50.810 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 2, REMAINDER 1);
2025-02-01 03:24:50.813 UTC client backend[26686] pg_regress/create_table ERROR:  modulus for hash partition must be an integer value greater than zero
2025-02-01 03:24:50.813 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 0, REMAINDER 1);
2025-02-01 03:24:50.814 UTC client backend[26686] pg_regress/create_table ERROR:  remainder for hash partition must be less than modulus
2025-02-01 03:24:50.814 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part PARTITION OF hash_parted2 FOR VALUES WITH (MODULUS 8, REMAINDER 8);
2025-02-01 03:24:50.830 UTC client backend[26686] pg_regress/create_table ERROR:  column "b" specified more than once
2025-02-01 03:24:50.830 UTC client backend[26686] 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-02-01 03:24:50.834 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop inherited constraint "check_a" of relation "part_b"
2025-02-01 03:24:50.834 UTC client backend[26686] pg_regress/create_table STATEMENT:  ALTER TABLE part_b DROP CONSTRAINT check_a;
2025-02-01 03:24:50.834 UTC client backend[26686] pg_regress/create_table ERROR:  cannot drop inherited constraint "check_b" of relation "part_b"
2025-02-01 03:24:50.834 UTC client backend[26686] pg_regress/create_table STATEMENT:  ALTER TABLE part_b DROP CONSTRAINT check_b;
2025-02-01 03:24:50.836 UTC client backend[26686] pg_regress/create_table ERROR:  column "c" named in partition key does not exist at character 98
2025-02-01 03:24:50.836 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE fail_part_col_not_found PARTITION OF parted FOR VALUES IN ('c') PARTITION BY RANGE (c);
2025-02-01 03:24:50.842 UTC client backend[26686] pg_regress/create_table ERROR:  null value in column "b" of relation "parted_notnull_inh_test1" violates not-null constraint
2025-02-01 03:24:50.842 UTC client backend[26686] pg_regress/create_table DETAIL:  Failing row contains (1, null).
2025-02-01 03:24:50.842 UTC client backend[26686] pg_regress/create_table STATEMENT:  insert into parted_notnull_inh_test (b) values (null);
2025-02-01 03:24:51.266 UTC client backend[26686] pg_regress/create_table ERROR:  cannot specify storage parameters for a partitioned table
2025-02-01 03:24:51.266 UTC client backend[26686] pg_regress/create_table HINT:  Specify storage parameters for its leaf partitions instead.
2025-02-01 03:24:51.266 UTC client backend[26686] pg_regress/create_table STATEMENT:  CREATE TABLE parted_col_comment (a int, b text) PARTITION BY LIST (a) WITH (fillfactor=100);
2025-02-01 03:24:51.312 UTC client backend[26686] pg_regress/create_table ERROR:  cannot create a permanent relation as partition of temporary relation "temp_parted"
2025-02-01 03:24:51.312 UTC client backend[26686] pg_regress/create_table STATEMENT:  create table perm_part partition of temp_parted default;
2025-02-01 03:24:51.313 UTC client backend[26686] pg_regress/create_table ERROR:  cannot create a temporary relation as partition of permanent relation "perm_parted"
2025-02-01 03:24:51.313 UTC client backend[26686] pg_regress/create_table STATEMENT:  create temp table temp_part partition of perm_parted default;
2025-02-01 03:24:51.321 UTC client backend[26686] 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-02-01 03:24:51.321 UTC client backend[26686] 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-02-01 03:24:51.321 UTC client backend[26686] pg_regress/create_table STATEMENT:  insert into tab_part_create values (1);
2025-02-01 03:24:51.339 UTC client backend[26686] pg_regress/create_table ERROR:  updated partition constraint for default partition "defcheck_def" would be violated by some row
2025-02-01 03:24:51.339 UTC client backend[26686] pg_regress/create_table STATEMENT:  create table defcheck_0 partition of defcheck for values in (0);
2025-02-01 03:24:51.491 UTC client backend[27107] pg_regress/create_index ERROR:  syntax error at or near "ON" at character 28
2025-02-01 03:24:51.491 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops);
2025-02-01 03:24:51.521 UTC client backend[27109] pg_regress/index_including ERROR:  could not create unique index "tbl_include_unique2_idx_unique"
2025-02-01 03:24:51.521 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2025-02-01 03:24:51.521 UTC client backend[27109] 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-02-01 03:24:51.522 UTC client backend[27109] pg_regress/index_including ERROR:  could not create unique index "tbl_include_unique2_c1_c2_c3_c4_key"
2025-02-01 03:24:51.522 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2025-02-01 03:24:51.522 UTC client backend[27109] pg_regress/index_including STATEMENT:  ALTER TABLE tbl_include_unique2 add UNIQUE (c1, c2) INCLUDE (c3, c4);
2025-02-01 03:24:51.533 UTC client backend[27109] pg_regress/index_including ERROR:  could not create unique index "tbl_include_box_pk_pkey"
2025-02-01 03:24:51.533 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) is duplicated.
2025-02-01 03:24:51.533 UTC client backend[27109] pg_regress/index_including STATEMENT:  ALTER TABLE tbl_include_box_pk add PRIMARY KEY (c1, c2) INCLUDE (c3, c4);
2025-02-01 03:24:51.536 UTC client backend[27109] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "covering"
2025-02-01 03:24:51.536 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2025-02-01 03:24:51.536 UTC client backend[27109] 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-02-01 03:24:51.541 UTC client backend[27109] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "covering"
2025-02-01 03:24:51.541 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2025-02-01 03:24:51.541 UTC client backend[27109] 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-02-01 03:24:51.541 UTC client backend[27109] pg_regress/index_including ERROR:  null value in column "c2" of relation "tbl" violates not-null constraint
2025-02-01 03:24:51.541 UTC client backend[27109] pg_regress/index_including DETAIL:  Failing row contains (1, null, 3, (4,4),(4,4)).
2025-02-01 03:24:51.541 UTC client backend[27109] 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-02-01 03:24:51.551 UTC client backend[27113] pg_regress/create_view ERROR:  relation "noview" does not exist
2025-02-01 03:24:51.551 UTC client backend[27113] pg_regress/create_view STATEMENT:  COMMENT ON VIEW noview IS 'no view';
2025-02-01 03:24:51.556 UTC client backend[27109] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_c1_c2_c3_c4_key"
2025-02-01 03:24:51.556 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2025-02-01 03:24:51.556 UTC client backend[27109] 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-02-01 03:24:51.559 UTC client backend[27113] pg_regress/create_view ERROR:  cannot drop constraint view_base_table_pkey on table view_base_table because other objects depend on it
2025-02-01 03:24:51.559 UTC client backend[27113] pg_regress/create_view DETAIL:  view key_dependent_view depends on constraint view_base_table_pkey on table view_base_table
2025-02-01 03:24:51.559 UTC client backend[27113] pg_regress/create_view HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:51.559 UTC client backend[27113] pg_regress/create_view STATEMENT:  ALTER TABLE view_base_table DROP CONSTRAINT view_base_table_pkey;
2025-02-01 03:24:51.559 UTC client backend[27109] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_pkey"
2025-02-01 03:24:51.559 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2025-02-01 03:24:51.559 UTC client backend[27109] 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-02-01 03:24:51.560 UTC client backend[27109] pg_regress/index_including ERROR:  null value in column "c2" of relation "tbl" violates not-null constraint
2025-02-01 03:24:51.560 UTC client backend[27109] pg_regress/index_including DETAIL:  Failing row contains (1, null, 3, (4,4),(4,4)).
2025-02-01 03:24:51.560 UTC client backend[27109] 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-02-01 03:24:51.575 UTC client backend[27109] pg_regress/index_including ERROR:  conflicting key value violates exclusion constraint "tbl_c1_c3_c4_excl"
2025-02-01 03:24:51.575 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1)=(1) conflicts with existing key (c1)=(1).
2025-02-01 03:24:51.575 UTC client backend[27109] 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-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view ERROR:  cannot drop columns from view
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a FROM viewtest_tbl WHERE a <> 20;
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view ERROR:  cannot change name of view column "a" to "?column?"
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view HINT:  Use ALTER VIEW ... RENAME COLUMN ... to change name of view column instead.
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT 1, * FROM viewtest_tbl;
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view ERROR:  cannot change data type of view column "b" from integer to numeric
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b::numeric, c, d FROM viewtest_tbl;
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view ERROR:  cannot change data type of view column "c" from numeric(10,1) to numeric(10,2)
2025-02-01 03:24:51.579 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b, c::numeric(10,2), d FROM viewtest_tbl;
2025-02-01 03:24:51.580 UTC client backend[27113] pg_regress/create_view ERROR:  cannot change collation of view column "d" from "C" to "POSIX"
2025-02-01 03:24:51.580 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE OR REPLACE VIEW viewtest AS
		SELECT a, b, c, d COLLATE "POSIX" FROM viewtest_tbl;
2025-02-01 03:24:51.600 UTC client backend[27113] pg_regress/create_view ERROR:  cannot create temporary relation in non-temporary schema
2025-02-01 03:24:51.600 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE VIEW temp_view_test.v3_temp AS SELECT * FROM temp_table;
2025-02-01 03:24:51.600 UTC client backend[27113] pg_regress/create_view ERROR:  cannot create temporary relation in non-temporary schema
2025-02-01 03:24:51.600 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE SCHEMA test_view_schema
	    CREATE TEMP VIEW testview AS SELECT 1;
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including ERROR:  cannot alter statistics on non-expression column "c1" of index "tbl_idx"
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including HINT:  Alter statistics on table column instead.
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 1 SET STATISTICS 1000;
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including ERROR:  cannot alter statistics on included column "c2" of index "tbl_idx"
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 3 SET STATISTICS 1000;
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including ERROR:  column number 4 of relation "tbl_idx" does not exist
2025-02-01 03:24:51.699 UTC client backend[27109] pg_regress/index_including STATEMENT:  ALTER INDEX tbl_idx ALTER COLUMN 4 SET STATISTICS 1000;
2025-02-01 03:24:51.837 UTC client backend[27113] pg_regress/create_view ERROR:  invalid value for boolean option "security_barrier": 100
2025-02-01 03:24:51.837 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview5 WITH (security_barrier=100)	-- Error
	       AS SELECT * FROM tbl1 WHERE a > 100;
2025-02-01 03:24:51.837 UTC client backend[27113] pg_regress/create_view ERROR:  unrecognized parameter "invalid_option"
2025-02-01 03:24:51.837 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview6 WITH (invalid_option)		-- Error
	       AS SELECT * FROM tbl1 WHERE a < 100;
2025-02-01 03:24:51.851 UTC client backend[27113] pg_regress/create_view ERROR:  invalid value for boolean option "security_invoker": 100
2025-02-01 03:24:51.851 UTC client backend[27113] pg_regress/create_view STATEMENT:  CREATE VIEW mysecview10 WITH (security_invoker=100)	-- Error
	       AS SELECT * FROM tbl1 WHERE a <> 100;
2025-02-01 03:24:51.906 UTC client backend[27109] pg_regress/index_including ERROR:  relation "tbl_c1_c2_c3_c4_key" does not exist
2025-02-01 03:24:51.906 UTC client backend[27109] pg_regress/index_including STATEMENT:  REINDEX INDEX tbl_c1_c2_c3_c4_key;
2025-02-01 03:24:51.925 UTC client backend[27109] pg_regress/index_including ERROR:  access method "brin" does not support included columns
2025-02-01 03:24:51.925 UTC client backend[27109] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING brin(c1, c2) INCLUDE (c3, c4);
2025-02-01 03:24:51.927 UTC client backend[27109] pg_regress/index_including ERROR:  access method "gin" does not support included columns
2025-02-01 03:24:51.927 UTC client backend[27109] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING gin(c1, c2) INCLUDE (c3, c4);
2025-02-01 03:24:51.928 UTC client backend[27109] pg_regress/index_including ERROR:  access method "hash" does not support included columns
2025-02-01 03:24:51.928 UTC client backend[27109] pg_regress/index_including STATEMENT:  CREATE INDEX on tbl USING hash(c1, c2) INCLUDE (c3, c4);
2025-02-01 03:24:51.936 UTC client backend[27107] pg_regress/create_index ERROR:  relation "six_wrong" does not exist
2025-02-01 03:24:51.936 UTC client backend[27107] pg_regress/create_index STATEMENT:  COMMENT ON INDEX six_wrong IS 'bad index';
2025-02-01 03:24:51.963 UTC client backend[27109] pg_regress/index_including ERROR:  duplicate key value violates unique constraint "tbl_idx_unique"
2025-02-01 03:24:51.963 UTC client backend[27109] pg_regress/index_including DETAIL:  Key (c1, c2)=(1, 2) already exists.
2025-02-01 03:24:51.963 UTC client backend[27109] pg_regress/index_including STATEMENT:  UPDATE tbl SET c2 = 2 WHERE c1 = 1;
2025-02-01 03:24:52.480 UTC client backend[27108] pg_regress/index_including_gist ERROR:  conflicting key value violates exclusion constraint "tbl_gist_c4_c1_c2_c3_excl"
2025-02-01 03:24:52.480 UTC client backend[27108] pg_regress/index_including_gist DETAIL:  Key (c4)=((4,5),(2,3)) conflicts with existing key (c4)=((2,3),(1,2)).
2025-02-01 03:24:52.480 UTC client backend[27108] 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-02-01 03:24:52.558 UTC client backend[27113] pg_regress/create_view ERROR:  cannot drop column f3 of table tt14t because other objects depend on it
2025-02-01 03:24:52.558 UTC client backend[27113] pg_regress/create_view DETAIL:  view tt14v depends on column f3 of table tt14t
2025-02-01 03:24:52.558 UTC client backend[27113] pg_regress/create_view HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:52.558 UTC client backend[27113] pg_regress/create_view STATEMENT:  alter table tt14t drop column f3;
2025-02-01 03:24:52.562 UTC client backend[27113] pg_regress/create_view ERROR:  attribute 3 of type record has been dropped
2025-02-01 03:24:52.562 UTC client backend[27113] pg_regress/create_view STATEMENT:  select * from tt14v;
2025-02-01 03:24:52.567 UTC client backend[27113] pg_regress/create_view ERROR:  cannot alter type of a column used by a view or rule
2025-02-01 03:24:52.567 UTC client backend[27113] pg_regress/create_view DETAIL:  rule _RETURN on view tt14v depends on column "f4"
2025-02-01 03:24:52.567 UTC client backend[27113] pg_regress/create_view STATEMENT:  alter table tt14t alter column f4 type integer using f4::integer;
2025-02-01 03:24:52.583 UTC client backend[27113] pg_regress/create_view ERROR:  attribute 4 of type record has wrong type
2025-02-01 03:24:52.583 UTC client backend[27113] pg_regress/create_view DETAIL:  Table has type integer, but query expects text.
2025-02-01 03:24:52.583 UTC client backend[27113] pg_regress/create_view STATEMENT:  select * from tt14v;
2025-02-01 03:24:52.638 UTC client backend[27113] pg_regress/create_view ERROR:  operator does not exist: text = text[] at character 20
2025-02-01 03:24:52.638 UTC client backend[27113] pg_regress/create_view HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:52.638 UTC client backend[27113] pg_regress/create_view STATEMENT:  select 'foo'::text = any((select array['abc','def','foo']::text[]));
2025-02-01 03:24:52.693 UTC client backend[27113] pg_regress/create_view ERROR:  access to non-system view "tt27v" is restricted
2025-02-01 03:24:52.693 UTC client backend[27113] pg_regress/create_view STATEMENT:  select a from tt27v where a > 0;
2025-02-01 03:24:52.693 UTC client backend[27113] pg_regress/create_view ERROR:  access to non-system view "tt27v" is restricted
2025-02-01 03:24:52.693 UTC client backend[27113] pg_regress/create_view STATEMENT:  insert into tt27v values (1);
2025-02-01 03:24:52.900 UTC client backend[27107] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "unique_idx2"
2025-02-01 03:24:52.900 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (i)=(null) already exists.
2025-02-01 03:24:52.900 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO unique_tbl (t) VALUES ('seven');
2025-02-01 03:24:52.902 UTC client backend[27107] pg_regress/create_index ERROR:  could not create unique index "unique_idx4"
2025-02-01 03:24:52.902 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (i)=(null) is duplicated.
2025-02-01 03:24:52.902 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX unique_idx4 ON unique_tbl (i) NULLS NOT DISTINCT;
2025-02-01 03:24:52.968 UTC client backend[27107] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "func_index_index"
2025-02-01 03:24:52.968 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (textcat(f1, f2))=(ABCDEF) already exists.
2025-02-01 03:24:52.968 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO func_index_heap VALUES('ABCD', 'EF');
2025-02-01 03:24:53.008 UTC client backend[27107] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "func_index_index"
2025-02-01 03:24:53.008 UTC client backend[27107] pg_regress/create_index DETAIL:  Key ((f1 || f2))=(ABCDEF) already exists.
2025-02-01 03:24:53.008 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO func_index_heap VALUES('ABCD', 'EF');
2025-02-01 03:24:53.026 UTC client backend[27107] pg_regress/create_index ERROR:  column "row" has pseudo-type record
2025-02-01 03:24:53.026 UTC client backend[27107] pg_regress/create_index STATEMENT:  create index on func_index_heap ((f1 || f2), (row(f1, f2)));
2025-02-01 03:24:53.034 UTC client backend[27107] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "covering_index_index"
2025-02-01 03:24:53.034 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (f1, f2)=(1, 2) already exists.
2025-02-01 03:24:53.034 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO covering_index_heap VALUES(1,2,'BBB');
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index ERROR:  duplicate key value violates unique constraint "concur_index2"
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (f1)=(b) already exists.
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO concur_heap VALUES ('b','x');
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index ERROR:  could not create unique index "concur_index3"
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (f2)=(b) is duplicated.
2025-02-01 03:24:53.081 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2);
2025-02-01 03:24:53.086 UTC client backend[27107] pg_regress/create_index ERROR:  CREATE INDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:53.086 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX CONCURRENTLY concur_index7 ON concur_heap(f1);
2025-02-01 03:24:53.116 UTC client backend[27107] pg_regress/create_index ERROR:  could not create unique index "concur_index3"
2025-02-01 03:24:53.116 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (f2)=(b) is duplicated.
2025-02-01 03:24:53.116 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_heap;
2025-02-01 03:24:53.197 UTC client backend[27107] pg_regress/create_index ERROR:  CREATE INDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:53.197 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX CONCURRENTLY concur_temp_ind ON concur_temp(f1);
2025-02-01 03:24:53.421 UTC client backend[27107] pg_regress/create_index ERROR:  DROP INDEX CONCURRENTLY does not support dropping multiple objects
2025-02-01 03:24:53.421 UTC client backend[27107] pg_regress/create_index STATEMENT:  DROP INDEX CONCURRENTLY "concur_index2", "concur_index3";
2025-02-01 03:24:53.422 UTC client backend[27107] pg_regress/create_index ERROR:  DROP INDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:53.422 UTC client backend[27107] pg_regress/create_index STATEMENT:  DROP INDEX CONCURRENTLY "concur_index5";
2025-02-01 03:24:53.485 UTC client backend[27107] pg_regress/create_index ERROR:  cannot drop index cwi_replaced_pkey because constraint cwi_replaced_pkey on table cwi_test requires it
2025-02-01 03:24:53.485 UTC client backend[27107] pg_regress/create_index HINT:  You can drop constraint cwi_replaced_pkey on table cwi_test instead.
2025-02-01 03:24:53.485 UTC client backend[27107] pg_regress/create_index STATEMENT:  DROP INDEX cwi_replaced_pkey;
2025-02-01 03:24:53.486 UTC client backend[27107] pg_regress/create_index ERROR:  index "cwi_uniq3_idx" column number 1 does not have default sorting behavior at character 26
2025-02-01 03:24:53.486 UTC client backend[27107] pg_regress/create_index DETAIL:  Cannot create a primary key or unique constraint using such an index.
2025-02-01 03:24:53.486 UTC client backend[27107] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq3_idx;
2025-02-01 03:24:53.487 UTC client backend[27107] pg_regress/create_index ERROR:  index "cwi_uniq4_idx" column number 1 does not have default sorting behavior at character 26
2025-02-01 03:24:53.487 UTC client backend[27107] pg_regress/create_index DETAIL:  Cannot create a primary key or unique constraint using such an index.
2025-02-01 03:24:53.487 UTC client backend[27107] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD UNIQUE USING INDEX cwi_uniq4_idx;
2025-02-01 03:24:53.490 UTC client backend[27107] pg_regress/create_index ERROR:  ALTER TABLE / ADD CONSTRAINT USING INDEX is not supported on partitioned tables
2025-02-01 03:24:53.490 UTC client backend[27107] pg_regress/create_index STATEMENT:  alter table cwi_test add primary key using index cwi_test_a_idx ;
2025-02-01 03:24:53.492 UTC client backend[27107] pg_regress/create_index ERROR:  primary keys cannot use NULLS NOT DISTINCT indexes
2025-02-01 03:24:53.492 UTC client backend[27107] pg_regress/create_index STATEMENT:  ALTER TABLE cwi_test ADD PRIMARY KEY USING INDEX cwi_a_nnd;
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index ERROR:  relation "syscolcol_table" does not exist
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscolcol_table (ctid);
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index ERROR:  index creation on system columns is not supported
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscol_table ((ctid >= '(1000,0)'));
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index ERROR:  index creation on system columns is not supported
2025-02-01 03:24:53.494 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE INDEX ON syscol_table (a) WHERE ctid >= '(1000,0)';
2025-02-01 03:24:53.735 UTC client backend[27107] pg_regress/create_index ERROR:  concurrent index creation for exclusion constraints is not supported
2025-02-01 03:24:53.735 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY  concur_reindex_tab3_c2_excl;
2025-02-01 03:24:53.735 UTC client backend[27107] pg_regress/create_index WARNING:  cannot reindex exclusion constraint index "public.concur_reindex_tab3_c2_excl" concurrently, skipping
2025-02-01 03:24:53.737 UTC client backend[27107] pg_regress/create_index ERROR:  conflicting key value violates exclusion constraint "concur_reindex_tab3_c2_excl"
2025-02-01 03:24:53.737 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (c2)=([2,5)) conflicts with existing key (c2)=([1,3)).
2025-02-01 03:24:53.737 UTC client backend[27107] pg_regress/create_index STATEMENT:  INSERT INTO concur_reindex_tab3 VALUES  (4, '[2,4]');
2025-02-01 03:24:53.875 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_index" is not a table or materialized view
2025-02-01 03:24:53.875 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part_index;
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_index" is not a table or materialized view
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_part_index;
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_index_10" is not a table or materialized view
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part_index_10;
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_index_10" is not a table or materialized view
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_part_index_10;
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX INDEX cannot run inside a transaction block
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index CONTEXT:  while reindexing partitioned index "public.concur_reindex_part_index"
2025-02-01 03:24:53.876 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part_index;
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part" is not an index
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part;
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part" is not an index
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_part;
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_10" is not an index
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX concur_reindex_part_10;
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index ERROR:  "concur_reindex_part_10" is not an index
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_part_10;
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX TABLE cannot run inside a transaction block
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index CONTEXT:  while reindexing partitioned table "public.concur_reindex_part"
2025-02-01 03:24:53.898 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE concur_reindex_part;
2025-02-01 03:24:53.928 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:53.928 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY concur_reindex_tab;
2025-02-01 03:24:53.928 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.928 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY pg_class;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY pg_class_oid_index;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE CONCURRENTLY pg_toast.pg_toast_1262;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY pg_toast.pg_toast_1262_index;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX SYSTEM CONCURRENTLY postgres;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX (CONCURRENTLY) SYSTEM postgres;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX (CONCURRENTLY) SYSTEM;
2025-02-01 03:24:53.929 UTC client backend[27107] pg_regress/create_index WARNING:  cannot reindex system catalogs concurrently, skipping all
2025-02-01 03:24:53.930 UTC client backend[27107] pg_regress/create_index ERROR:  can only reindex the currently open database
2025-02-01 03:24:53.930 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX DATABASE not_current_database;
2025-02-01 03:24:53.962 UTC client backend[27107] pg_regress/create_index ERROR:  could not create unique index "concur_reindex_ind5"
2025-02-01 03:24:53.962 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (c1)=(1) is duplicated.
2025-02-01 03:24:53.962 UTC client backend[27107] pg_regress/create_index STATEMENT:  CREATE UNIQUE INDEX CONCURRENTLY concur_reindex_ind5 ON concur_reindex_tab4 (c1);
2025-02-01 03:24:53.963 UTC client backend[27107] pg_regress/create_index ERROR:  could not create unique index "concur_reindex_ind5_ccnew"
2025-02-01 03:24:53.963 UTC client backend[27107] pg_regress/create_index DETAIL:  Key (c1)=(1) is duplicated.
2025-02-01 03:24:53.963 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_reindex_ind5;
2025-02-01 03:24:53.979 UTC client backend[27107] pg_regress/create_index WARNING:  skipping reindex of invalid index "public.concur_reindex_ind5"
2025-02-01 03:24:53.979 UTC client backend[27107] pg_regress/create_index HINT:  Use DROP INDEX or REINDEX INDEX.
2025-02-01 03:24:54.044 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:54.044 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_temp_ind_1;
2025-02-01 03:24:54.118 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:24:54.118 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX CONCURRENTLY concur_temp_ind_3;
2025-02-01 03:24:54.504 UTC client backend[27107] pg_regress/create_index ERROR:  schema "schema_to_reindex" does not exist
2025-02-01 03:24:54.504 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2025-02-01 03:24:54.588 UTC client backend[27107] pg_regress/create_index ERROR:  REINDEX SCHEMA cannot run inside a transaction block
2025-02-01 03:24:54.588 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2025-02-01 03:24:54.611 UTC client backend[27107] pg_regress/create_index ERROR:  must be owner of schema schema_to_reindex
2025-02-01 03:24:54.611 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX SCHEMA schema_to_reindex;
2025-02-01 03:24:54.614 UTC client backend[27107] pg_regress/create_index ERROR:  permission denied for table pg_toast_1262
2025-02-01 03:24:54.614 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX TABLE pg_toast.pg_toast_1262;
2025-02-01 03:24:54.614 UTC client backend[27107] pg_regress/create_index ERROR:  permission denied for index pg_toast_1262_index
2025-02-01 03:24:54.614 UTC client backend[27107] pg_regress/create_index STATEMENT:  REINDEX INDEX pg_toast.pg_toast_1262_index;
2025-02-01 03:24:54.749 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  table "test_exists" does not exist
2025-02-01 03:24:54.749 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TABLE test_exists;
2025-02-01 03:24:54.751 UTC client backend[27621] pg_regress/create_am ERROR:  function int4in(internal) does not exist
2025-02-01 03:24:54.751 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE INDEX HANDLER int4in;
2025-02-01 03:24:54.751 UTC client backend[27621] pg_regress/create_am ERROR:  function heap_tableam_handler must return type index_am_handler
2025-02-01 03:24:54.751 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE INDEX HANDLER heap_tableam_handler;
2025-02-01 03:24:54.753 UTC client backend[27621] pg_regress/create_am ERROR:  data type box has no default operator class for access method "gist2"
2025-02-01 03:24:54.753 UTC client backend[27621] 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-02-01 03:24:54.753 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE INDEX grect2ind2 ON fast_emp4000 USING gist2 (home_base);
2025-02-01 03:24:54.761 UTC client backend[27620] pg_regress/errors ERROR:  relation "nonesuch" does not exist at character 15
2025-02-01 03:24:54.761 UTC client backend[27620] pg_regress/errors STATEMENT:  select * from nonesuch;
2025-02-01 03:24:54.761 UTC client backend[27620] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 8
2025-02-01 03:24:54.761 UTC client backend[27620] pg_regress/errors STATEMENT:  select nonesuch from pg_database;
2025-02-01 03:24:54.762 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "from" at character 17
2025-02-01 03:24:54.762 UTC client backend[27620] pg_regress/errors STATEMENT:  select distinct from pg_database;
2025-02-01 03:24:54.762 UTC client backend[27620] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 33
2025-02-01 03:24:54.762 UTC client backend[27620] pg_regress/errors STATEMENT:  select * from pg_database where nonesuch = pg_database.datname;
2025-02-01 03:24:54.765 UTC client backend[27620] pg_regress/errors ERROR:  column "nonesuch" does not exist at character 55
2025-02-01 03:24:54.765 UTC client backend[27620] pg_regress/errors STATEMENT:  select * from pg_database where pg_database.datname = nonesuch;
2025-02-01 03:24:54.765 UTC client backend[27631] pg_regress/typed_table ERROR:  type "nothing" does not exist at character 25
2025-02-01 03:24:54.765 UTC client backend[27631] pg_regress/typed_table STATEMENT:  CREATE TABLE ttable1 OF nothing;
2025-02-01 03:24:54.765 UTC client backend[27620] pg_regress/errors ERROR:  column "foobar" does not exist at character 21
2025-02-01 03:24:54.765 UTC client backend[27620] pg_regress/errors STATEMENT:  select distinct on (foobar) * from pg_database;
2025-02-01 03:24:54.765 UTC client backend[27625] pg_regress/create_cast ERROR:  function casttestfunc(text) does not exist at character 8
2025-02-01 03:24:54.765 UTC client backend[27625] pg_regress/create_cast HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:54.765 UTC client backend[27625] pg_regress/create_cast STATEMENT:  SELECT casttestfunc('foo'::text);
2025-02-01 03:24:54.766 UTC client backend[27620] pg_regress/errors ERROR:  FOR UPDATE is not allowed with GROUP BY clause
2025-02-01 03:24:54.766 UTC client backend[27620] pg_regress/errors STATEMENT:  select null from pg_database group by datname for update;
2025-02-01 03:24:54.766 UTC client backend[27625] pg_regress/create_cast ERROR:  function casttestfunc(text) does not exist at character 8
2025-02-01 03:24:54.766 UTC client backend[27625] pg_regress/create_cast HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:54.766 UTC client backend[27625] pg_regress/create_cast STATEMENT:  SELECT casttestfunc('foo'::text);
2025-02-01 03:24:54.766 UTC client backend[27620] pg_regress/errors ERROR:  FOR UPDATE is not allowed with GROUP BY clause
2025-02-01 03:24:54.766 UTC client backend[27620] pg_regress/errors STATEMENT:  select null from pg_database group by grouping sets (()) for update;
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 12
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors STATEMENT:  delete from;
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors ERROR:  relation "nonesuch" does not exist at character 13
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors STATEMENT:  delete from nonesuch;
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 11
2025-02-01 03:24:54.767 UTC client backend[27620] pg_regress/errors STATEMENT:  drop table;
2025-02-01 03:24:54.767 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  view "test_view_exists" does not exist
2025-02-01 03:24:54.767 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP VIEW test_view_exists;
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors ERROR:  table "nonesuch" does not exist
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors STATEMENT:  drop table nonesuch;
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 19
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table rename;
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors ERROR:  relation "nonesuch" does not exist
2025-02-01 03:24:54.768 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table nonesuch rename to newnonesuch;
2025-02-01 03:24:54.770 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  view "test_view_exists" does not exist
2025-02-01 03:24:54.770 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP VIEW test_view_exists;
2025-02-01 03:24:54.770 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  index "test_index_exists" does not exist
2025-02-01 03:24:54.770 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP INDEX test_index_exists;
2025-02-01 03:24:54.772 UTC client backend[27620] pg_regress/errors ERROR:  relation "nonesuch" does not exist
2025-02-01 03:24:54.772 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table nonesuch rename to stud_emp;
2025-02-01 03:24:54.772 UTC client backend[27620] pg_regress/errors ERROR:  relation "student" already exists
2025-02-01 03:24:54.772 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table stud_emp rename to student;
2025-02-01 03:24:54.773 UTC client backend[27625] pg_regress/create_cast ERROR:  cannot cast type integer to casttesttype at character 18
2025-02-01 03:24:54.773 UTC client backend[27625] pg_regress/create_cast STATEMENT:  SELECT 1234::int4::casttesttype;
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors ERROR:  relation "stud_emp" already exists
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table stud_emp rename to stud_emp;
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors ERROR:  relation "nonesuchrel" does not exist
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table nonesuchrel rename column nonesuchatt to newnonesuchatt;
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors ERROR:  column "nonesuchatt" does not exist
2025-02-01 03:24:54.775 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table emp rename column nonesuchatt to newnonesuchatt;
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors ERROR:  column "manager" of relation "stud_emp" already exists
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table emp rename column salary to manager;
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors ERROR:  column name "ctid" conflicts with a system column name
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors STATEMENT:  alter table emp rename column salary to ctid;
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors WARNING:  there is no transaction in progress
2025-02-01 03:24:54.778 UTC client backend[27620] pg_regress/errors WARNING:  there is no transaction in progress
2025-02-01 03:24:54.779 UTC client backend[27620] pg_regress/errors ERROR:  function int2um(integer) does not exist
2025-02-01 03:24:54.779 UTC client backend[27620] pg_regress/errors STATEMENT:  create aggregate newavg2 (sfunc = int4pl,
				  basetype = int4,
				  stype = int4,
				  finalfunc = int2um,
				  initcond = '0');
2025-02-01 03:24:54.780 UTC client backend[27620] pg_regress/errors ERROR:  aggregate input type must be specified
2025-02-01 03:24:54.780 UTC client backend[27620] pg_regress/errors STATEMENT:  create aggregate newcnt1 (sfunc = int4inc,
				  stype = int4,
				  initcond = '0');
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 11
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop index;
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "314159" at character 12
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop index 314159;
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  index "nonesuch" does not exist
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop index nonesuch;
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 15
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate;
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 23
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate newcnt1;
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "314159" at character 16
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate 314159 (int);
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors ERROR:  type "nonesuch" does not exist
2025-02-01 03:24:54.781 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate newcnt (nonesuch);
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors ERROR:  aggregate nonesuch(integer) does not exist
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate nonesuch (int4);
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors ERROR:  aggregate newcnt(real) does not exist
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors STATEMENT:  drop aggregate newcnt (float4);
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "(" at character 15
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors STATEMENT:  drop function ();
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "314159" at character 15
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors STATEMENT:  drop function 314159();
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors ERROR:  function nonesuch() does not exist
2025-02-01 03:24:54.782 UTC client backend[27620] pg_regress/errors STATEMENT:  drop function nonesuch();
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 10
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop type;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "314159" at character 11
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop type 314159;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  type "nonesuch" does not exist
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop type nonesuch;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 14
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 21
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator equals;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 18
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator ===;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "," at character 19
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator int4, int4;
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "(" at character 15
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator (int4, int4);
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ")" at character 20
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator === ();
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  missing argument at character 24
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors HINT:  Use NONE to denote the missing argument of a unary operator.
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator === (int4);
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors ERROR:  operator does not exist: integer === integer
2025-02-01 03:24:54.783 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator === (int4, int4);
2025-02-01 03:24:54.784 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  index "test_index_exists" does not exist
2025-02-01 03:24:54.784 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP INDEX test_index_exists;
2025-02-01 03:24:54.784 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  sequence "test_sequence_exists" does not exist
2025-02-01 03:24:54.784 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP SEQUENCE test_sequence_exists;
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors ERROR:  missing argument at character 26
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors HINT:  Use NONE to denote the missing argument of a unary operator.
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator = (nonesuch);
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "," at character 19
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator = ( , int4);
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors ERROR:  type "nonesuch" does not exist
2025-02-01 03:24:54.786 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator = (nonesuch, int4);
2025-02-01 03:24:54.787 UTC client backend[27620] pg_regress/errors ERROR:  type "nonesuch" does not exist
2025-02-01 03:24:54.787 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator = (int4, nonesuch);
2025-02-01 03:24:54.787 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ")" at character 24
2025-02-01 03:24:54.787 UTC client backend[27620] pg_regress/errors STATEMENT:  drop operator = (int4, );
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 10
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop rule;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "314159" at character 11
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop rule 314159;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  relation "noplace" does not exist
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop rule nonesuch on noplace;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "tuple" at character 6
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop tuple rule nonesuch;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "instance" at character 6
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop instance rule nonesuch on noplace;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "rewrite" at character 6
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  drop rewrite rule nonesuch;
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.788 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0;
2025-02-01 03:24:54.789 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  sequence "test_sequence_exists" does not exist
2025-02-01 03:24:54.789 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP SEQUENCE test_sequence_exists;
2025-02-01 03:24:54.789 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  schema "test_schema_exists" does not exist
2025-02-01 03:24:54.789 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP SCHEMA test_schema_exists;
2025-02-01 03:24:54.790 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  schema "test_schema_exists" does not exist
2025-02-01 03:24:54.790 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP SCHEMA test_schema_exists;
2025-02-01 03:24:54.791 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  type "test_type_exists" does not exist
2025-02-01 03:24:54.791 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TYPE test_type_exists;
2025-02-01 03:24:54.791 UTC client backend[27632] pg_regress/constraints ERROR:  syntax error at or near ")" at character 45
2025-02-01 03:24:54.791 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE error_tbl (i int DEFAULT (100, ));
2025-02-01 03:24:54.792 UTC client backend[27632] pg_regress/constraints ERROR:  syntax error at or near "IN" at character 43
2025-02-01 03:24:54.792 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE error_tbl (b1 bool DEFAULT 1 IN (1, 2));
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1::int8/0;
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0::int8;
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.792 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1::int2/0;
2025-02-01 03:24:54.793 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.793 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0::int2;
2025-02-01 03:24:54.793 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.793 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1::numeric/0;
2025-02-01 03:24:54.794 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  type "test_type_exists" does not exist
2025-02-01 03:24:54.794 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TYPE test_type_exists;
2025-02-01 03:24:54.794 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  type "test_domain_exists" does not exist
2025-02-01 03:24:54.794 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP DOMAIN test_domain_exists;
2025-02-01 03:24:54.795 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.795 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0::numeric;
2025-02-01 03:24:54.795 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.795 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1::float8/0;
2025-02-01 03:24:54.797 UTC client backend[27630] pg_regress/create_aggregate ERROR:  aggregate newavg_wrong(integer) does not exist
2025-02-01 03:24:54.797 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  COMMENT ON AGGREGATE newavg_wrong (int4) IS 'an agg comment';
2025-02-01 03:24:54.797 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.797 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0::float8;
2025-02-01 03:24:54.798 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.798 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1::float4/0;
2025-02-01 03:24:54.798 UTC client backend[27620] pg_regress/errors ERROR:  division by zero
2025-02-01 03:24:54.798 UTC client backend[27620] pg_regress/errors STATEMENT:  select 1/0::float4;
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "xxx" at character 1
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors STATEMENT:  xxx;
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "foo" at character 8
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors STATEMENT:  CREATE foo;
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near ";" at character 14
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors STATEMENT:  CREATE TABLE ;
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at end of input at character 13
2025-02-01 03:24:54.799 UTC client backend[27620] pg_regress/errors STATEMENT:  CREATE TABLE
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "foo" at character 29
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors STATEMENT:  INSERT INTO foo VALUES(123) foo;
2025-02-01 03:24:54.800 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  type "test_domain_exists" does not exist
2025-02-01 03:24:54.800 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP DOMAIN test_domain_exists;
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "123" at character 13
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors STATEMENT:  INSERT INTO 123
	VALUES(123);
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "123" at character 29
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors STATEMENT:  INSERT INTO foo
	VALUES(123) 123
	;
2025-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 94
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 90
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 35
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 90
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 100
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.800 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 45
2025-02-01 03:24:54.800 UTC client backend[27620] 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-02-01 03:24:54.801 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 153
2025-02-01 03:24:54.801 UTC client backend[27620] 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-02-01 03:24:54.801 UTC client backend[27620] pg_regress/errors ERROR:  syntax error at or near "NUL" at character 180
2025-02-01 03:24:54.801 UTC client backend[27620] 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-02-01 03:24:54.801 UTC client backend[27622] pg_regress/hash_func ERROR:  could not identify a hash function for type bit varying
2025-02-01 03:24:54.801 UTC client backend[27622] pg_regress/hash_func STATEMENT:  SELECT v as value, hash_array(v)::bit(32) as standard
	FROM   (VALUES ('{101}'::varbit[])) x(v);
2025-02-01 03:24:54.802 UTC client backend[27622] pg_regress/hash_func ERROR:  could not identify an extended hash function for type bit varying
2025-02-01 03:24:54.802 UTC client backend[27622] 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-02-01 03:24:54.803 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_u2" does not exist
2025-02-01 03:24:54.803 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP USER regress_test_u2;
2025-02-01 03:24:54.803 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_u1" does not exist
2025-02-01 03:24:54.803 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP USER regress_test_u1;
2025-02-01 03:24:54.804 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_r2" does not exist
2025-02-01 03:24:54.804 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP ROLE regress_test_r2;
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_r1" does not exist
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP ROLE regress_test_r1;
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_g2" does not exist
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP GROUP regress_test_g2;
2025-02-01 03:24:54.805 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2025-02-01 03:24:54.805 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (3).
2025-02-01 03:24:54.805 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (3);
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  role "regress_test_g1" does not exist
2025-02-01 03:24:54.805 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP GROUP regress_test_g1;
2025-02-01 03:24:54.806 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2025-02-01 03:24:54.806 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (2).
2025-02-01 03:24:54.806 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (2);
2025-02-01 03:24:54.807 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  conversion "test_conversion_exists" does not exist
2025-02-01 03:24:54.807 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP CONVERSION test_conversion_exists;
2025-02-01 03:24:54.807 UTC client backend[27630] pg_regress/create_aggregate ERROR:  aggregate nosuchagg(*) does not exist
2025-02-01 03:24:54.807 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  COMMENT ON AGGREGATE nosuchagg (*) IS 'should fail';
2025-02-01 03:24:54.807 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check_tbl" violates check constraint "check_con"
2025-02-01 03:24:54.807 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (1).
2025-02-01 03:24:54.807 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK_TBL VALUES (1);
2025-02-01 03:24:54.817 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  text search parser "test_tsparser_exists" does not exist
2025-02-01 03:24:54.817 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH PARSER test_tsparser_exists;
2025-02-01 03:24:54.819 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  text search dictionary "test_tsdict_exists" does not exist
2025-02-01 03:24:54.819 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH DICTIONARY test_tsdict_exists;
2025-02-01 03:24:54.821 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  text search template "test_tstemplate_exists" does not exist
2025-02-01 03:24:54.821 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH TEMPLATE test_tstemplate_exists;
2025-02-01 03:24:54.822 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  text search configuration "test_tsconfig_exists" does not exist
2025-02-01 03:24:54.822 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TEXT SEARCH CONFIGURATION test_tsconfig_exists;
2025-02-01 03:24:54.824 UTC client backend[27630] pg_regress/create_aggregate ERROR:  function least_accum(bigint, bigint) requires run-time type coercion
2025-02-01 03:24:54.824 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  create aggregate least_agg(int4) (
	  stype = int8, sfunc = least_accum
	);
2025-02-01 03:24:54.826 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  extension "test_extension_exists" does not exist
2025-02-01 03:24:54.826 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP EXTENSION test_extension_exists;
2025-02-01 03:24:54.827 UTC client backend[27630] pg_regress/create_aggregate ERROR:  function least_accum(bigint, bigint) requires run-time type coercion
2025-02-01 03:24:54.827 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  create aggregate least_agg(int4) (
	  stype = int8, sfunc = least_accum
	);
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  function test_function_exists() does not exist
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_function_exists();
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  function test_function_exists(integer, text, integer[]) does not exist
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_function_exists(int, text, int[]);
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  aggregate test_aggregate_exists(*) does not exist
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP AGGREGATE test_aggregate_exists(*);
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  aggregate test_aggregate_exists(integer) does not exist
2025-02-01 03:24:54.827 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP AGGREGATE test_aggregate_exists(int);
2025-02-01 03:24:54.828 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  operator does not exist: integer @#@ integer
2025-02-01 03:24:54.828 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR @#@ (int, int);
2025-02-01 03:24:54.839 UTC client backend[27621] pg_regress/create_am ERROR:  cannot drop access method gist2 because other objects depend on it
2025-02-01 03:24:54.839 UTC client backend[27621] pg_regress/create_am DETAIL:  index grect2ind2 depends on operator class box_ops for access method gist2
2025-02-01 03:24:54.839 UTC client backend[27621] pg_regress/create_am HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:54.839 UTC client backend[27621] pg_regress/create_am STATEMENT:  DROP ACCESS METHOD gist2;
2025-02-01 03:24:54.840 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  language "test_language_exists" does not exist
2025-02-01 03:24:54.840 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP LANGUAGE test_language_exists;
2025-02-01 03:24:54.841 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  cast from type text to type text does not exist
2025-02-01 03:24:54.841 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP CAST (text AS text);
2025-02-01 03:24:54.841 UTC client backend[27624] pg_regress/create_function_sql ERROR:  only superuser can define a leakproof function
2025-02-01 03:24:54.841 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  ALTER FUNCTION functest_E_2(int) LEAKPROOF;
2025-02-01 03:24:54.841 UTC client backend[27624] pg_regress/create_function_sql ERROR:  only superuser can define a leakproof function
2025-02-01 03:24:54.841 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_E_3(int) RETURNS bool LANGUAGE 'sql'
	       LEAKPROOF AS 'SELECT $1 < 200';
2025-02-01 03:24:54.842 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  trigger "test_trigger_exists" for table "test_exists" does not exist
2025-02-01 03:24:54.842 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON test_exists;
2025-02-01 03:24:54.842 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2025-02-01 03:24:54.842 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (1, x check failed, -2).
2025-02-01 03:24:54.842 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (1, 'x check failed', -2);
2025-02-01 03:24:54.843 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  relation "no_such_table" does not exist
2025-02-01 03:24:54.843 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON no_such_table;
2025-02-01 03:24:54.843 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2025-02-01 03:24:54.843 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (5, z check failed, 10).
2025-02-01 03:24:54.843 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (5, 'z check failed', 10);
2025-02-01 03:24:54.843 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  schema "no_such_schema" does not exist
2025-02-01 03:24:54.843 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TRIGGER test_trigger_exists ON no_such_schema.no_such_table;
2025-02-01 03:24:54.847 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2025-02-01 03:24:54.847 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (0, check failed, -2).
2025-02-01 03:24:54.847 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (0, 'check failed', -2);
2025-02-01 03:24:54.847 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  rule "test_rule_exists" for relation "test_exists" does not exist
2025-02-01 03:24:54.847 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON test_exists;
2025-02-01 03:24:54.848 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  relation "no_such_table" does not exist
2025-02-01 03:24:54.848 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON no_such_table;
2025-02-01 03:24:54.848 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "check2_tbl" violates check constraint "sequence_con"
2025-02-01 03:24:54.848 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (6, check failed, 11).
2025-02-01 03:24:54.848 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO CHECK2_TBL VALUES (6, 'check failed', 11);
2025-02-01 03:24:54.848 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  schema "no_such_schema" does not exist
2025-02-01 03:24:54.848 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP RULE test_rule_exists ON no_such_schema.no_such_table;
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am ERROR:  invalid value for parameter "default_table_access_method": ""
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am DETAIL:  "default_table_access_method" cannot be empty.
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am STATEMENT:  SET default_table_access_method = '';
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am ERROR:  invalid value for parameter "default_table_access_method": "I do not exist AM"
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am DETAIL:  Table access method "I do not exist AM" does not exist.
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am STATEMENT:  SET default_table_access_method = 'I do not exist AM';
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am ERROR:  access method "btree" is not of type TABLE
2025-02-01 03:24:54.849 UTC client backend[27621] pg_regress/create_am STATEMENT:  SET default_table_access_method = 'btree';
2025-02-01 03:24:54.851 UTC client backend[27621] pg_regress/create_am ERROR:  function int4in(internal) does not exist
2025-02-01 03:24:54.851 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE TABLE HANDLER int4in;
2025-02-01 03:24:54.851 UTC client backend[27621] pg_regress/create_am ERROR:  function bthandler must return type table_am_handler
2025-02-01 03:24:54.851 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE ACCESS METHOD bogus TYPE TABLE HANDLER bthandler;
2025-02-01 03:24:54.853 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  foreign-data wrapper "test_fdw_exists" does not exist
2025-02-01 03:24:54.853 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP FOREIGN DATA WRAPPER test_fdw_exists;
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate ERROR:  must specify both or neither of serialization and deserialization functions
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_serialize
	);
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate ERROR:  function numeric_avg_deserialize(internal) does not exist
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_deserialize,
		deserialfunc = numeric_avg_deserialize
	);
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate ERROR:  function numeric_avg_serialize(bytea, internal) does not exist
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE myavg (numeric)
	(
		stype = internal,
		sfunc = numeric_avg_accum,
		serialfunc = numeric_avg_serialize,
		deserialfunc = numeric_avg_serialize
	);
2025-02-01 03:24:54.853 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  server "test_server_exists" does not exist
2025-02-01 03:24:54.853 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP SERVER test_server_exists;
2025-02-01 03:24:54.853 UTC client backend[27630] pg_regress/create_aggregate ERROR:  function int4larger(internal, internal) does not exist
2025-02-01 03:24:54.853 UTC client backend[27630] 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-02-01 03:24:54.854 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  operator class "test_operator_class" does not exist for access method "btree"
2025-02-01 03:24:54.854 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS test_operator_class USING btree;
2025-02-01 03:24:54.855 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2025-02-01 03:24:54.855 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS test_operator_class USING no_such_am;
2025-02-01 03:24:54.856 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2025-02-01 03:24:54.856 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR CLASS IF EXISTS test_operator_class USING no_such_am;
2025-02-01 03:24:54.856 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  operator family "test_operator_family" does not exist for access method "btree"
2025-02-01 03:24:54.856 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY test_operator_family USING btree;
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY test_operator_family USING no_such_am;
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP OPERATOR FAMILY IF EXISTS test_operator_family USING no_such_am;
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  access method "no_such_am" does not exist
2025-02-01 03:24:54.857 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP ACCESS METHOD no_such_am;
2025-02-01 03:24:54.858 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot add column to typed table
2025-02-01 03:24:54.858 UTC client backend[27631] pg_regress/typed_table STATEMENT:  ALTER TABLE persons ADD COLUMN comment text;
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot drop column from typed table
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table STATEMENT:  ALTER TABLE persons DROP COLUMN name;
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot rename column of typed table
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table STATEMENT:  ALTER TABLE persons RENAME COLUMN id TO num;
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot alter column type of typed table at character 34
2025-02-01 03:24:54.860 UTC client backend[27631] pg_regress/typed_table STATEMENT:  ALTER TABLE persons ALTER COLUMN name TYPE varchar;
2025-02-01 03:24:54.863 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  table "test_exists" does not exist
2025-02-01 03:24:54.863 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP TABLE test_exists;
2025-02-01 03:24:54.864 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot change inheritance of typed table
2025-02-01 03:24:54.864 UTC client backend[27631] pg_regress/typed_table STATEMENT:  ALTER TABLE persons INHERIT stuff;
2025-02-01 03:24:54.865 UTC client backend[27631] pg_regress/typed_table ERROR:  column "myname" does not exist
2025-02-01 03:24:54.865 UTC client backend[27631] pg_regress/typed_table STATEMENT:  CREATE TABLE personsx OF person_type (myname WITH OPTIONS NOT NULL);
2025-02-01 03:24:54.865 UTC client backend[27622] pg_regress/hash_func ERROR:  could not identify a hash function for type bit varying
2025-02-01 03:24:54.865 UTC client backend[27622] 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-02-01 03:24:54.866 UTC client backend[27622] pg_regress/hash_func ERROR:  could not identify an extended hash function for type bit varying
2025-02-01 03:24:54.866 UTC client backend[27622] 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-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate ERROR:  cannot change return type of existing function
2025-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate HINT:  Use DROP AGGREGATE myavg(numeric) first.
2025-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE myavg (numeric)
	(
		stype = numeric,
		sfunc = numeric_add,
		finalfunc = numeric_out
	);
2025-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate ERROR:  cannot change routine kind
2025-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate DETAIL:  "myavg" is an ordinary aggregate function.
2025-02-01 03:24:54.874 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE myavg (order by numeric)
	(
		stype = numeric,
		sfunc = numeric_add
	);
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 41
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am STATEMENT:  SELECT INTO tableam_tblselectinto_heap2 USING heap2 FROM tableam_tbl_heap2;
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 32
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE VIEW tableam_view_heap2 USING heap2 AS SELECT * FROM tableam_tbl_heap2;
2025-02-01 03:24:54.879 UTC client backend[27630] pg_regress/create_aggregate ERROR:  cannot change routine kind
2025-02-01 03:24:54.879 UTC client backend[27630] pg_regress/create_aggregate DETAIL:  "sum3" is a function.
2025-02-01 03:24:54.879 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE OR REPLACE AGGREGATE sum3 (int8,int8,int8)
	(
		stype = int8,
		sfunc = sum4
	);
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am ERROR:  syntax error at or near "USING" at character 35
2025-02-01 03:24:54.879 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE SEQUENCE tableam_seq_heap2 USING heap2;
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate ERROR:  parameter "parallel" must be SAFE, RESTRICTED, or UNSAFE
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE mysum (int)
	(
		stype = int,
		sfunc = int4pl,
		parallel = pear
	);
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate ERROR:  strictness of aggregate's forward and inverse transition functions must match
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE invalidsumdouble (float8)
	(
	    stype = float8,
	    sfunc = float8pl,
	    mstype = float8,
	    msfunc = float8pl,
	    minvfunc = float8mi_n
	);
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate ERROR:  return type of inverse transition function float8mi_int is not double precision
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE wrongreturntype (float8)
	(
	    stype = float8,
	    sfunc = float8pl,
	    mstype = float8,
	    msfunc = float8pl,
	    minvfunc = float8mi_int
	);
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Sfunc1" not recognized
2025-02-01 03:24:54.880 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Basetype" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Stype1" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Initcond1" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Parallel" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate ERROR:  aggregate stype must be specified
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate STATEMENT:  CREATE AGGREGATE case_agg ( -- old syntax
		"Sfunc1" = int4pl,
		"Basetype" = int4,
		"Stype1" = int4,
		"Initcond1" = '0',
		"Parallel" = safe
	);
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Stype" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Sfunc" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc_extra" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Finalfunc_modify" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate WARNING:  aggregate attribute "Parallel" not recognized
2025-02-01 03:24:54.881 UTC client backend[27630] pg_regress/create_aggregate ERROR:  aggregate stype must be specified
2025-02-01 03:24:54.881 UTC client backend[27630] 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-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql ERROR:  duplicate function body specified
2025-02-01 03:24:54.883 UTC client backend[27624] 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-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql ERROR:  SQL function with unquoted function body cannot have polymorphic arguments
2025-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_S_xx(x anyarray) RETURNS anyelement
	    LANGUAGE SQL
	    RETURN x[1];
2025-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql ERROR:  operator does not exist: date > integer at character 85
2025-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:24:54.883 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION functest_S_xx(x date) RETURNS boolean
	    LANGUAGE SQL
	    RETURN x > 1;
2025-02-01 03:24:54.885 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.885 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (2, -NULL-, -2).
2025-02-01 03:24:54.885 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,z) VALUES (2, -2);
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  function name "test_ambiguous_funcname" is not unique
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists HINT:  Specify the argument list to select the function unambiguously.
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION test_ambiguous_funcname;
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  function name "test_ambiguous_funcname" is not unique
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists HINT:  Specify the argument list to select the function unambiguously.
2025-02-01 03:24:54.886 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP FUNCTION IF EXISTS test_ambiguous_funcname;
2025-02-01 03:24:54.887 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.887 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (2, Y, -2).
2025-02-01 03:24:54.887 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y) VALUES ('Y');
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  procedure name "test_ambiguous_procname" is not unique
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists HINT:  Specify the argument list to select the procedure unambiguously.
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP PROCEDURE test_ambiguous_procname;
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  procedure name "test_ambiguous_procname" is not unique
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists HINT:  Specify the argument list to select the procedure unambiguously.
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP PROCEDURE IF EXISTS test_ambiguous_procname;
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  routine name "test_ambiguous_procname" is not unique
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists HINT:  Specify the argument list to select the routine unambiguously.
2025-02-01 03:24:54.888 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  DROP ROUTINE IF EXISTS test_ambiguous_procname;
2025-02-01 03:24:54.889 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  database "test_database_exists" does not exist
2025-02-01 03:24:54.889 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  drop database test_database_exists (force);
2025-02-01 03:24:54.889 UTC client backend[27618] pg_regress/drop_if_exists ERROR:  database "test_database_exists" does not exist
2025-02-01 03:24:54.889 UTC client backend[27618] pg_regress/drop_if_exists STATEMENT:  drop database test_database_exists with (force);
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_check"
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (1, -NULL-, -2).
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,z) VALUES (1, -2);
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, -5).
2025-02-01 03:24:54.891 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL VALUES (5, 'check failed', -5);
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_check"
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, 4).
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y,z) VALUES ('check failed', 4);
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (5, check failed, -5).
2025-02-01 03:24:54.892 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(x,y) VALUES (5, 'check failed');
2025-02-01 03:24:54.893 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.893 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (8, Y, -8).
2025-02-01 03:24:54.893 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y) VALUES ('Y');
2025-02-01 03:24:54.894 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "check_fkeys2_pkey_bad" for table "fkeys2" does not exist
2025-02-01 03:24:54.894 UTC client backend[27636] pg_regress/triggers STATEMENT:  COMMENT ON TRIGGER check_fkeys2_pkey_bad ON fkeys2 IS 'wrong';
2025-02-01 03:24:54.902 UTC client backend[27619] pg_regress/inherit ERROR:  null value in column "aa" of relation "z" violates not-null constraint
2025-02-01 03:24:54.902 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (null, text).
2025-02-01 03:24:54.902 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO z VALUES (NULL, 'text');
2025-02-01 03:24:54.909 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "sys_col_check_tbl" violates check constraint "sys_col_check_tbl_check"
2025-02-01 03:24:54.909 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (Olympia, Washington, t, 100).
2025-02-01 03:24:54.909 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO SYS_COL_CHECK_TBL VALUES ('Olympia', 'Washington', true, 100);
2025-02-01 03:24:54.924 UTC client backend[27636] pg_regress/triggers ERROR:  tuple references non-existent key
2025-02-01 03:24:54.924 UTC client backend[27636] pg_regress/triggers DETAIL:  Trigger "check_fkeys2_pkey_exist" found tuple referencing non-existent key in "pkeys".
2025-02-01 03:24:54.924 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into fkeys2 values (70, '5', 3);
2025-02-01 03:24:54.927 UTC client backend[27632] pg_regress/constraints ERROR:  system column "ctid" reference in check constraint is invalid at character 138
2025-02-01 03:24:54.927 UTC client backend[27632] 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-02-01 03:24:54.936 UTC client backend[27636] pg_regress/triggers ERROR:  tuple references non-existent key
2025-02-01 03:24:54.936 UTC client backend[27636] pg_regress/triggers DETAIL:  Trigger "check_fkeys_pkey_exist" found tuple referencing non-existent key in "pkeys".
2025-02-01 03:24:54.936 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into fkeys values (70, '5', 1);
2025-02-01 03:24:54.937 UTC client backend[27636] pg_regress/triggers ERROR:  tuple references non-existent key
2025-02-01 03:24:54.937 UTC client backend[27636] pg_regress/triggers DETAIL:  Trigger "check_fkeys_pkey2_exist" found tuple referencing non-existent key in "fkeys2".
2025-02-01 03:24:54.937 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into fkeys values (60, '6', 4);
2025-02-01 03:24:54.941 UTC client backend[27636] pg_regress/triggers ERROR:  "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys"
2025-02-01 03:24:54.941 UTC client backend[27636] pg_regress/triggers CONTEXT:  SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 "
2025-02-01 03:24:54.941 UTC client backend[27636] pg_regress/triggers STATEMENT:  delete from pkeys where pkey1 = 30 and pkey2 = '3';
2025-02-01 03:24:54.947 UTC client backend[27636] pg_regress/triggers ERROR:  "check_fkeys2_fkey_restrict": tuple is referenced in "fkeys"
2025-02-01 03:24:54.947 UTC client backend[27636] pg_regress/triggers CONTEXT:  SQL statement "delete from fkeys2 where fkey21 = $1 and fkey22 = $2 "
2025-02-01 03:24:54.947 UTC client backend[27636] pg_regress/triggers STATEMENT:  update pkeys set pkey1 = 7, pkey2 = '70' where pkey1 = 50 and pkey2 = '5';
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_child_check"
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (7, -NULL-, -7, 42, 6).
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6);
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_tbl_check"
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (6, -NULL-, -7, 42, 7).
2025-02-01 03:24:54.949 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7);
2025-02-01 03:24:54.957 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_child" violates check constraint "insert_tbl_con"
2025-02-01 03:24:54.957 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (6, check failed, -6, 42, 7).
2025-02-01 03:24:54.957 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7);
2025-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view1"
2025-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing DISTINCT are not automatically updatable.
2025-02-01 03:24:54.979 UTC client backend[27623] 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-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view1;
2025-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view2"
2025-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing GROUP BY are not automatically updatable.
2025-02-01 03:24:54.979 UTC client backend[27623] 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-02-01 03:24:54.979 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view2;
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view3"
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing HAVING are not automatically updatable.
2025-02-01 03:24:54.980 UTC client backend[27623] 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-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view3;
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view4"
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that return aggregate functions are not automatically updatable.
2025-02-01 03:24:54.980 UTC client backend[27623] 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-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view4;
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view5"
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that return window functions are not automatically updatable.
2025-02-01 03:24:54.980 UTC client backend[27623] 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-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view5;
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view6"
2025-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing UNION, INTERSECT, or EXCEPT are not automatically updatable.
2025-02-01 03:24:54.980 UTC client backend[27623] 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-02-01 03:24:54.980 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view6;
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view7"
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing WITH are not automatically updatable.
2025-02-01 03:24:54.981 UTC client backend[27623] 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-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view7 SET a=a+1;
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view8"
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2025-02-01 03:24:54.981 UTC client backend[27623] 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-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view8 SET a=a+1;
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view9"
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2025-02-01 03:24:54.981 UTC client backend[27623] 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-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view9 SET a=a+1;
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view10"
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.981 UTC client backend[27623] 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-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view10 SET a=a+1;
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view11"
2025-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.981 UTC client backend[27623] 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-02-01 03:24:54.981 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view11 SET a=a+1;
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view12"
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.982 UTC client backend[27623] 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-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view12 SET a=a+1;
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view13"
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.982 UTC client backend[27623] 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-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO ro_view13 VALUES (3, 'Row 3');
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view13"
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views HINT:  To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger.
2025-02-01 03:24:54.982 UTC client backend[27623] 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-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view13"
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views HINT:  To enable updating the view using MERGE, provide an INSTEAD OF UPDATE trigger.
2025-02-01 03:24:54.982 UTC client backend[27623] 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-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view13"
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:54.982 UTC client backend[27623] pg_regress/updatable_views HINT:  To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger.
2025-02-01 03:24:54.982 UTC client backend[27623] 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-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "ctid" of view "rw_view14"
2025-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2025-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view14 VALUES (null, 3, 'Row 3');
2025-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "ctid" of view "rw_view14"
2025-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2025-02-01 03:24:54.985 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view14 SET ctid=null WHERE a=3;
2025-02-01 03:24:54.986 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot merge into column "ctid" of view "rw_view14"
2025-02-01 03:24:54.986 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2025-02-01 03:24:54.986 UTC client backend[27623] 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-02-01 03:24:55.003 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test_check"
2025-02-01 03:24:55.003 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (-3).
2025-02-01 03:24:55.003 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST) VALUES (-3);
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "atacc2" violates check constraint "atacc1_test_check"
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (-3, null).
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO ATACC2 (TEST) VALUES (-3);
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test_check"
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (-3, null).
2025-02-01 03:24:55.006 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST) VALUES (-3);
2025-02-01 03:24:55.008 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2025-02-01 03:24:55.008 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.008 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 VALUES (3, 'ROW 3');
2025-02-01 03:24:55.010 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2025-02-01 03:24:55.010 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.010 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 (a) VALUES (3) ON CONFLICT (a) DO UPDATE set upper = 'blarg';
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "upper" of view "rw_view15"
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view15 (a) VALUES (4);
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "upper" of view "rw_view15"
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view15 SET upper='ROW 3' WHERE a=3;
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "upper" of view "rw_view15"
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.011 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view15 SET upper=DEFAULT WHERE a=3;
2025-02-01 03:24:55.012 UTC client backend[27623] pg_regress/updatable_views ERROR:  multiple assignments to same column "a"
2025-02-01 03:24:55.012 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view16 VALUES (3, 'Row 3', 3);
2025-02-01 03:24:55.012 UTC client backend[27623] pg_regress/updatable_views ERROR:  multiple assignments to same column "a"
2025-02-01 03:24:55.012 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view16 SET a=3, aa=-3 WHERE a=3;
2025-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into view "ro_view1"
2025-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing DISTINCT are not automatically updatable.
2025-02-01 03:24:55.013 UTC client backend[27623] 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-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO ro_view17 VALUES (3, 'ROW 3');
2025-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "ro_view18"
2025-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:55.013 UTC client backend[27623] 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-02-01 03:24:55.013 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM ro_view18;
2025-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view19"
2025-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that do not select from a single table or view are not automatically updatable.
2025-02-01 03:24:55.014 UTC client backend[27623] 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-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view19 SET last_value=1000;
2025-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "ro_view20"
2025-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views that return set-returning functions are not automatically updatable.
2025-02-01 03:24:55.014 UTC client backend[27623] 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-02-01 03:24:55.014 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE ro_view20 SET b=upper(b);
2025-02-01 03:24:55.015 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into view "rw_view16"
2025-02-01 03:24:55.015 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2025-02-01 03:24:55.015 UTC client backend[27623] 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-02-01 03:24:55.015 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view16 (a, b) VALUES (3, 'Row 3');
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update view "rw_view16"
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2025-02-01 03:24:55.016 UTC client backend[27623] 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-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view16 SET b='ROW 2' WHERE a=2;
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "rw_view16"
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views with conditional DO INSTEAD rules are not automatically updatable.
2025-02-01 03:24:55.016 UTC client backend[27623] 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-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view16 WHERE a=2;
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot execute MERGE on relation "rw_view16"
2025-02-01 03:24:55.016 UTC client backend[27623] pg_regress/updatable_views DETAIL:  MERGE is not supported for relations with rules.
2025-02-01 03:24:55.016 UTC client backend[27623] 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-02-01 03:24:55.017 UTC client backend[27631] pg_regress/typed_table ERROR:  column "name" specified more than once
2025-02-01 03:24:55.017 UTC client backend[27631] 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-02-01 03:24:55.018 UTC client backend[27631] pg_regress/typed_table ERROR:  cannot drop type person_type because other objects depend on it
2025-02-01 03:24:55.018 UTC client backend[27631] 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-02-01 03:24:55.018 UTC client backend[27631] pg_regress/typed_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:55.018 UTC client backend[27631] pg_regress/typed_table STATEMENT:  DROP TYPE person_type RESTRICT;
2025-02-01 03:24:55.028 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "atacc1" violates check constraint "atacc1_test2_check"
2025-02-01 03:24:55.028 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (null, 3).
2025-02-01 03:24:55.028 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO ATACC1 (TEST2) VALUES (3);
2025-02-01 03:24:55.028 UTC client backend[27631] pg_regress/typed_table ERROR:  type stuff is the row type of another table
2025-02-01 03:24:55.028 UTC client backend[27631] pg_regress/typed_table DETAIL:  A typed table must use a stand-alone composite type created with CREATE TYPE.
2025-02-01 03:24:55.028 UTC client backend[27631] pg_regress/typed_table STATEMENT:  CREATE TABLE persons5 OF stuff;
2025-02-01 03:24:55.032 UTC client backend[27631] pg_regress/typed_table ERROR:  type tt_enum_type is not a composite type
2025-02-01 03:24:55.032 UTC client backend[27631] pg_regress/typed_table STATEMENT:  CREATE TABLE of_tt_enum_type OF tt_enum_type;
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql ERROR:  could not find a function named "functest_b_1"
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  DROP FUNCTION functest_b_1;
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql ERROR:  function name "functest_b_2" is not unique
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql HINT:  Specify the argument list to select the function unambiguously.
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  DROP FUNCTION functest_b_2;
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql ERROR:  cannot change routine kind
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql DETAIL:  "functest1" is a function.
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE OR REPLACE FUNCTION functest1(a int) RETURNS int LANGUAGE SQL WINDOW AS 'SELECT $1';
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql ERROR:  cannot change routine kind
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql DETAIL:  "functest1" is a function.
2025-02-01 03:24:55.035 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE OR REPLACE PROCEDURE functest1(a int) LANGUAGE SQL AS 'SELECT $1';
2025-02-01 03:24:55.036 UTC client backend[27627] pg_regress/vacuum ERROR:  ANALYZE cannot be executed from VACUUM or ANALYZE
2025-02-01 03:24:55.036 UTC client backend[27627] pg_regress/vacuum CONTEXT:  SQL function "do_analyze" statement 1
	SQL function "wrap_do_analyze" statement 1
2025-02-01 03:24:55.036 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE vaccluster;
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql ERROR:  return type mismatch in function declared to return integer
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql DETAIL:  Actual return type is text.
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql CONTEXT:  SQL function "test1"
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT ''not an integer'';';
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql ERROR:  syntax error at or near "not" at character 62
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'not even SQL';
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql ERROR:  return type mismatch in function declared to return integer
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql DETAIL:  Final statement must return exactly one column.
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql CONTEXT:  SQL function "test1"
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT 1, 2, 3;';
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql ERROR:  there is no parameter $2 at character 69
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'SELECT $2;';
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql ERROR:  only one AS item needed for language "sql"
2025-02-01 03:24:55.059 UTC client backend[27624] pg_regress/create_function_sql STATEMENT:  CREATE FUNCTION test1 (int) RETURNS int LANGUAGE SQL
	    AS 'a', 'b';
2025-02-01 03:24:55.071 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:55.071 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (8, try again, -8).
2025-02-01 03:24:55.071 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO INSERT_TBL(y,z) SELECT yd, -8 FROM tmp WHERE yd = 'try again';
2025-02-01 03:24:55.073 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "insert_tbl" violates check constraint "insert_tbl_con"
2025-02-01 03:24:55.073 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (-4, Y, 4).
2025-02-01 03:24:55.073 UTC client backend[27632] pg_regress/constraints STATEMENT:  UPDATE INSERT_TBL SET x = z, z = x;
2025-02-01 03:24:55.094 UTC client backend[27632] pg_regress/constraints ERROR:  new row for relation "copy_tbl" violates check constraint "copy_con"
2025-02-01 03:24:55.094 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (7, check failed, 6).
2025-02-01 03:24:55.094 UTC client backend[27632] pg_regress/constraints CONTEXT:  COPY copy_tbl, line 2: "7	check failed	6"
2025-02-01 03:24:55.094 UTC client backend[27632] pg_regress/constraints STATEMENT:  COPY COPY_TBL FROM '/tmp/cirrus-ci-build/src/test/regress/data/constrf.data';
2025-02-01 03:24:55.111 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "primary_tbl_pkey"
2025-02-01 03:24:55.111 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.111 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL VALUES (1, 'three');
2025-02-01 03:24:55.114 UTC client backend[27632] pg_regress/constraints ERROR:  null value in column "i" of relation "primary_tbl" violates not-null constraint
2025-02-01 03:24:55.114 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (null, six).
2025-02-01 03:24:55.114 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL (t) VALUES ('six');
2025-02-01 03:24:55.115 UTC client backend[27621] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2025-02-01 03:24:55.115 UTC client backend[27621] pg_regress/create_am STATEMENT:  ALTER TABLE heaptable SET ACCESS METHOD heap, SET ACCESS METHOD heap2;
2025-02-01 03:24:55.119 UTC client backend[27621] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2025-02-01 03:24:55.119 UTC client backend[27621] pg_regress/create_am STATEMENT:  ALTER TABLE heaptable SET ACCESS METHOD DEFAULT, SET ACCESS METHOD heap2;
2025-02-01 03:24:55.119 UTC client backend[27621] pg_regress/create_am ERROR:  cannot have multiple SET ACCESS METHOD subcommands
2025-02-01 03:24:55.119 UTC client backend[27621] pg_regress/create_am STATEMENT:  ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap, SET ACCESS METHOD heap2;
2025-02-01 03:24:55.134 UTC client backend[27632] pg_regress/constraints ERROR:  null value in column "i" of relation "primary_tbl" violates not-null constraint
2025-02-01 03:24:55.134 UTC client backend[27632] pg_regress/constraints DETAIL:  Failing row contains (null, six).
2025-02-01 03:24:55.134 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO PRIMARY_TBL (t) VALUES ('six');
2025-02-01 03:24:55.179 UTC client backend[27636] pg_regress/triggers ERROR:  ttdummy (tttest): you cannot change price_on and/or price_off columns (use set_ttdummy)
2025-02-01 03:24:55.179 UTC client backend[27636] pg_regress/triggers STATEMENT:  update tttest set price_on = -1 where price_id = 1;
2025-02-01 03:24:55.181 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.181 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.181 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'three');
2025-02-01 03:24:55.185 UTC client backend[27632] pg_regress/constraints ERROR:  ON CONFLICT DO UPDATE command cannot affect row a second time
2025-02-01 03:24:55.185 UTC client backend[27632] pg_regress/constraints HINT:  Ensure that no rows proposed for insertion within the same command have duplicate constrained values.
2025-02-01 03:24:55.185 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'a'), (2, 'b'), (2, 'b') ON CONFLICT (i) DO UPDATE SET t = 'fails';
2025-02-01 03:24:55.193 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.193 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.193 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'three');
2025-02-01 03:24:55.197 UTC client backend[27627] pg_regress/vacuum ERROR:  ANALYZE cannot be executed from VACUUM or ANALYZE
2025-02-01 03:24:55.197 UTC client backend[27627] pg_regress/vacuum CONTEXT:  SQL function "do_analyze" statement 1
	SQL function "wrap_do_analyze" statement 1
2025-02-01 03:24:55.197 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM FULL vaccluster;
2025-02-01 03:24:55.200 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.200 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(null) already exists.
2025-02-01 03:24:55.200 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL (t) VALUES ('seven');
2025-02-01 03:24:55.215 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_t_key"
2025-02-01 03:24:55.215 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i, t)=(1, one) already exists.
2025-02-01 03:24:55.215 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO UNIQUE_TBL VALUES (1, 'one');
2025-02-01 03:24:55.240 UTC client backend[27619] pg_regress/inherit ERROR:  column "tomorrow" inherits conflicting default values
2025-02-01 03:24:55.240 UTC client backend[27619] pg_regress/inherit HINT:  To resolve the conflict, specify a default explicitly.
2025-02-01 03:24:55.240 UTC client backend[27619] pg_regress/inherit STATEMENT:  CREATE TABLE otherchild () INHERITS (firstparent, thirdparent);
2025-02-01 03:24:55.243 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.243 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.243 UTC client backend[27632] pg_regress/constraints STATEMENT:  UPDATE unique_tbl SET i = 1 WHERE i = 0;
2025-02-01 03:24:55.276 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.276 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2025-02-01 03:24:55.276 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMIT;
2025-02-01 03:24:55.278 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.278 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2025-02-01 03:24:55.278 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO unique_tbl VALUES (3, 'Three');
2025-02-01 03:24:55.282 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.282 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2025-02-01 03:24:55.282 UTC client backend[27632] pg_regress/constraints STATEMENT:  SET CONSTRAINTS ALL IMMEDIATE;
2025-02-01 03:24:55.287 UTC client backend[27621] pg_regress/create_am ERROR:  zero-length delimited identifier at or near """" at character 37
2025-02-01 03:24:55.287 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "";
2025-02-01 03:24:55.292 UTC client backend[27621] pg_regress/create_am ERROR:  access method "i_do_not_exist_am" does not exist
2025-02-01 03:24:55.292 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING i_do_not_exist_am;
2025-02-01 03:24:55.293 UTC client backend[27621] pg_regress/create_am ERROR:  access method "I do not exist AM" does not exist
2025-02-01 03:24:55.293 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "I do not exist AM";
2025-02-01 03:24:55.293 UTC client backend[27621] pg_regress/create_am ERROR:  access method "btree" is not of type TABLE
2025-02-01 03:24:55.293 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE TABLE i_am_a_failure() USING "btree";
2025-02-01 03:24:55.297 UTC client backend[27621] pg_regress/create_am ERROR:  "tableam_parted_a_heap2" is not partitioned
2025-02-01 03:24:55.297 UTC client backend[27621] pg_regress/create_am STATEMENT:  CREATE FOREIGN TABLE fp PARTITION OF tableam_parted_a_heap2 DEFAULT SERVER x;
2025-02-01 03:24:55.300 UTC client backend[27621] pg_regress/create_am ERROR:  cannot drop access method heap2 because other objects depend on it
2025-02-01 03:24:55.300 UTC client backend[27621] 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-02-01 03:24:55.300 UTC client backend[27621] pg_regress/create_am HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:55.300 UTC client backend[27621] pg_regress/create_am STATEMENT:  DROP ACCESS METHOD heap2;
2025-02-01 03:24:55.317 UTC client backend[27636] pg_regress/triggers ERROR:  duplicate trigger events specified at or near "ON" at character 63
2025-02-01 03:24:55.317 UTC client backend[27636] 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-02-01 03:24:55.317 UTC client backend[27636] pg_regress/triggers ERROR:  column "a" specified more than once
2025-02-01 03:24:55.317 UTC client backend[27636] 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-02-01 03:24:55.317 UTC client backend[27636] pg_regress/triggers ERROR:  syntax error at or near "OF" at character 42
2025-02-01 03:24:55.317 UTC client backend[27636] 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-02-01 03:24:55.317 UTC client backend[27636] pg_regress/triggers ERROR:  INSERT trigger's WHEN condition cannot reference OLD values at character 88
2025-02-01 03:24:55.317 UTC client backend[27636] 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-02-01 03:24:55.317 UTC client backend[27636] pg_regress/triggers ERROR:  DELETE trigger's WHEN condition cannot reference NEW values at character 97
2025-02-01 03:24:55.317 UTC client backend[27636] 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-02-01 03:24:55.318 UTC client backend[27636] pg_regress/triggers ERROR:  BEFORE trigger's WHEN condition cannot reference NEW system columns at character 88
2025-02-01 03:24:55.318 UTC client backend[27636] 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-02-01 03:24:55.318 UTC client backend[27636] pg_regress/triggers ERROR:  statement trigger's WHEN condition cannot reference column values at character 90
2025-02-01 03:24:55.318 UTC client backend[27636] 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-02-01 03:24:55.318 UTC client backend[27636] pg_regress/triggers ERROR:  cannot drop column b of table main_table because other objects depend on it
2025-02-01 03:24:55.318 UTC client backend[27636] 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-02-01 03:24:55.318 UTC client backend[27636] pg_regress/triggers HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:24:55.318 UTC client backend[27636] pg_regress/triggers STATEMENT:  ALTER TABLE main_table DROP COLUMN b;
2025-02-01 03:24:55.318 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key"
2025-02-01 03:24:55.318 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.318 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO parted_uniq_tbl VALUES (1);
2025-02-01 03:24:55.323 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "parted_uniq_tbl_1_i_key"
2025-02-01 03:24:55.323 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(1) already exists.
2025-02-01 03:24:55.323 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMIT;
2025-02-01 03:24:55.347 UTC client backend[27619] pg_regress/inherit ERROR:  cannot alter inherited column "f1" of relation "childtab"
2025-02-01 03:24:55.347 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table parent1 alter column f1 type bigint;
2025-02-01 03:24:55.401 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "p2chk" conflicts with inherited constraint on relation "c2"
2025-02-01 03:24:55.401 UTC client backend[27619] pg_regress/inherit STATEMENT:  create table c2 (constraint p2chk check (ff1 > 10) no inherit) inherits (p1);
2025-02-01 03:24:55.451 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.451 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.451 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE INSERT ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row');
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE UPDATE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row');
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE DELETE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row');
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER INSERT ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_ins_row');
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.452 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER UPDATE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_upd_row');
2025-02-01 03:24:55.453 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.453 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have row-level BEFORE or AFTER triggers.
2025-02-01 03:24:55.453 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER DELETE ON main_view
	FOR EACH ROW EXECUTE PROCEDURE trigger_func('before_del_row');
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have TRUNCATE triggers.
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig BEFORE TRUNCATE ON main_view
	EXECUTE PROCEDURE trigger_func('before_tru_row');
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  "main_view" is a view
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers DETAIL:  Views cannot have TRUNCATE triggers.
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig AFTER TRUNCATE ON main_view
	EXECUTE PROCEDURE trigger_func('before_tru_row');
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  "main_table" is a table
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2025-02-01 03:24:55.454 UTC client backend[27636] 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-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  "main_table" is a table
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2025-02-01 03:24:55.454 UTC client backend[27636] 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-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  "main_table" is a table
2025-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2025-02-01 03:24:55.454 UTC client backend[27636] 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-02-01 03:24:55.454 UTC client backend[27636] pg_regress/triggers ERROR:  INSTEAD OF triggers cannot have WHEN conditions
2025-02-01 03:24:55.454 UTC client backend[27636] 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-02-01 03:24:55.455 UTC client backend[27636] pg_regress/triggers ERROR:  INSTEAD OF triggers cannot have column lists
2025-02-01 03:24:55.455 UTC client backend[27636] 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-02-01 03:24:55.455 UTC client backend[27636] pg_regress/triggers ERROR:  INSTEAD OF triggers must be FOR EACH ROW
2025-02-01 03:24:55.455 UTC client backend[27636] pg_regress/triggers STATEMENT:  CREATE TRIGGER invalid_trig INSTEAD OF UPDATE ON main_view
	EXECUTE PROCEDURE view_trigger('instead_of_upd');
2025-02-01 03:24:55.455 UTC client backend[27632] pg_regress/constraints ERROR:  duplicate key value violates unique constraint "unique_tbl_i_key"
2025-02-01 03:24:55.455 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (i)=(3) already exists.
2025-02-01 03:24:55.455 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMIT;
2025-02-01 03:24:55.461 UTC client backend[27632] pg_regress/constraints ERROR:  misplaced ENFORCED clause at character 41
2025-02-01 03:24:55.461 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE UNIQUE_EN_TBL(i int UNIQUE ENFORCED);
2025-02-01 03:24:55.462 UTC client backend[27632] pg_regress/constraints ERROR:  misplaced NOT ENFORCED clause at character 44
2025-02-01 03:24:55.462 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE UNIQUE_NOTEN_TBL(i int UNIQUE NOT ENFORCED);
2025-02-01 03:24:55.462 UTC client backend[27632] pg_regress/constraints ERROR:  ALTER CONSTRAINT statement constraints cannot be marked ENFORCED at character 58
2025-02-01 03:24:55.462 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key ENFORCED;
2025-02-01 03:24:55.463 UTC client backend[27632] pg_regress/constraints ERROR:  ALTER CONSTRAINT statement constraints cannot be marked NOT ENFORCED at character 58
2025-02-01 03:24:55.463 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE unique_tbl ALTER CONSTRAINT unique_tbl_i_key NOT ENFORCED;
2025-02-01 03:24:55.463 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "ac" violates check constraint "ac_check"
2025-02-01 03:24:55.463 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (null).
2025-02-01 03:24:55.463 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into ac (aa) values (NULL);
2025-02-01 03:24:55.464 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "bc" violates check constraint "ac_check"
2025-02-01 03:24:55.464 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (null, null).
2025-02-01 03:24:55.464 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into bc (aa) values (NULL);
2025-02-01 03:24:55.467 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "ac_check" of relation "bc"
2025-02-01 03:24:55.467 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table bc drop constraint ac_check;
2025-02-01 03:24:55.469 UTC client backend[27633] pg_regress/infinite_recurse ERROR:  stack depth limit exceeded
2025-02-01 03:24:55.469 UTC client backend[27633] 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-02-01 03:24:55.469 UTC client backend[27633] pg_regress/infinite_recurse CONTEXT:  SQL function "infinite_recurse" during inlining
	SQL function "infinite_recurse" during startup
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
	SQL function "infinite_recurse" statement 1
2025-02-01 03:24:55.469 UTC client backend[27633] pg_regress/infinite_recurse STATEMENT:  select infinite_recurse();
2025-02-01 03:24:55.474 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "circles_c1_c2_excl"
2025-02-01 03:24:55.474 UTC client backend[27632] 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-02-01 03:24:55.474 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO circles VALUES('<(20,20), 10>', '<(0,0), 4>');
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "ac" violates check constraint "ac_aa_check"
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (null).
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into ac (aa) values (NULL);
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "bc" violates check constraint "ac_aa_check"
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (null, null).
2025-02-01 03:24:55.475 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into bc (aa) values (NULL);
2025-02-01 03:24:55.475 UTC client backend[27632] pg_regress/constraints ERROR:  ON CONFLICT DO UPDATE not supported with exclusion constraints
2025-02-01 03:24:55.475 UTC client backend[27632] 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-02-01 03:24:55.477 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "ac_aa_check" of relation "bc"
2025-02-01 03:24:55.477 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table bc drop constraint ac_aa_check;
2025-02-01 03:24:55.486 UTC client backend[27632] pg_regress/constraints ERROR:  could not create exclusion constraint "circles_c1_c2_excl1"
2025-02-01 03:24:55.486 UTC client backend[27632] 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-02-01 03:24:55.486 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE circles ADD EXCLUDE USING gist
	  (c1 WITH &&, (c2::circle) WITH &&);
2025-02-01 03:24:55.496 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2025-02-01 03:24:55.496 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (f1)=(1) conflicts with existing key (f1)=(1).
2025-02-01 03:24:55.496 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO deferred_excl VALUES(1);
2025-02-01 03:24:55.497 UTC client backend[27632] pg_regress/constraints ERROR:  ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters
2025-02-01 03:24:55.497 UTC client backend[27632] pg_regress/constraints STATEMENT:  INSERT INTO deferred_excl VALUES(1) ON CONFLICT ON CONSTRAINT deferred_excl_con DO NOTHING;
2025-02-01 03:24:55.500 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2025-02-01 03:24:55.500 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (f1)=(2) conflicts with existing key (f1)=(2).
2025-02-01 03:24:55.500 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMIT;
2025-02-01 03:24:55.501 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot execute MERGE on relation "rw_view1"
2025-02-01 03:24:55.501 UTC client backend[27623] pg_regress/updatable_views DETAIL:  MERGE is not supported for relations with rules.
2025-02-01 03:24:55.501 UTC client backend[27623] 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-02-01 03:24:55.502 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting key value violates exclusion constraint "deferred_excl_con"
2025-02-01 03:24:55.502 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (f1)=(3) conflicts with existing key (f1)=(3).
2025-02-01 03:24:55.502 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMIT;
2025-02-01 03:24:55.511 UTC client backend[27632] pg_regress/constraints ERROR:  could not create exclusion constraint "deferred_excl_f1_excl"
2025-02-01 03:24:55.511 UTC client backend[27632] pg_regress/constraints DETAIL:  Key (f1)=(3) conflicts with key (f1)=(3).
2025-02-01 03:24:55.511 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE deferred_excl ADD EXCLUDE (f1 WITH =);
2025-02-01 03:24:55.548 UTC client backend[27619] pg_regress/inherit ERROR:  check constraint "cc" of relation "c1" is violated by some row
2025-02-01 03:24:55.548 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p2 add constraint cc check (f2>0);
2025-02-01 03:24:55.548 UTC client backend[27619] pg_regress/inherit ERROR:  check constraint "p2_f2_check" of relation "c1" is violated by some row
2025-02-01 03:24:55.548 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p2 add check (f2>0);
2025-02-01 03:24:55.552 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "c1" violates check constraint "p2_f2_check"
2025-02-01 03:24:55.552 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (1, -1, 2).
2025-02-01 03:24:55.552 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into c1 values(1,-1,2);
2025-02-01 03:24:55.555 UTC client backend[27627] pg_regress/vacuum ERROR:  parallel workers for vacuum must be between 0 and 1024 at character 9
2025-02-01 03:24:55.555 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL -1) pvactst;
2025-02-01 03:24:55.560 UTC client backend[27627] pg_regress/vacuum ERROR:  VACUUM FULL cannot be performed in parallel
2025-02-01 03:24:55.560 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL 2, FULL TRUE) pvactst;
2025-02-01 03:24:55.560 UTC client backend[27627] pg_regress/vacuum ERROR:  parallel option requires a value between 0 and 1024 at character 9
2025-02-01 03:24:55.560 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (PARALLEL) pvactst;
2025-02-01 03:24:55.566 UTC client backend[27627] pg_regress/vacuum WARNING:  disabling parallel option of vacuum on "tmp" --- cannot vacuum temporary tables in parallel
2025-02-01 03:24:55.579 UTC client backend[27632] pg_regress/constraints ERROR:  constraint "notnull_tbl1_a_not_null" for relation "notnull_tbl1" already exists
2025-02-01 03:24:55.579 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE notnull_tbl1 ADD COLUMN b INT CONSTRAINT notnull_tbl1_a_not_null NOT NULL;
2025-02-01 03:24:55.637 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot delete from view "rw_view1"
2025-02-01 03:24:55.637 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2025-02-01 03:24:55.637 UTC client backend[27623] pg_regress/updatable_views HINT:  To enable deleting from the view using MERGE, provide an INSTEAD OF DELETE trigger.
2025-02-01 03:24:55.637 UTC client backend[27623] 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-02-01 03:24:55.639 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into view "rw_view1"
2025-02-01 03:24:55.639 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Views containing LIMIT or OFFSET are not automatically updatable.
2025-02-01 03:24:55.639 UTC client backend[27623] pg_regress/updatable_views HINT:  To enable inserting into the view using MERGE, provide an INSTEAD OF INSERT trigger.
2025-02-01 03:24:55.639 UTC client backend[27623] 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-02-01 03:24:55.642 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot merge into view "rw_view2"
2025-02-01 03:24:55.642 UTC client backend[27623] pg_regress/updatable_views DETAIL:  MERGE is not supported for views with INSTEAD OF triggers for some actions but not all.
2025-02-01 03:24:55.642 UTC client backend[27623] 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-02-01 03:24:55.642 UTC client backend[27623] 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-02-01 03:24:55.665 UTC client backend[27619] pg_regress/inherit ERROR:  cannot rename inherited column "b"
2025-02-01 03:24:55.665 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inht1 RENAME b TO bb;
2025-02-01 03:24:55.666 UTC client backend[27619] pg_regress/inherit ERROR:  cannot rename inherited column "aa"
2025-02-01 03:24:55.666 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inhts RENAME aa TO aaa;
2025-02-01 03:24:55.672 UTC client backend[27627] pg_regress/vacuum ERROR:  null value in column "i" of relation "vac_truncate_test" violates not-null constraint
2025-02-01 03:24:55.672 UTC client backend[27627] pg_regress/vacuum DETAIL:  Failing row contains (null, null).
2025-02-01 03:24:55.672 UTC client backend[27627] pg_regress/vacuum STATEMENT:  INSERT INTO vac_truncate_test VALUES (1, NULL), (NULL, NULL);
2025-02-01 03:24:55.678 UTC client backend[27636] pg_regress/triggers ERROR:  No such country: "Japon"
2025-02-01 03:24:55.678 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function city_update() line 9 at RAISE
2025-02-01 03:24:55.678 UTC client backend[27636] pg_regress/triggers STATEMENT:  UPDATE city_view SET country_name = 'Japon' WHERE city_name = 'Tokyo';
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0);
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3);
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES ('Row 3', 3.0, 3);
2025-02-01 03:24:55.686 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.686 UTC client backend[27623] 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-02-01 03:24:55.688 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.688 UTC client backend[27623] 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-02-01 03:24:55.689 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.689 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE base_tbl SET b=b;
2025-02-01 03:24:55.691 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.691 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET aa=aa;
2025-02-01 03:24:55.692 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.692 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bb=bb;
2025-02-01 03:24:55.695 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.695 UTC client backend[27623] 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-02-01 03:24:55.697 UTC client backend[27627] pg_regress/vacuum ERROR:  column "a" of relation "vacparted" appears more than once
2025-02-01 03:24:55.697 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM ANALYZE vacparted(a,b,a);
2025-02-01 03:24:55.697 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.697 UTC client backend[27623] 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-02-01 03:24:55.697 UTC client backend[27627] pg_regress/vacuum ERROR:  column "b" of relation "vacparted" appears more than once
2025-02-01 03:24:55.697 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE vacparted(a,b,b);
2025-02-01 03:24:55.697 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.697 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM base_tbl;
2025-02-01 03:24:55.697 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.697 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view1;
2025-02-01 03:24:55.698 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.698 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view2;
2025-02-01 03:24:55.703 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.703 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4);
2025-02-01 03:24:55.704 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.704 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view1 WHERE aa=2;
2025-02-01 03:24:55.705 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.705 UTC client backend[27623] 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-02-01 03:24:55.712 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.712 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO base_tbl VALUES (5, 'Row 5', 5.0);
2025-02-01 03:24:55.713 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.713 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES ('Row 6', 6.0, 6);
2025-02-01 03:24:55.713 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.713 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM base_tbl WHERE a=3;
2025-02-01 03:24:55.714 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.714 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view2 WHERE aa=4;
2025-02-01 03:24:55.715 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.715 UTC client backend[27623] 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-02-01 03:24:55.726 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.726 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1;
2025-02-01 03:24:55.727 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.727 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1 FOR UPDATE;
2025-02-01 03:24:55.727 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.727 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET b = 'foo' WHERE a = 1;
2025-02-01 03:24:55.727 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.727 UTC client backend[27623] 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-02-01 03:24:55.729 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.729 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.729 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.729 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2 FOR UPDATE;
2025-02-01 03:24:55.730 UTC client backend[27619] pg_regress/inherit ERROR:  cannot rename inherited column "b"
2025-02-01 03:24:55.730 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inht1 RENAME b TO bb;
2025-02-01 03:24:55.732 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.732 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM vacparted, does_not_exist;
2025-02-01 03:24:55.732 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.732 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET b = 'bar' WHERE a = 1;
2025-02-01 03:24:55.733 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.733 UTC client backend[27623] 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-02-01 03:24:55.734 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.734 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (FREEZE) does_not_exist, vaccluster;
2025-02-01 03:24:55.734 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.734 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1 FOR UPDATE;
2025-02-01 03:24:55.735 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.735 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET b = 'foo' WHERE a = 1;
2025-02-01 03:24:55.735 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.735 UTC client backend[27623] 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-02-01 03:24:55.735 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.735 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.736 UTC client backend[27627] pg_regress/vacuum ERROR:  column "does_not_exist" of relation "vactst" does not exist
2025-02-01 03:24:55.736 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM ANALYZE vactst (does_not_exist), vacparted (b);
2025-02-01 03:24:55.740 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.740 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2 FOR UPDATE;
2025-02-01 03:24:55.741 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.741 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET b = 'bar' WHERE a = 1;
2025-02-01 03:24:55.741 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.741 UTC client backend[27623] 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-02-01 03:24:55.743 UTC client backend[27627] pg_regress/vacuum ERROR:  ANALYZE option must be specified when a column list is provided
2025-02-01 03:24:55.743 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM FULL vactst, vacparted (a, b), vaccluster (i);
2025-02-01 03:24:55.743 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.743 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2 FOR UPDATE;
2025-02-01 03:24:55.743 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.743 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET b = 'bar' WHERE a = 1;
2025-02-01 03:24:55.744 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.744 UTC client backend[27623] 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-02-01 03:24:55.747 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.747 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE vactst, does_not_exist, vacparted;
2025-02-01 03:24:55.747 UTC client backend[27627] pg_regress/vacuum ERROR:  column "does_not_exist" of relation "vacparted" does not exist
2025-02-01 03:24:55.747 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE vactst (i), vacparted (does_not_exist);
2025-02-01 03:24:55.751 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.751 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2 FOR UPDATE;
2025-02-01 03:24:55.751 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.751 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET b = 'bar' WHERE a = 1;
2025-02-01 03:24:55.756 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.756 UTC client backend[27623] 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-02-01 03:24:55.762 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.762 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1 FOR UPDATE;
2025-02-01 03:24:55.762 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.762 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET b = 'foo' WHERE a = 1;
2025-02-01 03:24:55.763 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.763 UTC client backend[27623] 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-02-01 03:24:55.763 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.763 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2 FOR UPDATE;
2025-02-01 03:24:55.763 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.763 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET b = 'bar' WHERE a = 1;
2025-02-01 03:24:55.764 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.764 UTC client backend[27623] 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-02-01 03:24:55.764 UTC client backend[27627] pg_regress/vacuum WARNING:  VACUUM ONLY of partitioned table "vacparted" has no effect
2025-02-01 03:24:55.783 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.783 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM base_tbl;
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1;
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO base_tbl VALUES (3, 'Row 3', 3.0);
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES ('Row 3', 3.0, 3);
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.785 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE base_tbl SET a=a;
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET bb=bb, cc=cc;
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.786 UTC client backend[27623] 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-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM base_tbl;
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view1;
2025-02-01 03:24:55.786 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.786 UTC client backend[27623] 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-02-01 03:24:55.793 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.793 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE base_tbl SET b=b;
2025-02-01 03:24:55.794 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.794 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE (VERBOSE) does_not_exist;
2025-02-01 03:24:55.794 UTC client backend[27627] pg_regress/vacuum ERROR:  syntax error at or near "arg" at character 22
2025-02-01 03:24:55.794 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE (nonexistent-arg) does_not_exist;
2025-02-01 03:24:55.794 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting not-null constraint names "foo" and "bar"
2025-02-01 03:24:55.794 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial constraint foo not null constraint bar not null);
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum ERROR:  unrecognized ANALYZE option "nonexistentarg" at character 10
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE (nonexistentarg) does_not_exit;
2025-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET aa=aa;
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE (SKIP_LOCKED, VERBOSE) does_not_exist;
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum ERROR:  relation "does_not_exist" does not exist
2025-02-01 03:24:55.795 UTC client backend[27627] pg_regress/vacuum STATEMENT:  ANALYZE (VERBOSE, SKIP_LOCKED) does_not_exist;
2025-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET bb=bb;
2025-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.795 UTC client backend[27623] 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-02-01 03:24:55.795 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.795 UTC client backend[27623] 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-02-01 03:24:55.798 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.798 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4);
2025-02-01 03:24:55.799 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.799 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view1 WHERE aa=2;
2025-02-01 03:24:55.799 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declarations for not-null constraints on column "a"
2025-02-01 03:24:55.799 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial constraint foo not null no inherit constraint foo not null);
2025-02-01 03:24:55.799 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.799 UTC client backend[27623] 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-02-01 03:24:55.800 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:55.800 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int constraint foo not null, constraint foo not null a no inherit);
2025-02-01 03:24:55.802 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.802 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES ('Row 4', 4.0, 4);
2025-02-01 03:24:55.802 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.802 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  DELETE FROM rw_view1 WHERE aa=2;
2025-02-01 03:24:55.803 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.803 UTC client backend[27623] 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-02-01 03:24:55.803 UTC client backend[27636] pg_regress/triggers ERROR:  U9999
2025-02-01 03:24:55.803 UTC client backend[27636] 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-02-01 03:24:55.803 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into depth_a values (1);
2025-02-01 03:24:55.804 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting not-null constraint names "foo" and "bar"
2025-02-01 03:24:55.804 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial constraint foo not null, constraint bar not null a);
2025-02-01 03:24:55.805 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting not-null constraint names "foo" and "bar"
2025-02-01 03:24:55.805 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial, constraint foo not null a, constraint bar not null a);
2025-02-01 03:24:55.815 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:55.815 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial, constraint foo not null a no inherit);
2025-02-01 03:24:55.816 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declarations for not-null constraints on column "a"
2025-02-01 03:24:55.816 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a serial not null no inherit);
2025-02-01 03:24:55.820 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting not-null constraint names "foo" and "foo2"
2025-02-01 03:24:55.820 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (like notnull_tbl1, constraint foo2 not null a);
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declarations for not-null constraints on column "a"
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int primary key constraint foo not null no inherit);
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declarations for not-null constraints on column "a"
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int not null no inherit primary key);
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:55.821 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int primary key, not null a no inherit);
2025-02-01 03:24:55.824 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:55.824 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int, primary key(a), not null a no inherit);
2025-02-01 03:24:55.825 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:55.825 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int generated by default as identity, constraint foo not null a no inherit);
2025-02-01 03:24:55.831 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.831 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1;
2025-02-01 03:24:55.831 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.831 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET aa=aa;
2025-02-01 03:24:55.831 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.831 UTC client backend[27623] 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-02-01 03:24:55.833 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.833 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.833 UTC client backend[27627] pg_regress/vacuum ERROR:  PROCESS_TOAST required with VACUUM FULL
2025-02-01 03:24:55.833 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (PROCESS_TOAST FALSE, FULL) vac_option_tab;
2025-02-01 03:24:55.833 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.833 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.833 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.833 UTC client backend[27623] 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-02-01 03:24:55.835 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.835 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET cc=cc;
2025-02-01 03:24:55.835 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.835 UTC client backend[27623] 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-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.836 UTC client backend[27623] 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-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.836 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.837 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.837 UTC client backend[27623] 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-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.838 UTC client backend[27623] 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-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.838 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.839 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.839 UTC client backend[27623] 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-02-01 03:24:55.840 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.840 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.840 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.840 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.841 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.841 UTC client backend[27623] 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-02-01 03:24:55.841 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.841 UTC client backend[27623] 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-02-01 03:24:55.841 UTC client backend[27632] pg_regress/constraints ERROR:  conflicting NO INHERIT declarations for not-null constraints on column "a"
2025-02-01 03:24:55.841 UTC client backend[27632] pg_regress/constraints STATEMENT:  create table notnull_tbl_fail (a int generated by default as identity not null no inherit);
2025-02-01 03:24:55.841 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.841 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET ccc=ccc;
2025-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.842 UTC client backend[27623] 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-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.842 UTC client backend[27623] 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-02-01 03:24:55.842 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.842 UTC client backend[27623] 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-02-01 03:24:55.846 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.846 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.846 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.846 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.847 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.847 UTC client backend[27623] 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-02-01 03:24:55.847 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.847 UTC client backend[27623] 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-02-01 03:24:55.848 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.848 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view1;
2025-02-01 03:24:55.848 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.848 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET aa=aa;
2025-02-01 03:24:55.848 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.848 UTC client backend[27623] 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-02-01 03:24:55.849 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.849 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.849 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.849 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.849 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.849 UTC client backend[27623] 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-02-01 03:24:55.850 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.850 UTC client backend[27623] 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-02-01 03:24:55.851 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.851 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.851 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.851 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.852 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.852 UTC client backend[27623] 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-02-01 03:24:55.852 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.852 UTC client backend[27623] 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-02-01 03:24:55.853 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.853 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  SELECT * FROM rw_view2;
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET ccc=ccc;
2025-02-01 03:24:55.854 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.854 UTC client backend[27623] 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-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 16777220) vac_option_tab;
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 120) vac_option_tab;
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT option must be 0 or between 128 kB and 16777216 kB
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum HINT:  Value exceeds integer range.
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT 10000000000) vac_option_tab;
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum ERROR:  BUFFER_USAGE_LIMIT cannot be specified for VACUUM FULL
2025-02-01 03:24:55.855 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (BUFFER_USAGE_LIMIT '512 kB', FULL) vac_option_tab;
2025-02-01 03:24:55.856 UTC client backend[27627] pg_regress/vacuum ERROR:  ONLY_DATABASE_STATS cannot be specified with a list of tables
2025-02-01 03:24:55.856 UTC client backend[27627] pg_regress/vacuum STATEMENT:  VACUUM (ONLY_DATABASE_STATS) vactst;
2025-02-01 03:24:55.860 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.860 UTC client backend[27623] 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-02-01 03:24:55.861 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.861 UTC client backend[27623] 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-02-01 03:24:55.863 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.863 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET aaa=aaa;
2025-02-01 03:24:55.864 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.864 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET bbb=bbb;
2025-02-01 03:24:55.865 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:55.865 UTC client backend[27623] 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-02-01 03:24:55.866 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:55.866 UTC client backend[27623] 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-02-01 03:24:55.884 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned", skipping it
2025-02-01 03:24:55.885 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned", skipping it
2025-02-01 03:24:55.885 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned", skipping it
2025-02-01 03:24:55.885 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_class", skipping it
2025-02-01 03:24:55.886 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "pg_class", skipping it
2025-02-01 03:24:55.886 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_class", skipping it
2025-02-01 03:24:55.887 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_authid", skipping it
2025-02-01 03:24:55.887 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "pg_authid", skipping it
2025-02-01 03:24:55.889 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "pg_authid", skipping it
2025-02-01 03:24:55.889 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2025-02-01 03:24:55.889 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.889 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.889 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.890 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.891 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_parted", skipping it
2025-02-01 03:24:55.891 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2025-02-01 03:24:55.891 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.891 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2025-02-01 03:24:55.891 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.892 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2025-02-01 03:24:55.892 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.892 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.893 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.893 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.896 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.898 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.899 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.902 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.902 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.912 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.914 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2025-02-01 03:24:55.914 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.917 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.918 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_parted", skipping it
2025-02-01 03:24:55.918 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.918 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.918 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_parted", skipping it
2025-02-01 03:24:55.919 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.919 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.923 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.923 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.923 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.925 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.925 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2025-02-01 03:24:55.925 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.925 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part1", skipping it
2025-02-01 03:24:55.925 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to analyze "vacowned_part2", skipping it
2025-02-01 03:24:55.928 UTC client backend[27636] pg_regress/triggers ERROR:  tuple to be updated was already modified by an operation triggered by the current command
2025-02-01 03:24:55.928 UTC client backend[27636] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2025-02-01 03:24:55.928 UTC client backend[27636] pg_regress/triggers STATEMENT:  update parent set val1 = 'b' where aid = 1;
2025-02-01 03:24:55.929 UTC client backend[27636] pg_regress/triggers ERROR:  tuple to be updated or deleted was already modified by an operation triggered by the current command
2025-02-01 03:24:55.929 UTC client backend[27636] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2025-02-01 03:24:55.929 UTC client backend[27636] 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-02-01 03:24:55.931 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.932 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.932 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part1", skipping it
2025-02-01 03:24:55.932 UTC client backend[27636] pg_regress/triggers ERROR:  tuple to be deleted was already modified by an operation triggered by the current command
2025-02-01 03:24:55.932 UTC client backend[27636] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2025-02-01 03:24:55.932 UTC client backend[27636] pg_regress/triggers STATEMENT:  delete from parent where aid = 1;
2025-02-01 03:24:55.933 UTC client backend[27627] pg_regress/vacuum WARNING:  permission denied to vacuum "vacowned_part2", skipping it
2025-02-01 03:24:55.933 UTC client backend[27636] pg_regress/triggers ERROR:  tuple to be updated or deleted was already modified by an operation triggered by the current command
2025-02-01 03:24:55.933 UTC client backend[27636] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2025-02-01 03:24:55.933 UTC client backend[27636] pg_regress/triggers STATEMENT:  merge into parent p using (values (1)) as v(id) on p.aid = v.id
	  when matched then delete;
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "ctid" of view "rw_view1"
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that refer to system columns are not updatable.
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES (null, null, 1.1, null);
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "s" of view "rw_view1"
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 (s, c, a) VALUES (null, null, 1.1);
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "s" of view "rw_view1"
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.958 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 (s, c, a) VALUES (default, default, 1.1);
2025-02-01 03:24:55.958 UTC client backend[27632] pg_regress/constraints ERROR:  not-null constraints on partitioned tables cannot be NO INHERIT
2025-02-01 03:24:55.958 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE ATACC1 (a int NOT NULL NO INHERIT) PARTITION BY LIST (a);
2025-02-01 03:24:55.959 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "s" of view "rw_view1"
2025-02-01 03:24:55.959 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.959 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET s = s WHERE a = 1.1;
2025-02-01 03:24:55.959 UTC client backend[27632] pg_regress/constraints ERROR:  not-null constraints on partitioned tables cannot be NO INHERIT
2025-02-01 03:24:55.959 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE ATACC1 (a int, NOT NULL a NO INHERIT) PARTITION BY LIST (a);
2025-02-01 03:24:55.960 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "t" of view "rw_view2"
2025-02-01 03:24:55.960 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.960 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (null, null, null, 1.1, null);
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "s" of view "rw_view1"
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2(s, c, base_a) VALUES (null, null, 1.1);
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "s" of view "rw_view1"
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET s = s WHERE base_a = 1.1;
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "t" of view "rw_view2"
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.961 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET t = t WHERE base_a = 1.1;
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "t" of view "rw_view3"
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view3 VALUES (null, null, null, null);
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "s" of view "rw_view1"
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view3(s) VALUES (null);
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot update column "s" of view "rw_view1"
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:55.965 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view3 SET s = s;
2025-02-01 03:24:55.986 UTC client backend[27632] pg_regress/constraints ERROR:  cannot change NO INHERIT status of NOT NULL constraint "a_is_not_null" on relation "atacc2"
2025-02-01 03:24:55.986 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE ATACC1 ADD CONSTRAINT ditto NOT NULL a;
2025-02-01 03:24:55.995 UTC client backend[27636] pg_regress/triggers ERROR:  tuple to be updated was already modified by an operation triggered by the current command
2025-02-01 03:24:55.995 UTC client backend[27636] pg_regress/triggers HINT:  Consider using an AFTER trigger instead of a BEFORE trigger to propagate changes to other rows.
2025-02-01 03:24:55.995 UTC client backend[27636] pg_regress/triggers STATEMENT:  delete from self_ref_trigger;
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert a non-DEFAULT value into column "idplus1"
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Column "idplus1" is a generated column.
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO base_tbl (id, idplus1) VALUES (5, 6);
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert a non-DEFAULT value into column "idplus1"
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Column "idplus1" is a generated column.
2025-02-01 03:24:56.007 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 (id, idplus1) VALUES (6, 7);
2025-02-01 03:24:56.012 UTC client backend[27632] pg_regress/constraints ERROR:  constraint "blah" for relation "notnull_tbl2" already exists
2025-02-01 03:24:56.012 UTC client backend[27632] pg_regress/constraints STATEMENT:  CREATE TABLE notnull_tbl2 (a INTEGER CONSTRAINT blah NOT NULL, b INTEGER CONSTRAINT blah NOT NULL);
2025-02-01 03:24:56.015 UTC client backend[27632] pg_regress/constraints ERROR:  column "a" is in a primary key
2025-02-01 03:24:56.015 UTC client backend[27632] pg_regress/constraints STATEMENT:  ALTER TABLE notnull_tbl2 ALTER a DROP NOT NULL;
2025-02-01 03:24:56.056 UTC client backend[27636] pg_regress/triggers ERROR:  cannot ALTER TABLE "trigger_ddl_table" because it is being used by active queries in this session
2025-02-01 03:24:56.056 UTC client backend[27636] 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-02-01 03:24:56.056 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into trigger_ddl_table values (1, 42);
2025-02-01 03:24:56.058 UTC client backend[27636] pg_regress/triggers ERROR:  cannot CREATE INDEX "trigger_ddl_table" because it is being used by active queries in this session
2025-02-01 03:24:56.058 UTC client backend[27636] 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-02-01 03:24:56.058 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into trigger_ddl_table values (1, 42);
2025-02-01 03:24:56.080 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (1,black)
2025-02-01 03:24:56.080 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.080 UTC client backend[27636] pg_regress/triggers WARNING:  after insert (new): (1,black)
2025-02-01 03:24:56.080 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (2,red)
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new, modified): (3,"red trig modified")
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers WARNING:  after insert (new): (3,"red trig modified")
2025-02-01 03:24:56.085 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2025-02-01 03:24:56.086 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (3,orange)
2025-02-01 03:24:56.086 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers WARNING:  before update (old): (3,"red trig modified")
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers WARNING:  before update (new): (3,"updated red trig modified")
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers WARNING:  after update (old): (3,"red trig modified")
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers WARNING:  after update (new): (3,"updated red trig modified")
2025-02-01 03:24:56.087 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (4, 3).
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES(4,3);
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (5, null).
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES(5,null);
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (3, -5).
2025-02-01 03:24:56.087 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET b = -5 WHERE a = 3;
2025-02-01 03:24:56.088 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.088 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (10, 10).
2025-02-01 03:24:56.088 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1(a) VALUES (10);
2025-02-01 03:24:56.089 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.089 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (11, 10).
2025-02-01 03:24:56.089 UTC client backend[27623] 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-02-01 03:24:56.089 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.089 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (3, 3).
2025-02-01 03:24:56.089 UTC client backend[27623] 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-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (4,green)
2025-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new, modified): (5,"green trig modified")
2025-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2025-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers WARNING:  after insert (new): (5,"green trig modified")
2025-02-01 03:24:56.090 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (5,purple)
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers WARNING:  before update (old): (5,"green trig modified")
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers WARNING:  before update (new): (5,"updated green trig modified")
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers WARNING:  after update (old): (5,"green trig modified")
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers WARNING:  after update (new): (5,"updated green trig modified")
2025-02-01 03:24:56.092 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (6,white)
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new, modified): (7,"white trig modified")
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers WARNING:  after insert (new): (7,"white trig modified")
2025-02-01 03:24:56.099 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (7,pink)
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers WARNING:  before update (old): (7,"white trig modified")
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 4 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers WARNING:  before update (new): (7,"updated white trig modified")
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 5 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers WARNING:  after update (old): (7,"white trig modified")
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 4 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers WARNING:  after update (new): (7,"updated white trig modified")
2025-02-01 03:24:56.100 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 5 at RAISE
2025-02-01 03:24:56.100 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.100 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-5).
2025-02-01 03:24:56.100 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (-5);
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (15).
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (15);
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-5).
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET a = a - 10;
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (15).
2025-02-01 03:24:56.101 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET a = a + 10;
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new): (8,yellow)
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 7 at RAISE
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers WARNING:  before insert (new, modified): (9,"yellow trig modified")
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_before_func() line 11 at RAISE
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers WARNING:  after insert (new): (9,"yellow trig modified")
2025-02-01 03:24:56.106 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function upsert_after_func() line 7 at RAISE
2025-02-01 03:24:56.109 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_check_constraint7" conflicts with NOT ENFORCED constraint on relation "p1_c1"
2025-02-01 03:24:56.109 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1 add constraint inh_check_constraint7 check (f1 < 10) enforced;
2025-02-01 03:24:56.117 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_check_constraint8" conflicts with NOT ENFORCED constraint on relation "p1_c1"
2025-02-01 03:24:56.117 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1_c1 add constraint inh_check_constraint8 check (f1 < 10) not enforced;
2025-02-01 03:24:56.117 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.117 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (20).
2025-02-01 03:24:56.117 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (20);
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views ERROR:  invalid value for enum option "check_option": here
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Valid values are "local" and "cascaded".
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  ALTER VIEW rw_view1 SET (check_option=here);
2025-02-01 03:24:56.118 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_check_constraint2" conflicts with NOT ENFORCED constraint on relation "p1_fail"
2025-02-01 03:24:56.118 UTC client backend[27619] pg_regress/inherit STATEMENT:  create table p1_fail(f1 int constraint inh_check_constraint2 check (f1 < 10) not enforced) inherits(p1);
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-20).
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (-20);
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (30).
2025-02-01 03:24:56.118 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (30);
2025-02-01 03:24:56.131 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_check_constraint6" conflicts with NOT ENFORCED constraint on relation "p1_fail"
2025-02-01 03:24:56.131 UTC client backend[27619] pg_regress/inherit STATEMENT:  create table p1_fail(f1 int constraint inh_check_constraint6 check (f1 < 10) not enforced) inherits(p1, p1_c1);
2025-02-01 03:24:56.139 UTC client backend[27636] pg_regress/triggers ERROR:  "my_view" is a view
2025-02-01 03:24:56.139 UTC client backend[27636] pg_regress/triggers DETAIL:  Triggers on views cannot have transition tables.
2025-02-01 03:24:56.139 UTC client backend[27636] 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-02-01 03:24:56.145 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.145 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-3).
2025-02-01 03:24:56.145 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view3 VALUES (-3);
2025-02-01 03:24:56.149 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.149 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (10, {4,5}).
2025-02-01 03:24:56.149 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES (10, ARRAY[4,5]);
2025-02-01 03:24:56.150 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.150 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (1, {-1,-2,3}).
2025-02-01 03:24:56.150 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET b[1] = -b[1] WHERE a = 1;
2025-02-01 03:24:56.156 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "p1_a_check" conflicts with NOT ENFORCED constraint on child table "p1_c1"
2025-02-01 03:24:56.156 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1_c1 inherit p1;
2025-02-01 03:24:56.157 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.157 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (10, {4,5}).
2025-02-01 03:24:56.157 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  EXECUTE ins(10, ARRAY[4,5]);
2025-02-01 03:24:56.162 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.162 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (15).
2025-02-01 03:24:56.162 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES (15);
2025-02-01 03:24:56.163 UTC client backend[27636] pg_regress/triggers ERROR:  "parted_trig" is a table
2025-02-01 03:24:56.163 UTC client backend[27636] pg_regress/triggers DETAIL:  Tables cannot have INSTEAD OF triggers.
2025-02-01 03:24:56.163 UTC client backend[27636] pg_regress/triggers STATEMENT:  create trigger failed instead of update on parted_trig
	  for each row execute procedure trigger_nothing();
2025-02-01 03:24:56.163 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.163 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (15).
2025-02-01 03:24:56.163 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET a = a + 5;
2025-02-01 03:24:56.164 UTC client backend[27636] pg_regress/triggers ERROR:  "parted_trig" is a partitioned table
2025-02-01 03:24:56.164 UTC client backend[27636] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported on partitioned tables.
2025-02-01 03:24:56.164 UTC client backend[27636] 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-02-01 03:24:56.167 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c1"
2025-02-01 03:24:56.167 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1_c1 drop constraint f1_pos;
2025-02-01 03:24:56.179 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.179 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (15, 10).
2025-02-01 03:24:56.179 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view1 VALUES (15, 20);
2025-02-01 03:24:56.183 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view1"
2025-02-01 03:24:56.183 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (20, 10).
2025-02-01 03:24:56.183 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view1 SET a = 20, b = 30;
2025-02-01 03:24:56.193 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.193 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-5).
2025-02-01 03:24:56.193 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO rw_view2 VALUES (-5);
2025-02-01 03:24:56.193 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.193 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-5).
2025-02-01 03:24:56.193 UTC client backend[27623] 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-02-01 03:24:56.199 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.199 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-5).
2025-02-01 03:24:56.199 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE rw_view2 SET a = a - 10;
2025-02-01 03:24:56.200 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "rw_view2"
2025-02-01 03:24:56.200 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-4).
2025-02-01 03:24:56.200 UTC client backend[27623] 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-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart1 because trigger trg1 on table trigpart requires it
2025-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2025-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart1;
2025-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart2 because trigger trg1 on table trigpart requires it
2025-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2025-02-01 03:24:56.223 UTC client backend[27636] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart2;
2025-02-01 03:24:56.224 UTC client backend[27636] pg_regress/triggers ERROR:  cannot drop trigger trg1 on table trigpart3 because trigger trg1 on table trigpart requires it
2025-02-01 03:24:56.224 UTC client backend[27636] pg_regress/triggers HINT:  You can drop trigger trg1 on table trigpart instead.
2025-02-01 03:24:56.224 UTC client backend[27636] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart3;
2025-02-01 03:24:56.299 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "trg1" for table "trigpart3" does not exist
2025-02-01 03:24:56.299 UTC client backend[27636] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart3;
2025-02-01 03:24:56.299 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c2"
2025-02-01 03:24:56.299 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1_c2 drop constraint f1_pos;
2025-02-01 03:24:56.300 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "f1_pos" of relation "p1_c1c2"
2025-02-01 03:24:56.300 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table p1_c1c2 drop constraint f1_pos;
2025-02-01 03:24:56.302 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "trg1" for table "trigpart41" does not exist
2025-02-01 03:24:56.302 UTC client backend[27636] pg_regress/triggers STATEMENT:  drop trigger trg1 on trigpart41;
2025-02-01 03:24:56.322 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_check_constraint" conflicts with NOT VALID constraint on relation "invalid_check_con_child"
2025-02-01 03:24:56.322 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table invalid_check_con add constraint inh_check_constraint check(f1 > 0);
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "invalid_check_con" violates check constraint "inh_check_constraint"
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0).
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into invalid_check_con values(0);
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "invalid_check_con_child" violates check constraint "inh_check_constraint"
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0).
2025-02-01 03:24:56.341 UTC client backend[27619] pg_regress/inherit STATEMENT:  insert into invalid_check_con_child values(0);
2025-02-01 03:24:56.361 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "trg1" for relation "trigpart3" already exists
2025-02-01 03:24:56.361 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter table trigpart attach partition trigpart3 FOR VALUES FROM (2000) to (3000);
2025-02-01 03:24:56.395 UTC client backend[27632] pg_regress/constraints ERROR:  column "a" of relation "cnn_part1" contains null values
2025-02-01 03:24:56.395 UTC client backend[27632] pg_regress/constraints STATEMENT:  alter table cnn2_parted add primary key (a);
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "v1"
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-2, minus two, 20).
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO v2 VALUES (-2, 'minus two', 20);
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "v2"
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (3, three, 30).
2025-02-01 03:24:56.515 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO v2 VALUES (3, 'three', 30);
2025-02-01 03:24:56.517 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "v1"
2025-02-01 03:24:56.517 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-1, ONE, 10).
2025-02-01 03:24:56.517 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE v2 SET a = -1 WHERE a = 1;
2025-02-01 03:24:56.522 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "v2"
2025-02-01 03:24:56.522 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (1, ONE, 30).
2025-02-01 03:24:56.522 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  UPDATE v2 SET c = 30 WHERE a = 1;
2025-02-01 03:24:56.553 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "v1"
2025-02-01 03:24:56.553 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (-1, invalid).
2025-02-01 03:24:56.553 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  INSERT INTO v1 VALUES (-1, 'invalid');
2025-02-01 03:24:56.597 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "uv_ptv_wco"
2025-02-01 03:24:56.597 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (1, 2, null).
2025-02-01 03:24:56.597 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into uv_ptv_wco values (1, 2);
2025-02-01 03:24:56.598 UTC client backend[27623] pg_regress/updatable_views ERROR:  MERGE command cannot affect row a second time
2025-02-01 03:24:56.598 UTC client backend[27623] pg_regress/updatable_views HINT:  Ensure that not more than one source row matches any one target row.
2025-02-01 03:24:56.598 UTC client backend[27623] 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-02-01 03:24:56.599 UTC client backend[27623] pg_regress/updatable_views ERROR:  no partition of relation "uv_pt1" found for row
2025-02-01 03:24:56.599 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Partition key of the failing row contains (b) = (5).
2025-02-01 03:24:56.599 UTC client backend[27623] 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-02-01 03:24:56.623 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "wcowrtest_v"
2025-02-01 03:24:56.623 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (1).
2025-02-01 03:24:56.623 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into wcowrtest_v values (1);
2025-02-01 03:24:56.642 UTC client backend[27623] pg_regress/updatable_views ERROR:  new row violates check option for view "wcowrtest_v2"
2025-02-01 03:24:56.642 UTC client backend[27623] pg_regress/updatable_views DETAIL:  Failing row contains (2, no such row in sometable).
2025-02-01 03:24:56.642 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into wcowrtest_v2 values (2, 'no such row in sometable');
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints ERROR:  constraint "no_constraint" for table "constraint_comments_tbl" does not exist
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT no_constraint ON constraint_comments_tbl IS 'yes, the comment';
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints ERROR:  constraint "no_constraint" for domain constraint_comments_dom does not exist
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT no_constraint ON DOMAIN constraint_comments_dom IS 'yes, another comment';
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints ERROR:  relation "no_comments_tbl" does not exist
2025-02-01 03:24:56.682 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON no_comments_tbl IS 'bad comment';
2025-02-01 03:24:56.683 UTC client backend[27632] pg_regress/constraints ERROR:  type "no_comments_dom" does not exist
2025-02-01 03:24:56.683 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON DOMAIN no_comments_dom IS 'another bad comment';
2025-02-01 03:24:56.684 UTC client backend[27632] pg_regress/constraints ERROR:  must be owner of relation constraint_comments_tbl
2025-02-01 03:24:56.684 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON constraint_comments_tbl IS 'no, the comment';
2025-02-01 03:24:56.684 UTC client backend[27632] pg_regress/constraints ERROR:  must be owner of type constraint_comments_dom
2025-02-01 03:24:56.684 UTC client backend[27632] pg_regress/constraints STATEMENT:  COMMENT ON CONSTRAINT the_constraint ON DOMAIN constraint_comments_dom IS 'no, another comment';
2025-02-01 03:24:56.715 UTC client backend[27623] pg_regress/updatable_views ERROR:  cannot insert into column "cc" of view "uv_iocu_view"
2025-02-01 03:24:56.715 UTC client backend[27623] pg_regress/updatable_views DETAIL:  View columns that are not columns of their base relation are not updatable.
2025-02-01 03:24:56.715 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into uv_iocu_view (aa) values (1)
	   on conflict (aa) do update set cc = 'XXX';
2025-02-01 03:24:56.734 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:56.734 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into rw_view1 values ('yyy',2.0,1)
	  on conflict (aa) do update set bb = excluded.cc;
2025-02-01 03:24:56.734 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:56.734 UTC client backend[27623] 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-02-01 03:24:56.739 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:56.739 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into rw_view1 values ('zzz',2.0,1)
	  on conflict (aa) do update set cc = 3.0;
2025-02-01 03:24:56.745 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for table base_tbl
2025-02-01 03:24:56.745 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into rw_view2 (aa,bb) values (1,'xxx')
	  on conflict (aa) do update set bb = excluded.bb;
2025-02-01 03:24:56.754 UTC client backend[27623] pg_regress/updatable_views ERROR:  permission denied for view rw_view1
2025-02-01 03:24:56.754 UTC client backend[27623] pg_regress/updatable_views STATEMENT:  insert into rw_view4 (aa,bb) values (1,'yyy')
	  on conflict (aa) do update set bb = excluded.bb;
2025-02-01 03:24:56.784 UTC client backend[27619] pg_regress/inherit ERROR:  cannot define not-null constraint on column "a2" with NO INHERIT
2025-02-01 03:24:56.784 UTC client backend[27619] pg_regress/inherit DETAIL:  The column has an inherited not-null constraint.
2025-02-01 03:24:56.784 UTC client backend[27619] pg_regress/inherit STATEMENT:  create table cc3 (a2 int not null no inherit) inherits (cc1);
2025-02-01 03:24:56.785 UTC client backend[27619] pg_regress/inherit ERROR:  cannot change NO INHERIT status of NOT NULL constraint "nn" on relation "cc2"
2025-02-01 03:24:56.785 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table cc2 add not null a2 no inherit;
2025-02-01 03:24:56.785 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "nn" of relation "cc2"
2025-02-01 03:24:56.785 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table cc2 alter column a2 drop not null;
2025-02-01 03:24:56.799 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "pp1_f1_not_null" of relation "cc2"
2025-02-01 03:24:56.799 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table cc2 alter column f1 drop not null;
2025-02-01 03:24:56.837 UTC client backend[27619] pg_regress/inherit ERROR:  cannot drop inherited constraint "pp1_f1_not_null" of relation "cc1"
2025-02-01 03:24:56.837 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table cc1 alter column f1 drop not null;
2025-02-01 03:24:56.882 UTC client backend[27636] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2025-02-01 03:24:56.882 UTC client backend[27636] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1_1".
2025-02-01 03:24:56.882 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'uno uno v2');
2025-02-01 03:24:56.885 UTC client backend[27636] pg_regress/triggers ERROR:  no partition of relation "parted" found for row
2025-02-01 03:24:56.885 UTC client backend[27636] pg_regress/triggers DETAIL:  Partition key of the failing row contains (a) = (2).
2025-02-01 03:24:56.885 UTC client backend[27636] pg_regress/triggers STATEMENT:  update parted set c = c || 'v3';
2025-02-01 03:24:56.888 UTC client backend[27636] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2025-02-01 03:24:56.888 UTC client backend[27636] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1_1".
2025-02-01 03:24:56.888 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'uno uno v4');
2025-02-01 03:24:56.896 UTC client backend[27636] pg_regress/triggers ERROR:  no partition of relation "parted_1" found for row
2025-02-01 03:24:56.896 UTC client backend[27636] pg_regress/triggers DETAIL:  Partition key of the failing row contains (b) = (2).
2025-02-01 03:24:56.896 UTC client backend[27636] pg_regress/triggers STATEMENT:  update parted set c = c || 'v5';
2025-02-01 03:24:57.014 UTC client backend[27636] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2025-02-01 03:24:57.014 UTC client backend[27636] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_1".
2025-02-01 03:24:57.014 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into parted values (1, 1, 'one fail');
2025-02-01 03:24:57.019 UTC client backend[27636] pg_regress/triggers ERROR:  moving row to another partition during a BEFORE FOR EACH ROW trigger is not supported
2025-02-01 03:24:57.019 UTC client backend[27636] pg_regress/triggers DETAIL:  Before executing trigger "t", the row was to be in partition "public.parted_2".
2025-02-01 03:24:57.019 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into parted values (1, 2, 'two fail');
2025-02-01 03:24:57.039 UTC client backend[27619] 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-02-01 03:24:57.039 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inh_nn_parent ADD CONSTRAINT nna NOT NULL a;
2025-02-01 03:24:57.039 UTC client backend[27619] 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-02-01 03:24:57.039 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inh_nn_parent ALTER a SET NOT NULL;
2025-02-01 03:24:57.047 UTC client backend[27619] pg_regress/inherit ERROR:  cannot change NO INHERIT status of NOT NULL constraint "foo" on relation "inh_nn_lvl3"
2025-02-01 03:24:57.047 UTC client backend[27619] pg_regress/inherit STATEMENT:  ALTER TABLE inh_nn_lvl1 ADD PRIMARY KEY (a);
2025-02-01 03:24:57.049 UTC client backend[27619] pg_regress/inherit ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:57.049 UTC client backend[27619] pg_regress/inherit STATEMENT:  CREATE TABLE inh_nn1 (a int primary key, b int, not null a no inherit);
2025-02-01 03:24:57.051 UTC client backend[27619] pg_regress/inherit ERROR:  cannot define not-null constraint on column "a" with NO INHERIT
2025-02-01 03:24:57.051 UTC client backend[27619] pg_regress/inherit DETAIL:  The column has an inherited not-null constraint.
2025-02-01 03:24:57.051 UTC client backend[27619] pg_regress/inherit STATEMENT:  CREATE TABLE inh_nn2 (a int not null no inherit) INHERITS (inh_nn1);
2025-02-01 03:24:57.052 UTC client backend[27619] pg_regress/inherit ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:57.052 UTC client backend[27619] pg_regress/inherit STATEMENT:  CREATE TABLE inh_nn3 (a int not null, b int,  not null a no inherit);
2025-02-01 03:24:57.053 UTC client backend[27619] pg_regress/inherit ERROR:  conflicting NO INHERIT declaration for not-null constraint on column "a"
2025-02-01 03:24:57.053 UTC client backend[27619] pg_regress/inherit STATEMENT:  CREATE TABLE inh_nn4 (a int not null no inherit, b int,  not null a);
2025-02-01 03:24:57.055 UTC client backend[27619] pg_regress/inherit ERROR:  table "inh_nn2" does not exist
2025-02-01 03:24:57.055 UTC client backend[27619] pg_regress/inherit STATEMENT:  DROP TABLE inh_nn1, inh_nn2, inh_nn3, inh_nn4;
2025-02-01 03:24:57.063 UTC client backend[27619] pg_regress/inherit ERROR:  column "f1" in child table "inh_child2" must be marked NOT NULL
2025-02-01 03:24:57.063 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table inh_child2 inherit inh_child1;
2025-02-01 03:24:57.184 UTC client backend[27619] pg_regress/inherit ERROR:  column "a" in child table "inh_child" must be marked NOT NULL
2025-02-01 03:24:57.184 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table inh_child inherit inh_parent;
2025-02-01 03:24:57.187 UTC client backend[27619] pg_regress/inherit ERROR:  constraint "inh_child_a_not_null" conflicts with non-inherited constraint on child table "inh_child"
2025-02-01 03:24:57.187 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table inh_child inherit inh_parent;
2025-02-01 03:24:57.260 UTC client backend[27619] pg_regress/inherit ERROR:  must be owner of table inh_child
2025-02-01 03:24:57.260 UTC client backend[27619] pg_regress/inherit STATEMENT:  alter table inh_parent alter a drop not null;
2025-02-01 03:24:57.276 UTC client backend[27619] pg_regress/inherit ERROR:  cannot inherit from temporary relation "inh_temp_parent"
2025-02-01 03:24:57.276 UTC client backend[27619] pg_regress/inherit STATEMENT:  create table inh_perm_child () inherits (inh_temp_parent);
2025-02-01 03:24:57.624 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.624 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.624 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (1);
2025-02-01 03:24:57.699 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.699 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.699 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (1);
2025-02-01 03:24:57.700 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.700 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.700 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (11);
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (21);
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.703 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (30);
2025-02-01 03:24:57.704 UTC client backend[27636] pg_regress/triggers ERROR:  except
2025-02-01 03:24:57.704 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function tgf() line 1 at RAISE
2025-02-01 03:24:57.704 UTC client backend[27636] pg_regress/triggers STATEMENT:  INSERT INTO trgfire VALUES (40);
2025-02-01 03:24:57.704 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2025-02-01 03:24:57.704 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 10).
2025-02-01 03:24:57.704 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', '10');
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 10).
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', '10');
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 10).
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', '10');
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_fastdef" violates not-null constraint
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0, 1, null).
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '1', NULL);
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_plaindef" violates not-null constraint
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 1, null).
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '1', NULL);
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit ERROR:  null value in column "data" of relation "errtst_child_reorder" violates not-null constraint
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 1, null).
2025-02-01 03:24:57.708 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '1', NULL);
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "shdata_small"
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0, 5, 5).
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ( '0', '5', '5');
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "shdata_small"
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 5, 5).
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('10', '5', '5');
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "shdata_small"
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 5, 5).
2025-02-01 03:24:57.709 UTC client backend[27619] pg_regress/inherit STATEMENT:  INSERT INTO errtst_parent(partid, shdata, data) VALUES ('20', '5', '5');
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 15).
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 0;
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 15).
2025-02-01 03:24:57.719 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 10;
2025-02-01 03:24:57.721 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2025-02-01 03:24:57.721 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 15).
2025-02-01 03:24:57.721 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET data = data + 10 WHERE partid = 20;
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates partition constraint
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 5).
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_child_fastdef SET partid = partid + 10 WHERE partid = 0;
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates partition constraint
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 5).
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_child_plaindef SET partid = partid + 10 WHERE partid = 10;
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates partition constraint
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (5, 1, 30).
2025-02-01 03:24:57.727 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_child_reorder SET partid = partid + 10 WHERE partid = 20;
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_plaindef" violates check constraint "errtst_child_plaindef_data_check"
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (10, 1, 15).
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 10, data = data + 10 WHERE partid = 0;
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_reorder" violates check constraint "errtst_child_reorder_data_check"
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (20, 1, 15).
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 20, data = data + 10 WHERE partid = 10;
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit ERROR:  new row for relation "errtst_child_fastdef" violates check constraint "errtest_child_fastdef_data_check"
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit DETAIL:  Failing row contains (0, 1, 15).
2025-02-01 03:24:57.729 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 0, data = data + 10 WHERE partid = 20;
2025-02-01 03:24:57.730 UTC client backend[27619] pg_regress/inherit ERROR:  no partition of relation "errtst_parent" found for row
2025-02-01 03:24:57.730 UTC client backend[27619] pg_regress/inherit DETAIL:  Partition key of the failing row contains (partid) = (30).
2025-02-01 03:24:57.730 UTC client backend[27619] pg_regress/inherit STATEMENT:  UPDATE errtst_parent SET partid = 30, data = data + 10 WHERE partid = 20;
2025-02-01 03:24:57.886 UTC client backend[27636] pg_regress/triggers ERROR:  ROW triggers with transition tables are not supported on partitions
2025-02-01 03:24:57.886 UTC client backend[27636] 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-02-01 03:24:57.888 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "child_row_trig" prevents table "child" from becoming a partition
2025-02-01 03:24:57.888 UTC client backend[27636] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported on partitions.
2025-02-01 03:24:57.888 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter table parent attach partition child for values in ('AAA');
2025-02-01 03:24:58.037 UTC client backend[27636] pg_regress/triggers ERROR:  ROW triggers with transition tables are not supported on inheritance children
2025-02-01 03:24:58.037 UTC client backend[27636] 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-02-01 03:24:58.039 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "child_row_trig" prevents table "child" from becoming an inheritance child
2025-02-01 03:24:58.039 UTC client backend[27636] pg_regress/triggers DETAIL:  ROW triggers with transition tables are not supported in inheritance hierarchies.
2025-02-01 03:24:58.039 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter table child inherit parent;
2025-02-01 03:24:58.154 UTC client backend[27636] pg_regress/triggers ERROR:  transition tables cannot be specified for triggers with more than one event
2025-02-01 03:24:58.154 UTC client backend[27636] 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-02-01 03:24:58.163 UTC client backend[27636] pg_regress/triggers ERROR:  transition tables cannot be specified for triggers with column lists
2025-02-01 03:24:58.163 UTC client backend[27636] 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-02-01 03:24:58.188 UTC client backend[27636] pg_regress/triggers ERROR:  transition table "new_table" cannot be referenced in a persistent object
2025-02-01 03:24:58.188 UTC client backend[27636] 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-02-01 03:24:58.188 UTC client backend[27636] pg_regress/triggers STATEMENT:  insert into my_table values (42);
2025-02-01 03:24:58.861 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "my_trig" for relation "my_table" already exists
2025-02-01 03:24:58.861 UTC client backend[27636] pg_regress/triggers STATEMENT:  create trigger my_trig
	  before insert on my_table
	  for each row execute procedure funcB();
2025-02-01 03:24:59.064 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "my_trig" for relation "parted_trig_1" is an internal or a child trigger
2025-02-01 03:24:59.064 UTC client backend[27636] pg_regress/triggers STATEMENT:  create or replace trigger my_trig
	  after insert on parted_trig_1
	  for each row execute procedure funcB();
2025-02-01 03:24:59.107 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "my_trig" for relation "parted_trig_1" already exists
2025-02-01 03:24:59.107 UTC client backend[27636] pg_regress/triggers STATEMENT:  create trigger my_trig
	  after insert on parted_trig
	  for each row execute procedure funcB();
2025-02-01 03:24:59.524 UTC client backend[27636] pg_regress/triggers ERROR:  BOOM!
2025-02-01 03:24:59.524 UTC client backend[27636] pg_regress/triggers CONTEXT:  PL/pgSQL function convslot_trig4() line 1 at RAISE
2025-02-01 03:24:59.524 UTC client backend[27636] pg_regress/triggers STATEMENT:  update convslot_test_parent set val = 3;
2025-02-01 03:24:59.666 UTC client backend[27636] pg_regress/triggers ERROR:  syntax error at or near "only" at character 20
2025-02-01 03:24:59.666 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter trigger a on only grandparent rename to b;
2025-02-01 03:24:59.667 UTC client backend[27636] pg_regress/triggers ERROR:  cannot rename trigger "b" on table "middle"
2025-02-01 03:24:59.667 UTC client backend[27636] pg_regress/triggers HINT:  Rename the trigger on the partitioned table "grandparent" instead.
2025-02-01 03:24:59.667 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter trigger b on middle rename to c;
2025-02-01 03:24:59.673 UTC client backend[27636] pg_regress/triggers ERROR:  trigger "c" for relation "middle" already exists
2025-02-01 03:24:59.673 UTC client backend[27636] pg_regress/triggers STATEMENT:  alter trigger b on grandparent rename to c;
2025-02-01 03:25:00.003 UTC client backend[27636] pg_regress/triggers ERROR:  division by zero
2025-02-01 03:25:00.003 UTC client backend[27636] pg_regress/triggers CONTEXT:  SQL statement "SELECT 1 / 0"
	PL/pgSQL function whoami() line 4 at PERFORM
2025-02-01 03:25:00.003 UTC client backend[27636] pg_regress/triggers STATEMENT:  commit;
2025-02-01 03:25:00.596 UTC client backend[28458] pg_regress/select_distinct_on ERROR:  SELECT DISTINCT ON expressions must match initial ORDER BY expressions at character 30
2025-02-01 03:25:00.596 UTC client backend[28458] 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-02-01 03:25:00.600 UTC client backend[28455] pg_regress/case ERROR:  division by zero
2025-02-01 03:25:00.600 UTC client backend[28455] pg_regress/case STATEMENT:  SELECT CASE WHEN i > 100 THEN 1/0 ELSE 0 END FROM case_tbl;
2025-02-01 03:25:00.619 UTC client backend[28459] 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-02-01 03:25:00.619 UTC client backend[28459] pg_regress/select_having STATEMENT:  SELECT a FROM test_having HAVING min(a) < max(a);
2025-02-01 03:25:00.623 UTC client backend[28448] pg_regress/delete ERROR:  invalid reference to FROM-clause entry for table "delete_test" at character 34
2025-02-01 03:25:00.623 UTC client backend[28448] pg_regress/delete HINT:  Perhaps you meant to reference the table alias "dt".
2025-02-01 03:25:00.623 UTC client backend[28448] pg_regress/delete STATEMENT:  DELETE FROM delete_test dt WHERE delete_test.a > 25;
2025-02-01 03:25:00.625 UTC client backend[28459] 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-02-01 03:25:00.625 UTC client backend[28459] pg_regress/select_having STATEMENT:  SELECT 1 AS one FROM test_having HAVING a > 1;
2025-02-01 03:25:00.625 UTC client backend[28466] 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-02-01 03:25:00.625 UTC client backend[28466] pg_regress/select_implicit STATEMENT:  SELECT count(*) FROM test_missing_target GROUP BY a ORDER BY b;
2025-02-01 03:25:00.629 UTC client backend[28450] pg_regress/union ERROR:  FOR NO KEY UPDATE is not allowed with UNION/INTERSECT/EXCEPT
2025-02-01 03:25:00.629 UTC client backend[28450] pg_regress/union STATEMENT:  SELECT q1 FROM int8_tbl EXCEPT ALL SELECT q1 FROM int8_tbl FOR NO KEY UPDATE;
2025-02-01 03:25:00.632 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  transaction identifier "regress_foo3" is already in use
2025-02-01 03:25:00.632 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  PREPARE TRANSACTION 'regress_foo3';
2025-02-01 03:25:00.634 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  could not serialize access due to read/write dependencies among transactions
2025-02-01 03:25:00.634 UTC client backend[28456] pg_regress/prepared_xacts DETAIL:  Reason code: Canceled on identification as a pivot, during write.
2025-02-01 03:25:00.634 UTC client backend[28456] pg_regress/prepared_xacts HINT:  The transaction might succeed if retried.
2025-02-01 03:25:00.634 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  INSERT INTO pxtest1 VALUES ('fff');
2025-02-01 03:25:00.636 UTC client backend[28466] pg_regress/select_implicit ERROR:  GROUP BY position 3 is not in select list at character 54
2025-02-01 03:25:00.636 UTC client backend[28466] pg_regress/select_implicit STATEMENT:  SELECT c, count(*) FROM test_missing_target GROUP BY 3;
2025-02-01 03:25:00.636 UTC client backend[28466] pg_regress/select_implicit ERROR:  column reference "b" is ambiguous at character 105
2025-02-01 03:25:00.636 UTC client backend[28466] 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-02-01 03:25:00.641 UTC client backend[28463] pg_regress/namespace ERROR:  column "c" does not exist at character 70
2025-02-01 03:25:00.641 UTC client backend[28463] pg_regress/namespace STATEMENT:  CREATE SCHEMA test_ns_schema_2
	       CREATE VIEW abc_view AS SELECT c FROM abc;
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays ERROR:  value too long for type character(5)
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays STATEMENT:  INSERT INTO arrtest (f)
	   VALUES ('{"too long"}');
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays ERROR:  subscripted assignment to "b" requires type integer but expression is of type timestamp with time zone at character 22
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays STATEMENT:  INSERT INTO arrtest (b[2]) VALUES(now());
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays ERROR:  subscripted assignment to "b" requires type integer[] but expression is of type timestamp with time zone at character 22
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:00.648 UTC client backend[28449] pg_regress/arrays STATEMENT:  INSERT INTO arrtest (b[1:2]) VALUES(now());
2025-02-01 03:25:00.651 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  cannot PREPARE while holding both session-level and transaction-level locks on the same object
2025-02-01 03:25:00.651 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  PREPARE TRANSACTION 'regress_foo6';
2025-02-01 03:25:00.655 UTC client backend[28466] 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-02-01 03:25:00.655 UTC client backend[28466] pg_regress/select_implicit STATEMENT:  SELECT count(a) FROM test_missing_target GROUP BY a ORDER BY b;
2025-02-01 03:25:00.656 UTC client backend[28466] pg_regress/select_implicit ERROR:  column reference "b" is ambiguous at character 109
2025-02-01 03:25:00.656 UTC client backend[28466] 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-02-01 03:25:00.656 UTC client backend[28460] pg_regress/join ERROR:  column reference "i" is ambiguous at character 8
2025-02-01 03:25:00.656 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT i, k, t
	  FROM J1_TBL CROSS JOIN J2_TBL;
2025-02-01 03:25:00.656 UTC client backend[28466] pg_regress/select_implicit ERROR:  column reference "b" is ambiguous at character 14
2025-02-01 03:25:00.656 UTC client backend[28466] 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-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions ERROR:  parameter "transaction_isolation" cannot be reset
2025-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions STATEMENT:  RESET transaction_isolation;
2025-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions ERROR:  parameter "transaction_read_only" cannot be reset
2025-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions STATEMENT:  RESET transaction_read_only;
2025-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions ERROR:  parameter "transaction_deferrable" cannot be reset
2025-02-01 03:25:00.665 UTC client backend[28470] pg_regress/transactions STATEMENT:  RESET transaction_deferrable;
2025-02-01 03:25:00.666 UTC client backend[28470] pg_regress/transactions ERROR:  parameter "transaction_read_only" cannot be set locally in functions
2025-02-01 03:25:00.666 UTC client backend[28470] pg_regress/transactions STATEMENT:  CREATE FUNCTION errfunc() RETURNS int LANGUAGE SQL AS 'SELECT 1'
	SET transaction_read_only = on;
2025-02-01 03:25:00.667 UTC client backend[28467] pg_regress/subselect ERROR:  more than one row returned by a subquery used as an expression
2025-02-01 03:25:00.667 UTC client backend[28467] pg_regress/subselect STATEMENT:  SELECT ROW(1, 2) = (SELECT f1, f2 FROM SUBSELECT_TBL);
2025-02-01 03:25:00.668 UTC client backend[28462] pg_regress/update ERROR:  column "t" of relation "update_test" does not exist at character 26
2025-02-01 03:25:00.668 UTC client backend[28462] pg_regress/update HINT:  SET target columns cannot be qualified with the relation name.
2025-02-01 03:25:00.668 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE update_test t SET t.b = t.b + 10 WHERE t.a = 10;
2025-02-01 03:25:00.669 UTC client backend[28462] pg_regress/update ERROR:  column "a" is of type integer but expression is of type record at character 28
2025-02-01 03:25:00.669 UTC client backend[28462] pg_regress/update HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:00.669 UTC client backend[28462] 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-02-01 03:25:00.670 UTC client backend[28462] pg_regress/update ERROR:  multiple assignments to same column "b"
2025-02-01 03:25:00.670 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE update_test SET (c,b) = ('car', a+b), b = a + 1 WHERE a = 10;
2025-02-01 03:25:00.671 UTC client backend[28462] pg_regress/update ERROR:  more than one row returned by a subquery used as an expression
2025-02-01 03:25:00.671 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE update_test SET (b,a) = (select a+1,b from update_test);
2025-02-01 03:25:00.672 UTC client backend[28462] pg_regress/update ERROR:  source for a multiple-column UPDATE item must be a sub-SELECT or ROW() expression at character 33
2025-02-01 03:25:00.672 UTC client backend[28462] 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-02-01 03:25:00.672 UTC client backend[28462] pg_regress/update ERROR:  invalid reference to FROM-clause entry for table "update_test" at character 33
2025-02-01 03:25:00.672 UTC client backend[28462] pg_regress/update HINT:  Perhaps you meant to reference the table alias "t".
2025-02-01 03:25:00.672 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE update_test AS t SET b = update_test.b + 10 WHERE t.a = 10;
2025-02-01 03:25:00.675 UTC client backend[28463] pg_regress/namespace ERROR:  schema "test_ns_schema_renamed" already exists
2025-02-01 03:25:00.675 UTC client backend[28463] pg_regress/namespace STATEMENT:  CREATE SCHEMA test_ns_schema_renamed;
2025-02-01 03:25:00.676 UTC client backend[28463] pg_regress/namespace ERROR:  CREATE SCHEMA IF NOT EXISTS cannot include schema elements at character 79
2025-02-01 03:25:00.676 UTC client backend[28463] pg_regress/namespace STATEMENT:  CREATE SCHEMA IF NOT EXISTS test_ns_schema_renamed -- fail, disallowed
	       CREATE TABLE abc (
	              a serial,
	              b int UNIQUE
	       );
2025-02-01 03:25:00.679 UTC client backend[28461] pg_regress/random ERROR:  lower bound must be less than or equal to upper bound
2025-02-01 03:25:00.679 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random(1, 0);
2025-02-01 03:25:00.680 UTC client backend[28461] pg_regress/random ERROR:  lower bound must be less than or equal to upper bound
2025-02-01 03:25:00.680 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random(1000000000001, 1000000000000);
2025-02-01 03:25:00.680 UTC client backend[28461] pg_regress/random ERROR:  lower bound must be less than or equal to upper bound
2025-02-01 03:25:00.680 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random(-2.0, -3.0);
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random ERROR:  lower bound cannot be NaN
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random('NaN'::numeric, 10);
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random ERROR:  lower bound cannot be infinity
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random('-Inf'::numeric, 0);
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random ERROR:  upper bound cannot be NaN
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random(0, 'NaN'::numeric);
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random ERROR:  upper bound cannot be infinity
2025-02-01 03:25:00.683 UTC client backend[28461] pg_regress/random STATEMENT:  SELECT random(0, 'Inf'::numeric);
2025-02-01 03:25:00.685 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  cursor "foo" does not exist
2025-02-01 03:25:00.685 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  FETCH 1 FROM foo;
2025-02-01 03:25:00.685 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  relation "pxtest2" does not exist at character 15
2025-02-01 03:25:00.685 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  SELECT * FROM pxtest2;
2025-02-01 03:25:00.687 UTC client backend[28456] pg_regress/prepared_xacts ERROR:  could not obtain lock on relation "pxtest3"
2025-02-01 03:25:00.687 UTC client backend[28456] pg_regress/prepared_xacts STATEMENT:  lock table pxtest3 in access share mode nowait;
2025-02-01 03:25:00.687 UTC client backend[28457] pg_regress/select_into ERROR:  permission denied for table tbl_withdata1
2025-02-01 03:25:00.687 UTC client backend[28457] pg_regress/select_into STATEMENT:  INSERT INTO selinto_schema.tbl_withdata1 VALUES (4);
2025-02-01 03:25:00.688 UTC client backend[28449] pg_regress/arrays ERROR:  number of array dimensions (7) exceeds the maximum allowed (6)
2025-02-01 03:25:00.688 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT ('{}'::int[])[1][2][3][4][5][6][7];
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays ERROR:  array subscript in assignment must not be null
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE arrtest
	  SET c[NULL] = '{"can''t assign"}'
	  WHERE array_dims(c) is not null;
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays ERROR:  array subscript in assignment must not be null
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE arrtest
	  SET c[NULL:1] = '{"can''t assign"}'
	  WHERE array_dims(c) is not null;
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays ERROR:  array subscript in assignment must not be null
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE arrtest
	  SET c[1:NULL] = '{"can''t assign"}'
	  WHERE array_dims(c) is not null;
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays ERROR:  cannot subscript type timestamp with time zone because it does not support subscripting at character 9
2025-02-01 03:25:00.689 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT (now())[1];
2025-02-01 03:25:00.715 UTC client backend[28449] pg_regress/arrays ERROR:  source array too small
2025-02-01 03:25:00.715 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE arrtest_s SET a[:] = '{23, 24, 25}';
2025-02-01 03:25:00.715 UTC client backend[28449] pg_regress/arrays ERROR:  array slice subscript must provide both boundaries
2025-02-01 03:25:00.715 UTC client backend[28449] pg_regress/arrays DETAIL:  When assigning to a slice of an empty array value, slice boundaries must be fully specified.
2025-02-01 03:25:00.715 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE arrtest_s SET a[:] = '{11, 12, 13, 14, 15}';
2025-02-01 03:25:00.718 UTC client backend[28449] pg_regress/arrays ERROR:  slices of fixed-length arrays not implemented
2025-02-01 03:25:00.718 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT f1[0:1] FROM POINT_TBL;
2025-02-01 03:25:00.720 UTC client backend[28449] pg_regress/arrays ERROR:  slices of fixed-length arrays not implemented
2025-02-01 03:25:00.720 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT f1[0:] FROM POINT_TBL;
2025-02-01 03:25:00.721 UTC client backend[28449] pg_regress/arrays ERROR:  slices of fixed-length arrays not implemented
2025-02-01 03:25:00.721 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT f1[:1] FROM POINT_TBL;
2025-02-01 03:25:00.722 UTC client backend[28449] pg_regress/arrays ERROR:  slices of fixed-length arrays not implemented
2025-02-01 03:25:00.722 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT f1[:] FROM POINT_TBL;
2025-02-01 03:25:00.736 UTC client backend[28449] pg_regress/arrays ERROR:  array subscript out of range
2025-02-01 03:25:00.736 UTC client backend[28449] pg_regress/arrays STATEMENT:  UPDATE point_tbl SET f1[3] = 10 WHERE f1::text = '(-10,-10)'::point::text RETURNING *;
2025-02-01 03:25:00.738 UTC client backend[28477] pg_regress/prepared_xacts ERROR:  could not obtain lock on relation "pxtest3"
2025-02-01 03:25:00.738 UTC client backend[28477] pg_regress/prepared_xacts STATEMENT:  lock table pxtest3 in access share mode nowait;
2025-02-01 03:25:00.743 UTC client backend[28471] pg_regress/portals ERROR:  cursor can only scan forward
2025-02-01 03:25:00.743 UTC client backend[28471] pg_regress/portals HINT:  Declare it with SCROLL option to enable backward scan.
2025-02-01 03:25:00.743 UTC client backend[28471] pg_regress/portals STATEMENT:  FETCH BACKWARD 1 FROM foo24;
2025-02-01 03:25:00.745 UTC client backend[28471] pg_regress/portals ERROR:  cursor can only scan forward
2025-02-01 03:25:00.745 UTC client backend[28471] pg_regress/portals HINT:  Declare it with SCROLL option to enable backward scan.
2025-02-01 03:25:00.745 UTC client backend[28471] pg_regress/portals STATEMENT:  FETCH ABSOLUTE 1 FROM foo24;
2025-02-01 03:25:00.750 UTC client backend[28457] pg_regress/select_into ERROR:  too many column names were specified
2025-02-01 03:25:00.750 UTC client backend[28457] pg_regress/select_into STATEMENT:  CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base;
2025-02-01 03:25:00.751 UTC client backend[28457] pg_regress/select_into ERROR:  too many column names were specified
2025-02-01 03:25:00.751 UTC client backend[28457] pg_regress/select_into STATEMENT:  CREATE TABLE ctas_nodata (ii, jj, kk) AS SELECT i, j FROM ctas_base WITH NO DATA;
2025-02-01 03:25:00.791 UTC client backend[28471] pg_regress/portals ERROR:  cursor can only scan forward
2025-02-01 03:25:00.791 UTC client backend[28471] pg_regress/portals HINT:  Declare it with SCROLL option to enable backward scan.
2025-02-01 03:25:00.791 UTC client backend[28471] pg_regress/portals STATEMENT:  FETCH ABSOLUTE 4 FROM foo25ns;
2025-02-01 03:25:00.798 UTC client backend[28471] pg_regress/portals ERROR:  cursor "foo26" does not exist
2025-02-01 03:25:00.798 UTC client backend[28471] pg_regress/portals STATEMENT:  FETCH FROM foo26;
2025-02-01 03:25:00.801 UTC client backend[28470] pg_regress/transactions ERROR:  transaction read-write mode must be set before any query
2025-02-01 03:25:00.801 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION READ WRITE;
2025-02-01 03:25:00.801 UTC client backend[28477] pg_regress/prepared_xacts ERROR:  relation "pxtest3" does not exist at character 15
2025-02-01 03:25:00.801 UTC client backend[28477] pg_regress/prepared_xacts STATEMENT:  SELECT * FROM pxtest3;
2025-02-01 03:25:00.802 UTC client backend[28470] pg_regress/transactions ERROR:  cannot set transaction read-write mode inside a read-only transaction
2025-02-01 03:25:00.802 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION READ WRITE;
2025-02-01 03:25:00.803 UTC client backend[28470] pg_regress/transactions ERROR:  cannot set transaction read-write mode inside a read-only transaction
2025-02-01 03:25:00.803 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION READ WRITE;
2025-02-01 03:25:00.805 UTC client backend[28470] pg_regress/transactions ERROR:  cannot execute DROP TABLE in a read-only transaction
2025-02-01 03:25:00.805 UTC client backend[28470] pg_regress/transactions STATEMENT:  DROP TABLE writetest;
2025-02-01 03:25:00.805 UTC client backend[28470] pg_regress/transactions ERROR:  cannot execute INSERT in a read-only transaction
2025-02-01 03:25:00.805 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO writetest VALUES (1);
2025-02-01 03:25:00.806 UTC client backend[28470] pg_regress/transactions ERROR:  cannot execute UPDATE in a read-only transaction
2025-02-01 03:25:00.806 UTC client backend[28470] pg_regress/transactions STATEMENT:  EXECUTE test;
2025-02-01 03:25:00.806 UTC client backend[28470] pg_regress/transactions ERROR:  cannot execute CREATE TABLE AS in a read-only transaction
2025-02-01 03:25:00.806 UTC client backend[28470] pg_regress/transactions STATEMENT:  CREATE TABLE test AS SELECT * FROM writetest;
2025-02-01 03:25:00.816 UTC client backend[28477] pg_regress/prepared_xacts ERROR:  table "pxtest3" does not exist
2025-02-01 03:25:00.816 UTC client backend[28477] pg_regress/prepared_xacts STATEMENT:  DROP TABLE pxtest3;
2025-02-01 03:25:00.817 UTC client backend[28457] pg_regress/select_into ERROR:  SELECT ... INTO is not allowed here at character 38
2025-02-01 03:25:00.817 UTC client backend[28457] pg_regress/select_into STATEMENT:  DECLARE foo CURSOR FOR SELECT 1 INTO int4_tbl;
2025-02-01 03:25:00.819 UTC client backend[28457] pg_regress/select_into ERROR:  COPY (SELECT INTO) is not supported
2025-02-01 03:25:00.819 UTC client backend[28457] pg_regress/select_into STATEMENT:  COPY (SELECT 1 INTO frak UNION SELECT 2) TO 'blob';
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into ERROR:  SELECT ... INTO is not allowed here at character 30
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into STATEMENT:  SELECT * FROM (SELECT 1 INTO f) bar;
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into ERROR:  views must not contain SELECT INTO
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into STATEMENT:  CREATE VIEW foo AS SELECT 1 INTO int4_tbl;
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into ERROR:  SELECT ... INTO is not allowed here at character 36
2025-02-01 03:25:00.820 UTC client backend[28457] pg_regress/select_into STATEMENT:  INSERT INTO int4_tbl SELECT 1 INTO f;
2025-02-01 03:25:00.824 UTC client backend[28457] pg_regress/select_into ERROR:  relation "ctas_ine_tbl" already exists
2025-02-01 03:25:00.824 UTC client backend[28457] pg_regress/select_into STATEMENT:  CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0;
2025-02-01 03:25:00.825 UTC client backend[28457] pg_regress/select_into ERROR:  relation "ctas_ine_tbl" already exists
2025-02-01 03:25:00.825 UTC client backend[28457] pg_regress/select_into STATEMENT:  CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0 WITH NO DATA;
2025-02-01 03:25:00.825 UTC client backend[28449] pg_regress/arrays ERROR:  searching for elements in multidimensional arrays is not supported
2025-02-01 03:25:00.825 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT array_position(ARRAY[[1,2],[3,4]], 3);
2025-02-01 03:25:00.825 UTC client backend[28457] pg_regress/select_into ERROR:  relation "ctas_ine_tbl" already exists
2025-02-01 03:25:00.825 UTC client backend[28457] pg_regress/select_into STATEMENT:  EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF)
	  CREATE TABLE ctas_ine_tbl AS SELECT 1 / 0;
2025-02-01 03:25:00.826 UTC client backend[28457] pg_regress/select_into ERROR:  relation "ctas_ine_tbl" already exists
2025-02-01 03:25:00.826 UTC client backend[28457] 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-02-01 03:25:00.826 UTC client backend[28470] pg_regress/transactions ERROR:  relation "trans_bar" does not exist at character 15
2025-02-01 03:25:00.826 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT * FROM trans_bar;
2025-02-01 03:25:00.829 UTC client backend[28457] pg_regress/select_into ERROR:  relation "ctas_ine_tbl" already exists
2025-02-01 03:25:00.829 UTC client backend[28457] pg_regress/select_into STATEMENT:  EXPLAIN (ANALYZE, COSTS OFF, SUMMARY OFF, TIMING OFF)
	  CREATE TABLE ctas_ine_tbl AS EXECUTE ctas_ine_query;
2025-02-01 03:25:00.830 UTC client backend[28470] pg_regress/transactions ERROR:  relation "trans_bar" does not exist at character 13
2025-02-01 03:25:00.830 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT into trans_bar VALUES (1);
2025-02-01 03:25:00.831 UTC client backend[28449] pg_regress/arrays ERROR:  searching for elements in multidimensional arrays is not supported
2025-02-01 03:25:00.831 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT array_positions(ARRAY[[1,2],[3,4]], 4);
2025-02-01 03:25:00.843 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate functions are not allowed in WHERE at character 114
2025-02-01 03:25:00.843 UTC client backend[28454] 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-02-01 03:25:00.849 UTC client backend[28470] pg_regress/transactions ERROR:  column "trans_foo" does not exist at character 8
2025-02-01 03:25:00.849 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT trans_foo;
2025-02-01 03:25:00.855 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:00.860 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:00.861 UTC client backend[28470] pg_regress/transactions ERROR:  column "trans_foo" does not exist at character 8
2025-02-01 03:25:00.861 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT trans_foo;
2025-02-01 03:25:00.880 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.1", size 147456
2025-02-01 03:25:00.880 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_group_1 AS
	SELECT DISTINCT g%1000 FROM generate_series(0,9999) g;
2025-02-01 03:25:00.880 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.0", size 140000
2025-02-01 03:25:00.880 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_group_1 AS
	SELECT DISTINCT g%1000 FROM generate_series(0,9999) g;
2025-02-01 03:25:00.894 UTC client backend[28470] pg_regress/transactions ERROR:  SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:00.894 UTC client backend[28470] pg_regress/transactions STATEMENT:  SAVEPOINT one;
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK TO SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions STATEMENT:  ROLLBACK TO SAVEPOINT one;
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions ERROR:  RELEASE SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions STATEMENT:  RELEASE SAVEPOINT one;
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:00.896 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 0/0;
2025-02-01 03:25:00.897 UTC client backend[28470] pg_regress/transactions ERROR:  current transaction is aborted, commands ignored until end of transaction block
2025-02-01 03:25:00.897 UTC client backend[28470] pg_regress/transactions STATEMENT:  SAVEPOINT two;
2025-02-01 03:25:00.897 UTC client backend[28470] pg_regress/transactions ERROR:  current transaction is aborted, commands ignored until end of transaction block
2025-02-01 03:25:00.897 UTC client backend[28470] pg_regress/transactions STATEMENT:  RELEASE SAVEPOINT one;
2025-02-01 03:25:00.903 UTC client backend[28471] pg_regress/portals ERROR:  cursor can only scan forward
2025-02-01 03:25:00.903 UTC client backend[28471] pg_regress/portals HINT:  Declare it with SCROLL option to enable backward scan.
2025-02-01 03:25:00.903 UTC client backend[28471] pg_regress/portals STATEMENT:  FETCH RELATIVE 0 FROM c1;
2025-02-01 03:25:00.907 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:00.907 UTC client backend[28470] pg_regress/transactions STATEMENT:  FETCH 10 FROM c;
2025-02-01 03:25:00.908 UTC client backend[28470] pg_regress/transactions ERROR:  portal "c" cannot be run
2025-02-01 03:25:00.908 UTC client backend[28470] pg_regress/transactions STATEMENT:  FETCH 10 FROM c;
2025-02-01 03:25:00.909 UTC client backend[28470] pg_regress/transactions ERROR:  portal "c" cannot be run
2025-02-01 03:25:00.909 UTC client backend[28470] pg_regress/transactions STATEMENT:  FETCH 10 FROM c;
2025-02-01 03:25:00.909 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "part_c_100_200" violates partition constraint
2025-02-01 03:25:00.909 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (105, 85, null, b, 15).
2025-02-01 03:25:00.909 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE part_c_100_200 set c = c - 20, d = c WHERE c = 105;
2025-02-01 03:25:00.910 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "part_b_10_b_20" violates partition constraint
2025-02-01 03:25:00.910 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (null, 96, a, 12, 1).
2025-02-01 03:25:00.910 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE part_b_10_b_20 set a = 'a';
2025-02-01 03:25:00.922 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "part_b_10_b_20" violates partition constraint
2025-02-01 03:25:00.922 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (2, 117, b, 7, 2).
2025-02-01 03:25:00.922 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE part_b_10_b_20 set b = b - 6 WHERE c > 116 returning *;
2025-02-01 03:25:00.923 UTC client backend[28449] pg_regress/arrays ERROR:  op ANY/ALL (array) requires operator to yield boolean at character 11
2025-02-01 03:25:00.923 UTC client backend[28449] pg_regress/arrays STATEMENT:  select 33 * any ('{1,2,3}');
2025-02-01 03:25:00.923 UTC client backend[28449] pg_regress/arrays ERROR:  op ANY/ALL (array) requires array on right side at character 11
2025-02-01 03:25:00.923 UTC client backend[28449] pg_regress/arrays STATEMENT:  select 33 * any (44);
2025-02-01 03:25:00.927 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c1" is not a simply updatable scan of table "uctest"
2025-02-01 03:25:00.927 UTC client backend[28471] pg_regress/portals STATEMENT:  UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1;
2025-02-01 03:25:00.931 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c1" has multiple FOR UPDATE/SHARE references to table "uctest"
2025-02-01 03:25:00.931 UTC client backend[28471] pg_regress/portals STATEMENT:  UPDATE uctest SET f1 = f1 + 10 WHERE CURRENT OF c1;
2025-02-01 03:25:00.933 UTC client backend[28470] pg_regress/transactions ERROR:  duplicate key value violates unique constraint "koju_a_key"
2025-02-01 03:25:00.933 UTC client backend[28470] pg_regress/transactions DETAIL:  Key (a)=(1) already exists.
2025-02-01 03:25:00.933 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO koju VALUES (1);
2025-02-01 03:25:00.935 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c1" does not exist
2025-02-01 03:25:00.935 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF c1;
2025-02-01 03:25:00.937 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.2", size 140000
2025-02-01 03:25:00.937 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_group_2 AS
	SELECT DISTINCT (g%1000)::text FROM generate_series(0,9999) g;
2025-02-01 03:25:00.939 UTC client backend[28470] pg_regress/transactions ERROR:  duplicate key value violates unique constraint "koju_a_key"
2025-02-01 03:25:00.939 UTC client backend[28470] pg_regress/transactions DETAIL:  Key (a)=(1) already exists.
2025-02-01 03:25:00.939 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO koju VALUES (1);
2025-02-01 03:25:00.939 UTC client backend[28449] pg_regress/arrays ERROR:  duplicate key value violates unique constraint "arr_tbl_f1_key"
2025-02-01 03:25:00.939 UTC client backend[28449] pg_regress/arrays DETAIL:  Key (f1)=({1,2,3}) already exists.
2025-02-01 03:25:00.939 UTC client backend[28449] pg_regress/arrays STATEMENT:  insert into arr_tbl values ('{1,2,3}');
2025-02-01 03:25:00.939 UTC client backend[28471] pg_regress/portals ERROR:  cursor "cx" is held from a previous transaction
2025-02-01 03:25:00.939 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF cx;
2025-02-01 03:25:00.946 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c" is not a simply updatable scan of table "uctest"
2025-02-01 03:25:00.946 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF c;
2025-02-01 03:25:00.946 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c" does not have a FOR UPDATE/SHARE reference to table "uctest"
2025-02-01 03:25:00.946 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF c;
2025-02-01 03:25:00.951 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c" is not a simply updatable scan of table "tenk1"
2025-02-01 03:25:00.951 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM tenk1 WHERE CURRENT OF c;
2025-02-01 03:25:00.957 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c" is not a simply updatable scan of table "uctest"
2025-02-01 03:25:00.957 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF c;
2025-02-01 03:25:00.959 UTC client backend[28471] pg_regress/portals ERROR:  cursor "c1" is not positioned on a row
2025-02-01 03:25:00.959 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM uctest WHERE CURRENT OF c1;
2025-02-01 03:25:00.959 UTC client backend[28471] pg_regress/portals ERROR:  FOR UPDATE is not allowed with aggregate functions
2025-02-01 03:25:00.959 UTC client backend[28471] pg_regress/portals STATEMENT:  DECLARE c1 CURSOR FOR SELECT MIN(f1) FROM uctest FOR UPDATE;
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays ERROR:  array size exceeds the maximum allowed (134217727)
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays STATEMENT:  update arr_pk_tbl set f1[2147483647] = 42 where pk = 10;
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays ERROR:  array size exceeds the maximum allowed (134217727)
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays STATEMENT:  update arr_pk_tbl set f1[2147483646:2147483647] = array[4,2] where pk = 10;
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays ERROR:  array size exceeds the maximum allowed (134217727)
2025-02-01 03:25:00.960 UTC client backend[28449] pg_regress/arrays STATEMENT:  insert into arr_pk_tbl(pk, f1[0:2147483647]) values (2, '{}');
2025-02-01 03:25:00.961 UTC client backend[28449] pg_regress/arrays ERROR:  array size exceeds the maximum allowed (134217727)
2025-02-01 03:25:00.961 UTC client backend[28449] pg_regress/arrays STATEMENT:  insert into arr_pk_tbl(pk, f1[-2147483648:2147483647]) values (2, '{}');
2025-02-01 03:25:00.961 UTC client backend[28449] pg_regress/arrays ERROR:  array size exceeds the maximum allowed (134217727)
2025-02-01 03:25:00.961 UTC client backend[28449] pg_regress/arrays CONTEXT:  PL/pgSQL function inline_code_block line 4 at assignment
2025-02-01 03:25:00.961 UTC client backend[28449] pg_regress/arrays STATEMENT:  do $$ declare a int[];
	begin
	  a := '[-2147483648:-2147483647]={1,2}'::int[];
	  a[2147483647] := 42;
	end $$;
2025-02-01 03:25:00.968 UTC client backend[28471] pg_regress/portals ERROR:  WHERE CURRENT OF on a view is not implemented
2025-02-01 03:25:00.968 UTC client backend[28471] pg_regress/portals STATEMENT:  DELETE FROM ucview WHERE CURRENT OF c1;
2025-02-01 03:25:00.968 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.5", size 204800
2025-02-01 03:25:00.968 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_hash_1 AS
	SELECT DISTINCT g%1000 FROM generate_series(0,9999) g;
2025-02-01 03:25:00.968 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.4", size 140000
2025-02-01 03:25:00.968 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_hash_1 AS
	SELECT DISTINCT g%1000 FROM generate_series(0,9999) g;
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1,{2}},{2,3}}" at character 8
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1,{2}},{2,3}}'::text[];
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1,2},\{2,3}}" at character 8
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays STATEMENT:  select E'{{1,2},\\{2,3}}'::text[];
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{"a"b}" at character 8
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays DETAIL:  Incorrectly quoted array element.
2025-02-01 03:25:00.969 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{"a"b}'::text[];
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{a"b"}" at character 8
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays DETAIL:  Incorrectly quoted array element.
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{a"b"}'::text[];
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{"a""b"}" at character 8
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays DETAIL:  Incorrectly quoted array element.
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{"a""b"}'::text[];
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{"1 2" x},{3}}" at character 8
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays DETAIL:  Incorrectly quoted array element.
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{"1 2" x},{3}}'::text[];
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{"1 2"} x,{3}}" at character 8
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected array element.
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{"1 2"} x,{3}}'::text[];
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{}}" at character 8
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays DETAIL:  Junk after closing right brace.
2025-02-01 03:25:00.970 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{ }}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Junk after closing right brace.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{ }}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "}{" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Array value must start with "{" or dimension information.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '}{'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{foo{}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "{" character.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{foo{}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{"foo"{}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "{" character.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{"foo"{}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{foo,,bar}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "," character.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{foo,,bar}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1},{{2}}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1},{{2}}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{{1}},{2}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{{1}},{2}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{},{{}}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{},{{}}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{{}},{}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{{}},{}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1},{}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1},{}}'::text[];
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{},{1}}" at character 8
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:00.973 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{},{1}}'::text[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  upper bound cannot be less than lower bound at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[1:0]={}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  array upper bound is too large: 2147483647 at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[2147483646:2147483647]={1,2}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  upper bound cannot be less than lower bound at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[1:-1]={}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "[2]={1}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Specified array dimensions do not match array contents.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[2]={1}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "[1:]={1}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Missing array dimension value.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[1:]={1}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "[:1]={1}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  "[" must introduce explicitly-specified array dimensions.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[:1]={1}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  cannot determine type of empty array at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays HINT:  Explicitly cast to the desired type, for example ARRAY[]::integer[].
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1,},{1},}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "}" character.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1,},{1},}'::text[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1,},{1}}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "}" character.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1,},{1}}'::text[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{{1,}}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "}" character.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{{1,}}'::text[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  malformed array literal: "{1,}" at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays DETAIL:  Unexpected "}" character.
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '{1,}'::text[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  array bound is out of integer range at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[21474836488:21474836489]={1,2}'::int[];
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays ERROR:  array bound is out of integer range at character 8
2025-02-01 03:25:00.974 UTC client backend[28449] pg_regress/arrays STATEMENT:  select '[-2147483649:-2147483648]={1,2}'::int[];
2025-02-01 03:25:00.980 UTC client backend[28470] pg_regress/transactions ERROR:  cursor "foo" does not exist
2025-02-01 03:25:00.980 UTC client backend[28470] pg_regress/transactions STATEMENT:  fetch from foo;
2025-02-01 03:25:00.983 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "j1_tbl" at character 57
2025-02-01 03:25:00.983 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "j1_tbl", but it cannot be referenced from this part of the query.
2025-02-01 03:25:00.983 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT * FROM (J1_TBL JOIN J2_TBL USING (i)) AS x WHERE J1_TBL.t = 'one';
2025-02-01 03:25:00.985 UTC client backend[28460] pg_regress/join ERROR:  column x.t does not exist at character 55
2025-02-01 03:25:00.985 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT * FROM J1_TBL JOIN J2_TBL USING (i) AS x WHERE x.t = 'one';
2025-02-01 03:25:00.991 UTC client backend[28460] pg_regress/join ERROR:  missing FROM-clause entry for table "x" at character 63
2025-02-01 03:25:00.991 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT * FROM (J1_TBL JOIN J2_TBL USING (i) AS x) AS xx WHERE x.i = 1;
2025-02-01 03:25:00.991 UTC client backend[28460] pg_regress/join ERROR:  table name "a1" specified more than once
2025-02-01 03:25:00.991 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT * FROM J1_TBL a1 JOIN J2_TBL a2 USING (i) AS a1;
2025-02-01 03:25:00.992 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.7", size 204800
2025-02-01 03:25:00.992 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_hash_2 AS
	SELECT DISTINCT (g%1000)::text FROM generate_series(0,9999) g;
2025-02-01 03:25:00.992 UTC client backend[28453] pg_regress/select_distinct LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28453.6", size 140000
2025-02-01 03:25:00.992 UTC client backend[28453] pg_regress/select_distinct STATEMENT:  CREATE TABLE distinct_hash_2 AS
	SELECT DISTINCT (g%1000)::text FROM generate_series(0,9999) g;
2025-02-01 03:25:01.003 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:01.003 UTC client backend[28470] 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-02-01 03:25:01.003 UTC client backend[28470] pg_regress/transactions STATEMENT:  FETCH ctt;
2025-02-01 03:25:01.004 UTC client backend[28470] pg_regress/transactions ERROR:  portal "ctt" cannot be run
2025-02-01 03:25:01.004 UTC client backend[28470] pg_regress/transactions STATEMENT:  FETCH ctt;
2025-02-01 03:25:01.034 UTC client backend[28470] pg_regress/transactions ERROR:  invalid input syntax for type integer: "error" at character 31
2025-02-01 03:25:01.034 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES ('error');
2025-02-01 03:25:01.035 UTC client backend[28470] pg_regress/transactions ERROR:  current transaction is aborted, commands ignored until end of transaction block
2025-02-01 03:25:01.035 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES (3);
2025-02-01 03:25:01.036 UTC client backend[28470] pg_regress/transactions ERROR:  invalid input syntax for type integer: "error" at character 31
2025-02-01 03:25:01.036 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES ('error');
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays ERROR:  dimension array or low bound array cannot be null
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, null, array[2,2]);
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays ERROR:  dimension array or low bound array cannot be null
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, array[2,2], null);
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays ERROR:  wrong number of array subscripts
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays DETAIL:  Low bound array has different size than dimensions array.
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, array[2,2], '{}');
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays ERROR:  wrong number of array subscripts
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays DETAIL:  Low bound array has different size than dimensions array.
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, array[3,3], array[1,1,1]);
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays ERROR:  dimension values cannot be null
2025-02-01 03:25:01.049 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, array[1,2,null]);
2025-02-01 03:25:01.050 UTC client backend[28449] pg_regress/arrays ERROR:  wrong number of array subscripts
2025-02-01 03:25:01.050 UTC client backend[28449] pg_regress/arrays DETAIL:  Dimension array must be one dimensional.
2025-02-01 03:25:01.050 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_fill(1, array[[1,2],[3,4]]);
2025-02-01 03:25:01.052 UTC client backend[28470] pg_regress/transactions ERROR:  invalid input syntax for type integer: "error" at character 31
2025-02-01 03:25:01.052 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES ('error');
2025-02-01 03:25:01.056 UTC client backend[28470] pg_regress/transactions ERROR:  COMMIT AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.056 UTC client backend[28470] pg_regress/transactions STATEMENT:  COMMIT AND CHAIN;
2025-02-01 03:25:01.056 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.056 UTC client backend[28470] pg_regress/transactions STATEMENT:  ROLLBACK AND CHAIN;
2025-02-01 03:25:01.071 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:01.071 UTC client backend[28470] pg_regress/transactions STATEMENT:  insert into i_table values(2); select * from i_table; select 1/0;
2025-02-01 03:25:01.072 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.073 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.075 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.080 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.081 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:01.081 UTC client backend[28470] pg_regress/transactions STATEMENT:  insert into i_table values(7); commit; insert into i_table values(8); select 1/0;
2025-02-01 03:25:01.083 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.088 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.089 UTC client backend[28470] pg_regress/transactions ERROR:  VACUUM cannot run inside a transaction block
2025-02-01 03:25:01.089 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 1; VACUUM;
2025-02-01 03:25:01.089 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.090 UTC client backend[28470] pg_regress/transactions ERROR:  VACUUM cannot run inside a transaction block
2025-02-01 03:25:01.090 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 1; COMMIT; VACUUM;
2025-02-01 03:25:01.091 UTC client backend[28470] pg_regress/transactions ERROR:  SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:01.091 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 1; SAVEPOINT sp;
2025-02-01 03:25:01.092 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.092 UTC client backend[28470] pg_regress/transactions ERROR:  SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:01.092 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 1; COMMIT; SAVEPOINT sp;
2025-02-01 03:25:01.094 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK TO SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:01.094 UTC client backend[28470] pg_regress/transactions STATEMENT:  ROLLBACK TO SAVEPOINT sp; SELECT 2;
2025-02-01 03:25:01.094 UTC client backend[28470] pg_regress/transactions ERROR:  RELEASE SAVEPOINT can only be used in transaction blocks
2025-02-01 03:25:01.094 UTC client backend[28470] pg_regress/transactions STATEMENT:  SELECT 2; RELEASE SAVEPOINT sp; SELECT 3;
2025-02-01 03:25:01.096 UTC client backend[28470] pg_regress/transactions ERROR:  COMMIT AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.096 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION READ ONLY; COMMIT AND CHAIN;
2025-02-01 03:25:01.097 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.097 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION READ ONLY; ROLLBACK AND CHAIN;
2025-02-01 03:25:01.104 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.106 UTC client backend[28470] pg_regress/transactions ERROR:  COMMIT AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.106 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES (7); COMMIT; INSERT INTO trans_abc VALUES (8); COMMIT AND CHAIN;
2025-02-01 03:25:01.108 UTC client backend[28470] pg_regress/transactions WARNING:  there is no transaction in progress
2025-02-01 03:25:01.108 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.108 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES (9); ROLLBACK; INSERT INTO trans_abc VALUES (10); ROLLBACK AND CHAIN;
2025-02-01 03:25:01.109 UTC client backend[28470] pg_regress/transactions ERROR:  COMMIT AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.109 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES (11); COMMIT AND CHAIN; INSERT INTO trans_abc VALUES (12); COMMIT;
2025-02-01 03:25:01.110 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.110 UTC client backend[28470] pg_regress/transactions STATEMENT:  INSERT INTO trans_abc VALUES (13); ROLLBACK AND CHAIN; INSERT INTO trans_abc VALUES (14); ROLLBACK;
2025-02-01 03:25:01.113 UTC client backend[28449] pg_regress/arrays ERROR:  cannot accumulate empty arrays
2025-02-01 03:25:01.113 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_agg('{}'::int[]) from generate_series(1,2);
2025-02-01 03:25:01.118 UTC client backend[28449] pg_regress/arrays ERROR:  cannot accumulate null arrays
2025-02-01 03:25:01.118 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_agg(null::int[]) from generate_series(1,2);
2025-02-01 03:25:01.119 UTC client backend[28449] pg_regress/arrays ERROR:  cannot accumulate arrays of different dimensionality
2025-02-01 03:25:01.119 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_agg(ar)
	  from (values ('{1,2}'::int[]), ('{3}'::int[])) v(ar);
2025-02-01 03:25:01.121 UTC client backend[28470] pg_regress/transactions ERROR:  COMMIT AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.121 UTC client backend[28470] 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-02-01 03:25:01.123 UTC client backend[28470] pg_regress/transactions ERROR:  ROLLBACK AND CHAIN can only be used in transaction blocks
2025-02-01 03:25:01.123 UTC client backend[28470] 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-02-01 03:25:01.129 UTC client backend[28470] pg_regress/transactions ERROR:  invalid snapshot identifier: "Incorrect Identifier"
2025-02-01 03:25:01.129 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION SNAPSHOT 'Incorrect Identifier';
2025-02-01 03:25:01.132 UTC client backend[28470] pg_regress/transactions ERROR:  snapshot "FFF-FFF-F" does not exist
2025-02-01 03:25:01.132 UTC client backend[28470] pg_regress/transactions STATEMENT:  SET TRANSACTION SNAPSHOT 'FFF-FFF-F';
2025-02-01 03:25:01.132 UTC client backend[28449] pg_regress/arrays ERROR:  removing elements from multidimensional arrays is not supported
2025-02-01 03:25:01.132 UTC client backend[28449] pg_regress/arrays STATEMENT:  select array_remove('{{1,2,2},{1,4,3}}', 2);
2025-02-01 03:25:01.132 UTC client backend[28470] pg_regress/transactions ERROR:  division by zero
2025-02-01 03:25:01.132 UTC client backend[28470] pg_regress/transactions STATEMENT:  select 1/0;
2025-02-01 03:25:01.133 UTC client backend[28470] pg_regress/transactions ERROR:  savepoint "x" does not exist
2025-02-01 03:25:01.133 UTC client backend[28470] pg_regress/transactions STATEMENT:  rollback to X;
2025-02-01 03:25:01.149 UTC client backend[28467] pg_regress/subselect ERROR:  operator does not exist: bigint = text at character 33
2025-02-01 03:25:01.149 UTC client backend[28467] pg_regress/subselect HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:01.149 UTC client backend[28467] pg_regress/subselect STATEMENT:  select * from int8_tbl where q1 in (select c1 from inner_text);
2025-02-01 03:25:01.179 UTC client backend[28450] pg_regress/union ERROR:  column "q2" does not exist at character 65
2025-02-01 03:25:01.179 UTC client backend[28450] 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-02-01 03:25:01.179 UTC client backend[28450] pg_regress/union STATEMENT:  SELECT q1 FROM int8_tbl EXCEPT SELECT q2 FROM int8_tbl ORDER BY q2 LIMIT 1;
2025-02-01 03:25:01.197 UTC client backend[28450] pg_regress/union ERROR:  invalid input syntax for type numeric: "foo" at character 36
2025-02-01 03:25:01.197 UTC client backend[28450] pg_regress/union STATEMENT:  SELECT '3.4'::numeric UNION SELECT 'foo';
2025-02-01 03:25:01.216 UTC client backend[28462] pg_regress/update ERROR:  new row violates check option for view "upview"
2025-02-01 03:25:01.216 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (a, 4, 120, 1, 1).
2025-02-01 03:25:01.216 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE upview set c = 120 WHERE b = 4;
2025-02-01 03:25:01.245 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 12
2025-02-01 03:25:01.245 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select max(min(unique1)) from tenk1;
2025-02-01 03:25:01.246 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 20
2025-02-01 03:25:01.246 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select (select max(min(unique1)) from int8_tbl) from tenk1;
2025-02-01 03:25:01.247 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 49
2025-02-01 03:25:01.247 UTC client backend[28454] 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-02-01 03:25:01.305 UTC client backend[28462] pg_regress/update ERROR:  new row violates check option for view "upview"
2025-02-01 03:25:01.305 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (b, 15, 120, 1, 1).
2025-02-01 03:25:01.305 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE upview set a = 'b', b = 15, c = 120 WHERE b = 4;
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays ERROR:  function width_bucket(text, integer[]) does not exist at character 8
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT width_bucket('5'::text, ARRAY[3, 4]::integer[]);
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays ERROR:  thresholds array must not contain NULLs
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT width_bucket(5, ARRAY[3, 4, NULL]);
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays ERROR:  thresholds must be one-dimensional array
2025-02-01 03:25:01.370 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT width_bucket(5, ARRAY[ARRAY[1, 2], ARRAY[3, 4]]);
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays ERROR:  number of elements to trim must be between 0 and 3
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT trim_array(ARRAY[1, 2, 3], -1);
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays ERROR:  number of elements to trim must be between 0 and 3
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT trim_array(ARRAY[1, 2, 3], 10);
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays ERROR:  number of elements to trim must be between 0 and 0
2025-02-01 03:25:01.371 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT trim_array(ARRAY[]::int[], 1);
2025-02-01 03:25:01.373 UTC client backend[28449] pg_regress/arrays ERROR:  sample size must be between 0 and 6
2025-02-01 03:25:01.373 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT array_sample('{1,2,3,4,5,6}'::int[], -1);
2025-02-01 03:25:01.373 UTC client backend[28449] pg_regress/arrays ERROR:  sample size must be between 0 and 6
2025-02-01 03:25:01.373 UTC client backend[28449] pg_regress/arrays STATEMENT:  SELECT array_sample('{1,2,3,4,5,6}'::int[], 7);
2025-02-01 03:25:01.429 UTC client backend[28454] 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-02-01 03:25:01.429 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select t1.f1 from t1 left join t2 using (f1) group by f1;
2025-02-01 03:25:01.508 UTC client backend[28462] pg_regress/update ERROR:  new row violates row-level security policy for table "range_parted"
2025-02-01 03:25:01.508 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE range_parted set a = 'b', c = 151 WHERE a = 'a' and c = 200;
2025-02-01 03:25:01.561 UTC client backend[28462] pg_regress/update ERROR:  new row violates row-level security policy for table "range_parted"
2025-02-01 03:25:01.561 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE range_parted set a = 'b', c = 150 WHERE a = 'a' and c = 200;
2025-02-01 03:25:01.596 UTC client backend[28462] pg_regress/update ERROR:  new row violates row-level security policy "policy_range_parted_subplan" for table "range_parted"
2025-02-01 03:25:01.596 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE range_parted set a = 'b', c = 122 WHERE a = 'a' and c = 200;
2025-02-01 03:25:01.618 UTC client backend[28460] pg_regress/join ERROR:  column t1.x does not exist at character 8
2025-02-01 03:25:01.618 UTC client backend[28460] pg_regress/join HINT:  Perhaps you meant to reference the column "t3.x".
2025-02-01 03:25:01.618 UTC client backend[28460] pg_regress/join STATEMENT:  select t1.x from t1 join t3 on (t1.a = t3.x);
2025-02-01 03:25:01.623 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 39
2025-02-01 03:25:01.623 UTC client backend[28454] 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-02-01 03:25:01.623 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41
2025-02-01 03:25:01.623 UTC client backend[28454] 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-02-01 03:25:01.623 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 43
2025-02-01 03:25:01.623 UTC client backend[28454] 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-02-01 03:25:01.624 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 41
2025-02-01 03:25:01.624 UTC client backend[28454] 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-02-01 03:25:01.635 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 51
2025-02-01 03:25:01.635 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select string_agg(distinct f1::text, ',' order by f1) from varchar_tbl;
2025-02-01 03:25:01.635 UTC client backend[28454] pg_regress/aggregates ERROR:  in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list at character 45
2025-02-01 03:25:01.635 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select string_agg(distinct f1, ',' order by f1::text) from varchar_tbl;
2025-02-01 03:25:01.647 UTC client backend[28462] pg_regress/update ERROR:  new row violates row-level security policy "policy_range_parted_wholerow" for table "range_parted"
2025-02-01 03:25:01.647 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE range_parted set a = 'b', c = 116 WHERE a = 'a' and c = 200;
2025-02-01 03:25:01.759 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "part_def" violates partition constraint
2025-02-01 03:25:01.759 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (a, 9, null, null, null).
2025-02-01 03:25:01.759 UTC client backend[28462] pg_regress/update STATEMENT:  update part_def set a = 'a' where a = 'd';
2025-02-01 03:25:01.760 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "part_a_10_a_20" violates partition constraint
2025-02-01 03:25:01.760 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (ad, 10, 200, 1, null).
2025-02-01 03:25:01.760 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE part_a_10_a_20 set a = 'ad' WHERE a = 'a';
2025-02-01 03:25:01.799 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "list_default" violates partition constraint
2025-02-01 03:25:01.799 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (a, 10).
2025-02-01 03:25:01.799 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE list_default set a = 'a' WHERE a = 'd';
2025-02-01 03:25:01.808 UTC client backend[28462] pg_regress/update ERROR:  cannot retrieve a system column in this context
2025-02-01 03:25:01.808 UTC client backend[28462] pg_regress/update STATEMENT:  insert into utrtest values (2, 'bar')
	  returning *, tableoid::regclass, xmin = pg_current_xact_id()::xid as xmin_ok;
2025-02-01 03:25:01.810 UTC client backend[28462] pg_regress/update ERROR:  cannot retrieve a system column in this context
2025-02-01 03:25:01.810 UTC client backend[28462] 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-02-01 03:25:01.830 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "sub_parted" violates partition constraint
2025-02-01 03:25:01.830 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (2, 2, 10).
2025-02-01 03:25:01.830 UTC client backend[28462] pg_regress/update STATEMENT:  UPDATE sub_parted set a = 2 WHERE c = 10;
2025-02-01 03:25:01.847 UTC client backend[28462] pg_regress/update ERROR:  new row for relation "hpart1" violates partition constraint
2025-02-01 03:25:01.847 UTC client backend[28462] pg_regress/update DETAIL:  Failing row contains (3, 4).
2025-02-01 03:25:01.847 UTC client backend[28462] pg_regress/update STATEMENT:  update hpart1 set a = 3, b=4 where a = 1;
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate functions are not allowed in FILTER at character 35
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select max(unique1) filter (where sum(ten) > 0) from tenk1;
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 43
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select (select max(unique1) filter (where sum(ten) > 0) from int8_tbl) from tenk1;
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate functions are not allowed in FILTER at character 35
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select max(unique1) filter (where bool_or(ten > 0)) from tenk1;
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 43
2025-02-01 03:25:01.941 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select (select max(unique1) filter (where bool_or(ten > 0)) from int8_tbl) from tenk1;
2025-02-01 03:25:01.942 UTC client backend[28454] pg_regress/aggregates ERROR:  cannot use multiple ORDER BY clauses with WITHIN GROUP at character 41
2025-02-01 03:25:01.942 UTC client backend[28454] 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-02-01 03:25:01.942 UTC client backend[28454] pg_regress/aggregates ERROR:  sum is not an ordered-set aggregate, so it cannot have WITHIN GROUP at character 11
2025-02-01 03:25:01.942 UTC client backend[28454] 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-02-01 03:25:01.942 UTC client backend[28454] pg_regress/aggregates ERROR:  WITHIN GROUP is required for ordered-set aggregate percentile_cont at character 11
2025-02-01 03:25:01.942 UTC client backend[28454] 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-02-01 03:25:02.001 UTC client backend[28460] pg_regress/join ERROR:  FOR UPDATE cannot be applied to a join at character 101
2025-02-01 03:25:02.001 UTC client backend[28460] 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-02-01 03:25:02.002 UTC client backend[28460] pg_regress/join ERROR:  relation "foo" in FOR UPDATE clause not found in FROM clause at character 110
2025-02-01 03:25:02.002 UTC client backend[28460] 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-02-01 03:25:02.002 UTC client backend[28460] pg_regress/join ERROR:  FOR UPDATE cannot be applied to a join at character 110
2025-02-01 03:25:02.002 UTC client backend[28460] 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-02-01 03:25:02.011 UTC client backend[28454] 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-02-01 03:25:02.011 UTC client backend[28454] pg_regress/aggregates DETAIL:  Direct arguments of an ordered-set aggregate must use only grouped columns.
2025-02-01 03:25:02.011 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank(x) within group (order by x) from generate_series(1,5) x;
2025-02-01 03:25:02.011 UTC client backend[28454] pg_regress/aggregates ERROR:  outer-level aggregate cannot contain a lower-level variable in its direct arguments at character 37
2025-02-01 03:25:02.011 UTC client backend[28454] 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-02-01 03:25:02.011 UTC client backend[28454] pg_regress/aggregates ERROR:  aggregate function calls cannot be nested at character 13
2025-02-01 03:25:02.011 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank(sum(x)) within group (order by x) from generate_series(1,5) x;
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates ERROR:  WITHIN GROUP types text and integer cannot be matched at character 13
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank(3) within group (order by x) from (values ('fred'),('jim')) v(x);
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates ERROR:  function rank(integer, name, name) does not exist at character 8
2025-02-01 03:25:02.012 UTC client backend[28454] 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-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank(3) within group (order by stringu1,stringu2) from tenk1;
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates ERROR:  invalid input syntax for type integer: "fred" at character 13
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank('fred') within group (order by x) from generate_series(1,5) x;
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates ERROR:  collation mismatch between explicit collations "C" and "POSIX" at character 64
2025-02-01 03:25:02.012 UTC client backend[28454] pg_regress/aggregates STATEMENT:  select rank('adam'::text collate "C") within group (order by x collate "POSIX")
	  from (values ('fred'),('jim')) v(x);
2025-02-01 03:25:02.257 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:02.491 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 3596 buffers (21.9%), wrote 4 SLRU buffers; 0 WAL file(s) added, 0 removed, 4 recycled; write=0.119 s, sync=0.001 s, total=0.235 s; sync files=0, longest=0.000 s, average=0.000 s; distance=66804 kB, estimate=66804 kB; lsn=0/773AFC8, redo lsn=0/76E9080
2025-02-01 03:25:02.504 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:02.517 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 123 buffers (0.8%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.001 s, total=0.014 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1015 kB, estimate=60225 kB; lsn=0/78639E0, redo lsn=0/77E6FF8
2025-02-01 03:25:02.538 UTC checkpointer[25314] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:02.552 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.1", size 280000
2025-02-01 03:25:02.552 UTC client backend[28454] pg_regress/aggregates STATEMENT:  create table agg_data_20k as
	select g from generate_series(0, 19999) g;
2025-02-01 03:25:02.553 UTC checkpointer[25314] LOG:  checkpoint complete: wrote 149 buffers (0.9%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.001 s, total=0.016 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1767 kB, estimate=54380 kB; lsn=0/7A00808, redo lsn=0/79A0EE0
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index ERROR:  value 9 out of bounds for option "fillfactor"
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index STATEMENT:  CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops)
		WITH (fillfactor=9);
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index ERROR:  value 101 out of bounds for option "fillfactor"
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:02.565 UTC client backend[28464] pg_regress/hash_index STATEMENT:  CREATE INDEX hash_f8_index2 ON hash_f8_heap USING hash (random float8_ops)
		WITH (fillfactor=101);
2025-02-01 03:25:02.650 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.2", size 401408
2025-02-01 03:25:02.650 UTC client backend[28454] 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-02-01 03:25:02.702 UTC client backend[28460] pg_regress/join ERROR:  column reference "f1" is ambiguous at character 78
2025-02-01 03:25:02.702 UTC client backend[28460] pg_regress/join STATEMENT:  select * from
	  int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = f1;
2025-02-01 03:25:02.702 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "y" at character 78
2025-02-01 03:25:02.702 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "y", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.702 UTC client backend[28460] pg_regress/join STATEMENT:  select * from
	  int8_tbl x join (int4_tbl x cross join int4_tbl y) j on q1 = y.f1;
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join ERROR:  column t1.uunique1 does not exist at character 8
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join HINT:  Perhaps you meant to reference the column "t1.unique1".
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join STATEMENT:  select t1.uunique1 from
	  tenk1 t1 join tenk2 t2 on t1.two = t2.two;
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join ERROR:  column t2.uunique1 does not exist at character 8
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join HINT:  Perhaps you meant to reference the column "t2.unique1".
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join STATEMENT:  select t2.uunique1 from
	  tenk1 t1 join tenk2 t2 on t1.two = t2.two;
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join ERROR:  column "uunique1" does not exist at character 8
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join HINT:  Perhaps you meant to reference the column "t1.unique1" or the column "t2.unique1".
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join STATEMENT:  select uunique1 from
	  tenk1 t1 join tenk2 t2 on t1.two = t2.two;
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join ERROR:  column "ctid" does not exist at character 8
2025-02-01 03:25:02.703 UTC client backend[28460] 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-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join HINT:  Try using a table-qualified name.
2025-02-01 03:25:02.703 UTC client backend[28460] pg_regress/join STATEMENT:  select ctid from
	  tenk1 t1 join tenk2 t2 on t1.two = t2.two;
2025-02-01 03:25:02.704 UTC client backend[28460] pg_regress/join ERROR:  column atts.relid does not exist at character 8
2025-02-01 03:25:02.704 UTC client backend[28460] 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-02-01 03:25:02.743 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.5", size 786432
2025-02-01 03:25:02.743 UTC client backend[28454] 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-02-01 03:25:02.764 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.6", size 204800
2025-02-01 03:25:02.764 UTC client backend[28454] 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-02-01 03:25:02.765 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.7", size 204800
2025-02-01 03:25:02.765 UTC client backend[28454] 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-02-01 03:25:02.767 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.8", size 204800
2025-02-01 03:25:02.767 UTC client backend[28454] 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-02-01 03:25:02.773 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.9", size 204800
2025-02-01 03:25:02.773 UTC client backend[28454] 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-02-01 03:25:02.780 UTC client backend[28454] pg_regress/aggregates LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp28454.10", size 229376
2025-02-01 03:25:02.780 UTC client backend[28454] 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-02-01 03:25:02.868 UTC client backend[28460] pg_regress/join ERROR:  join expression "ss" has 3 columns available but 4 columns specified
2025-02-01 03:25:02.868 UTC client backend[28460] pg_regress/join STATEMENT:  SELECT * FROM (int8_tbl i cross join int4_tbl j) ss(a,b,c,d);
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  column "f1" does not exist at character 38
2025-02-01 03:25:02.871 UTC client backend[28460] 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-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join HINT:  To reference that column, you must mark this subquery with LATERAL.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a, (select f1 as g) ss;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "a" at character 38
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "a", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join HINT:  To reference that table, you must mark this subquery with LATERAL.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a, (select a.f1 as g) ss;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  column "f1" does not exist at character 48
2025-02-01 03:25:02.871 UTC client backend[28460] 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-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join HINT:  To reference that column, you must mark this subquery with LATERAL.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a cross join (select f1 as g) ss;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "a" at character 48
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "a", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join HINT:  To reference that table, you must mark this subquery with LATERAL.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a cross join (select a.f1 as g) ss;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "a" at character 67
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join DETAIL:  The combining JOIN type must be INNER or LEFT for a LATERAL reference.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a right join lateral generate_series(0, a.f1) g on true;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "a" at character 66
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join DETAIL:  The combining JOIN type must be INNER or LEFT for a LATERAL reference.
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select f1,g from int4_tbl a full join lateral generate_series(0, a.f1) g on true;
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  table reference "x" is ambiguous at character 78
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select * from
	  int8_tbl x cross join (int4_tbl x cross join lateral (select x.f1) ss);
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join ERROR:  aggregate functions are not allowed in FROM clause of their own query level at character 40
2025-02-01 03:25:02.871 UTC client backend[28460] pg_regress/join STATEMENT:  select 1 from tenk1 a, lateral (select max(a.unique1) from int4_tbl b) ss;
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join ERROR:  column "x1" does not exist at character 64
2025-02-01 03:25:02.872 UTC client backend[28460] 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-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join STATEMENT:  update xx1 set x2 = f1 from (select * from int4_tbl where f1 = x1) ss;
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "xx1" at character 64
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "xx1", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join STATEMENT:  update xx1 set x2 = f1 from (select * from int4_tbl where f1 = xx1.x1) ss;
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "xx1" at character 72
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join HINT:  There is an entry for table "xx1", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.872 UTC client backend[28460] pg_regress/join STATEMENT:  update xx1 set x2 = f1 from lateral (select * from int4_tbl where f1 = x1) ss;
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join ERROR:  table name "xx1" specified more than once
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join STATEMENT:  update xx1 set x2 = f1 from xx1, lateral (select * from int4_tbl where f1 = x1) ss;
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join ERROR:  column "x1" does not exist at character 58
2025-02-01 03:25:02.873 UTC client backend[28460] 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-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join STATEMENT:  delete from xx1 using (select * from int4_tbl where f1 = x1) ss;
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "xx1" at character 58
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join DETAIL:  There is an entry for table "xx1", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join STATEMENT:  delete from xx1 using (select * from int4_tbl where f1 = xx1.x1) ss;
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join ERROR:  invalid reference to FROM-clause entry for table "xx1" at character 66
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join HINT:  There is an entry for table "xx1", but it cannot be referenced from this part of the query.
2025-02-01 03:25:02.873 UTC client backend[28460] pg_regress/join STATEMENT:  delete from xx1 using lateral (select * from int4_tbl where f1 = x1) ss;
2025-02-01 03:25:05.506 UTC client backend[28451] pg_regress/btree_index ERROR:  operator class int4_ops has no options
2025-02-01 03:25:05.506 UTC client backend[28451] pg_regress/btree_index STATEMENT:  create index on btree_tall_tbl (id int4_ops(foo=1));
2025-02-01 03:25:05.563 UTC client backend[28451] pg_regress/btree_index ERROR:  ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_tall_idx2"
2025-02-01 03:25:05.563 UTC client backend[28451] pg_regress/btree_index DETAIL:  This operation is not supported for indexes.
2025-02-01 03:25:05.563 UTC client backend[28451] pg_regress/btree_index STATEMENT:  ALTER INDEX btree_tall_idx2 ALTER COLUMN id SET (n_distinct=100);
2025-02-01 03:25:05.565 UTC client backend[28451] pg_regress/btree_index ERROR:  ALTER action ALTER COLUMN ... SET cannot be performed on relation "btree_part_idx"
2025-02-01 03:25:05.565 UTC client backend[28451] pg_regress/btree_index DETAIL:  This operation is not supported for partitioned indexes.
2025-02-01 03:25:05.565 UTC client backend[28451] pg_regress/btree_index STATEMENT:  ALTER INDEX btree_part_idx ALTER COLUMN id SET (n_distinct=100);
2025-02-01 03:25:05.889 UTC client backend[29309] pg_regress/privileges ERROR:  role "regress_priv_user5" already exists
2025-02-01 03:25:05.889 UTC client backend[29309] pg_regress/privileges STATEMENT:  CREATE USER regress_priv_user5;
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges ERROR:  ADMIN option cannot be granted back to your own grantor
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges STATEMENT:  GRANT regress_priv_user1 TO regress_priv_user2 WITH ADMIN OPTION GRANTED BY regress_priv_user3;
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges ERROR:  dependent privileges exist
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges HINT:  Use CASCADE to revoke them too.
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges STATEMENT:  REVOKE ADMIN OPTION FOR regress_priv_user1 FROM regress_priv_user2;
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges ERROR:  dependent privileges exist
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges HINT:  Use CASCADE to revoke them too.
2025-02-01 03:25:05.891 UTC client backend[29309] pg_regress/privileges STATEMENT:  REVOKE regress_priv_user1 FROM regress_priv_user2;
2025-02-01 03:25:05.894 UTC client backend[29309] pg_regress/privileges ERROR:  role "regress_priv_user2" cannot be dropped because some objects depend on it
2025-02-01 03:25:05.894 UTC client backend[29309] pg_regress/privileges DETAIL:  privileges for membership of role regress_priv_user3 in role regress_priv_user1
2025-02-01 03:25:05.894 UTC client backend[29309] pg_regress/privileges STATEMENT:  DROP ROLE regress_priv_user2;
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist ERROR:  invalid value for enum option "buffering": invalid_value
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist DETAIL:  Valid values are "on", "off", and "auto".
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist STATEMENT:  create index gist_pointidx5 on gist_point_tbl using gist(p) with (buffering = invalid_value);
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist ERROR:  value 9 out of bounds for option "fillfactor"
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:05.906 UTC client backend[29315] pg_regress/gist STATEMENT:  create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=9);
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON TABLE seclabel_tbl1 IS 'classified';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  security label provider "dummy" is not loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL FOR 'dummy' ON TABLE seclabel_tbl1 IS 'classified';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON TABLE seclabel_tbl1 IS '...invalid label...';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON TABLE seclabel_tbl3 IS 'unclassified';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON ROLE regress_seclabel_user1 IS 'classified';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  security label provider "dummy" is not loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL FOR 'dummy' ON ROLE regress_seclabel_user1 IS 'classified';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON ROLE regress_seclabel_user1 IS '...invalid label...';
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label ERROR:  no security label providers have been loaded
2025-02-01 03:25:05.908 UTC client backend[29308] pg_regress/security_label STATEMENT:  SECURITY LABEL ON ROLE regress_seclabel_user3 IS 'unclassified';
2025-02-01 03:25:05.911 UTC client backend[29315] pg_regress/gist ERROR:  value 101 out of bounds for option "fillfactor"
2025-02-01 03:25:05.911 UTC client backend[29315] pg_regress/gist DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:05.911 UTC client backend[29315] pg_regress/gist STATEMENT:  create index gist_pointidx5 on gist_point_tbl using gist(p) with (fillfactor=101);
2025-02-01 03:25:05.917 UTC client backend[29309] pg_regress/privileges ERROR:  role "regress_priv_user2" cannot be dropped because some objects depend on it
2025-02-01 03:25:05.917 UTC client backend[29309] pg_regress/privileges DETAIL:  privileges for membership of role regress_priv_user3 in role regress_priv_user1
2025-02-01 03:25:05.917 UTC client backend[29309] pg_regress/privileges STATEMENT:  DROP ROLE regress_priv_user2;
2025-02-01 03:25:05.921 UTC client backend[29309] pg_regress/privileges ERROR:  role "regress_priv_user3" cannot be dropped because some objects depend on it
2025-02-01 03:25:05.921 UTC client backend[29309] pg_regress/privileges DETAIL:  privileges for membership of role regress_priv_user4 in role regress_priv_user1
2025-02-01 03:25:05.921 UTC client backend[29309] pg_regress/privileges STATEMENT:  DROP ROLE regress_priv_user3;
2025-02-01 03:25:05.922 UTC client backend[29309] pg_regress/privileges ERROR:  role "regress_priv_user5" cannot be dropped because some objects depend on it
2025-02-01 03:25:05.922 UTC client backend[29309] pg_regress/privileges DETAIL:  privileges for membership of role regress_priv_user6 in role regress_priv_user1
2025-02-01 03:25:05.922 UTC client backend[29309] pg_regress/privileges STATEMENT:  DROP ROLE regress_priv_user5;
2025-02-01 03:25:05.922 UTC client backend[29300] pg_regress/collate ERROR:  collations are not supported by type integer at character 44
2025-02-01 03:25:05.922 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE TABLE collate_test_fail (
	    a int COLLATE "C",
	    b text
	);
2025-02-01 03:25:05.935 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest3" is already an identity column
2025-02-01 03:25:05.935 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest3 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:05.943 UTC client backend[29323] pg_regress/password ERROR:  invalid value for parameter "password_encryption": "novalue"
2025-02-01 03:25:05.943 UTC client backend[29323] pg_regress/password HINT:  Available values: md5, scram-sha-256.
2025-02-01 03:25:05.943 UTC client backend[29323] pg_regress/password STATEMENT:  SET password_encryption = 'novalue';
2025-02-01 03:25:05.945 UTC client backend[29323] pg_regress/password ERROR:  invalid value for parameter "password_encryption": "true"
2025-02-01 03:25:05.945 UTC client backend[29323] pg_regress/password HINT:  Available values: md5, scram-sha-256.
2025-02-01 03:25:05.945 UTC client backend[29323] pg_regress/password STATEMENT:  SET password_encryption = true;
2025-02-01 03:25:05.946 UTC client backend[29323] pg_regress/password WARNING:  setting an MD5-encrypted password
2025-02-01 03:25:05.946 UTC client backend[29323] pg_regress/password DETAIL:  MD5 password support is deprecated and will be removed in a future release of PostgreSQL.
2025-02-01 03:25:05.946 UTC client backend[29323] pg_regress/password HINT:  Refer to the PostgreSQL documentation for details about migrating to another password type.
2025-02-01 03:25:05.947 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to set role "pg_read_all_settings"
2025-02-01 03:25:05.947 UTC client backend[29309] pg_regress/privileges STATEMENT:  SET ROLE pg_read_all_settings;
2025-02-01 03:25:05.947 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to set role "pg_read_all_stats"
2025-02-01 03:25:05.947 UTC client backend[29309] pg_regress/privileges STATEMENT:  SET ROLE pg_read_all_stats;
2025-02-01 03:25:05.950 UTC client backend[29323] pg_regress/password WARNING:  setting an MD5-encrypted password
2025-02-01 03:25:05.950 UTC client backend[29323] pg_regress/password DETAIL:  MD5 password support is deprecated and will be removed in a future release of PostgreSQL.
2025-02-01 03:25:05.950 UTC client backend[29323] pg_regress/password HINT:  Refer to the PostgreSQL documentation for details about migrating to another password type.
2025-02-01 03:25:05.958 UTC client backend[29301] pg_regress/rowsecurity ERROR:  unrecognized row security option "ugly" at character 33
2025-02-01 03:25:05.958 UTC client backend[29301] pg_regress/rowsecurity HINT:  Only PERMISSIVE or RESTRICTIVE policies are supported currently.
2025-02-01 03:25:05.958 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  CREATE POLICY p1 ON document AS UGLY
	    USING (dlevel <= (SELECT seclv FROM uaccount WHERE pguser = current_user));
2025-02-01 03:25:05.968 UTC client backend[29322] pg_regress/matview ERROR:  materialized view "mvtest_tm" has not been populated
2025-02-01 03:25:05.968 UTC client backend[29322] pg_regress/matview HINT:  Use the REFRESH MATERIALIZED VIEW command.
2025-02-01 03:25:05.968 UTC client backend[29322] pg_regress/matview STATEMENT:  SELECT * FROM mvtest_tm ORDER BY type;
2025-02-01 03:25:05.991 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use non-unique index "test_replica_identity_keyab" as replica identity
2025-02-01 03:25:05.991 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_keyab;
2025-02-01 03:25:06.000 UTC client backend[29307] pg_regress/replica_identity ERROR:  index "test_replica_identity_nonkey" cannot be used as replica identity because column "nonkey" is nullable
2025-02-01 03:25:06.000 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_nonkey;
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password WARNING:  setting an MD5-encrypted password
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password DETAIL:  MD5 password support is deprecated and will be removed in a future release of PostgreSQL.
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password HINT:  Refer to the PostgreSQL documentation for details about migrating to another password type.
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password WARNING:  setting an MD5-encrypted password
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password DETAIL:  MD5 password support is deprecated and will be removed in a future release of PostgreSQL.
2025-02-01 03:25:06.002 UTC client backend[29323] pg_regress/password HINT:  Refer to the PostgreSQL documentation for details about migrating to another password type.
2025-02-01 03:25:06.007 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use non-unique index "test_replica_identity_hash" as replica identity
2025-02-01 03:25:06.007 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_hash;
2025-02-01 03:25:06.007 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use expression index "test_replica_identity_expr" as replica identity
2025-02-01 03:25:06.007 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_expr;
2025-02-01 03:25:06.011 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use partial index "test_replica_identity_partial" as replica identity
2025-02-01 03:25:06.011 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_partial;
2025-02-01 03:25:06.011 UTC client backend[29307] pg_regress/replica_identity ERROR:  "test_replica_identity_othertable_pkey" is not an index for table "test_replica_identity"
2025-02-01 03:25:06.011 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_othertable_pkey;
2025-02-01 03:25:06.012 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use non-immediate index "test_replica_identity_unique_defer" as replica identity
2025-02-01 03:25:06.012 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity REPLICA IDENTITY USING INDEX test_replica_identity_unique_defer;
2025-02-01 03:25:06.012 UTC client backend[29307] pg_regress/replica_identity ERROR:  cannot use non-immediate index "pk" as replica identity
2025-02-01 03:25:06.012 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity_t3 REPLICA IDENTITY USING INDEX pk;
2025-02-01 03:25:06.018 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between explicit collations "C" and "POSIX" at character 58
2025-02-01 03:25:06.018 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT * FROM collate_test1 WHERE b COLLATE "C" >= 'bbc' COLLATE "POSIX";
2025-02-01 03:25:06.019 UTC client backend[29300] pg_regress/collate ERROR:  collations are not supported by type integer at character 31
2025-02-01 03:25:06.019 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE DOMAIN testdomain_i AS int COLLATE "POSIX";
2025-02-01 03:25:06.019 UTC client backend[29317] pg_regress/lock ERROR:  permission denied for table lock_tbl2
2025-02-01 03:25:06.019 UTC client backend[29317] pg_regress/lock STATEMENT:  LOCK TABLE lock_tbl2;
2025-02-01 03:25:06.020 UTC client backend[29317] pg_regress/lock ERROR:  permission denied for view lock_view1
2025-02-01 03:25:06.020 UTC client backend[29317] pg_regress/lock STATEMENT:  LOCK TABLE lock_view1;
2025-02-01 03:25:06.023 UTC client backend[29313] pg_regress/object_address WARNING:  "wal_level" is insufficient to publish logical changes
2025-02-01 03:25:06.023 UTC client backend[29313] pg_regress/object_address HINT:  Set "wal_level" to "logical" before creating subscriptions.
2025-02-01 03:25:06.023 UTC client backend[29313] pg_regress/object_address WARNING:  "wal_level" is insufficient to publish logical changes
2025-02-01 03:25:06.023 UTC client backend[29313] pg_regress/object_address HINT:  Set "wal_level" to "logical" before creating subscriptions.
2025-02-01 03:25:06.024 UTC client backend[29313] pg_regress/object_address WARNING:  subscription was created, but is not connected
2025-02-01 03:25:06.024 UTC client backend[29313] pg_regress/object_address HINT:  To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription.
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address ERROR:  unrecognized object type "stone"
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('stone', '{}', '{}');
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be at least 1
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('table', '{}', '{}');
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address ERROR:  name or argument lists may not contain nulls
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('table', '{NULL}', '{}');
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address WARNING:  error for toast table: unsupported object type "toast table"
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address WARNING:  error for index column: unsupported object type "index column"
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence column: unsupported object type "sequence column"
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address WARNING:  error for toast table column: unsupported object type "toast table column"
2025-02-01 03:25:06.029 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.030 UTC client backend[29313] pg_regress/object_address WARNING:  error for view column: unsupported object type "view column"
2025-02-01 03:25:06.030 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.035 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest4" must be declared NOT NULL before identity can be added
2025-02-01 03:25:06.035 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.035 UTC client backend[29317] pg_regress/lock ERROR:  permission denied for view lock_view8
2025-02-01 03:25:06.035 UTC client backend[29317] pg_regress/lock STATEMENT:  LOCK TABLE lock_view8;
2025-02-01 03:25:06.036 UTC client backend[29314] pg_regress/identity ERROR:  column "c" of relation "itest4" does not exist
2025-02-01 03:25:06.036 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN c ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.036 UTC client backend[29317] pg_regress/lock ERROR:  permission denied for table lock_tbl1
2025-02-01 03:25:06.036 UTC client backend[29317] pg_regress/lock STATEMENT:  LOCK TABLE lock_view8;
2025-02-01 03:25:06.036 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest4" is an identity column
2025-02-01 03:25:06.036 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN a DROP NOT NULL;
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view column: unsupported object type "materialized view column"
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 11 at RAISE
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address ERROR:  operator 1 (int4, bool) of operator family integer_ops for access method btree does not exist
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address STATEMENT:  select * from pg_get_object_address('operator of access method', '{btree,integer_ops,1}', '{int4,bool}');
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address ERROR:  operator 99 (int4, int4) of operator family integer_ops for access method btree does not exist
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address STATEMENT:  select * from pg_get_object_address('operator of access method', '{btree,integer_ops,99}', '{int4,int4}');
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address ERROR:  function 1 (int4, bool) of operator family integer_ops for access method btree does not exist
2025-02-01 03:25:06.037 UTC client backend[29313] pg_regress/object_address STATEMENT:  select * from pg_get_object_address('function of access method', '{btree,integer_ops,1}', '{int4,bool}');
2025-02-01 03:25:06.038 UTC client backend[29313] pg_regress/object_address ERROR:  function 99 (int4, int4) of operator family integer_ops for access method btree does not exist
2025-02-01 03:25:06.038 UTC client backend[29313] pg_regress/object_address STATEMENT:  select * from pg_get_object_address('function of access method', '{btree,integer_ops,99}', '{int4,int4}');
2025-02-01 03:25:06.038 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.038 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.039 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for index,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for sequence,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.040 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for materialized view,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{eins},{}: relation "eins" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{addr_nsp,zwei},{}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{eins,zwei,drei},{}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{eins},{}: column name must be qualified
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{eins},{integer}: column name must be qualified
2025-02-01 03:25:06.041 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.042 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest4" is already an identity column
2025-02-01 03:25:06.042 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.042 UTC client backend[29314] pg_regress/identity ERROR:  identity column type must be smallint, integer, or bigint
2025-02-01 03:25:06.042 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN b ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address WARNING:  error for table column,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{eins},{}: column name must be qualified
2025-02-01 03:25:06.046 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.047 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{eins},{integer}: column name must be qualified
2025-02-01 03:25:06.047 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for foreign table column,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{eins},{}: aggregate eins(*) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{eins},{integer}: aggregate eins(integer) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{addr_nsp,zwei},{}: aggregate addr_nsp.zwei(*) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{addr_nsp,zwei},{integer}: aggregate addr_nsp.zwei(integer) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for aggregate,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{eins},{}: function eins() does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{eins},{integer}: function eins(integer) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{addr_nsp,zwei},{}: function addr_nsp.zwei() does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{addr_nsp,zwei},{integer}: function addr_nsp.zwei(integer) does not exist
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address WARNING:  error for function,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.048 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{eins},{}: procedure eins() does not exist
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{eins},{integer}: procedure eins(integer) does not exist
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{addr_nsp,zwei},{}: procedure addr_nsp.zwei() does not exist
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{addr_nsp,zwei},{integer}: procedure addr_nsp.zwei(integer) does not exist
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address WARNING:  error for procedure,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.049 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{eins},{}: type "eins" does not exist
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{eins},{integer}: type "eins" does not exist
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for type,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{eins},{integer}: type "eins" does not exist
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for cast,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{eins},{}: must specify relation and object name
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{eins},{integer}: must specify relation and object name
2025-02-01 03:25:06.051 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for table constraint,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{eins},{integer}: type "eins" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for domain constraint,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{eins},{}: conversion "eins" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{eins},{integer}: conversion "eins" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{addr_nsp,zwei},{}: conversion "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{addr_nsp,zwei},{integer}: conversion "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address WARNING:  error for conversion,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.052 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{eins},{}: column name must be qualified
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{eins},{integer}: column name must be qualified
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.053 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for default value,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{eins},{}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{eins},{integer}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{addr_nsp,zwei},{}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{addr_nsp,zwei},{integer}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{eins,zwei,drei},{}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator,{eins,zwei,drei},{integer}: argument list length must be exactly 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{eins},{}: name list length must be at least 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{eins},{integer}: name list length must be at least 2
2025-02-01 03:25:06.055 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{eins,zwei,drei},{}: access method "eins" does not exist
2025-02-01 03:25:06.056 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.057 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator class,{eins,zwei,drei},{integer}: access method "eins" does not exist
2025-02-01 03:25:06.057 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.057 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{eins},{}: name list length must be at least 2
2025-02-01 03:25:06.057 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{eins},{integer}: name list length must be at least 2
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{addr_nsp,zwei},{}: access method "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{addr_nsp,zwei},{integer}: access method "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{eins,zwei,drei},{}: access method "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator family,{eins,zwei,drei},{integer}: access method "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{eins},{}: must specify relation and object name
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{eins},{integer}: must specify relation and object name
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for rule,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{eins},{}: must specify relation and object name
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{eins},{integer}: must specify relation and object name
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address WARNING:  error for trigger,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.058 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{eins},{}: text search parser "eins" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{eins},{integer}: text search parser "eins" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{addr_nsp,zwei},{}: text search parser "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{addr_nsp,zwei},{integer}: text search parser "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search parser,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{eins},{}: text search dictionary "eins" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{eins},{integer}: text search dictionary "eins" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{addr_nsp,zwei},{}: text search dictionary "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{addr_nsp,zwei},{integer}: text search dictionary "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.059 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search dictionary,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{eins},{}: text search template "eins" does not exist
2025-02-01 03:25:06.060 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{eins},{integer}: text search template "eins" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{addr_nsp,zwei},{}: text search template "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{addr_nsp,zwei},{integer}: text search template "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search template,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{eins},{}: text search configuration "eins" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{eins},{integer}: text search configuration "eins" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{addr_nsp,zwei},{}: text search configuration "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{addr_nsp,zwei},{integer}: text search configuration "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{eins,zwei,drei},{}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for text search configuration,{eins,zwei,drei},{integer}: cross-database references are not implemented: eins.zwei.drei
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{eins},{}: must specify relation and object name
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{eins},{integer}: must specify relation and object name
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{addr_nsp,zwei},{}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{addr_nsp,zwei},{integer}: relation "addr_nsp" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{eins,zwei,drei},{}: schema "eins" does not exist
2025-02-01 03:25:06.061 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address WARNING:  error for policy,{eins,zwei,drei},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{eins},{integer}: user mapping for user "eins" on server "integer" does not exist
2025-02-01 03:25:06.062 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.064 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.064 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.064 UTC client backend[29323] pg_regress/password WARNING:  setting an MD5-encrypted password
2025-02-01 03:25:06.064 UTC client backend[29323] pg_regress/password DETAIL:  MD5 password support is deprecated and will be removed in a future release of PostgreSQL.
2025-02-01 03:25:06.064 UTC client backend[29323] pg_regress/password HINT:  Refer to the PostgreSQL documentation for details about migrating to another password type.
2025-02-01 03:25:06.064 UTC client backend[29314] pg_regress/identity ERROR:  identity column type must be smallint, integer, or bigint
2025-02-01 03:25:06.064 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest_err_1 (a text generated by default as identity);
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity ERROR:  multiple identity specifications for column "a" of table "itest_err_2" at character 62
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest_err_2 (a int generated always as identity generated by default as identity);
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity ERROR:  both default and identity specified for column "a" of table "itest_err_3" at character 43
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest_err_3 (a int default 5 generated by default as identity);
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity ERROR:  both default and identity specified for column "a" of table "itest_err_4"
2025-02-01 03:25:06.065 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest_err_4 (a serial generated by default as identity);
2025-02-01 03:25:06.066 UTC client backend[29305] pg_regress/generated_stored ERROR:  multiple generation clauses specified for column "b" of table "gtest_err_1" at character 87
2025-02-01 03:25:06.066 UTC client backend[29305] 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-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample ERROR:  tablesample method foobar does not exist at character 45
2025-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE FOOBAR (1);
2025-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample ERROR:  TABLESAMPLE parameter cannot be null
2025-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (NULL);
2025-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample ERROR:  TABLESAMPLE REPEATABLE parameter cannot be null
2025-02-01 03:25:06.066 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (50) REPEATABLE (NULL);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  sample percentage must be between 0 and 100
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (-1);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  sample percentage must be between 0 and 100
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE BERNOULLI (200);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  sample percentage must be between 0 and 100
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (-1);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  sample percentage must be between 0 and 100
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (200);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  TABLESAMPLE clause can only be applied to tables and materialized views at character 16
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT id FROM test_tablesample_v1 TABLESAMPLE BERNOULLI (1);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  cannot insert into view "test_tablesample_v1"
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample DETAIL:  Views containing TABLESAMPLE are not automatically updatable.
2025-02-01 03:25:06.067 UTC client backend[29299] 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-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  INSERT INTO test_tablesample_v1 VALUES(1);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  TABLESAMPLE clause can only be applied to tables and materialized views at character 69
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  WITH query_select AS (SELECT * FROM test_tablesample)
	SELECT * FROM query_select TABLESAMPLE BERNOULLI (5.5) REPEATABLE (1);
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample ERROR:  syntax error at or near "TABLESAMPLE" at character 55
2025-02-01 03:25:06.067 UTC client backend[29299] pg_regress/tablesample STATEMENT:  SELECT q.* FROM (SELECT * FROM test_tablesample) as q TABLESAMPLE BERNOULLI (5);
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for user mapping,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{eins},{integer}: unrecognized default ACL object type "i"
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{addr_nsp,zwei},{}: argument list length must be exactly 1
2025-02-01 03:25:06.071 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{addr_nsp,zwei},{integer}: unrecognized default ACL object type "i"
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{eins,zwei,drei},{}: argument list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for default acl,{eins,zwei,drei},{integer}: unrecognized default ACL object type "i"
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{eins},{integer}: type "eins" does not exist
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for transform,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{eins},{}: name list length must be at least 3
2025-02-01 03:25:06.072 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.073 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{eins},{integer}: name list length must be at least 3
2025-02-01 03:25:06.073 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{addr_nsp,zwei},{}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{eins,zwei,drei},{}: argument list length must be exactly 2
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for operator of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{eins},{}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{eins},{integer}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{addr_nsp,zwei},{}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{addr_nsp,zwei},{integer}: name list length must be at least 3
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{eins,zwei,drei},{}: argument list length must be exactly 2
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for function of access method,{eins,zwei,drei},{integer}: argument list length must be exactly 2
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{eins},{integer}: schema "eins" does not exist
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{addr_nsp,zwei},{}: name list length must be exactly 1
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{addr_nsp,zwei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{eins,zwei,drei},{}: name list length must be exactly 1
2025-02-01 03:25:06.075 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication namespace,{eins,zwei,drei},{integer}: name list length must be exactly 1
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{eins},{}: argument list length must be exactly 1
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{eins},{integer}: relation "eins" does not exist
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{addr_nsp,zwei},{}: argument list length must be exactly 1
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{addr_nsp,zwei},{integer}: relation "addr_nsp.zwei" does not exist
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{eins,zwei,drei},{}: argument list length must be exactly 1
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address WARNING:  error for publication relation,{eins,zwei,drei},{integer}: cross-database references are not implemented: "eins.zwei.drei"
2025-02-01 03:25:06.076 UTC client backend[29313] pg_regress/object_address CONTEXT:  PL/pgSQL function inline_code_block line 27 at RAISE
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to alter role
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges DETAIL:  Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members.
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges STATEMENT:  ALTER GROUP regress_priv_group2 ADD USER regress_priv_user2;
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to alter role
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges DETAIL:  Only roles with the ADMIN option on role "regress_priv_group2" may add or drop members.
2025-02-01 03:25:06.083 UTC client backend[29309] pg_regress/privileges STATEMENT:  ALTER GROUP regress_priv_group2 DROP USER regress_priv_user2;
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  language "one" does not exist
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('language', '{one}', '{}');
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('language', '{one,two}', '{}');
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  large object 123 does not exist
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('large object', '{123}', '{}');
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('large object', '{123,456}', '{}');
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  invalid input syntax for type oid: "blargh"
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('large object', '{blargh}', '{}');
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address ERROR:  schema "one" does not exist
2025-02-01 03:25:06.084 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('schema', '{one}', '{}');
2025-02-01 03:25:06.087 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use generated column "b" in column generation expression at character 74
2025-02-01 03:25:06.087 UTC client backend[29305] pg_regress/generated_stored DETAIL:  A generated column cannot reference another generated column.
2025-02-01 03:25:06.087 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_2a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (b * 2) STORED);
2025-02-01 03:25:06.090 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to alter role
2025-02-01 03:25:06.090 UTC client backend[29309] 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-02-01 03:25:06.090 UTC client backend[29309] pg_regress/privileges STATEMENT:  ALTER USER regress_priv_user2 PASSWORD 'verysecret';
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest5 VALUES (1, 'a');
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest5 VALUES (2, 'b'), (3, 'c');
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.092 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest5 VALUES (DEFAULT, 'b'), (3, 'c');
2025-02-01 03:25:06.093 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.093 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.093 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.093 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest5 VALUES (2, 'b'), (DEFAULT, 'c');
2025-02-01 03:25:06.094 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied to grant privileges as role "regress_priv_role"
2025-02-01 03:25:06.094 UTC client backend[29309] pg_regress/privileges DETAIL:  The grantor must have the ADMIN option on role "regress_priv_role".
2025-02-01 03:25:06.094 UTC client backend[29309] pg_regress/privileges STATEMENT:  GRANT regress_priv_role TO regress_priv_user1 WITH ADMIN OPTION GRANTED BY regress_priv_role;
2025-02-01 03:25:06.095 UTC client backend[29309] pg_regress/privileges ERROR:  role "foo" does not exist
2025-02-01 03:25:06.095 UTC client backend[29309] pg_regress/privileges STATEMENT:  REVOKE ADMIN OPTION FOR regress_priv_role FROM regress_priv_user1 GRANTED BY foo;
2025-02-01 03:25:06.095 UTC client backend[29309] pg_regress/privileges WARNING:  role "regress_priv_user1" has not been granted membership in role "regress_priv_role" by role "regress_priv_user2"
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('schema', '{one,two}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  role "one" does not exist
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('role', '{one}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('role', '{one,two}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  database "one" does not exist
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('database', '{one}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('database', '{one,two}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  tablespace "one" does not exist
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('tablespace', '{one}', '{}');
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.099 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('tablespace', '{one,two}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  foreign-data wrapper "one" does not exist
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('foreign-data wrapper', '{one}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('foreign-data wrapper', '{one,two}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  server "one" does not exist
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('server', '{one}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('server', '{one,two}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  extension "one" does not exist
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('extension', '{one}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('extension', '{one,two}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  event trigger "one" does not exist
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('event trigger', '{one}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('event trigger', '{one,two}', '{}');
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address ERROR:  access method "one" does not exist
2025-02-01 03:25:06.100 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('access method', '{one}', '{}');
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('access method', '{one,two}', '{}');
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address ERROR:  publication "one" does not exist
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('publication', '{one}', '{}');
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('publication', '{one,two}', '{}');
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address ERROR:  subscription "one" does not exist
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('subscription', '{one}', '{}');
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address ERROR:  name list length must be exactly 1
2025-02-01 03:25:06.101 UTC client backend[29313] pg_regress/object_address STATEMENT:  SELECT pg_get_object_address('subscription', '{one,two}', '{}');
2025-02-01 03:25:06.107 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between explicit collations "C" and "POSIX" at character 36
2025-02-01 03:25:06.107 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT string_agg(x COLLATE "C", y COLLATE "POSIX") FROM collate_test10;
2025-02-01 03:25:06.107 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.107 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.107 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.107 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest2 VALUES (10, 'xyz');
2025-02-01 03:25:06.108 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between implicit collations "C" and "POSIX" at character 32
2025-02-01 03:25:06.108 UTC client backend[29300] pg_regress/collate HINT:  You can choose the collation by applying the COLLATE clause to one or both expressions.
2025-02-01 03:25:06.108 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT array_agg(a ORDER BY x||y) FROM collate_test10;
2025-02-01 03:25:06.109 UTC client backend[29314] pg_regress/identity ERROR:  column "a" can only be updated to DEFAULT
2025-02-01 03:25:06.109 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.109 UTC client backend[29314] pg_regress/identity STATEMENT:  UPDATE itest2 SET a = 101 WHERE a = 1;
2025-02-01 03:25:06.111 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use generated column "b" in column generation expression at character 116
2025-02-01 03:25:06.111 UTC client backend[29305] pg_regress/generated_stored DETAIL:  A generated column cannot reference another generated column.
2025-02-01 03:25:06.111 UTC client backend[29305] 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-02-01 03:25:06.123 UTC client backend[29309] pg_regress/privileges ERROR:  grantor must be current user
2025-02-01 03:25:06.123 UTC client backend[29309] pg_regress/privileges STATEMENT:  GRANT TRUNCATE ON atest2 TO regress_priv_user4 GRANTED BY regress_priv_user5;
2025-02-01 03:25:06.123 UTC client backend[29300] pg_regress/collate ERROR:  could not determine which collation to use for string comparison
2025-02-01 03:25:06.123 UTC client backend[29300] pg_regress/collate HINT:  Use the COLLATE clause to set the collation explicitly.
2025-02-01 03:25:06.123 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2 ORDER BY 2;
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between implicit collations "C" and "POSIX" at character 48
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate HINT:  You can choose the collation by applying the COLLATE clause to one or both expressions.
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT a, b FROM collate_test1 UNION SELECT a, b FROM collate_test2 ORDER BY 2;
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between implicit collations "C" and "POSIX" at character 52
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate HINT:  You can choose the collation by applying the COLLATE clause to one or both expressions.
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT a, b FROM collate_test1 INTERSECT SELECT a, b FROM collate_test2 ORDER BY 2;
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between implicit collations "C" and "POSIX" at character 49
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate HINT:  You can choose the collation by applying the COLLATE clause to one or both expressions.
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT a, b FROM collate_test1 EXCEPT SELECT a, b FROM collate_test2 ORDER BY 2;
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate ERROR:  no collation was derived for column "b" with collatable type text
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate HINT:  Use the COLLATE clause to set the collation explicitly.
2025-02-01 03:25:06.124 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE TABLE test_u AS SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test2;
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate ERROR:  could not determine which collation to use for string comparison
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate HINT:  Use the COLLATE clause to set the collation explicitly.
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate STATEMENT:  select x < y from collate_test10;
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate ERROR:  collation mismatch between implicit collations "C" and "POSIX" at character 47
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate HINT:  You can choose the collation by applying the COLLATE clause to one or both expressions.
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate STATEMENT:  select x, y from collate_test10 order by x || y;
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate ERROR:  recursive query "foo" column 1 has collation "C" in non-recursive term but collation "POSIX" overall at character 37
2025-02-01 03:25:06.125 UTC client backend[29300] pg_regress/collate HINT:  Use the COLLATE clause to set the collation of the non-recursive term.
2025-02-01 03:25:06.125 UTC client backend[29300] 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-02-01 03:25:06.126 UTC client backend[29300] pg_regress/collate ERROR:  could not determine which collation to use for string hashing
2025-02-01 03:25:06.126 UTC client backend[29300] pg_regress/collate HINT:  Use the COLLATE clause to set the collation explicitly.
2025-02-01 03:25:06.126 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT * FROM collate_test10 WHERE (x, y) NOT IN (SELECT y, x FROM collate_test10);
2025-02-01 03:25:06.126 UTC client backend[29300] pg_regress/collate ERROR:  syntax error at or near "COLLATE" at character 26
2025-02-01 03:25:06.126 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT CAST('42' AS text COLLATE "C");
2025-02-01 03:25:06.134 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.134 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest2 VALUES ('foo', true);
2025-02-01 03:25:06.136 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use whole-row variable in column generation expression at character 88
2025-02-01 03:25:06.136 UTC client backend[29305] pg_regress/generated_stored DETAIL:  This would cause the generated column to depend on its own value.
2025-02-01 03:25:06.136 UTC client backend[29305] 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-02-01 03:25:06.137 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "c" does not exist at character 73
2025-02-01 03:25:06.137 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_3 (a int PRIMARY KEY, b int GENERATED ALWAYS AS (c * 2) STORED);
2025-02-01 03:25:06.138 UTC client backend[29305] pg_regress/generated_stored ERROR:  generation expression is not immutable
2025-02-01 03:25:06.138 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) STORED);
2025-02-01 03:25:06.141 UTC client backend[29305] pg_regress/generated_stored ERROR:  both default and generation expression specified for column "b" of table "gtest_err_5a" at character 63
2025-02-01 03:25:06.141 UTC client backend[29305] 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-02-01 03:25:06.141 UTC client backend[29305] pg_regress/generated_stored ERROR:  both identity and generation expression specified for column "b" of table "gtest_err_5b" at character 82
2025-02-01 03:25:06.141 UTC client backend[29305] 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-02-01 03:25:06.142 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use system column "xmin" in column generation expression at character 75
2025-02-01 03:25:06.142 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_6a (a int PRIMARY KEY, b bool GENERATED ALWAYS AS (xmin <> 37) STORED);
2025-02-01 03:25:06.142 UTC client backend[29305] pg_regress/generated_stored ERROR:  aggregate functions are not allowed in column generation expressions at character 74
2025-02-01 03:25:06.142 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_7a (a int PRIMARY KEY, b int GENERATED ALWAYS AS (avg(a)) STORED);
2025-02-01 03:25:06.144 UTC client backend[29305] pg_regress/generated_stored ERROR:  window functions are not allowed in column generation expressions at character 74
2025-02-01 03:25:06.144 UTC client backend[29305] 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-02-01 03:25:06.146 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use subquery in column generation expression at character 74
2025-02-01 03:25:06.146 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_7c (a int PRIMARY KEY, b int GENERATED ALWAYS AS ((SELECT a)) STORED);
2025-02-01 03:25:06.146 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.146 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest2 SET col2 = NOT col2;
2025-02-01 03:25:06.147 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest4" is not an identity column
2025-02-01 03:25:06.147 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest4 ALTER COLUMN a DROP IDENTITY;
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest2 FOR UPDATE;
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atest2;
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges STATEMENT:  TRUNCATE atest2;
2025-02-01 03:25:06.147 UTC client backend[29300] pg_regress/collate ERROR:  collations are not supported by type integer
2025-02-01 03:25:06.147 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE INDEX collate_test1_idx5 ON collate_test1 (a COLLATE "POSIX");
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges STATEMENT:  LOCK atest2 IN ACCESS EXCLUSIVE MODE;
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges STATEMENT:  COPY atest2 FROM stdin;
2025-02-01 03:25:06.147 UTC client backend[29309] pg_regress/privileges WARNING:  no privileges were granted for "atest1"
2025-02-01 03:25:06.149 UTC client backend[29314] pg_regress/identity ERROR:  null value in column "a" of relation "itest4" violates not-null constraint
2025-02-01 03:25:06.149 UTC client backend[29314] pg_regress/identity DETAIL:  Failing row contains (null, ).
2025-02-01 03:25:06.149 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itest4 DEFAULT VALUES;
2025-02-01 03:25:06.149 UTC client backend[29305] pg_regress/generated_stored ERROR:  set-returning functions are not allowed in column generation expressions at character 74
2025-02-01 03:25:06.149 UTC client backend[29305] 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-02-01 03:25:06.149 UTC client backend[29300] pg_regress/collate ERROR:  collations are not supported by type integer at character 54
2025-02-01 03:25:06.149 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE INDEX collate_test1_idx6 ON collate_test1 ((a COLLATE "POSIX"));
2025-02-01 03:25:06.151 UTC client backend[29305] pg_regress/generated_stored ERROR:  for a generated column, GENERATED ALWAYS must be specified at character 62
2025-02-01 03:25:06.151 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_err_8 (a int PRIMARY KEY, b int GENERATED BY DEFAULT AS (a * 2) STORED);
2025-02-01 03:25:06.153 UTC client backend[29314] pg_regress/identity ERROR:  relation "itest4_a_seq" does not exist at character 27
2025-02-01 03:25:06.153 UTC client backend[29314] pg_regress/identity STATEMENT:  SELECT sequence_name FROM itest4_a_seq;
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest2 VALUES ('foo', true);
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest1
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest1;
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.159 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest2;
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1 VALUES (3, 33);
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1 VALUES (3, 33), (4, 44);
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1 VALUES (3, DEFAULT), (4, 44);
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.164 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1 VALUES (3, 33), (4, DEFAULT);
2025-02-01 03:25:06.164 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table pg_class
2025-02-01 03:25:06.164 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE pg_catalog.pg_class SET relname = '123';
2025-02-01 03:25:06.164 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table pg_class
2025-02-01 03:25:06.164 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM pg_catalog.pg_class;
2025-02-01 03:25:06.165 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table pg_toast_1213
2025-02-01 03:25:06.165 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE pg_toast.pg_toast_1213 SET chunk_id = 1;
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest2;
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest1
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest1 VALUES (2, 'two');
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.168 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest2 VALUES ('foo', true);
2025-02-01 03:25:06.169 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest1
2025-02-01 03:25:06.169 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest1 SELECT 1, b FROM atest1;
2025-02-01 03:25:06.169 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest1
2025-02-01 03:25:06.169 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest1 SET a = 1 WHERE a = 2;
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest2 SET col2 = NOT col2;
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest1
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest1 FOR UPDATE;
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest2 FOR UPDATE;
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atest2;
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.171 UTC client backend[29309] pg_regress/privileges STATEMENT:  TRUNCATE atest2;
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges STATEMENT:  COPY atest2 FROM stdin;
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest1 WHERE ( b IN ( SELECT col1 FROM atest2 ) );
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.174 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest2 WHERE ( col1 IN ( SELECT b FROM atest1 ) );
2025-02-01 03:25:06.179 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" can only be updated to DEFAULT
2025-02-01 03:25:06.179 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.179 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  UPDATE gtest1 SET b = 11 WHERE a = 1;
2025-02-01 03:25:06.182 UTC client backend[29305] pg_regress/generated_stored ERROR:  integer out of range
2025-02-01 03:25:06.182 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1 VALUES (2000000000);
2025-02-01 03:25:06.193 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy "p1r" for table "document"
2025-02-01 03:25:06.193 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO document VALUES (100, 44, 1, 'regress_rls_dave', 'testing sorting of policies');
2025-02-01 03:25:06.193 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy "p2r" for table "document"
2025-02-01 03:25:06.193 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO document VALUES (100, 55, 1, 'regress_rls_dave', 'testing sorting of policies');
2025-02-01 03:25:06.194 UTC client backend[29301] pg_regress/rowsecurity ERROR:  must be owner of table document
2025-02-01 03:25:06.194 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  ALTER POLICY p1 ON document USING (true);
2025-02-01 03:25:06.194 UTC client backend[29301] pg_regress/rowsecurity ERROR:  must be owner of relation document
2025-02-01 03:25:06.194 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP POLICY p1 ON document;
2025-02-01 03:25:06.197 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:06.197 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:06.197 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:06.197 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT INTO itestv11 VALUES (10, 'xyz');
2025-02-01 03:25:06.198 UTC client backend[29300] pg_regress/collate ERROR:  insert or update on table "collate_test21" violates foreign key constraint "collate_test21_f2_fkey"
2025-02-01 03:25:06.198 UTC client backend[29300] pg_regress/collate DETAIL:  Key (f2)=(baz) is not present in table "collate_test20".
2025-02-01 03:25:06.198 UTC client backend[29300] pg_regress/collate STATEMENT:  INSERT INTO collate_test21 VALUES ('baz');
2025-02-01 03:25:06.204 UTC client backend[29300] pg_regress/collate ERROR:  insert or update on table "collate_test22" violates foreign key constraint "collate_test22_f2_fkey"
2025-02-01 03:25:06.204 UTC client backend[29300] pg_regress/collate DETAIL:  Key (f2)=(baz) is not present in table "collate_test20".
2025-02-01 03:25:06.204 UTC client backend[29300] pg_regress/collate STATEMENT:  ALTER TABLE collate_test22 ADD FOREIGN KEY (f2) REFERENCES collate_test20;
2025-02-01 03:25:06.235 UTC client backend[29300] pg_regress/collate ERROR:  parameter "locale" must be specified
2025-02-01 03:25:06.235 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION builtin2 ( PROVIDER = builtin );
2025-02-01 03:25:06.235 UTC client backend[29301] pg_regress/rowsecurity ERROR:  update or delete on table "category" violates foreign key constraint "document_cid_fkey" on table "document"
2025-02-01 03:25:06.235 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  Key is still referenced from table "document".
2025-02-01 03:25:06.235 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DELETE FROM category WHERE cid = 33;
2025-02-01 03:25:06.235 UTC client backend[29300] pg_regress/collate ERROR:  invalid locale name "en_US" for builtin provider
2025-02-01 03:25:06.235 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION builtin2 ( PROVIDER = builtin, LOCALE = "en_US" );
2025-02-01 03:25:06.236 UTC client backend[29300] pg_regress/collate ERROR:  parameter "locale" must be specified
2025-02-01 03:25:06.236 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION builtin2 ( PROVIDER = builtin, LC_CTYPE = "C", LC_COLLATE = "C" );
2025-02-01 03:25:06.242 UTC client backend[29300] pg_regress/collate ERROR:  collation "default" cannot be copied
2025-02-01 03:25:06.242 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION mycoll3 FROM "default";
2025-02-01 03:25:06.242 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest1" is an identity column
2025-02-01 03:25:06.242 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest1 ALTER COLUMN a SET DEFAULT 1;
2025-02-01 03:25:06.244 UTC client backend[29301] pg_regress/rowsecurity ERROR:  duplicate key value violates unique constraint "document_pkey"
2025-02-01 03:25:06.244 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO document VALUES (8, 44, 1, 'regress_rls_bob', 'my third manga');
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate ERROR:  cannot drop collation mycoll2 because other objects depend on it
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate DETAIL:  column f1 of table collate_test23 depends on collation mycoll2
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate STATEMENT:  DROP COLLATION mycoll2;
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate ERROR:  collation attribute "Lc_Collate" not recognized at character 29
2025-02-01 03:25:06.244 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION case_coll ("Lc_Collate" = "POSIX", "Lc_Ctype" = "POSIX");
2025-02-01 03:25:06.244 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.244 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO document VALUES (8, 44, 1, 'regress_rls_carol', 'my third manga');
2025-02-01 03:25:06.244 UTC client backend[29314] pg_regress/identity ERROR:  column "a" of relation "itest5" already has a default value
2025-02-01 03:25:06.244 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest5 ALTER COLUMN a ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.245 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.245 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  UPDATE document SET did = 8, dauthor = 'regress_rls_carol' WHERE did = 5;
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (4, 8);
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (6, 66), (7, 77);
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (6, DEFAULT), (7, 77);
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.245 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (6, 66), (7, DEFAULT);
2025-02-01 03:25:06.247 UTC client backend[29300] pg_regress/collate ERROR:  collations are not supported by type integer
2025-02-01 03:25:06.247 UTC client backend[29300] pg_regress/collate STATEMENT:  SELECT collation for ((SELECT a FROM collate_test1 LIMIT 1));
2025-02-01 03:25:06.252 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.252 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.252 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (8, DEFAULT);
2025-02-01 03:25:06.253 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot insert a non-DEFAULT value into column "b"
2025-02-01 03:25:06.253 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:06.253 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest1v VALUES (8, DEFAULT), (9, DEFAULT);
2025-02-01 03:25:06.258 UTC client backend[29323] pg_regress/password ERROR:  encrypted password is too long
2025-02-01 03:25:06.258 UTC client backend[29323] pg_regress/password DETAIL:  Encrypted passwords must be no longer than 512 bytes.
2025-02-01 03:25:06.258 UTC client backend[29323] pg_regress/password STATEMENT:  CREATE ROLE regress_passwd10 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU=';
2025-02-01 03:25:06.262 UTC client backend[29323] pg_regress/password ERROR:  encrypted password is too long
2025-02-01 03:25:06.262 UTC client backend[29323] pg_regress/password DETAIL:  Encrypted passwords must be no longer than 512 bytes.
2025-02-01 03:25:06.262 UTC client backend[29323] pg_regress/password STATEMENT:  ALTER ROLE regress_passwd9 PASSWORD 'SCRAM-SHA-256$000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004096:wNFxNSk1hAXBkgub8py3bg==$65zC6E+R0U7tiYTC9+Wtq4Thw6gUDj3eDCINij8TflU=:rC1I7tcVugrHEY2DT0iPjGyjM4aJxkMM9n8WBxtUtHU=';
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 54
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_COLLATE = "NONSENSE", LC_CTYPE = "POSIX");
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 52
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LC_CTYPE = "NONSENSE", LC_COLLATE = "POSIX");
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 48
2025-02-01 03:25:06.281 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (PROVIDER = icu, PROVIDER = NONSENSE, LC_COLLATE = "POSIX", LC_CTYPE = "POSIX");
2025-02-01 03:25:06.287 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 47
2025-02-01 03:25:06.287 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION case_sensitive (LOCALE = '', LOCALE = "NONSENSE");
2025-02-01 03:25:06.288 UTC client backend[29314] pg_regress/identity ERROR:  identity column type must be smallint, integer, or bigint
2025-02-01 03:25:06.288 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest3 ALTER COLUMN a TYPE text;
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 54
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (DETERMINISTIC = TRUE, DETERMINISTIC = NONSENSE, LOCALE = '');
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options at character 47
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (VERSION = '1', VERSION = "NONSENSE", LOCALE = '');
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate DETAIL:  LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE.
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LC_CTYPE = "POSIX", LOCALE = '');
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate DETAIL:  LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE.
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (LC_COLLATE = "POSIX", LOCALE = '');
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate DETAIL:  LOCALE cannot be specified together with LC_COLLATE or LC_CTYPE.
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (LC_CTYPE = "POSIX", LOCALE = '');
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate ERROR:  conflicting or redundant options
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate DETAIL:  FROM cannot be specified together with any other options.
2025-02-01 03:25:06.289 UTC client backend[29300] pg_regress/collate STATEMENT:  CREATE COLLATION coll_dup_chk (FROM = "C", VERSION = "1");
2025-02-01 03:25:06.348 UTC client backend[29305] pg_regress/generated_stored ERROR:  child column "b" specifies generation expression
2025-02-01 03:25:06.348 UTC client backend[29305] pg_regress/generated_stored HINT:  A child table column cannot be generated unless its parent column is.
2025-02-01 03:25:06.348 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest_normal_child (a int, b int GENERATED ALWAYS AS (a * 2) STORED) INHERITS (gtest_normal);
2025-02-01 03:25:06.355 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" in child table must not be a generated column
2025-02-01 03:25:06.355 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest_normal_child INHERIT gtest_normal;
2025-02-01 03:25:06.367 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" inherits from generated column but specifies default
2025-02-01 03:25:06.367 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtestx (x int, b int DEFAULT 10) INHERITS (gtest1);
2025-02-01 03:25:06.368 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" inherits from generated column but specifies identity
2025-02-01 03:25:06.368 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtestx (x int, b int GENERATED ALWAYS AS IDENTITY) INHERITS (gtest1);
2025-02-01 03:25:06.368 UTC client backend[29318] pg_regress/groupingsets ERROR:  aggregate functions are not allowed in FROM clause of their own query level at character 69
2025-02-01 03:25:06.368 UTC client backend[29318] 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-02-01 03:25:06.411 UTC client backend[29318] pg_regress/groupingsets ERROR:  arguments to GROUPING must be grouping expressions of the associated query level at character 25
2025-02-01 03:25:06.411 UTC client backend[29318] pg_regress/groupingsets STATEMENT:  select (select grouping(a,b) from gstest2) from gstest2 group by a,b;
2025-02-01 03:25:06.420 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" in child table must be a generated column
2025-02-01 03:25:06.420 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtestxx_1 INHERIT gtest1;
2025-02-01 03:25:06.447 UTC client backend[29305] pg_regress/generated_stored ERROR:  inherited column "b" has a generation conflict
2025-02-01 03:25:06.447 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest1_y () INHERITS (gtest0, gtesty);
2025-02-01 03:25:06.455 UTC client backend[29305] pg_regress/generated_stored ERROR:  inherited column "b" has a generation conflict
2025-02-01 03:25:06.455 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty);
2025-02-01 03:25:06.463 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" inherits conflicting generation expressions
2025-02-01 03:25:06.463 UTC client backend[29305] pg_regress/generated_stored HINT:  To resolve the conflict, specify a generation expression explicitly.
2025-02-01 03:25:06.463 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest1_y () INHERITS (gtest1, gtesty);
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets ERROR:  could not implement GROUP BY
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets DETAIL:  Some of the datatypes only support hashing, while others only support sorting.
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets STATEMENT:  select count(*) from gstest4 group by rollup(unhashable_col,unsortable_col);
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets ERROR:  could not implement GROUP BY
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets DETAIL:  Some of the datatypes only support hashing, while others only support sorting.
2025-02-01 03:25:06.473 UTC client backend[29318] pg_regress/groupingsets STATEMENT:  select array_agg(v order by v) from gstest4 group by grouping sets ((id,unsortable_col),(id));
2025-02-01 03:25:06.497 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "part_document"
2025-02-01 03:25:06.497 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_dave', 'testing pp1');
2025-02-01 03:25:06.497 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy "pp1r" for table "part_document"
2025-02-01 03:25:06.497 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO part_document VALUES (100, 99, 1, 'regress_rls_dave', 'testing pp1r');
2025-02-01 03:25:06.498 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy "pp1r" for table "part_document"
2025-02-01 03:25:06.498 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO part_document VALUES (100, 55, 1, 'regress_rls_dave', 'testing RLS with partitions');
2025-02-01 03:25:06.505 UTC client backend[29318] pg_regress/groupingsets ERROR:  aggregate functions are not allowed in FROM clause of their own query level at character 69
2025-02-01 03:25:06.505 UTC client backend[29318] 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-02-01 03:25:06.506 UTC client backend[29318] pg_regress/groupingsets ERROR:  aggregate functions are not allowed in FROM clause of their own query level at character 95
2025-02-01 03:25:06.506 UTC client backend[29318] 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-02-01 03:25:06.515 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "part_document_satire"
2025-02-01 03:25:06.515 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO part_document_satire VALUES (101, 55, 1, 'regress_rls_dave', 'testing RLS with partitions');
2025-02-01 03:25:06.517 UTC client backend[29301] pg_regress/rowsecurity ERROR:  must be owner of table part_document
2025-02-01 03:25:06.517 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  ALTER POLICY pp1 ON part_document USING (true);
2025-02-01 03:25:06.517 UTC client backend[29301] pg_regress/rowsecurity ERROR:  must be owner of relation part_document
2025-02-01 03:25:06.517 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP POLICY pp1 ON part_document;
2025-02-01 03:25:06.521 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest12
2025-02-01 03:25:06.521 UTC client backend[29309] pg_regress/privileges STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM atest12 WHERE a >>> 0;
2025-02-01 03:25:06.530 UTC client backend[29322] pg_regress/matview ERROR:  cannot refresh materialized view "public.mvtest_tvmm" concurrently
2025-02-01 03:25:06.530 UTC client backend[29322] pg_regress/matview HINT:  Create a unique index with no WHERE clause on one or more columns of the materialized view.
2025-02-01 03:25:06.530 UTC client backend[29322] pg_regress/matview STATEMENT:  REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm;
2025-02-01 03:25:06.530 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "part_document"
2025-02-01 03:25:06.530 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM part_document ORDER by did;
2025-02-01 03:25:06.530 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "part_document_satire"
2025-02-01 03:25:06.530 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM part_document_satire ORDER by did;
2025-02-01 03:25:06.534 UTC client backend[29307] pg_regress/replica_identity ERROR:  column "id" is in index used as replica identity
2025-02-01 03:25:06.534 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity3 ALTER COLUMN id DROP NOT NULL;
2025-02-01 03:25:06.535 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy "pp3" for table "part_document"
2025-02-01 03:25:06.535 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO part_document VALUES (100, 11, 5, 'regress_rls_carol', 'testing pp3');
2025-02-01 03:25:06.540 UTC client backend[29301] pg_regress/rowsecurity ERROR:  cannot drop table dependee because other objects depend on it
2025-02-01 03:25:06.540 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  policy d1 on table dependent depends on table dependee
2025-02-01 03:25:06.540 UTC client backend[29301] pg_regress/rowsecurity HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:06.540 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP TABLE dependee;
2025-02-01 03:25:06.556 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "rec1"
2025-02-01 03:25:06.556 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rec1;
2025-02-01 03:25:06.580 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest3
2025-02-01 03:25:06.580 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest3;
2025-02-01 03:25:06.582 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest3
2025-02-01 03:25:06.582 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atest3;
2025-02-01 03:25:06.582 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest3
2025-02-01 03:25:06.582 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atest3;
2025-02-01 03:25:06.588 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.588 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atestv2;
2025-02-01 03:25:06.592 UTC client backend[29322] pg_regress/matview ERROR:  CONCURRENTLY and WITH NO DATA options cannot be used together
2025-02-01 03:25:06.592 UTC client backend[29322] pg_regress/matview STATEMENT:  REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tvmm WITH NO DATA;
2025-02-01 03:25:06.593 UTC client backend[29322] pg_regress/matview ERROR:  cannot lock rows in materialized view "mvtest_tvvm"
2025-02-01 03:25:06.593 UTC client backend[29322] pg_regress/matview STATEMENT:  SELECT * FROM mvtest_tvvm FOR SHARE;
2025-02-01 03:25:06.596 UTC client backend[29322] pg_regress/matview ERROR:  cannot drop table mvtest_t because other objects depend on it
2025-02-01 03:25:06.596 UTC client backend[29322] 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-02-01 03:25:06.596 UTC client backend[29322] pg_regress/matview HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:06.596 UTC client backend[29322] pg_regress/matview STATEMENT:  DROP TABLE mvtest_t;
2025-02-01 03:25:06.597 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "rec1"
2025-02-01 03:25:06.597 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rec1;
2025-02-01 03:25:06.598 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" is a generated column
2025-02-01 03:25:06.598 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Generated columns cannot be used in COPY.
2025-02-01 03:25:06.598 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  COPY gtest1 (a, b) TO stdout;
2025-02-01 03:25:06.604 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" is a generated column
2025-02-01 03:25:06.604 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Generated columns cannot be used in COPY.
2025-02-01 03:25:06.604 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  COPY gtest1 (a, b) FROM stdin;
2025-02-01 03:25:06.606 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for view atestv2
2025-02-01 03:25:06.606 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atestv2;
2025-02-01 03:25:06.606 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "rec1"
2025-02-01 03:25:06.606 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rec1;
2025-02-01 03:25:06.606 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for view atestv0
2025-02-01 03:25:06.606 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atestv0;
2025-02-01 03:25:06.607 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table int8_tbl
2025-02-01 03:25:06.607 UTC client backend[29309] 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-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" is a generated column
2025-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Generated columns cannot be used in COPY.
2025-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  COPY gtest3 (a, b) TO stdout;
2025-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "b" is a generated column
2025-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Generated columns cannot be used in COPY.
2025-02-01 03:25:06.610 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  COPY gtest3 (a, b) FROM stdin;
2025-02-01 03:25:06.611 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table int8_tbl
2025-02-01 03:25:06.611 UTC client backend[29309] 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-02-01 03:25:06.616 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "rec1"
2025-02-01 03:25:06.616 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rec1;
2025-02-01 03:25:06.618 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for view atestv3
2025-02-01 03:25:06.618 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atestv3;
2025-02-01 03:25:06.619 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.619 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atestv2;
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest5;
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT two FROM atest5;
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges STATEMENT:  COPY atest5 (two) TO stdout;
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.645 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT atest5 FROM atest5;
2025-02-01 03:25:06.646 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.646 UTC client backend[29309] pg_regress/privileges STATEMENT:  COPY atest5 (one,two) TO stdout;
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT 1 FROM atest5 a JOIN atest5 b USING (two);
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT 1 FROM atest5 a NATURAL JOIN atest5 b;
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.652 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM (atest5 a JOIN atest5 b USING (one)) j;
2025-02-01 03:25:06.654 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.654 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT j.* FROM (atest5 a JOIN atest5 b USING (one)) j;
2025-02-01 03:25:06.658 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.658 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT (j.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one)) j;
2025-02-01 03:25:06.659 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.659 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j;
2025-02-01 03:25:06.659 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.659 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT j.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j;
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j;
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT j.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one)) j;
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.660 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM (atest5 a JOIN atest5 b USING (one));
2025-02-01 03:25:06.661 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "s1"
2025-02-01 03:25:06.661 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM s1 WHERE f_leak(b);
2025-02-01 03:25:06.662 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "s1"
2025-02-01 03:25:06.662 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO s1 VALUES (1, 'foo');
2025-02-01 03:25:06.665 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.665 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT a.* FROM (atest5 a JOIN atest5 b USING (one));
2025-02-01 03:25:06.666 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.666 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT (a.*) IS NULL FROM (atest5 a JOIN atest5 b USING (one));
2025-02-01 03:25:06.666 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.666 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT a.two FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.671 UTC client backend[29322] pg_regress/matview ERROR:  could not create unique index "mvtest_mv_a_idx"
2025-02-01 03:25:06.671 UTC client backend[29322] pg_regress/matview DETAIL:  Key (a)=(1) is duplicated.
2025-02-01 03:25:06.671 UTC client backend[29322] pg_regress/matview STATEMENT:  REFRESH MATERIALIZED VIEW mvtest_mv;
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT b.y FROM (atest5 a JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.671 UTC client backend[29314] pg_regress/identity ERROR:  column "b" of relation "itest6" is not an identity column
2025-02-01 03:25:06.671 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest6 ALTER COLUMN b SET INCREMENT BY 2;
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.671 UTC client backend[29314] pg_regress/identity ERROR:  cannot change ownership of identity sequence
2025-02-01 03:25:06.671 UTC client backend[29314] pg_regress/identity DETAIL:  Sequence "itest6_a_seq" is linked to table "itest6".
2025-02-01 03:25:06.671 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER SEQUENCE itest6_a_seq OWNED BY NONE;
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.671 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT b.y FROM (atest5 a LEFT JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT b.y FROM (atest5 a FULL JOIN atest5 b(one,x,y,z) USING (one));
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.672 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT 1 FROM atest5 WHERE two = 2;
2025-02-01 03:25:06.673 UTC client backend[29322] pg_regress/matview ERROR:  new data for materialized view "mvtest_mv" contains duplicate rows without any null columns
2025-02-01 03:25:06.673 UTC client backend[29322] pg_regress/matview DETAIL:  Row: (1,10)
2025-02-01 03:25:06.673 UTC client backend[29322] pg_regress/matview STATEMENT:  REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_mv;
2025-02-01 03:25:06.679 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.679 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest1, atest5;
2025-02-01 03:25:06.683 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.683 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT atest1.*,atest5.one FROM atest1 JOIN atest5 ON (atest1.a = atest5.two);
2025-02-01 03:25:06.684 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.684 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT one, two FROM atest5;
2025-02-01 03:25:06.687 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot drop column b of table gtest10 because other objects depend on it
2025-02-01 03:25:06.687 UTC client backend[29305] pg_regress/generated_stored DETAIL:  column c of table gtest10 depends on column b of table gtest10
2025-02-01 03:25:06.687 UTC client backend[29305] pg_regress/generated_stored HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:06.687 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest10 DROP COLUMN b;
2025-02-01 03:25:06.707 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.707 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT one, two FROM atest5 NATURAL JOIN atest6;
2025-02-01 03:25:06.708 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.708 UTC client backend[29309] pg_regress/privileges STATEMENT:  COPY atest5 FROM stdin;
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5 (three) VALUES (4);
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5 VALUES (5,5,5);
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest5 SET one = 8;
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.709 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest5 SET three = 5, one = 2;
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = 10 RETURNING atest5.three;
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set three = EXCLUDED.three;
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(two) VALUES (6) ON CONFLICT (two) DO UPDATE set one = 8;
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(three) VALUES (4) ON CONFLICT (two) DO UPDATE set three = 10;
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.710 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(four) VALUES (4);
2025-02-01 03:25:06.711 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.711 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(four) VALUES (4) ON CONFLICT (four) DO UPDATE set three = 3;
2025-02-01 03:25:06.711 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.711 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO atest5(four) VALUES (4) ON CONFLICT ON CONSTRAINT atest5_four_key DO UPDATE set three = 3;
2025-02-01 03:25:06.714 UTC client backend[29301] pg_regress/rowsecurity ERROR:  infinite recursion detected in policy for relation "s1"
2025-02-01 03:25:06.714 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM s1 WHERE f_leak(b);
2025-02-01 03:25:06.719 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.719 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT one FROM atest5;
2025-02-01 03:25:06.719 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.719 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atest5 SET one = 1;
2025-02-01 03:25:06.720 UTC client backend[29314] pg_regress/identity ERROR:  cannot recursively add identity column to table that has child tables
2025-02-01 03:25:06.720 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest7d ADD COLUMN b int GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.738 UTC client backend[29307] pg_regress/replica_identity ERROR:  constraint "test_replica_identity5_pkey" of relation "test_replica_identity5" does not exist
2025-02-01 03:25:06.738 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity5 DROP CONSTRAINT test_replica_identity5_pkey;
2025-02-01 03:25:06.738 UTC client backend[29307] pg_regress/replica_identity ERROR:  column "b" is in index used as replica identity
2025-02-01 03:25:06.738 UTC client backend[29307] pg_regress/replica_identity STATEMENT:  ALTER TABLE test_replica_identity5 ALTER b DROP NOT NULL;
2025-02-01 03:25:06.739 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table msource
2025-02-01 03:25:06.739 UTC client backend[29309] 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-02-01 03:25:06.739 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table msource
2025-02-01 03:25:06.739 UTC client backend[29309] 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-02-01 03:25:06.740 UTC client backend[29305] pg_regress/generated_stored ERROR:  permission denied for table gtest11
2025-02-01 03:25:06.740 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  SELECT a, b FROM gtest11;
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored ERROR:  permission denied for function gf1
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  SELECT gf1(10);
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored ERROR:  permission denied for function gf1
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest12 VALUES (3, 30), (4, 40);
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot drop function gf1(integer) because other objects depend on it
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored DETAIL:  column c of table gtest12 depends on function gf1(integer)
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:06.741 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  DROP FUNCTION gf1(int);
2025-02-01 03:25:06.743 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table msource
2025-02-01 03:25:06.743 UTC client backend[29309] 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-02-01 03:25:06.750 UTC client backend[29305] pg_regress/generated_stored ERROR:  new row for relation "gtest20" violates check constraint "gtest20_b_check"
2025-02-01 03:25:06.750 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Failing row contains (30, 60).
2025-02-01 03:25:06.750 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest20 (a) VALUES (30);
2025-02-01 03:25:06.751 UTC client backend[29305] pg_regress/generated_stored ERROR:  check constraint "gtest20_b_check" of relation "gtest20" is violated by some row
2025-02-01 03:25:06.751 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest20 ALTER COLUMN b SET EXPRESSION AS (a * 100);
2025-02-01 03:25:06.763 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table mtarget
2025-02-01 03:25:06.763 UTC client backend[29309] 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-02-01 03:25:06.763 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table mtarget
2025-02-01 03:25:06.763 UTC client backend[29309] 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-02-01 03:25:06.763 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table mtarget
2025-02-01 03:25:06.763 UTC client backend[29309] 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-02-01 03:25:06.764 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table mtarget
2025-02-01 03:25:06.764 UTC client backend[29309] 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-02-01 03:25:06.773 UTC client backend[29305] pg_regress/generated_stored ERROR:  check constraint "gtest20a_b_check" of relation "gtest20a" is violated by some row
2025-02-01 03:25:06.773 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest20a ADD CHECK (b < 50);
2025-02-01 03:25:06.780 UTC client backend[29305] pg_regress/generated_stored ERROR:  check constraint "chk" of relation "gtest20b" is violated by some row
2025-02-01 03:25:06.780 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest20b VALIDATE CONSTRAINT chk;
2025-02-01 03:25:06.782 UTC client backend[29305] pg_regress/generated_stored ERROR:  new row for relation "gtest20c" violates check constraint "whole_row_check"
2025-02-01 03:25:06.782 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Failing row contains (null, null).
2025-02-01 03:25:06.782 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest20c VALUES (NULL);
2025-02-01 03:25:06.787 UTC client backend[29305] pg_regress/generated_stored ERROR:  null value in column "b" of relation "gtest21a" violates not-null constraint
2025-02-01 03:25:06.787 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Failing row contains (0, null).
2025-02-01 03:25:06.787 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest21a (a) VALUES (0);
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  duplicate key value violates unique constraint "t1_pkey"
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO t1 (c1, c2) VALUES (1, 1);
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  duplicate key value violates unique constraint "t1_pkey"
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE t1 SET c2 = 1;
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "c1" of relation "t1" violates not-null constraint
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (c1, c2) = (null, null).
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO t1 (c1, c2) VALUES (null, null);
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "c1" of relation "t1" violates not-null constraint
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (c1, c3) = (null, null).
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO t1 (c3) VALUES (null);
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "c2" of relation "t1" violates not-null constraint
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (c1) = (5).
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO t1 (c1) VALUES (5);
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges ERROR:  new row for relation "t1" violates check constraint "t1_c3_check"
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (c1, c3) = (1, 10).
2025-02-01 03:25:06.795 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE t1 SET c3 = 10;
2025-02-01 03:25:06.798 UTC client backend[29305] pg_regress/generated_stored ERROR:  null value in column "b" of relation "gtest21b" violates not-null constraint
2025-02-01 03:25:06.798 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Failing row contains (0, null).
2025-02-01 03:25:06.798 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest21b (a) VALUES (0);
2025-02-01 03:25:06.811 UTC client backend[29305] pg_regress/generated_stored ERROR:  duplicate key value violates unique constraint "gtest22a_b_key"
2025-02-01 03:25:06.811 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Key (b)=(1) already exists.
2025-02-01 03:25:06.811 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest22a VALUES (3);
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "b" of relation "errtst_part_1" violates not-null constraint
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (a, b, c) = (aaa, null, null).
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges STATEMENT:  INSERT INTO errtst (a, b) VALUES ('aaa', NULL);
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "b" of relation "errtst_part_1" violates not-null constraint
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (a, b, c) = (aaa, null, ccc).
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE errtst SET b = NULL;
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "b" of relation "errtst_part_1" violates not-null constraint
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (a, b, c) = (aaa, null, ccc).
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE errtst SET a = 'aaa', b = NULL;
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "b" of relation "errtst_part_2" violates not-null constraint
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (a, b, c) = (aaaa, null, ccc).
2025-02-01 03:25:06.832 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE errtst SET a = 'aaaa', b = NULL;
2025-02-01 03:25:06.833 UTC client backend[29309] pg_regress/privileges ERROR:  null value in column "b" of relation "errtst_part_2" violates not-null constraint
2025-02-01 03:25:06.833 UTC client backend[29309] pg_regress/privileges DETAIL:  Failing row contains (a, b, c) = (aaaa, null, ccc).
2025-02-01 03:25:06.833 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE errtst SET a = 'aaaa', b = NULL WHERE a = 'aaa';
2025-02-01 03:25:06.849 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "b1"
2025-02-01 03:25:06.849 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO bv1 VALUES (-1, 'xxx');
2025-02-01 03:25:06.849 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "b1"
2025-02-01 03:25:06.849 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO bv1 VALUES (11, 'xxx');
2025-02-01 03:25:06.851 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest6
2025-02-01 03:25:06.851 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT atest6 FROM atest6;
2025-02-01 03:25:06.851 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.851 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT one FROM atest5 NATURAL JOIN atest6;
2025-02-01 03:25:06.851 UTC client backend[29305] pg_regress/generated_stored ERROR:  duplicate key value violates unique constraint "gtest22b_pkey"
2025-02-01 03:25:06.851 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Key (a, b)=(2, 1) already exists.
2025-02-01 03:25:06.851 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest22b VALUES (2);
2025-02-01 03:25:06.852 UTC client backend[29322] pg_regress/matview ERROR:  too many column names were specified
2025-02-01 03:25:06.852 UTC client backend[29322] pg_regress/matview STATEMENT:  CREATE MATERIALIZED VIEW mvtest_mv_v (ii, jj, kk) AS SELECT i, j FROM mvtest_v;
2025-02-01 03:25:06.855 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest6
2025-02-01 03:25:06.855 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT * FROM atest6;
2025-02-01 03:25:06.857 UTC client backend[29314] pg_regress/identity ERROR:  column "f22" of relation "itest8" contains null values
2025-02-01 03:25:06.857 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE itest8
	  ADD COLUMN f22 int NOT NULL,
	  ALTER COLUMN f22 ADD GENERATED ALWAYS AS IDENTITY;
2025-02-01 03:25:06.863 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest6
2025-02-01 03:25:06.863 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT 1 FROM atest6;
2025-02-01 03:25:06.864 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.864 UTC client backend[29301] 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-02-01 03:25:06.864 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atest5
2025-02-01 03:25:06.864 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atest5 WHERE one = 1;
2025-02-01 03:25:06.885 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.885 UTC client backend[29301] 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-02-01 03:25:06.886 UTC client backend[29322] pg_regress/matview ERROR:  too many column names were specified
2025-02-01 03:25:06.886 UTC client backend[29322] 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-02-01 03:25:06.907 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.907 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT fy FROM atestc;
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges STATEMENT:  SELECT f2 FROM atestc;
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges STATEMENT:  DELETE FROM atestc;
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.910 UTC client backend[29309] pg_regress/privileges STATEMENT:  UPDATE atestc SET f1 = 1;
2025-02-01 03:25:06.911 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.911 UTC client backend[29309] pg_regress/privileges STATEMENT:  TRUNCATE atestc;
2025-02-01 03:25:06.912 UTC client backend[29309] pg_regress/privileges ERROR:  permission denied for table atestc
2025-02-01 03:25:06.912 UTC client backend[29309] pg_regress/privileges STATEMENT:  LOCK atestc;
2025-02-01 03:25:06.915 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.915 UTC client backend[29301] 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-02-01 03:25:06.916 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.916 UTC client backend[29301] 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-02-01 03:25:06.918 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.918 UTC client backend[29301] 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-02-01 03:25:06.918 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.918 UTC client backend[29301] 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-02-01 03:25:06.920 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.920 UTC client backend[29301] 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-02-01 03:25:06.920 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.920 UTC client backend[29301] 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-02-01 03:25:06.920 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.920 UTC client backend[29301] 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-02-01 03:25:06.926 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.926 UTC client backend[29301] 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-02-01 03:25:06.936 UTC client backend[29301] pg_regress/rowsecurity ERROR:  target row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.936 UTC client backend[29301] 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-02-01 03:25:06.936 UTC client backend[29301] pg_regress/rowsecurity ERROR:  target row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.936 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  MERGE INTO document d
	USING (SELECT 3 as sdid) s
	ON did = s.sdid
	WHEN MATCHED THEN
		DELETE;
2025-02-01 03:25:06.937 UTC client backend[29301] pg_regress/rowsecurity ERROR:  target row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.937 UTC client backend[29301] 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-02-01 03:25:06.938 UTC client backend[29301] pg_regress/rowsecurity ERROR:  target row violates row-level security policy (USING expression) for table "document"
2025-02-01 03:25:06.938 UTC client backend[29301] 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-02-01 03:25:06.947 UTC client backend[29451] pg_regress/privileges ERROR:  language "c" is not trusted
2025-02-01 03:25:06.947 UTC client backend[29451] pg_regress/privileges DETAIL:  GRANT and REVOKE are not allowed on untrusted languages, because only superusers can use untrusted languages.
2025-02-01 03:25:06.947 UTC client backend[29451] pg_regress/privileges STATEMENT:  GRANT USAGE ON LANGUAGE c TO PUBLIC;
2025-02-01 03:25:06.947 UTC client backend[29451] pg_regress/privileges WARNING:  no privileges were granted for "sql"
2025-02-01 03:25:06.952 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.952 UTC client backend[29301] 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-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges ERROR:  priv_testproc1(integer) is not a function
2025-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges STATEMENT:  REVOKE ALL ON FUNCTION priv_testproc1(int) FROM PUBLIC;
2025-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges ERROR:  invalid privilege type USAGE for function
2025-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges STATEMENT:  GRANT USAGE ON FUNCTION priv_testfunc1(int) TO regress_priv_user3;
2025-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges ERROR:  invalid privilege type USAGE for function
2025-02-01 03:25:06.956 UTC client backend[29451] pg_regress/privileges STATEMENT:  GRANT USAGE ON FUNCTION priv_testagg1(int) TO regress_priv_user3;
2025-02-01 03:25:06.957 UTC client backend[29451] pg_regress/privileges ERROR:  invalid privilege type USAGE for procedure
2025-02-01 03:25:06.957 UTC client backend[29451] pg_regress/privileges STATEMENT:  GRANT USAGE ON PROCEDURE priv_testproc1(int) TO regress_priv_user3;
2025-02-01 03:25:06.957 UTC client backend[29451] pg_regress/privileges ERROR:  function priv_testfunc_nosuch(integer) does not exist
2025-02-01 03:25:06.957 UTC client backend[29451] pg_regress/privileges STATEMENT:  GRANT ALL PRIVILEGES ON FUNCTION priv_testfunc_nosuch(int) TO regress_priv_user4;
2025-02-01 03:25:06.958 UTC client backend[29451] pg_regress/privileges ERROR:  permission denied for language sql
2025-02-01 03:25:06.958 UTC client backend[29451] pg_regress/privileges STATEMENT:  CREATE FUNCTION priv_testfunc3(int) RETURNS int AS 'select 2 * $1;' LANGUAGE sql;
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges ERROR:  permission denied for function priv_testfunc1
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges STATEMENT:  SELECT priv_testfunc1(5);
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges ERROR:  permission denied for aggregate priv_testagg1
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges STATEMENT:  SELECT priv_testagg1(x) FROM (VALUES (1), (2), (3)) _(x);
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges ERROR:  permission denied for procedure priv_testproc1
2025-02-01 03:25:06.963 UTC client backend[29451] pg_regress/privileges STATEMENT:  CALL priv_testproc1(6);
2025-02-01 03:25:06.964 UTC client backend[29451] pg_regress/privileges ERROR:  permission denied for table atest2
2025-02-01 03:25:06.964 UTC client backend[29451] pg_regress/privileges STATEMENT:  SELECT col1 FROM atest2 WHERE col2 = true;
2025-02-01 03:25:06.964 UTC client backend[29301] pg_regress/rowsecurity ERROR:  duplicate key value violates unique constraint "document_pkey"
2025-02-01 03:25:06.964 UTC client backend[29301] 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-02-01 03:25:06.964 UTC client backend[29305] pg_regress/generated_stored ERROR:  invalid ON UPDATE action for foreign key constraint containing generated column
2025-02-01 03:25:06.964 UTC client backend[29305] 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-02-01 03:25:06.966 UTC client backend[29305] pg_regress/generated_stored ERROR:  invalid ON DELETE action for foreign key constraint containing generated column
2025-02-01 03:25:06.966 UTC client backend[29305] 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-02-01 03:25:06.968 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.968 UTC client backend[29301] 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-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges ERROR:  must be owner of function priv_testfunc1
2025-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges STATEMENT:  DROP FUNCTION priv_testfunc1(int);
2025-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges ERROR:  must be owner of aggregate priv_testagg1
2025-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges STATEMENT:  DROP AGGREGATE priv_testagg1(int);
2025-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges ERROR:  must be owner of procedure priv_testproc1
2025-02-01 03:25:06.971 UTC client backend[29451] pg_regress/privileges STATEMENT:  DROP PROCEDURE priv_testproc1(int);
2025-02-01 03:25:06.976 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "document"
2025-02-01 03:25:06.976 UTC client backend[29301] 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-02-01 03:25:07.003 UTC client backend[29314] pg_regress/identity ERROR:  identity columns are not supported on typed tables
2025-02-01 03:25:07.003 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest12 OF itest_type (f1 WITH OPTIONS GENERATED ALWAYS AS IDENTITY);
2025-02-01 03:25:07.021 UTC client backend[29322] pg_regress/matview ERROR:  division by zero
2025-02-01 03:25:07.021 UTC client backend[29322] pg_regress/matview STATEMENT:  create materialized view mvtest_error as select 1/0 as x;
2025-02-01 03:25:07.021 UTC client backend[29462] pg_regress/privileges ERROR:  permission denied for function int8
2025-02-01 03:25:07.021 UTC client backend[29462] pg_regress/privileges STATEMENT:  SELECT '{1}'::int4[]::int8[];
2025-02-01 03:25:07.027 UTC client backend[29322] pg_regress/matview ERROR:  division by zero
2025-02-01 03:25:07.027 UTC client backend[29322] pg_regress/matview STATEMENT:  refresh materialized view mvtest_error;
2025-02-01 03:25:07.043 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" in child table "pitest1_p2" must be marked NOT NULL
2025-02-01 03:25:07.043 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1 ATTACH PARTITION pitest1_p2 FOR VALUES FROM ('2016-08-01') TO ('2016-09-01');
2025-02-01 03:25:07.049 UTC client backend[29305] pg_regress/generated_stored ERROR:  insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey"
2025-02-01 03:25:07.049 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Key (b)=(10) is not present in table "gtest23a".
2025-02-01 03:25:07.049 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest23b VALUES (5);
2025-02-01 03:25:07.057 UTC client backend[29305] pg_regress/generated_stored ERROR:  insert or update on table "gtest23b" violates foreign key constraint "gtest23b_b_fkey"
2025-02-01 03:25:07.057 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Key (b)=(5) is not present in table "gtest23a".
2025-02-01 03:25:07.057 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest23b ALTER COLUMN b SET EXPRESSION AS (a * 5);
2025-02-01 03:25:07.116 UTC client backend[29305] pg_regress/generated_stored ERROR:  insert or update on table "gtest23q" violates foreign key constraint "gtest23q_b_fkey"
2025-02-01 03:25:07.116 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Key (b)=(5) is not present in table "gtest23p".
2025-02-01 03:25:07.116 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest23q VALUES (2, 5);
2025-02-01 03:25:07.116 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for view rls_view
2025-02-01 03:25:07.116 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.117 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for view rls_view
2025-02-01 03:25:07.117 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.118 UTC client backend[29469] pg_regress/privileges ERROR:  cannot set privileges of array types
2025-02-01 03:25:07.118 UTC client backend[29469] pg_regress/privileges HINT:  Set the privileges of the element type instead.
2025-02-01 03:25:07.118 UTC client backend[29469] pg_regress/privileges STATEMENT:  GRANT USAGE ON TYPE _priv_testtype1 TO regress_priv_user2;
2025-02-01 03:25:07.118 UTC client backend[29469] pg_regress/privileges ERROR:  "priv_testtype1" is not a domain
2025-02-01 03:25:07.118 UTC client backend[29469] pg_regress/privileges STATEMENT:  GRANT USAGE ON DOMAIN priv_testtype1 TO regress_priv_user2;
2025-02-01 03:25:07.119 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.119 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE AGGREGATE priv_testagg1a(priv_testdomain1) (sfunc = int4_sum, stype = bigint);
2025-02-01 03:25:07.119 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.119 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE DOMAIN priv_testdomain2a AS priv_testdomain1;
2025-02-01 03:25:07.120 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.120 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE CAST (priv_testdomain1 AS priv_testdomain3a) WITH FUNCTION castfunc(int);
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE FUNCTION priv_testfunc5a(a priv_testdomain1) RETURNS int LANGUAGE SQL AS $$ SELECT $1 $$;
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE FUNCTION priv_testfunc6a(b int) RETURNS priv_testdomain1 LANGUAGE SQL AS $$ SELECT $1::priv_testdomain1 $$;
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE OPERATOR !+! (PROCEDURE = int4pl, LEFTARG = priv_testdomain1, RIGHTARG = priv_testdomain1);
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.121 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE TABLE test5a (a int, b priv_testdomain1);
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testtype1
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE TABLE test6a OF priv_testtype1;
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testtype1
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE TABLE test10a (a int[], b priv_testtype1[]);
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.122 UTC client backend[29469] pg_regress/privileges STATEMENT:  ALTER TABLE test9a ADD COLUMN c priv_testdomain1;
2025-02-01 03:25:07.123 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.123 UTC client backend[29469] pg_regress/privileges STATEMENT:  ALTER TABLE test9a ALTER COLUMN b TYPE priv_testdomain1;
2025-02-01 03:25:07.123 UTC client backend[29322] pg_regress/matview ERROR:  relation "mvtest_mv_foo" already exists
2025-02-01 03:25:07.123 UTC client backend[29322] pg_regress/matview STATEMENT:  CREATE MATERIALIZED VIEW mvtest_mv_foo AS SELECT * FROM mvtest_foo_data;
2025-02-01 03:25:07.123 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.123 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE TYPE test7a AS (a int, b priv_testdomain1);
2025-02-01 03:25:07.123 UTC client backend[29322] pg_regress/matview WARNING:  IF NOT EXISTS is deprecated in materialized view creation at character 1
2025-02-01 03:25:07.123 UTC client backend[29322] pg_regress/matview HINT:  Use CREATE OR REPLACE MATERIALIZED VIEW mvtest_mv_foo.
2025-02-01 03:25:07.124 UTC client backend[29305] pg_regress/generated_stored ERROR:  value for domain gtestdomain1 violates check constraint "gtestdomain1_check"
2025-02-01 03:25:07.124 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest24 (a) VALUES (6);
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges STATEMENT:  ALTER TYPE test8a ADD ATTRIBUTE c priv_testdomain1;
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges STATEMENT:  ALTER TYPE test8a ALTER ATTRIBUTE b TYPE priv_testdomain1;
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testdomain1
2025-02-01 03:25:07.125 UTC client backend[29469] pg_regress/privileges STATEMENT:  CREATE TABLE test11a AS (SELECT 1::priv_testdomain1 AS a);
2025-02-01 03:25:07.126 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.126 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.127 UTC client backend[29469] pg_regress/privileges ERROR:  permission denied for type priv_testtype1
2025-02-01 03:25:07.127 UTC client backend[29469] pg_regress/privileges STATEMENT:  REVOKE ALL ON TYPE priv_testtype1 FROM PUBLIC;
2025-02-01 03:25:07.128 UTC client backend[29469] pg_regress/privileges WARNING:  cast will be ignored because the source data type is a domain
2025-02-01 03:25:07.131 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.131 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.134 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.134 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.136 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.136 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.144 UTC client backend[29305] pg_regress/generated_stored ERROR:  value for domain gtestdomain1 violates check constraint "gtestdomain1_check"
2025-02-01 03:25:07.144 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  INSERT INTO gtest24r (a) VALUES (6);
2025-02-01 03:25:07.157 UTC client backend[29305] pg_regress/generated_stored ERROR:  generated columns are not supported on typed tables
2025-02-01 03:25:07.157 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  CREATE TABLE gtest28 OF gtest_type (f1 WITH OPTIONS GENERATED ALWAYS AS (f2 *2) STORED);
2025-02-01 03:25:07.157 UTC client backend[29314] pg_regress/identity ERROR:  cannot change identity column of a partition
2025-02-01 03:25:07.157 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET GENERATED BY DEFAULT;
2025-02-01 03:25:07.158 UTC client backend[29314] pg_regress/identity ERROR:  cannot change identity column of a partition
2025-02-01 03:25:07.158 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest2_p1 ALTER COLUMN f3 SET INCREMENT BY 2;
2025-02-01 03:25:07.162 UTC client backend[29314] pg_regress/identity ERROR:  cannot change identity column of only the partitioned table
2025-02-01 03:25:07.162 UTC client backend[29314] pg_regress/identity HINT:  Do not specify the ONLY keyword.
2025-02-01 03:25:07.162 UTC client backend[29314] 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-02-01 03:25:07.167 UTC client backend[29305] pg_regress/generated_stored ERROR:  child column "f3" specifies generation expression
2025-02-01 03:25:07.167 UTC client backend[29305] pg_regress/generated_stored HINT:  A child table column cannot be generated unless its parent column is.
2025-02-01 03:25:07.167 UTC client backend[29305] 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-02-01 03:25:07.168 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "f3" in child table must not be a generated column
2025-02-01 03:25:07.168 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest_parent ATTACH PARTITION gtest_child FOR VALUES FROM ('2016-07-01') TO ('2016-08-01');
2025-02-01 03:25:07.172 UTC client backend[29314] pg_regress/identity ERROR:  null value in column "f3" of relation "pitest2_p1" violates not-null constraint
2025-02-01 03:25:07.172 UTC client backend[29314] pg_regress/identity DETAIL:  Failing row contains (07-07-2016, from pitest2_p1, null).
2025-02-01 03:25:07.172 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT into pitest2_p1 (f1, f2) VALUES ('2016-07-7', 'from pitest2_p1');
2025-02-01 03:25:07.185 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "f3" inherits from generated column but specifies default
2025-02-01 03:25:07.185 UTC client backend[29305] 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-02-01 03:25:07.185 UTC client backend[29305] pg_regress/generated_stored ERROR:  identity columns are not supported on partitions
2025-02-01 03:25:07.185 UTC client backend[29305] 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-02-01 03:25:07.187 UTC client backend[29469] pg_regress/privileges WARNING:  no privileges could be revoked for "priv_testtype1"
2025-02-01 03:25:07.191 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "f3" in child table must be a generated column
2025-02-01 03:25:07.191 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01');
2025-02-01 03:25:07.192 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.192 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.192 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.192 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.193 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.193 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.194 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "f3" in child table must be a generated column
2025-02-01 03:25:07.194 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01');
2025-02-01 03:25:07.194 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.194 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.201 UTC client backend[29314] pg_regress/identity ERROR:  cannot add identity to a column of a partition
2025-02-01 03:25:07.201 UTC client backend[29314] 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-02-01 03:25:07.203 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.203 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_view;
2025-02-01 03:25:07.207 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table z1_blacklist
2025-02-01 03:25:07.207 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  EXPLAIN (COSTS OFF) SELECT * FROM rls_view;
2025-02-01 03:25:07.207 UTC client backend[29305] pg_regress/generated_stored ERROR:  table "gtest_child3" being attached contains an identity column "f3"
2025-02-01 03:25:07.207 UTC client backend[29305] pg_regress/generated_stored DETAIL:  The new partition may not contain an identity column.
2025-02-01 03:25:07.207 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest_parent ATTACH PARTITION gtest_child3 FOR VALUES FROM ('2016-09-01') TO ('2016-10-01');
2025-02-01 03:25:07.208 UTC client backend[29314] pg_regress/identity ERROR:  cannot add identity to a column of only the partitioned table
2025-02-01 03:25:07.208 UTC client backend[29314] pg_regress/identity HINT:  Do not specify the ONLY keyword.
2025-02-01 03:25:07.208 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE ONLY pitest3
	            ALTER COLUMN f3 ADD GENERATED ALWAYS AS IDENTITY (START WITH 3);
2025-02-01 03:25:07.209 UTC client backend[29322] pg_regress/matview ERROR:  could not find suitable unique index on materialized view
2025-02-01 03:25:07.209 UTC client backend[29322] pg_regress/matview STATEMENT:  REFRESH MATERIALIZED VIEW CONCURRENTLY drop_idx_matview;
2025-02-01 03:25:07.223 UTC client backend[29314] pg_regress/identity ERROR:  cannot drop identity from a column of a partition
2025-02-01 03:25:07.223 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest3_p1 ALTER COLUMN f3 DROP IDENTITY;
2025-02-01 03:25:07.223 UTC client backend[29314] pg_regress/identity ERROR:  cannot drop identity from a column of only the partitioned table
2025-02-01 03:25:07.223 UTC client backend[29314] pg_regress/identity HINT:  Do not specify the ONLY keyword.
2025-02-01 03:25:07.223 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE ONLY pitest3 ALTER COLUMN f3 DROP IDENTITY;
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity ERROR:  null value in column "f3" of relation "pitest3_p1" violates not-null constraint
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity DETAIL:  Failing row contains (07-04-2016, from pitest3, null).
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT into pitest3(f1, f2) VALUES ('2016-07-4', 'from pitest3');
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity ERROR:  null value in column "f3" of relation "pitest3_p1" violates not-null constraint
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity DETAIL:  Failing row contains (07-05-2016, from pitest3_p1, null).
2025-02-01 03:25:07.225 UTC client backend[29314] pg_regress/identity STATEMENT:  INSERT into pitest3_p1 (f1, f2) VALUES ('2016-07-5', 'from pitest3_p1');
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" of relation "pitest1_p1" is an identity column
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1_p1 ALTER COLUMN f3 DROP NOT NULL;
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" of relation "pitest1" is an identity column
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1 ALTER COLUMN f3 DROP NOT NULL;
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" of relation "pitest1_p2" is an identity column
2025-02-01 03:25:07.231 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1_p2 ALTER COLUMN f3 SET DEFAULT 10000;
2025-02-01 03:25:07.232 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" of relation "pitest1" is an identity column
2025-02-01 03:25:07.232 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1 ALTER COLUMN f3 SET DEFAULT 10000;
2025-02-01 03:25:07.234 UTC client backend[29314] pg_regress/identity ERROR:  cannot add identity to a column of a partition
2025-02-01 03:25:07.234 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1_p2 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY;
2025-02-01 03:25:07.235 UTC client backend[29314] pg_regress/identity ERROR:  column "f3" of relation "pitest1" is already an identity column
2025-02-01 03:25:07.235 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1 ALTER COLUMN f3 ADD GENERATED BY DEFAULT AS IDENTITY;
2025-02-01 03:25:07.235 UTC client backend[29314] pg_regress/identity ERROR:  identity columns are not supported on partitions
2025-02-01 03:25:07.235 UTC client backend[29314] 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-02-01 03:25:07.236 UTC client backend[29314] pg_regress/identity ERROR:  identity columns are not supported on partitions
2025-02-01 03:25:07.236 UTC client backend[29314] 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-02-01 03:25:07.236 UTC client backend[29301] pg_regress/rowsecurity ERROR:  policy "p1" for table "y1" already exists
2025-02-01 03:25:07.236 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  CREATE POLICY p1 ON y1 FOR SELECT USING (a % 2 = 1);
2025-02-01 03:25:07.237 UTC client backend[29322] pg_regress/matview ERROR:  materialized view "mvtest2" has not been populated
2025-02-01 03:25:07.237 UTC client backend[29322] pg_regress/matview HINT:  Use the REFRESH MATERIALIZED VIEW command.
2025-02-01 03:25:07.237 UTC client backend[29322] pg_regress/matview STATEMENT:  SELECT * FROM mvtest2;
2025-02-01 03:25:07.244 UTC client backend[29485] pg_regress/privileges ERROR:  permission denied for table atest3
2025-02-01 03:25:07.244 UTC client backend[29485] pg_regress/privileges STATEMENT:  TRUNCATE atest3;
2025-02-01 03:25:07.245 UTC client backend[29314] pg_regress/identity ERROR:  table "pitest1_pfail" being attached contains an identity column "f3"
2025-02-01 03:25:07.245 UTC client backend[29314] pg_regress/identity DETAIL:  The new partition may not contain an identity column.
2025-02-01 03:25:07.245 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest1 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01');
2025-02-01 03:25:07.246 UTC client backend[29314] pg_regress/identity ERROR:  table "pitest1_pfail" being attached contains an identity column "f3"
2025-02-01 03:25:07.246 UTC client backend[29314] pg_regress/identity DETAIL:  The new partition may not contain an identity column.
2025-02-01 03:25:07.246 UTC client backend[29314] pg_regress/identity STATEMENT:  ALTER TABLE pitest3 ATTACH PARTITION pitest1_pfail FOR VALUES FROM ('2016-11-01') TO ('2016-12-01');
2025-02-01 03:25:07.248 UTC client backend[29485] pg_regress/privileges ERROR:  relation "pg_shad" does not exist
2025-02-01 03:25:07.248 UTC client backend[29485] pg_regress/privileges STATEMENT:  select has_table_privilege('pg_shad','select');
2025-02-01 03:25:07.248 UTC client backend[29485] pg_regress/privileges ERROR:  role "nosuchuser" does not exist
2025-02-01 03:25:07.248 UTC client backend[29485] pg_regress/privileges STATEMENT:  select has_table_privilege('nosuchuser','pg_authid','select');
2025-02-01 03:25:07.250 UTC client backend[29485] pg_regress/privileges ERROR:  unrecognized privilege type: "sel"
2025-02-01 03:25:07.250 UTC client backend[29485] pg_regress/privileges STATEMENT:  select has_table_privilege('pg_authid','sel');
2025-02-01 03:25:07.287 UTC client backend[29314] pg_regress/identity ERROR:  conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 63
2025-02-01 03:25:07.287 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest15 (id integer GENERATED ALWAYS AS IDENTITY NULL);
2025-02-01 03:25:07.287 UTC client backend[29314] pg_regress/identity ERROR:  conflicting NULL/NOT NULL declarations for column "id" of table "itest15" at character 39
2025-02-01 03:25:07.287 UTC client backend[29314] pg_regress/identity STATEMENT:  CREATE TABLE itest15 (id integer NULL GENERATED ALWAYS AS IDENTITY);
2025-02-01 03:25:07.298 UTC client backend[29489] pg_regress/privileges ERROR:  column "nosuchcol" of relation "pg_authid" does not exist
2025-02-01 03:25:07.298 UTC client backend[29489] pg_regress/privileges STATEMENT:  select has_column_privilege('pg_authid','nosuchcol','select');
2025-02-01 03:25:07.309 UTC client backend[29314] pg_regress/identity ERROR:  cannot insert a non-DEFAULT value into column "a"
2025-02-01 03:25:07.309 UTC client backend[29314] pg_regress/identity DETAIL:  Column "a" is an identity column defined as GENERATED ALWAYS.
2025-02-01 03:25:07.309 UTC client backend[29314] pg_regress/identity HINT:  Use OVERRIDING SYSTEM VALUE to override.
2025-02-01 03:25:07.309 UTC client backend[29314] 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-02-01 03:25:07.310 UTC client backend[29322] pg_regress/matview ERROR:  relation "matview_ine_tab" already exists
2025-02-01 03:25:07.310 UTC client backend[29322] pg_regress/matview STATEMENT:  CREATE MATERIALIZED VIEW matview_ine_tab AS SELECT 1 / 0;
2025-02-01 03:25:07.310 UTC client backend[29322] pg_regress/matview WARNING:  IF NOT EXISTS is deprecated in materialized view creation at character 1
2025-02-01 03:25:07.310 UTC client backend[29322] pg_regress/matview HINT:  Use CREATE OR REPLACE MATERIALIZED VIEW matview_ine_tab.
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview ERROR:  relation "matview_ine_tab" already exists
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview STATEMENT:  CREATE MATERIALIZED VIEW matview_ine_tab AS
	  SELECT 1 / 0 WITH NO DATA;
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview WARNING:  IF NOT EXISTS is deprecated in materialized view creation at character 1
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview HINT:  Use CREATE OR REPLACE MATERIALIZED VIEW matview_ine_tab.
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview ERROR:  relation "matview_ine_tab" already exists
2025-02-01 03:25:07.312 UTC client backend[29322] 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-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview WARNING:  IF NOT EXISTS is deprecated in materialized view creation at character 70
2025-02-01 03:25:07.312 UTC client backend[29322] pg_regress/matview HINT:  Use CREATE OR REPLACE MATERIALIZED VIEW matview_ine_tab.
2025-02-01 03:25:07.312 UTC client backend[29489] pg_regress/privileges ERROR:  column "f2" of relation "mytable" does not exist
2025-02-01 03:25:07.312 UTC client backend[29489] pg_regress/privileges STATEMENT:  select has_column_privilege('mytable','f2','select');
2025-02-01 03:25:07.313 UTC client backend[29322] pg_regress/matview ERROR:  relation "matview_ine_tab" already exists
2025-02-01 03:25:07.313 UTC client backend[29322] 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-02-01 03:25:07.313 UTC client backend[29322] pg_regress/matview WARNING:  IF NOT EXISTS is deprecated in materialized view creation at character 70
2025-02-01 03:25:07.313 UTC client backend[29322] pg_regress/matview HINT:  Use CREATE OR REPLACE MATERIALIZED VIEW matview_ine_tab.
2025-02-01 03:25:07.318 UTC client backend[29489] pg_regress/privileges WARNING:  no privileges were granted for "atest4"
2025-02-01 03:25:07.319 UTC client backend[29489] pg_regress/privileges ERROR:  dependent privileges exist
2025-02-01 03:25:07.319 UTC client backend[29489] pg_regress/privileges HINT:  Use CASCADE to revoke them too.
2025-02-01 03:25:07.319 UTC client backend[29489] pg_regress/privileges STATEMENT:  REVOKE SELECT ON atest4 FROM regress_priv_user2;
TRAP: failed Assert("queryDesc->sourceText != NULL"), File: "../src/backend/executor/execMain.c", Line: 194, PID: 29322
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(ExceptionalCondition+0x56)[0x55d554ec6aba]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(standard_ExecutorStart+0x32a)[0x55d55483120f]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(ExecutorStart+0xa4)[0x55d5548313eb]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0xb556d7)[0x55d5547506d7]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(RefreshMatViewByOid+0xb80)[0x55d554752a31]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(ExecRefreshMatView+0x90)[0x55d554752b70]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(ExecCreateTableAs+0x20e)[0x55d554708623]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0x103a579)[0x55d554c35579]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(standard_ProcessUtility+0x11bc)[0x55d554c33b78]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(ProcessUtility+0x152)[0x55d554c33cd3]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0x103467f)[0x55d554c2f67f]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0x1034c2a)[0x55d554c2fc2a]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(PortalRun+0x1e2)[0x55d554c30192]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0x102e628)[0x55d554c29628]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(PostgresMain+0xa32)[0x55d554c2c381]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(BackendMain+0x92)[0x55d554c223d7]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(postmaster_child_launch+0x1b4)[0x55d554ad330a]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0xedd505)[0x55d554ad8505]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(+0xedf5d5)[0x55d554ada5d5]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(PostmasterMain+0x13f0)[0x55d554adbe34]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(main+0x28d)[0x55d554910a0b]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7fc80fe4624a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fc80fe46305]
postgres: postgres regression [local] CREATE MATERIALIZED VIEW(_start+0x21)[0x55d5544b6151]
2025-02-01 03:25:07.360 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "t1"
2025-02-01 03:25:07.360 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  WITH cte1 AS (UPDATE t1 SET a = a + 1 RETURNING *) SELECT * FROM cte1;
2025-02-01 03:25:07.361 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "t1"
2025-02-01 03:25:07.361 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  WITH cte1 AS (INSERT INTO t1 VALUES (21, 'Fail') RETURNING *) SELECT * FROM cte1;
2025-02-01 03:25:07.361 UTC client backend[29301] pg_regress/rowsecurity ERROR:  policy "p1" for table "t1" already exists
2025-02-01 03:25:07.361 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  ALTER POLICY p1 ON t1 RENAME TO p1;
2025-02-01 03:25:07.422 UTC client backend[29318] pg_regress/groupingsets LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29318.4", size 1720320
2025-02-01 03:25:07.422 UTC client backend[29318] 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-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin ERROR:  "brintest" is not an index
2025-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin STATEMENT:  SELECT brin_summarize_new_values('brintest');
2025-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin ERROR:  "tenk1_unique1" is not a BRIN index
2025-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin STATEMENT:  SELECT brin_summarize_new_values('tenk1_unique1');
2025-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin ERROR:  block number out of range: -1
2025-02-01 03:25:07.439 UTC client backend[29325] pg_regress/brin STATEMENT:  SELECT brin_desummarize_range('brinidx', -1);
2025-02-01 03:25:07.443 UTC client backend[29325] pg_regress/brin ERROR:  block number out of range: -1
2025-02-01 03:25:07.443 UTC client backend[29325] pg_regress/brin STATEMENT:  SELECT brin_summarize_range('brin_summarize_idx', -1);
2025-02-01 03:25:07.443 UTC client backend[29325] pg_regress/brin ERROR:  block number out of range: 4294967296
2025-02-01 03:25:07.443 UTC client backend[29325] pg_regress/brin STATEMENT:  SELECT brin_summarize_range('brin_summarize_idx', 4294967296);
2025-02-01 03:25:07.451 UTC client backend[29301] pg_regress/rowsecurity ERROR:  table "copy_t" does not exist
2025-02-01 03:25:07.451 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP TABLE copy_t CASCADE;
2025-02-01 03:25:07.469 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "copy_t"
2025-02-01 03:25:07.469 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.471 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "copy_t"
2025-02-01 03:25:07.471 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.471 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_t
2025-02-01 03:25:07.471 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY (SELECT * FROM copy_t ORDER BY a ASC) TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.515 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use generated column in partition key at character 126
2025-02-01 03:25:07.515 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "f3" is a generated column.
2025-02-01 03:25:07.515 UTC client backend[29305] 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-02-01 03:25:07.516 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use generated column in partition key at character 126
2025-02-01 03:25:07.516 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "f3" is a generated column.
2025-02-01 03:25:07.516 UTC client backend[29305] 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-02-01 03:25:07.527 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "copy_rel_to"
2025-02-01 03:25:07.527 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.529 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot use generated column "b" in column generation expression
2025-02-01 03:25:07.529 UTC client backend[29305] pg_regress/generated_stored DETAIL:  A generated column cannot reference another generated column.
2025-02-01 03:25:07.529 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (b * 4) STORED;
2025-02-01 03:25:07.530 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_rel_to
2025-02-01 03:25:07.530 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.530 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "z" does not exist
2025-02-01 03:25:07.530 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest25 ADD COLUMN x int GENERATED ALWAYS AS (z * 4) STORED;
2025-02-01 03:25:07.530 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_rel_to
2025-02-01 03:25:07.530 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.541 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "copy_rel_to"
2025-02-01 03:25:07.541 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.544 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_rel_to
2025-02-01 03:25:07.544 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.546 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_rel_to
2025-02-01 03:25:07.546 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_rel_to TO STDOUT WITH DELIMITER ',';
2025-02-01 03:25:07.553 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "copy_t"
2025-02-01 03:25:07.553 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_t FROM STDIN;
2025-02-01 03:25:07.553 UTC client backend[29301] pg_regress/rowsecurity ERROR:  COPY FROM not supported with row-level security
2025-02-01 03:25:07.553 UTC client backend[29301] pg_regress/rowsecurity HINT:  Use INSERT statements instead.
2025-02-01 03:25:07.553 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_t FROM STDIN;
2025-02-01 03:25:07.554 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_t
2025-02-01 03:25:07.554 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_t FROM STDIN;
2025-02-01 03:25:07.554 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table copy_t
2025-02-01 03:25:07.554 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  COPY copy_t FROM STDIN;
2025-02-01 03:25:07.570 UTC client backend[29311] pg_regress/spgist ERROR:  value 9 out of bounds for option "fillfactor"
2025-02-01 03:25:07.570 UTC client backend[29311] pg_regress/spgist DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:07.570 UTC client backend[29311] pg_regress/spgist STATEMENT:  create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 9);
2025-02-01 03:25:07.574 UTC client backend[29311] pg_regress/spgist ERROR:  value 101 out of bounds for option "fillfactor"
2025-02-01 03:25:07.574 UTC client backend[29311] pg_regress/spgist DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:07.574 UTC client backend[29311] pg_regress/spgist STATEMENT:  create index spgist_point_idx2 on spgist_point_tbl using spgist(p) with (fillfactor = 101);
2025-02-01 03:25:07.578 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot alter type of a column used by a generated column
2025-02-01 03:25:07.578 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "a" is used by generated column "x".
2025-02-01 03:25:07.578 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest27 ALTER COLUMN a TYPE text;
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot specify USING when altering type of generated column at character 34
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "x" is a generated column.
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest27 ALTER COLUMN x TYPE boolean USING x <> 0;
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "x" of relation "gtest27" is a generated column
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored HINT:  Use ALTER TABLE ... ALTER COLUMN ... DROP EXPRESSION instead.
2025-02-01 03:25:07.654 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest27 ALTER COLUMN x DROP DEFAULT;
2025-02-01 03:25:07.691 UTC client backend[29301] pg_regress/rowsecurity ERROR:  role "regress_rls_eve" cannot be dropped because some objects depend on it
2025-02-01 03:25:07.691 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  privileges for table tbl1
	target of policy p on table tbl1
2025-02-01 03:25:07.691 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP ROLE regress_rls_eve;
2025-02-01 03:25:07.693 UTC client backend[29301] pg_regress/rowsecurity ERROR:  role "regress_rls_eve" cannot be dropped because some objects depend on it
2025-02-01 03:25:07.693 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  privileges for table tbl1
2025-02-01 03:25:07.693 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP ROLE regress_rls_eve;
2025-02-01 03:25:07.697 UTC client backend[29301] pg_regress/rowsecurity ERROR:  role "regress_rls_frank" cannot be dropped because some objects depend on it
2025-02-01 03:25:07.697 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  target of policy p on table tbl1
2025-02-01 03:25:07.697 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP ROLE regress_rls_frank;
2025-02-01 03:25:07.699 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot alter type of a column used by a generated column
2025-02-01 03:25:07.699 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "a" is used by generated column "x".
2025-02-01 03:25:07.699 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest27
	  ALTER COLUMN a TYPE float8,
	  ALTER COLUMN b TYPE float8;
2025-02-01 03:25:07.712 UTC client backend[29301] pg_regress/rowsecurity ERROR:  aggregate functions are not allowed in policy expressions
2025-02-01 03:25:07.712 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  CREATE POLICY p ON t USING (max(c));
2025-02-01 03:25:07.735 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r2"
2025-02-01 03:25:07.735 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r2 VALUES (2);
2025-02-01 03:25:07.764 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "a" of relation "gtest29" is not a generated column
2025-02-01 03:25:07.764 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest29 ALTER COLUMN a SET EXPRESSION AS (a * 3);
2025-02-01 03:25:07.764 UTC client backend[29305] pg_regress/generated_stored ERROR:  column "a" of relation "gtest29" is not a stored generated column
2025-02-01 03:25:07.764 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest29 ALTER COLUMN a DROP EXPRESSION;
2025-02-01 03:25:07.767 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.767 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r1 VALUES (1);
2025-02-01 03:25:07.768 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "r1"
2025-02-01 03:25:07.768 UTC client backend[29301] pg_regress/rowsecurity HINT:  To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY.
2025-02-01 03:25:07.768 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  TABLE r1;
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "r1"
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity HINT:  To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY.
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  UPDATE r1 SET a = 1;
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "r1"
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity HINT:  To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY.
2025-02-01 03:25:07.769 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DELETE FROM r1;
2025-02-01 03:25:07.796 UTC client backend[29301] pg_regress/rowsecurity ERROR:  update or delete on table "r1" violates foreign key constraint "r2_a_fkey" on table "r2"
2025-02-01 03:25:07.796 UTC client backend[29301] pg_regress/rowsecurity DETAIL:  Key (a)=(10) is still referenced from table "r2".
2025-02-01 03:25:07.796 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DELETE FROM r1;
2025-02-01 03:25:07.881 UTC client backend[29301] pg_regress/rowsecurity ERROR:  query would be affected by row-level security policy for table "r1"
2025-02-01 03:25:07.881 UTC client backend[29301] pg_regress/rowsecurity HINT:  To disable the policy for the table's owner, use ALTER TABLE NO FORCE ROW LEVEL SECURITY.
2025-02-01 03:25:07.881 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  TABLE r1;
2025-02-01 03:25:07.881 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.881 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r1 VALUES (10), (20) RETURNING *;
2025-02-01 03:25:07.903 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.903 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  UPDATE r1 SET a = 30 RETURNING *;
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r1 VALUES (10)
	    ON CONFLICT (a) DO UPDATE SET a = 30 RETURNING *;
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r1 VALUES (10)
	    ON CONFLICT (a) DO UPDATE SET a = 30;
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity ERROR:  new row violates row-level security policy for table "r1"
2025-02-01 03:25:07.904 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  INSERT INTO r1 VALUES (10)
	    ON CONFLICT ON CONSTRAINT r1_pkey DO UPDATE SET a = 30;
2025-02-01 03:25:07.910 UTC client backend[29305] pg_regress/generated_stored ERROR:  ALTER TABLE / DROP EXPRESSION must be applied to child tables too
2025-02-01 03:25:07.910 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE ONLY gtest30 ALTER COLUMN b DROP EXPRESSION;
2025-02-01 03:25:07.945 UTC client backend[29301] pg_regress/rowsecurity ERROR:  policy "p1" for table "dob_t1" does not exist
2025-02-01 03:25:07.945 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP POLICY p1 ON dob_t1;
2025-02-01 03:25:07.948 UTC client backend[29301] pg_regress/rowsecurity ERROR:  policy "p1" for table "dob_t1" does not exist
2025-02-01 03:25:07.948 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  DROP POLICY p1 ON dob_t1;
2025-02-01 03:25:07.955 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot drop generation expression from inherited column
2025-02-01 03:25:07.955 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest30_1 ALTER COLUMN b DROP EXPRESSION;
2025-02-01 03:25:07.966 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.127", size 146674
2025-02-01 03:25:07.966 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.967 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type
2025-02-01 03:25:07.967 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar;
2025-02-01 03:25:07.968 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.130", size 145199
2025-02-01 03:25:07.968 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.970 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.132", size 149388
2025-02-01 03:25:07.970 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.970 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table ref_tbl
2025-02-01 03:25:07.970 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM ref_tbl;
2025-02-01 03:25:07.970 UTC client backend[29301] pg_regress/rowsecurity ERROR:  permission denied for table rls_tbl
2025-02-01 03:25:07.970 UTC client backend[29301] pg_regress/rowsecurity STATEMENT:  SELECT * FROM rls_tbl;
2025-02-01 03:25:07.976 UTC client backend[29305] pg_regress/generated_stored ERROR:  cannot alter table "gtest31_1" because column "gtest31_2.y" uses its row type
2025-02-01 03:25:07.976 UTC client backend[29305] pg_regress/generated_stored STATEMENT:  ALTER TABLE gtest31_1 ALTER COLUMN b TYPE varchar;
2025-02-01 03:25:07.985 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.129", size 149978
2025-02-01 03:25:07.985 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.987 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.128", size 149565
2025-02-01 03:25:07.987 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.989 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.133", size 145081
2025-02-01 03:25:07.989 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:07.996 UTC client backend[29305] pg_regress/generated_stored ERROR:  BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82
2025-02-01 03:25:07.996 UTC client backend[29305] pg_regress/generated_stored DETAIL:  Column "b" is a generated column.
2025-02-01 03:25:07.996 UTC client backend[29305] 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-02-01 03:25:07.997 UTC client backend[29305] pg_regress/generated_stored ERROR:  BEFORE trigger's WHEN condition cannot reference NEW generated columns at character 82
2025-02-01 03:25:07.997 UTC client backend[29305] pg_regress/generated_stored DETAIL:  A whole-row reference is used and the table contains generated columns.
2025-02-01 03:25:07.997 UTC client backend[29305] 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-02-01 03:25:08.011 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.131", size 147795
2025-02-01 03:25:08.011 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) FROM simple r JOIN bigger_than_it_looks s USING (id);
2025-02-01 03:25:08.057 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.141", size 146674
2025-02-01 03:25:08.057 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.057 UTC client backend[29319] 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-02-01 03:25:08.074 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.144", size 145199
2025-02-01 03:25:08.074 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.074 UTC client backend[29319] 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-02-01 03:25:08.076 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.146", size 149388
2025-02-01 03:25:08.076 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.076 UTC client backend[29319] 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-02-01 03:25:08.078 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.143", size 149978
2025-02-01 03:25:08.078 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.078 UTC client backend[29319] 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-02-01 03:25:08.080 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.142", size 149565
2025-02-01 03:25:08.080 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.080 UTC client backend[29319] 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-02-01 03:25:08.082 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.147", size 145081
2025-02-01 03:25:08.082 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.082 UTC client backend[29319] 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-02-01 03:25:08.103 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.145", size 147795
2025-02-01 03:25:08.103 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.103 UTC client backend[29319] 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-02-01 03:25:08.155 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.155", size 143429
2025-02-01 03:25:08.155 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.157 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.158", size 140715
2025-02-01 03:25:08.157 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.195 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.160", size 146497
2025-02-01 03:25:08.195 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.196 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.157", size 146733
2025-02-01 03:25:08.196 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.198 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.156", size 145317
2025-02-01 03:25:08.198 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.200 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.161", size 141836
2025-02-01 03:25:08.200 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.201 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.159", size 143901
2025-02-01 03:25:08.201 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.13.fileset/i1of4.p0.0", size 131072
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.13.fileset/i2of4.p0.0", size 131072
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.13.fileset/i3of4.p0.0", size 131072
2025-02-01 03:25:08.353 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join bigger_than_it_looks s using (id);
2025-02-01 03:25:08.415 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.14.fileset/i1of4.p0.0", size 131072
2025-02-01 03:25:08.415 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.415 UTC client backend[29319] 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-02-01 03:25:08.415 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.14.fileset/i2of4.p0.0", size 131072
2025-02-01 03:25:08.415 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.415 UTC client backend[29319] 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-02-01 03:25:08.416 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.14.fileset/i3of4.p0.0", size 131072
2025-02-01 03:25:08.416 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.416 UTC client backend[29319] 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-02-01 03:25:08.448 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.176", size 480000
2025-02-01 03:25:08.448 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.454 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.177", size 593422
2025-02-01 03:25:08.454 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.491 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.178", size 480000
2025-02-01 03:25:08.491 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.491 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select * from hash_join_batches(
	$$
	  select count(*) from simple r join extremely_skewed s using (id);
	$$);
2025-02-01 03:25:08.498 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.179", size 593422
2025-02-01 03:25:08.498 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.498 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select * from hash_join_batches(
	$$
	  select count(*) from simple r join extremely_skewed s using (id);
	$$);
2025-02-01 03:25:08.535 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.180", size 480000
2025-02-01 03:25:08.535 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.542 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.181", size 586224
2025-02-01 03:25:08.542 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.549 UTC client backend[29494] pg_regress/privileges LOG:  process 29494 still waiting for ShareLock on virtual transaction 36/363 after 1000.047 ms
2025-02-01 03:25:08.549 UTC client backend[29494] pg_regress/privileges DETAIL:  Process holding the lock: 29322. Wait queue: 29494.
2025-02-01 03:25:08.549 UTC client backend[29494] 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-02-01 03:25:08.553 UTC parallel worker[29603] LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29603.0", size 480000
2025-02-01 03:25:08.553 UTC parallel worker[29603] STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.594 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.182", size 480000
2025-02-01 03:25:08.594 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.594 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select * from hash_join_batches(
	$$
	  select count(*) from simple r join extremely_skewed s using (id);
	$$);
2025-02-01 03:25:08.616 UTC parallel worker[29618] LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29618.0", size 480000
2025-02-01 03:25:08.616 UTC parallel worker[29618] STATEMENT:  explain (analyze, format 'json') 
	  select count(*) from simple r join extremely_skewed s using (id);
	
2025-02-01 03:25:08.624 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.183", size 586696
2025-02-01 03:25:08.624 UTC client backend[29319] pg_regress/join_hash CONTEXT:  PL/pgSQL function hash_join_batches(text) line 6 at FOR over EXECUTE statement
2025-02-01 03:25:08.624 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select * from hash_join_batches(
	$$
	  select count(*) from simple r join extremely_skewed s using (id);
	$$);
2025-02-01 03:25:08.629 UTC client backend[29315] pg_regress/gist ERROR:  lossy distance functions are not supported in index-only scans
2025-02-01 03:25:08.629 UTC client backend[29315] pg_regress/gist STATEMENT:  select p from gist_tbl order by circle(p,1) <-> point(0,0) limit 1;
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o1of4.p1.0", size 131072
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o1of4.p0.0", size 196608
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o3of4.p0.0", size 196608
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o0of4.p0.0", size 196608
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/i3of4.p0.0", size 491520
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o2of4.p1.0", size 131072
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o0of4.p1.0", size 131072
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o3of4.p1.0", size 163840
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp29319.15.fileset/o2of4.p0.0", size 196608
2025-02-01 03:25:08.666 UTC client backend[29319] pg_regress/join_hash STATEMENT:  select count(*) from simple r join extremely_skewed s using (id);
2025-02-01 03:25:08.699 UTC postmaster[25306] LOG:  client backend (PID 29322) was terminated by signal 6: Aborted
2025-02-01 03:25:08.699 UTC postmaster[25306] DETAIL:  Failed process was running: CREATE OR REPLACE MATERIALIZED VIEW mvtest_replace AS
	  SELECT 2 AS a;
2025-02-01 03:25:08.699 UTC postmaster[25306] LOG:  terminating any other active server processes
2025-02-01 03:25:08.716 UTC postmaster[25306] LOG:  all server processes terminated; reinitializing
2025-02-01 03:25:08.803 UTC startup[29658] LOG:  database system was interrupted; last known up at 2025-02-01 03:25:02 UTC
2025-02-01 03:25:08.803 UTC startup[29658] LOG:  database system was not properly shut down; automatic recovery in progress
2025-02-01 03:25:08.807 UTC startup[29658] LOG:  redo starts at 0/79A0EE0
2025-02-01 03:25:09.137 UTC client backend[29813] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.137 UTC client backend[29813] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.140 UTC client backend[29814] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.140 UTC client backend[29814] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.302 UTC client backend[29852] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.302 UTC client backend[29852] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.302 UTC client backend[29851] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.302 UTC client backend[29851] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.304 UTC client backend[29853] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.304 UTC client backend[29853] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.307 UTC client backend[29856] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.307 UTC client backend[29856] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.308 UTC client backend[29858] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.308 UTC client backend[29858] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.310 UTC client backend[29857] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.310 UTC client backend[29857] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.315 UTC client backend[29861] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.315 UTC client backend[29861] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.318 UTC client backend[29862] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.318 UTC client backend[29862] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.320 UTC client backend[29863] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.320 UTC client backend[29863] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.321 UTC client backend[29855] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.321 UTC client backend[29855] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.323 UTC client backend[29864] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.323 UTC client backend[29864] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.324 UTC client backend[29854] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.324 UTC client backend[29854] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.329 UTC client backend[29866] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.329 UTC client backend[29866] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.333 UTC client backend[29859] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.333 UTC client backend[29859] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.311 UTC client backend[29860] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.311 UTC client backend[29860] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.340 UTC client backend[29868] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.340 UTC client backend[29868] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.351 UTC client backend[29867] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.351 UTC client backend[29867] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:09.353 UTC client backend[29865] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:09.353 UTC client backend[29865] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.675 UTC client backend[30088] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.675 UTC client backend[30088] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.697 UTC client backend[30092] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.697 UTC client backend[30092] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.697 UTC client backend[30089] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.697 UTC client backend[30089] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.701 UTC client backend[30091] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.701 UTC client backend[30091] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.703 UTC client backend[30093] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.703 UTC client backend[30093] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.708 UTC client backend[30096] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.708 UTC client backend[30096] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:10.712 UTC client backend[30097] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:10.712 UTC client backend[30097] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.296 UTC client backend[30193] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.296 UTC client backend[30193] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.388 UTC client backend[30214] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.388 UTC client backend[30214] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.599 UTC client backend[30251] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.599 UTC client backend[30251] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.676 UTC client backend[30263] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.676 UTC client backend[30263] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.715 UTC client backend[30269] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.715 UTC client backend[30269] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.829 UTC client backend[30313] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.829 UTC client backend[30313] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.836 UTC client backend[30314] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.836 UTC client backend[30314] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.843 UTC client backend[30312] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.843 UTC client backend[30312] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.846 UTC client backend[30315] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.846 UTC client backend[30315] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.847 UTC client backend[30317] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.847 UTC client backend[30317] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.875 UTC client backend[30321] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.875 UTC client backend[30321] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.878 UTC client backend[30320] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.878 UTC client backend[30320] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.883 UTC client backend[30327] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.883 UTC client backend[30327] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.883 UTC client backend[30325] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.883 UTC client backend[30325] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.885 UTC client backend[30324] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.885 UTC client backend[30324] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.887 UTC client backend[30326] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.887 UTC client backend[30326] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.887 UTC client backend[30318] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.887 UTC client backend[30318] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.891 UTC client backend[30322] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.891 UTC client backend[30322] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.895 UTC client backend[30323] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.895 UTC client backend[30323] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.915 UTC client backend[30330] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.915 UTC client backend[30330] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.931 UTC client backend[30331] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.931 UTC client backend[30331] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:11.933 UTC client backend[30332] [unknown] FATAL:  the database system is not yet accepting connections
2025-02-01 03:25:11.933 UTC client backend[30332] [unknown] DETAIL:  Consistent recovery state has not been yet reached.
2025-02-01 03:25:12.350 UTC startup[29658] LOG:  invalid record length at 0/BDECDE8: expected at least 24, got 0
2025-02-01 03:25:12.350 UTC startup[29658] LOG:  redo done at 0/BDECD30 system usage: CPU: user: 0.59 s, system: 0.10 s, elapsed: 3.54 s
2025-02-01 03:25:12.384 UTC checkpointer[29659] LOG:  checkpoint starting: end-of-recovery immediate wait
2025-02-01 03:25:12.456 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 4910 buffers (30.0%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 4 recycled; write=0.072 s, sync=0.001 s, total=0.073 s; sync files=0, longest=0.000 s, average=0.000 s; distance=69935 kB, estimate=69935 kB; lsn=0/BDECDE8, redo lsn=0/BDECDE8
2025-02-01 03:25:12.461 UTC postmaster[25306] LOG:  database system is ready to accept connections
2025-02-01 03:25:12.622 UTC client backend[30535] pg_regress/sqljson ERROR:  syntax error at or near ")" at character 13
2025-02-01 03:25:12.622 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON();
2025-02-01 03:25:12.623 UTC client backend[30535] pg_regress/sqljson ERROR:  JSON ENCODING clause is only allowed for bytea input type at character 28
2025-02-01 03:25:12.623 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON('{ "a" : 1 } ' FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.624 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  syntax error at or near "(" at character 18
2025-02-01 03:25:12.624 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT JSON_TABLE('[]', '$');
2025-02-01 03:25:12.624 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON ERROR behavior at character 72
2025-02-01 03:25:12.624 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause.
2025-02-01 03:25:12.624 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') DEFAULT 1 ON ERROR);
2025-02-01 03:25:12.625 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON ERROR behavior at character 72
2025-02-01 03:25:12.625 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause.
2025-02-01 03:25:12.625 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') NULL ON ERROR);
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot use non-string types with WITH UNIQUE KEYS clause at character 8
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON('   1   '::json WITH UNIQUE KEYS);
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot cast type integer to json at character 13
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON(123);
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.625 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON('{"a": 1, "a": 2}' WITH UNIQUE KEYS);
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') ERROR ON ERROR);
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  duplicate JSON_TABLE column or path name: js2 at character 63
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' as js2 COLUMNS (js2 int path '$'));
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  syntax error at or near ")" at character 45
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(NULL, '$' COLUMNS ());
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  JSON_TABLE function has 1 columns available but 2 columns specified
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE (NULL::jsonb, '$' COLUMNS (v1 timestamp)) AS f (v1, v2);
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  duplicate JSON_TABLE column or path name: js2 at character 74
2025-02-01 03:25:12.626 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb'"1.23"', '$.a' COLUMNS (js2 int path '$', js2 int path '$'));
2025-02-01 03:25:12.628 UTC client backend[30535] pg_regress/sqljson ERROR:  syntax error at or near ")" at character 20
2025-02-01 03:25:12.628 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SCALAR();
2025-02-01 03:25:12.632 UTC client backend[30535] pg_regress/sqljson ERROR:  syntax error at or near ")" at character 23
2025-02-01 03:25:12.632 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SERIALIZE();
2025-02-01 03:25:12.636 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot use type jsonb in RETURNING clause of JSON_SERIALIZE()
2025-02-01 03:25:12.636 UTC client backend[30535] pg_regress/sqljson HINT:  Try returning a string type or bytea.
2025-02-01 03:25:12.636 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING jsonb);
2025-02-01 03:25:12.637 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type
2025-02-01 03:25:12.637 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  value for domain jsonb_test_domain violates check constraint "jsonb_test_domain_check"
2025-02-01 03:25:12.637 UTC client backend[30536] 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-02-01 03:25:12.638 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot set JSON encoding for non-bytea output types at character 35
2025-02-01 03:25:12.638 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.639 UTC client backend[30535] pg_regress/sqljson ERROR:  unrecognized JSON encoding: invalid_encoding at character 56
2025-02-01 03:25:12.639 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING);
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson ERROR:  unsupported JSON encoding at character 36
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson HINT:  Only UTF8 JSON encoding is supported.
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF16);
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson ERROR:  unsupported JSON encoding at character 36
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson HINT:  Only UTF8 JSON encoding is supported.
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(RETURNING bytea FORMAT JSON ENCODING UTF32);
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot use non-string types with explicit FORMAT JSON clause at character 37
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON);
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson ERROR:  JSON ENCODING clause is only allowed for bytea input type at character 37
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson ERROR:  JSON ENCODING clause is only allowed for bytea input type at character 38
2025-02-01 03:25:12.640 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.641 UTC client backend[30535] pg_regress/sqljson ERROR:  JSON ENCODING clause is only allowed for bytea input type at character 39
2025-02-01 03:25:12.641 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT('foo': NULL::jsonb FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.641 UTC client backend[30535] pg_regress/sqljson ERROR:  null value not allowed for object key
2025-02-01 03:25:12.641 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(NULL: 1);
2025-02-01 03:25:12.644 UTC client backend[30535] pg_regress/sqljson ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.644 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(json '[1]': 123);
2025-02-01 03:25:12.649 UTC client backend[30535] pg_regress/sqljson ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.649 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(ARRAY[1,2,3]: 'aaa');
2025-02-01 03:25:12.651 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.651 UTC client backend[30534] pg_regress/json DETAIL:  Token "'" is invalid.
2025-02-01 03:25:12.651 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: '...
2025-02-01 03:25:12.651 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT $$''$$::json;
2025-02-01 03:25:12.651 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "2"
2025-02-01 03:25:12.651 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '2': NULL, '3': 1, repeat('x', 1000): 1, 2: repeat('a', 100) WITH UNIQUE);
2025-02-01 03:25:12.651 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.651 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '1': NULL WITH UNIQUE);
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE);
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '1': NULL NULL ON NULL WITH UNIQUE RETURNING jsonb);
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '1': NULL ABSENT ON NULL WITH UNIQUE RETURNING jsonb);
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 NULL ON NULL WITH UNIQUE);
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE);
2025-02-01 03:25:12.652 UTC client backend[30545] pg_regress/jsonpath ERROR:  invalid input syntax for type jsonpath: "" at character 8
2025-02-01 03:25:12.652 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select ''::jsonpath;
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.652 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT(1: 1, '2': NULL, '1': 1 ABSENT ON NULL WITH UNIQUE RETURNING jsonb);
2025-02-01 03:25:12.656 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.656 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "'" is invalid.
2025-02-01 03:25:12.656 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: '...
2025-02-01 03:25:12.656 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT $$''$$::jsonb;
2025-02-01 03:25:12.657 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot set JSON encoding for non-bytea output types at character 34
2025-02-01 03:25:12.657 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING UTF8);
2025-02-01 03:25:12.657 UTC client backend[30535] pg_regress/sqljson ERROR:  unrecognized JSON encoding: invalid_encoding at character 55
2025-02-01 03:25:12.657 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(RETURNING text FORMAT JSON ENCODING INVALID_ENCODING);
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token ""abc" is invalid.
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: "abc
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '"abc'::jsonb;
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb DETAIL:  Character with value 0x0a must be escaped.
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: "abc
2025-02-01 03:25:12.658 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '"abc
	def"'::jsonb;
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json DETAIL:  Token ""abc" is invalid.
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: "abc
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '"abc'::json;
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json DETAIL:  Character with value 0x0a must be escaped.
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: "abc
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '"abc
	def"'::json;
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson ERROR:  unsupported JSON encoding at character 35
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson HINT:  Only UTF8 JSON encoding is supported.
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF16);
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json DETAIL:  Escape sequence "\v" is invalid.
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: "\v...
2025-02-01 03:25:12.659 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '"\v"'::json;
2025-02-01 03:25:12.659 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.659 UTC client backend[30532] pg_regress/jsonb DETAIL:  Escape sequence "\v" is invalid.
2025-02-01 03:25:12.659 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: "\v...
2025-02-01 03:25:12.659 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '"\v"'::jsonb;
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson ERROR:  unsupported JSON encoding at character 35
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson HINT:  Only UTF8 JSON encoding is supported.
2025-02-01 03:25:12.659 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(RETURNING bytea FORMAT JSON ENCODING UTF32);
2025-02-01 03:25:12.660 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.660 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "01" is invalid.
2025-02-01 03:25:12.660 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: 01
2025-02-01 03:25:12.660 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '01'::jsonb;
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "1f2" is invalid.
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: 1f2
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '1f2'::jsonb;
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "0.x1" is invalid.
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: 0.x1
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '0.x1'::jsonb;
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "1.3ex100" is invalid.
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: 1.3ex100
2025-02-01 03:25:12.663 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '1.3ex100'::jsonb;
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected JSON value, but found "]".
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: [1,2,]
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '[1,2,]'::jsonb;
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: [1,2
2025-02-01 03:25:12.666 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '[1,2'::jsonb;
2025-02-01 03:25:12.667 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is out of bounds
2025-02-01 03:25:12.667 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1]', 'strict $[1]');
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: [1,[2]
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '[1,[2]'::jsonb;
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected ":", but found "}".
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc"}
2025-02-01 03:25:12.667 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc"}'::jsonb;
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected string or "}", but found "1".
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {1...
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{1:"abc"}'::jsonb;
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected ":", but found ",".
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc",...
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc",1}'::jsonb;
2025-02-01 03:25:12.668 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.668 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.668 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u"
2025-02-01 03:25:12.668 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u"'::json;
2025-02-01 03:25:12.668 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.668 UTC client backend[30534] pg_regress/json DETAIL:  Token "01" is invalid.
2025-02-01 03:25:12.668 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: 01
2025-02-01 03:25:12.668 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '01'::json;
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "=" is invalid.
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc"=...
2025-02-01 03:25:12.668 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc"=1}'::jsonb;
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected JSON value, but found ":".
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc"::...
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc"::1}'::jsonb;
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u00"
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u00"'::json;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  Token "1f2" is invalid.
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: 1f2
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '1f2'::json;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  Token "0.x1" is invalid.
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: 0.x1
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '0.x1'::json;
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u000g...
2025-02-01 03:25:12.669 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u000g"'::json;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  Token "1.3ex100" is invalid.
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: 1.3ex100
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '1.3ex100'::json;
2025-02-01 03:25:12.669 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is out of integer range
2025-02-01 03:25:12.669 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1]', 'lax $[10000000000000000]');
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected "," or "}", but found ":".
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc":1:...
2025-02-01 03:25:12.669 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc":1:2}'::jsonb;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  Expected JSON value, but found "]".
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: [1,2,]
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '[1,2,]'::json;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: [1,2
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '[1,2'::json;
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: [1,[2]
2025-02-01 03:25:12.669 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '[1,[2]'::json;
2025-02-01 03:25:12.670 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected string, but found "3".
2025-02-01 03:25:12.670 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: {"abc":1,3...
2025-02-01 03:25:12.670 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{"abc":1,3}'::jsonb;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected ":", but found "}".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc"}
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc"}'::json;
2025-02-01 03:25:12.670 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is out of integer range
2025-02-01 03:25:12.670 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1]', 'strict $[10000000000000000]');
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected string or "}", but found "1".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {1...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{1:"abc"}'::json;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected ":", but found ",".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc",...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc",1}'::json;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Token "=" is invalid.
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc"=...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc"=1}'::json;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected JSON value, but found ":".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc"::...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc"::1}'::json;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected "," or "}", but found ":".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc":1:...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc":1:2}'::json;
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json DETAIL:  Expected string, but found "3".
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: {"abc":1,3...
2025-02-01 03:25:12.670 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{"abc":1,3}'::json;
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode high surrogate must not follow a high surrogate.
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ud83d\ud83d...
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  select json '{ "a":  "\ud83d\ud83d" }' -> 'a';
2025-02-01 03:25:12.671 UTC client backend[30532] pg_regress/jsonb ERROR:  stack depth limit exceeded
2025-02-01 03:25:12.671 UTC client backend[30532] pg_regress/jsonb HINT:  Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate.
2025-02-01 03:25:12.671 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT repeat('[', 10000)::jsonb;
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ude04...
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  select json '{ "a":  "\ude04\ud83d" }' -> 'a';
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ud83dX...
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  select json '{ "a":  "\ud83dX" }' -> 'a';
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ude04...
2025-02-01 03:25:12.671 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  select json '{ "a":  "\ude04X" }' -> 'a';
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json ERROR:  stack depth limit exceeded
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json HINT:  Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate.
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT repeat('[', 10000)::json;
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json ERROR:  stack depth limit exceeded
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json HINT:  Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate.
2025-02-01 03:25:12.671 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT repeat('{"a":', 10000)::json;
2025-02-01 03:25:12.672 UTC client backend[30545] pg_regress/jsonpath ERROR:  LAST is allowed only in array subscripts at character 8
2025-02-01 03:25:12.672 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select 'last'::jsonpath;
2025-02-01 03:25:12.672 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8
2025-02-01 03:25:12.672 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '"\u"'::jsonpath;
2025-02-01 03:25:12.672 UTC client backend[30545] pg_regress/jsonpath ERROR:  LAST is allowed only in array subscripts at character 8
2025-02-01 03:25:12.672 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '$ ? (last > 0)'::jsonpath;
2025-02-01 03:25:12.673 UTC client backend[30532] pg_regress/jsonb ERROR:  stack depth limit exceeded
2025-02-01 03:25:12.673 UTC client backend[30532] pg_regress/jsonb HINT:  Increase the configuration parameter "max_stack_depth" (currently 100kB), after ensuring the platform's stack depth limit is adequate.
2025-02-01 03:25:12.673 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT repeat('{"a":', 10000)::jsonb;
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson ERROR:  subquery must return only one column at character 8
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(SELECT FROM (VALUES (1)) foo(i));
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '"\u00"'::jsonpath;
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson ERROR:  subquery must return only one column at character 8
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(SELECT i, i FROM (VALUES (1)) foo(i));
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '"\u000g"'::jsonpath;
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson ERROR:  subquery must return only one column at character 8
2025-02-01 03:25:12.673 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(SELECT * FROM (VALUES (1, 2)) foo(i, j));
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  unsupported Unicode escape sequence at character 8
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.673 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '"\u0000"'::jsonpath;
2025-02-01 03:25:12.674 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1.t" of jsonpath input at character 8
2025-02-01 03:25:12.674 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1.type()'::jsonpath;
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json DETAIL:  Expected end of input, but found "false".
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: true false
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT 'true false'::json;
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json DETAIL:  Expected end of input, but found ",".
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: true,...
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT 'true, false'::json;
2025-02-01 03:25:12.674 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.674 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode high surrogate must not follow a high surrogate.
2025-02-01 03:25:12.674 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '"\ud83d\ud83d"'::jsonpath;
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json DETAIL:  Token "truf" is invalid.
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: truf
2025-02-01 03:25:12.674 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT 'truf'::json;
2025-02-01 03:25:12.675 UTC client backend[30548] pg_regress/json_encoding ERROR:  unsupported Unicode escape sequence
2025-02-01 03:25:12.675 UTC client backend[30548] pg_regress/json_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.675 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "null \u0000...
2025-02-01 03:25:12.675 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  select json '{ "a":  "null \u0000 escape" }' ->> 'a' as fails;
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '"\ude04\ud83d"'::jsonpath;
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json DETAIL:  Token "trues" is invalid.
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: trues
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT 'trues'::json;
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '"\ud83dX"'::jsonpath;
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1: 
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ''::json;
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.675 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '"\ude04X"'::jsonpath;
2025-02-01 03:25:12.675 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  only one FOR ORDINALITY column is allowed at character 69
2025-02-01 03:25:12.675 UTC client backend[30536] 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-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 1:     
2025-02-01 03:25:12.675 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '    '::json;
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json DETAIL:  Expected JSON value, but found ",".
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 3: 		"two":,...
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{
			"one": 1,
			"two":,"two",  -- ERROR extraneous comma before field "two"
			"three":
			true}'::json;
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json DETAIL:  Expected JSON value, but found "}".
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json CONTEXT:  JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":}
2025-02-01 03:25:12.676 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT '{
			"one": 1,
			"two":"two",
			"averyveryveryveryveryveryveryveryveryverylongfieldname":}'::json;
2025-02-01 03:25:12.676 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.676 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_EXISTS(jsonb '1', 'strict $.a' ERROR ON ERROR);
2025-02-01 03:25:12.676 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid input syntax for type integer: "err"
2025-02-01 03:25:12.676 UTC client backend[30536] 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-02-01 03:25:12.677 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  unsupported Unicode escape sequence at character 8
2025-02-01 03:25:12.677 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.677 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '"null \u0000 escape"'::jsonpath as not_unescaped;
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected end of input, but found "false".
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: true false
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT 'true false'::jsonb;
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected end of input, but found ",".
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: true,...
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT 'true, false'::jsonb;
2025-02-01 03:25:12.677 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid input syntax for type integer: "err"
2025-02-01 03:25:12.677 UTC client backend[30536] 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-02-01 03:25:12.677 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  no SQL/JSON item found for specified path of column "a"
2025-02-01 03:25:12.677 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int PATH '$.a' ERROR ON EMPTY)) jt;
2025-02-01 03:25:12.677 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u" of jsonpath input at character 8
2025-02-01 03:25:12.677 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '$."\u"'::jsonpath;
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "truf" is invalid.
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: truf
2025-02-01 03:25:12.677 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT 'truf'::jsonb;
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb DETAIL:  Token "trues" is invalid.
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: trues
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT 'trues'::jsonb;
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u00" of jsonpath input at character 8
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '$."\u00"'::jsonpath;
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1: 
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ''::jsonb;
2025-02-01 03:25:12.678 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.678 UTC client backend[30536] 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-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid Unicode escape sequence at or near "\u000" of jsonpath input at character 8
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '$."\u000g"'::jsonpath;
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb DETAIL:  The input string ended unexpectedly.
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 1:     
2025-02-01 03:25:12.678 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '    '::jsonb;
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  unsupported Unicode escape sequence at character 8
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.678 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  SELECT '$."\u0000"'::jsonpath;
2025-02-01 03:25:12.678 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  no SQL/JSON item found for specified path of column "a"
2025-02-01 03:25:12.678 UTC client backend[30536] 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-02-01 03:25:12.678 UTC client backend[30545] pg_regress/jsonpath ERROR:  invalid regular expression: parentheses () not balanced at character 8
2025-02-01 03:25:12.678 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '$ ? (@ like_regex "(invalid pattern")'::jsonpath;
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected JSON value, but found ",".
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 3: 		"two":,...
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{
			"one": 1,
			"two":,"two",  -- ERROR extraneous comma before field "two"
			"three":
			true}'::jsonb;
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb DETAIL:  Expected JSON value, but found "}".
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb CONTEXT:  JSON data, line 4: ...yveryveryveryveryveryveryveryverylongfieldname":}
2025-02-01 03:25:12.679 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT '{
			"one": 1,
			"two":"two",
			"averyveryveryveryveryveryveryveryveryverylongfieldname":}'::jsonb;
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode high surrogate must not follow a high surrogate.
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '$."\ud83d\ud83d"'::jsonpath;
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '$."\ude04\ud83d"'::jsonpath;
2025-02-01 03:25:12.680 UTC client backend[30545] pg_regress/jsonpath ERROR:  XQuery "x" flag (expanded regular expressions) is not implemented at character 8
2025-02-01 03:25:12.680 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '$ ? (@ like_regex "pattern" flag "xsms")'::jsonpath;
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '$."\ud83dX"'::jsonpath;
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.680 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '$."\ude04X"'::jsonpath;
2025-02-01 03:25:12.680 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.680 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  invalid input syntax for type smallint: "false"
2025-02-01 03:25:12.680 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int2 EXISTS PATH '$.a'));
2025-02-01 03:25:12.681 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.681 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  invalid input syntax for type bigint: "false"
2025-02-01 03:25:12.681 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a int8 EXISTS PATH '$.a'));
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u"
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u"'::jsonb;
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u00"
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u00"'::jsonb;
2025-02-01 03:25:12.681 UTC client backend[30545] pg_regress/jsonpath ERROR:  invalid input syntax for type jsonpath at character 8
2025-02-01 03:25:12.681 UTC client backend[30545] pg_regress/jsonpath DETAIL:  Unrecognized flag character "a" in LIKE_REGEX predicate.
2025-02-01 03:25:12.681 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '$ ? (@ like_regex "pattern" flag "a")'::jsonpath;
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 8
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding DETAIL:  "\u" must be followed by four hexadecimal digits.
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u000g...
2025-02-01 03:25:12.681 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u000g"'::jsonb;
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  invalid input syntax for type real: "false"
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a float4 EXISTS PATH '$.a'));
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  value too long for type character(3)
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a'));
2025-02-01 03:25:12.682 UTC client backend[30545] pg_regress/jsonpath ERROR:  @ is not allowed in root expressions at character 8
2025-02-01 03:25:12.682 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '@ + 1'::jsonpath;
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  value too long for type character(3)
2025-02-01 03:25:12.682 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"a"', '$' COLUMNS (a char(3) EXISTS PATH '$.a' ERROR ON ERROR));
2025-02-01 03:25:12.683 UTC client backend[30553] pg_regress/jsonpath_encoding ERROR:  unsupported Unicode escape sequence at character 8
2025-02-01 03:25:12.683 UTC client backend[30553] pg_regress/jsonpath_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.683 UTC client backend[30553] pg_regress/jsonpath_encoding STATEMENT:  select '$."null \u0000 escape"'::jsonpath as not_unescaped;
2025-02-01 03:25:12.683 UTC client backend[30548] pg_regress/json_encoding ERROR:  unsupported Unicode escape sequence at character 8
2025-02-01 03:25:12.683 UTC client backend[30548] pg_regress/json_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.683 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: "\u0000...
2025-02-01 03:25:12.683 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT '"\u0000"'::jsonb;
2025-02-01 03:25:12.684 UTC client backend[30535] pg_regress/sqljson ERROR:  null value not allowed for object key
2025-02-01 03:25:12.684 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECTAGG(NULL: 1);
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 14
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode high surrogate must not follow a high surrogate.
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ud83d\ud83d...
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "\ud83d\ud83d" }' -> 'a';
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 14
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ude04...
2025-02-01 03:25:12.686 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "\ude04\ud83d" }' -> 'a';
2025-02-01 03:25:12.688 UTC client backend[30535] pg_regress/sqljson ERROR:  field name must not be null
2025-02-01 03:25:12.688 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECTAGG(NULL: 1 RETURNING jsonb);
2025-02-01 03:25:12.688 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.688 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_exists('[{"a": 1}, {"a": 2}, 3]', 'strict $[*].a', silent => false);
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 14
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ud83dX...
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "\ud83dX" }' -> 'a';
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding ERROR:  invalid input syntax for type json at character 14
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding DETAIL:  Unicode low surrogate must follow a high surrogate.
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "\ude04...
2025-02-01 03:25:12.689 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "\ude04X" }' -> 'a';
2025-02-01 03:25:12.689 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.689 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', 'strict $.a');
2025-02-01 03:25:12.689 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.689 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECTAGG(k: v WITH UNIQUE KEYS)
	FROM (VALUES (1, 1), (1, NULL), (2, 2)) foo(k, v);
2025-02-01 03:25:12.689 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath wildcard member accessor can only be applied to an object
2025-02-01 03:25:12.689 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', 'strict $.*');
2025-02-01 03:25:12.690 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.690 UTC client backend[30535] 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-02-01 03:25:12.690 UTC client backend[30548] pg_regress/json_encoding ERROR:  unsupported Unicode escape sequence at character 14
2025-02-01 03:25:12.690 UTC client backend[30548] pg_regress/json_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.690 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "null \u0000...
2025-02-01 03:25:12.690 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "null \u0000 escape" }' as fails;
2025-02-01 03:25:12.690 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.690 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.a');
2025-02-01 03:25:12.691 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.691 UTC client backend[30535] 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-02-01 03:25:12.691 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value
2025-02-01 03:25:12.691 UTC client backend[30535] 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-02-01 03:25:12.691 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  JSON object does not contain key "a"
2025-02-01 03:25:12.691 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', 'strict $.a');
2025-02-01 03:25:12.691 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.691 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  value for domain dint4_0 violates check constraint "dint4_0_check"
2025-02-01 03:25:12.691 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT a, a::bool FROM JSON_TABLE(jsonb '{"a":1}', '$' COLUMNS (a dint4_0 EXISTS PATH '$.b'));
2025-02-01 03:25:12.691 UTC client backend[30548] pg_regress/json_encoding ERROR:  unsupported Unicode escape sequence at character 14
2025-02-01 03:25:12.691 UTC client backend[30548] pg_regress/json_encoding DETAIL:  \u0000 cannot be converted to text.
2025-02-01 03:25:12.691 UTC client backend[30548] pg_regress/json_encoding CONTEXT:  JSON data, line 1: { "a":  "null \u0000...
2025-02-01 03:25:12.691 UTC client backend[30548] pg_regress/json_encoding STATEMENT:  SELECT jsonb '{ "a":  "null \u0000 escape" }' ->> 'a' as fails;
2025-02-01 03:25:12.692 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array accessor can only be applied to an array
2025-02-01 03:25:12.692 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', 'strict $[1]');
2025-02-01 03:25:12.693 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath wildcard array accessor can only be applied to an array
2025-02-01 03:25:12.693 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', 'strict $[*]');
2025-02-01 03:25:12.693 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "0"
2025-02-01 03:25:12.693 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECTAGG(mod(i,100): (i)::text FORMAT JSON WITH UNIQUE)
	FROM generate_series(0, 199) i;
2025-02-01 03:25:12.693 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is out of bounds
2025-02-01 03:25:12.693 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $[1]');
2025-02-01 03:25:12.694 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is not a single numeric value
2025-02-01 03:25:12.694 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $["a"]');
2025-02-01 03:25:12.695 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  value for domain dint4_0 violates check constraint "dint4_0_check"
2025-02-01 03:25:12.695 UTC client backend[30536] 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-02-01 03:25:12.695 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  could not coerce ON ERROR expression (FALSE) to the RETURNING type
2025-02-01 03:25:12.695 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  value for domain dint4_0 violates check constraint "dint4_0_check"
2025-02-01 03:25:12.695 UTC client backend[30536] 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-02-01 03:25:12.699 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 56
2025-02-01 03:25:12.699 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '"world"', '$' COLUMNS (item text PATH '$' WITH WRAPPER OMIT QUOTES));
2025-02-01 03:25:12.700 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  division by zero
2025-02-01 03:25:12.700 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[12, {"a": 13}, {"b": 14}]', 'lax $[0 to 10 / 0].a');
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  only string constants are supported in JSON_TABLE path specification at character 46
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '{"a": 123}', '$' || '.' || 'a' COLUMNS (foo int));
2025-02-01 03:25:12.703 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "1.23"
2025-02-01 03:25:12.703 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '"1.23"', '$' RETURNING int ERROR ON ERROR);
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  JSON path expression for column "b" must return single item when no wrapper is requested
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable HINT:  Use the WITH WRAPPER clause to wrap SQL/JSON items into an array.
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE('{"a": [{"b": "1"}, {"b": "2"}]}', '$' COLUMNS (b json path '$.a[*].b' ERROR ON ERROR));
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  duplicate JSON_TABLE column or path name: a at character 90
2025-02-01 03:25:12.703 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(
		jsonb '[]', '$' AS a
		COLUMNS (
			b int,
			NESTED PATH '$' AS a
			COLUMNS (
				c int
			)
		)
	) jt;
2025-02-01 03:25:12.703 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(2)
2025-02-01 03:25:12.703 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING char(2) ERROR ON ERROR);
2025-02-01 03:25:12.704 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  duplicate JSON_TABLE column or path name: b at character 85
2025-02-01 03:25:12.704 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(
		jsonb '[]', '$'
		COLUMNS (
			b int,
			NESTED PATH '$' AS b
			COLUMNS (
				c int
			)
		)
	) jt;
2025-02-01 03:25:12.704 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  duplicate JSON_TABLE column or path name: a at character 156
2025-02-01 03:25:12.704 UTC client backend[30536] 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-02-01 03:25:12.704 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "aaa"
2025-02-01 03:25:12.704 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int ERROR ON ERROR);
2025-02-01 03:25:12.705 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "00" of jsonpath input at character 8
2025-02-01 03:25:12.705 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '00'::jsonpath;
2025-02-01 03:25:12.705 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.705 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0755'::jsonpath;
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON ERROR expression (NULL) to the RETURNING type
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  domain sqljsonb_int_not_null does not allow null values
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null);
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  domain sqljsonb_int_not_null does not allow null values
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null ERROR ON ERROR);
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  domain sqljsonb_int_not_null does not allow null values
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb 'null', '$' RETURNING sqljsonb_int_not_null DEFAULT 2 ON EMPTY ERROR ON ERROR);
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  domain sqljsonb_int_not_null does not allow null values
2025-02-01 03:25:12.708 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1',  '$.a' RETURNING sqljsonb_int_not_null DEFAULT NULL ON EMPTY ERROR ON ERROR);
2025-02-01 03:25:12.709 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.709 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1,2,3]', 'strict $[*].a');
2025-02-01 03:25:12.710 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.710 UTC client backend[30535] 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-02-01 03:25:12.710 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is out of bounds
2025-02-01 03:25:12.710 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $[last]');
2025-02-01 03:25:12.711 UTC client backend[30535] pg_regress/sqljson ERROR:  duplicate JSON object key value: "1"
2025-02-01 03:25:12.711 UTC client backend[30535] 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-02-01 03:25:12.712 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath array subscript is not a single numeric value
2025-02-01 03:25:12.712 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1,2,3]', '$[last ? (@.type() == "string")]');
2025-02-01 03:25:12.713 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  could not find jsonpath variable "value"
2025-02-01 03:25:12.713 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)');
2025-02-01 03:25:12.713 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  "vars" argument is not an object
2025-02-01 03:25:12.713 UTC client backend[30546] pg_regress/jsonb_jsonpath DETAIL:  Jsonpath parameters should be encoded as key-value pairs of "vars" object.
2025-02-01 03:25:12.713 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '1');
2025-02-01 03:25:12.714 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  "vars" argument is not an object
2025-02-01 03:25:12.714 UTC client backend[30546] pg_regress/jsonb_jsonpath DETAIL:  Jsonpath parameters should be encoded as key-value pairs of "vars" object.
2025-02-01 03:25:12.714 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select * from jsonb_path_query('{"a": 10}', '$ ? (@.a < $value)', '[{"value" : 13}]');
2025-02-01 03:25:12.716 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1a" of jsonpath input at character 8
2025-02-01 03:25:12.716 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1a'::jsonpath;
2025-02-01 03:25:12.716 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1e" of jsonpath input at character 8
2025-02-01 03:25:12.716 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1e'::jsonpath;
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1.e" of jsonpath input at character 8
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1.e'::jsonpath;
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1.2a" of jsonpath input at character 8
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1.2a'::jsonpath;
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1.2e" of jsonpath input at character 8
2025-02-01 03:25:12.717 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1.2e'::jsonpath;
2025-02-01 03:25:12.718 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value for domain rgb violates check constraint "rgb_check"
2025-02-01 03:25:12.718 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE('"purple"'::jsonb, 'lax $[*]' RETURNING rgb ERROR ON ERROR);
2025-02-01 03:25:12.719 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1.2e3a" of jsonpath input at character 8
2025-02-01 03:25:12.719 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1.2e3a'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "0b" of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0b'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1b" of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1b'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0b0x'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "0o" of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0o'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1o" of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1o'::jsonpath;
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.722 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0o0x'::jsonpath;
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "0x" of jsonpath input at character 8
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0x'::jsonpath;
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1x" of jsonpath input at character 8
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1x'::jsonpath;
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.723 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0x0y'::jsonpath;
2025-02-01 03:25:12.724 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.724 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '_100'::jsonpath;
2025-02-01 03:25:12.724 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "100_" of jsonpath input at character 8
2025-02-01 03:25:12.724 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '100_'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '100__000'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '_1_000.5'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1_000_" of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1_000_.5'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1_000._" of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1_000._5'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1_000.5_" of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1_000.5_'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  trailing junk after numeric literal at or near "1_000.5e" of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '1_000.5e_1'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0b_10_0101'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0o_273'::jsonpath;
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath ERROR:  syntax error at end of jsonpath input at character 8
2025-02-01 03:25:12.725 UTC client backend[30545] pg_regress/jsonpath STATEMENT:  select '0x_42F'::jsonpath;
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  JSON path expression in JSON_VALUE must return single scalar item
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '[]', '$' ERROR ON ERROR);
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  JSON path expression in JSON_VALUE must return single scalar item
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '{}', '$' ERROR ON ERROR);
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  jsonpath member accessor can only be applied to an object
2025-02-01 03:25:12.727 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1', 'strict $.a' ERROR ON ERROR);
2025-02-01 03:25:12.728 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.728 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY ERROR ON ERROR);
2025-02-01 03:25:12.729 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.729 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1', 'lax $.a' ERROR ON EMPTY DEFAULT '3' ON ERROR);
2025-02-01 03:25:12.729 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  JSON path expression in JSON_VALUE must return single scalar item
2025-02-01 03:25:12.729 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '[1,2]', '$[*]' ERROR ON ERROR);
2025-02-01 03:25:12.730 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: " "
2025-02-01 03:25:12.730 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '[" "]', '$[*]' RETURNING int ERROR ON ERROR);
2025-02-01 03:25:12.730 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  cannot specify FORMAT JSON in RETURNING clause of JSON_VALUE() at character 55
2025-02-01 03:25:12.730 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING int FORMAT JSON);
2025-02-01 03:25:12.731 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  returning pseudo-types is not supported in SQL/JSON functions
2025-02-01 03:25:12.731 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '["1"]', '$[*]' RETURNING record);
2025-02-01 03:25:12.738 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "1.234"
2025-02-01 03:25:12.738 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  select json_value('{"a": 1.234}', '$.a' returning int error on error);
2025-02-01 03:25:12.738 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "1.234"
2025-02-01 03:25:12.738 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  select json_value('{"a": "1.234"}', '$.a' returning int error on error);
2025-02-01 03:25:12.745 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.745 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Token "aaa" is invalid.
2025-02-01 03:25:12.745 UTC client backend[30549] pg_regress/sqljson_queryfuncs CONTEXT:  JSON data, line 1: aaa
2025-02-01 03:25:12.745 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"aaa"', '$' OMIT QUOTES ERROR ON ERROR);
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type json
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Token "aaa" is invalid.
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs CONTEXT:  JSON data, line 1: aaa
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING json OMIT QUOTES ERROR ON ERROR);
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(3)
2025-02-01 03:25:12.747 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING char(3) ERROR ON ERROR);
2025-02-01 03:25:12.749 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8
2025-02-01 03:25:12.749 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[1]', '$' WITH WRAPPER OMIT QUOTES);
2025-02-01 03:25:12.749 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  SQL/JSON QUOTES behavior must not be specified when WITH WRAPPER is used at character 8
2025-02-01 03:25:12.749 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[1]', '$' WITH CONDITIONAL WRAPPER OMIT QUOTES);
2025-02-01 03:25:12.752 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  expected JSON array
2025-02-01 03:25:12.752 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb'{"rec": "{1,2,3}"}', '$.rec' returning int[] keep quotes error on error);
2025-02-01 03:25:12.753 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  malformed range literal: ""[1,2]""
2025-02-01 03:25:12.753 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Missing left parenthesis or bracket.
2025-02-01 03:25:12.753 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb'{"rec": "[1,2]"}', '$.rec' 	returning int4range keep quotes error on error);
2025-02-01 03:25:12.759 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  syntax error at or near "empty" at character 79
2025-02-01 03:25:12.759 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on empty));
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON ERROR behavior at character 57
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause.
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int) NULL ON ERROR);
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON EMPTY behavior for column "a" at character 56
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only ERROR, NULL, or DEFAULT expression is allowed in ON EMPTY for scalar columns.
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int true on empty));
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON ERROR behavior for column "a" at character 68
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for formatted columns.
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int omit quotes true on error));
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable ERROR:  invalid ON ERROR behavior for column "a" at character 63
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable DETAIL:  Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for EXISTS columns.
2025-02-01 03:25:12.760 UTC client backend[30536] pg_regress/sqljson_jsontable STATEMENT:  SELECT * FROM JSON_TABLE(jsonb '1', '$' COLUMNS (a int exists empty object on error));
2025-02-01 03:25:12.766 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.766 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY);
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY NULL ON ERROR);
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY ARRAY ON ERROR);
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.767 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY EMPTY OBJECT ON ERROR);
2025-02-01 03:25:12.768 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.768 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[]', '$[*]' ERROR ON EMPTY ERROR ON ERROR);
2025-02-01 03:25:12.768 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  JSON path expression in JSON_QUERY must return single item when no wrapper is requested
2025-02-01 03:25:12.768 UTC client backend[30549] pg_regress/sqljson_queryfuncs HINT:  Use the WITH WRAPPER clause to wrap SQL/JSON items into an array.
2025-02-01 03:25:12.768 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[1,2]', '$[*]' ERROR ON ERROR);
2025-02-01 03:25:12.770 UTC client backend[30534] pg_regress/json ERROR:  cannot call json_object_keys on a scalar
2025-02-01 03:25:12.770 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object_keys(test_json)
	FROM test_json
	WHERE json_type = 'scalar';
2025-02-01 03:25:12.771 UTC client backend[30534] pg_regress/json ERROR:  cannot call json_object_keys on an array
2025-02-01 03:25:12.771 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object_keys(test_json)
	FROM test_json
	WHERE json_type = 'array';
2025-02-01 03:25:12.771 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot call jsonb_object_keys on a scalar
2025-02-01 03:25:12.771 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'scalar';
2025-02-01 03:25:12.772 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot call jsonb_object_keys on an array
2025-02-01 03:25:12.772 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object_keys(test_json) FROM test_jsonb WHERE json_type = 'array';
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  expected JSON array
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR);
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON ERROR expression (EMPTY OBJECT) to the RETURNING type
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  expected JSON array
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"[3,4]"', '$[*]' RETURNING bigint[] EMPTY OBJECT ON ERROR);
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type smallint: ""123.1""
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 error on error);
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: ""123.1""
2025-02-01 03:25:12.773 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int4 error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type bigint: ""123.1""
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int8 error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type boolean: ""123.1""
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING bool error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type numeric: ""123.1""
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING numeric error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type real: ""123.1""
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING real error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type double precision: ""123.1""
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING float8 error on error);
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type smallint: "123.1"
2025-02-01 03:25:12.774 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '"123.1"', '$' RETURNING int2 omit quotes error on error);
2025-02-01 03:25:12.775 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  returning pseudo-types is not supported in SQL/JSON functions
2025-02-01 03:25:12.775 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[3,4]', '$[*]' RETURNING anyarray EMPTY OBJECT ON ERROR);
2025-02-01 03:25:12.775 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  division by zero
2025-02-01 03:25:12.775 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('0', '1 / $');
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  division by zero
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('0', '1 / $ + 2');
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  division by zero
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('0', '-(3 + 1 % $)');
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  right operand of jsonpath operator + is not a single numeric value
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$ + "2"');
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  right operand of jsonpath operator * is not a single numeric value
2025-02-01 03:25:12.776 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1, 2]', '3 * $');
2025-02-01 03:25:12.777 UTC client backend[30535] pg_regress/sqljson ERROR:  cannot use type integer in IS JSON predicate
2025-02-01 03:25:12.777 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT NULL::int IS JSON;
2025-02-01 03:25:12.777 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  operand of unary jsonpath operator - is not a numeric value
2025-02-01 03:25:12.777 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"a"', '-$');
2025-02-01 03:25:12.777 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  operand of unary jsonpath operator + is not a numeric value
2025-02-01 03:25:12.777 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1,"2",3]', '+$');
2025-02-01 03:25:12.777 UTC client backend[30535] pg_regress/sqljson ERROR:  invalid byte sequence for encoding "UTF8": 0x00
2025-02-01 03:25:12.777 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT bytea '\x00' IS JSON;
2025-02-01 03:25:12.779 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  cannot call populate_composite on a scalar
2025-02-01 03:25:12.779 UTC client backend[30549] 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-02-01 03:25:12.784 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "a"
2025-02-01 03:25:12.784 UTC client backend[30549] 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-02-01 03:25:12.784 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  left operand of jsonpath operator * is not a single numeric value
2025-02-01 03:25:12.784 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{"a": [1, 2]}', 'lax $.a * 3');
2025-02-01 03:25:12.786 UTC client backend[30534] pg_regress/json ERROR:  cannot get array length of a non-array
2025-02-01 03:25:12.786 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_array_length('{"f1":1,"f2":[5,6]}');
2025-02-01 03:25:12.786 UTC client backend[30534] pg_regress/json ERROR:  cannot get array length of a scalar
2025-02-01 03:25:12.786 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_array_length('4');
2025-02-01 03:25:12.786 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath wildcard member accessor can only be applied to an object
2025-02-01 03:25:12.786 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1,2,3,{"b": [3,4,5]}]', 'strict $.*');
2025-02-01 03:25:12.788 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  syntax error at or near "{" of jsonpath input
2025-02-01 03:25:12.788 UTC client backend[30549] 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-02-01 03:25:12.788 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid input syntax for type integer: "a"
2025-02-01 03:25:12.788 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '[1,2,null,"a"]', '$[*]' RETURNING int[] WITH WRAPPER ERROR ON ERROR);
2025-02-01 03:25:12.795 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON EMPTY expression (NULL) to the RETURNING type
2025-02-01 03:25:12.795 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  domain sqljsonb_int_not_null does not allow null values
2025-02-01 03:25:12.795 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null);
2025-02-01 03:25:12.795 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  no SQL/JSON item found for specified path
2025-02-01 03:25:12.795 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '{"a": 1}', '$.b' RETURNING sqljsonb_int_not_null ERROR ON EMPTY ERROR ON ERROR);
2025-02-01 03:25:12.802 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character varying(2)
2025-02-01 03:25:12.802 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SERIALIZE('{ "a" : 1 } ' RETURNING varchar(2));
2025-02-01 03:25:12.803 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character varying(2)
2025-02-01 03:25:12.803 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_OBJECT('a': JSON_OBJECT('b': 1 RETURNING varchar(2)));
2025-02-01 03:25:12.803 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character varying(2)
2025-02-01 03:25:12.803 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_ARRAY(JSON_ARRAY('{ "a" : 123 }' RETURNING varchar(2)));
2025-02-01 03:25:12.803 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character varying(2)
2025-02-01 03:25:12.803 UTC client backend[30535] 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-02-01 03:25:12.804 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character varying(2)
2025-02-01 03:25:12.804 UTC client backend[30535] 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-02-01 03:25:12.806 UTC client backend[30535] pg_regress/sqljson ERROR:  value too long for type character(2)
2025-02-01 03:25:12.806 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SERIALIZE('123' RETURNING sqljson_char2);
2025-02-01 03:25:12.806 UTC client backend[30535] pg_regress/sqljson ERROR:  value for domain sqljson_char2 violates check constraint "sqljson_char2_check"
2025-02-01 03:25:12.806 UTC client backend[30535] pg_regress/sqljson STATEMENT:  SELECT JSON_SERIALIZE('12' RETURNING sqljson_char2);
2025-02-01 03:25:12.821 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot get array length of a non-array
2025-02-01 03:25:12.821 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_array_length('{"f1":1,"f2":[5,6]}');
2025-02-01 03:25:12.821 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot get array length of a scalar
2025-02-01 03:25:12.821 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_array_length('4');
2025-02-01 03:25:12.822 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .size() can only be applied to an array
2025-02-01 03:25:12.822 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[1,null,true,"11",[],[1],[1,2,3],{},{"a":1,"b":2}]', 'strict $[*].size()');
2025-02-01 03:25:12.826 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .keyvalue() can only be applied to an object
2025-02-01 03:25:12.826 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[{},1]', '$[*].keyvalue()');
2025-02-01 03:25:12.834 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type timestamp: "[100,200,false]"
2025-02-01 03:25:12.834 UTC client backend[30534] 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-02-01 03:25:12.835 UTC client backend[30534] pg_regress/json ERROR:  domain js_int_not_null does not allow null values
2025-02-01 03:25:12.835 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"x": 43.2}') q;
2025-02-01 03:25:12.835 UTC client backend[30534] pg_regress/json ERROR:  domain js_int_not_null does not allow null values
2025-02-01 03:25:12.835 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT i FROM json_populate_record(NULL::jsrec_i_not_null, '{"i": null}') q;
2025-02-01 03:25:12.837 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.837 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ia".
2025-02-01 03:25:12.837 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": 123}') q;
2025-02-01 03:25:12.837 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .keyvalue() can only be applied to an object
2025-02-01 03:25:12.837 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue()');
2025-02-01 03:25:12.838 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .keyvalue() can only be applied to an object
2025-02-01 03:25:12.838 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[{"a": 1, "b": [1, 2]}, {"c": {"a": "bbb"}}]', 'strict $.keyvalue().a');
2025-02-01 03:25:12.839 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .double() can only be applied to a string or numeric value
2025-02-01 03:25:12.839 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.double()');
2025-02-01 03:25:12.840 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .double() can only be applied to a string or numeric value
2025-02-01 03:25:12.840 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.double()');
2025-02-01 03:25:12.847 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .double() can only be applied to a string or numeric value
2025-02-01 03:25:12.847 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.double()');
2025-02-01 03:25:12.847 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .double() can only be applied to a string or numeric value
2025-02-01 03:25:12.847 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.double()');
2025-02-01 03:25:12.848 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .double() is invalid for type double precision
2025-02-01 03:25:12.848 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.double()');
2025-02-01 03:25:12.848 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .double() is invalid for type double precision
2025-02-01 03:25:12.848 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1e1000', '$.double()');
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .double()
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.double()');
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .double()
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.double()');
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json HINT:  See the array element [1] of key "ia".
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], 2]}') q;
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .double()
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.double()');
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json ERROR:  malformed JSON array
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.849 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia FROM json_populate_record(NULL::jsrec, '{"ia": [[1], [2, 3]]}') q;
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .double()
2025-02-01 03:25:12.849 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.double()');
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .abs() can only be applied to a numeric value
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.abs()');
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .floor() can only be applied to a numeric value
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.floor()');
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .ceiling() can only be applied to a numeric value
2025-02-01 03:25:12.850 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.2"', '$.ceiling()');
2025-02-01 03:25:12.852 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.852 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ia1".
2025-02-01 03:25:12.852 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia1 FROM json_populate_record(NULL::jsrec, '{"ia1": 123}') q;
2025-02-01 03:25:12.853 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.853 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ia1d".
2025-02-01 03:25:12.853 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": 123}') q;
2025-02-01 03:25:12.853 UTC client backend[30534] pg_regress/json ERROR:  value for domain js_int_array_1d violates check constraint "js_int_array_1d_check"
2025-02-01 03:25:12.853 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia1d FROM json_populate_record(NULL::jsrec, '{"ia1d": [1, "2", null, 4]}') q;
2025-02-01 03:25:12.854 UTC client backend[30534] pg_regress/json ERROR:  malformed JSON array
2025-02-01 03:25:12.854 UTC client backend[30534] pg_regress/json DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.854 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], [3]]}') q;
2025-02-01 03:25:12.855 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.855 UTC client backend[30534] pg_regress/json HINT:  See the array element [1] of key "ia2".
2025-02-01 03:25:12.855 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia2 FROM json_populate_record(NULL::jsrec, '{"ia2": [[1, 2], 3, 4]}') q;
2025-02-01 03:25:12.855 UTC client backend[30534] pg_regress/json ERROR:  value for domain js_int_array_2d violates check constraint "js_int_array_2d_check"
2025-02-01 03:25:12.855 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ia2d FROM json_populate_record(NULL::jsrec, '{"ia2d": [[1, "2"], [null, 4]]}') q;
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .datetime() can only be applied to a string
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.datetime()');
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .datetime() can only be applied to a string
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.datetime()');
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .datetime() can only be applied to a string
2025-02-01 03:25:12.859 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.datetime()');
2025-02-01 03:25:12.860 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .datetime() can only be applied to a string
2025-02-01 03:25:12.860 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.datetime()');
2025-02-01 03:25:12.860 UTC client backend[30534] pg_regress/json ERROR:  malformed JSON array
2025-02-01 03:25:12.860 UTC client backend[30534] pg_regress/json DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.860 UTC client backend[30534] 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-02-01 03:25:12.861 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.861 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ta".
2025-02-01 03:25:12.861 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": 123}') q;
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .datetime() can only be applied to a string
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.datetime()');
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  datetime format is not recognized: "bogus"
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use a datetime template argument to specify the input data format.
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.datetime()');
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  invalid datetime format separator: "a"
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34"', '$.datetime("aaa")');
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  invalid value "aa" for "HH24"
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath DETAIL:  Value must be an integer.
2025-02-01 03:25:12.861 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"aaaa"', '$.datetime("HH24")');
2025-02-01 03:25:12.862 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.862 UTC client backend[30534] pg_regress/json HINT:  See the array element [1] of key "ta".
2025-02-01 03:25:12.862 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ta FROM json_populate_record(NULL::jsrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q;
2025-02-01 03:25:12.862 UTC client backend[30532] pg_regress/jsonb ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.862 UTC client backend[30532] pg_regress/jsonb HINT:  The arguments of jsonb_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.862 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object('{a,b,c}'::text[]);
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]);
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb HINT:  The arguments of jsonb_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object('a', 'b', 'c');
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb ERROR:  argument 1: key must not be null
2025-02-01 03:25:12.863 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(NULL, 'a');
2025-02-01 03:25:12.864 UTC client backend[30532] pg_regress/jsonb ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.864 UTC client backend[30532] pg_regress/jsonb HINT:  The arguments of jsonb_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.864 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(VARIADIC '{a,b,c}'::text[]);
2025-02-01 03:25:12.864 UTC client backend[30532] pg_regress/jsonb ERROR:  argument 1: key must not be null
2025-02-01 03:25:12.864 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(VARIADIC ARRAY[NULL, 'a']::text[]);
2025-02-01 03:25:12.864 UTC client backend[30534] pg_regress/json ERROR:  value too long for type character(10)
2025-02-01 03:25:12.864 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT c FROM json_populate_record(NULL::jsrec, '{"c": "aaaaaaaaaaaaa"}') q;
2025-02-01 03:25:12.864 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.864 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ca".
2025-02-01 03:25:12.864 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": 123}') q;
2025-02-01 03:25:12.865 UTC client backend[30534] pg_regress/json ERROR:  value too long for type character(10)
2025-02-01 03:25:12.865 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q;
2025-02-01 03:25:12.865 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.865 UTC client backend[30534] pg_regress/json HINT:  See the array element [1] of key "ca".
2025-02-01 03:25:12.865 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT ca FROM json_populate_record(NULL::jsrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q;
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb ERROR:  argument 1: key must not be null
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(null,2);
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r;
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object(json '{"a":1,"b":2}', 3);
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.865 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_build_object('{1,2,3}'::int[], 3);
2025-02-01 03:25:12.866 UTC client backend[30532] pg_regress/jsonb ERROR:  field name must not be null
2025-02-01 03:25:12.866 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object_agg(NULL, '{"a":1}');
2025-02-01 03:25:12.866 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  trailing characters remain in input string after datetime format
2025-02-01 03:25:12.866 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy")');
2025-02-01 03:25:12.866 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  trailing characters remain in input string after datetime format
2025-02-01 03:25:12.866 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy").type()');
2025-02-01 03:25:12.867 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  unmatched format character "T"
2025-02-01 03:25:12.867 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017t12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")');
2025-02-01 03:25:12.867 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  unmatched format character "T"
2025-02-01 03:25:12.867 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017 12:34:56"', '$.datetime("dd-mm-yyyy\"T\"HH24:MI:SS")');
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .bigint() can only be applied to a string or numeric value
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.bigint()');
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .bigint() can only be applied to a string or numeric value
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.bigint()');
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .bigint() can only be applied to a string or numeric value
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.bigint()');
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .bigint() can only be applied to a string or numeric value
2025-02-01 03:25:12.868 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.bigint()');
2025-02-01 03:25:12.869 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.869 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23"', '$.bigint()');
2025-02-01 03:25:12.871 UTC client backend[30532] pg_regress/jsonb ERROR:  field name must not be null
2025-02-01 03:25:12.871 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object_agg(name, type) FROM foo;
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb ERROR:  array must have even number of elements
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object('{a,b,c}');
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb ERROR:  array must have two columns
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object('{{a},{b}}');
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb ERROR:  array must have two columns
2025-02-01 03:25:12.872 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object('{{a,b,c},{b,c,d}}');
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb ERROR:  wrong number of array subscripts
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_object('{{{a,b},{c,d}},{{b,c},{d,e}}}');
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb ERROR:  wrong number of array subscripts
2025-02-01 03:25:12.873 UTC client backend[30532] 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-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb ERROR:  mismatched array dimensions
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}');
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb ERROR:  mismatched array dimensions
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}');
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb ERROR:  null value not allowed for object key
2025-02-01 03:25:12.873 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}');
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json HINT:  See the value of key "jsa".
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT jsa FROM json_populate_record(NULL::jsrec, '{"jsa": 123}') q;
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1e1000', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "nan" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "NaN" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "inf" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json ERROR:  cannot call populate_composite on a scalar
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": 123}') q;
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "-inf" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.875 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.bigint()');
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json ERROR:  cannot call populate_composite on an array
2025-02-01 03:25:12.875 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT rec FROM json_populate_record(NULL::jsrec, '{"rec": [1, 2]}') q;
2025-02-01 03:25:12.876 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.876 UTC client backend[30534] pg_regress/json HINT:  See the value of key "reca".
2025-02-01 03:25:12.876 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": 123}') q;
2025-02-01 03:25:12.876 UTC client backend[30534] pg_regress/json ERROR:  cannot call populate_composite on a scalar
2025-02-01 03:25:12.876 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT reca FROM json_populate_record(NULL::jsrec, '{"reca": [1, 2]}') q;
2025-02-01 03:25:12.877 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.877 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345678901234567890', '$.bigint()');
2025-02-01 03:25:12.877 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345678901234567890" of jsonpath item method .bigint() is invalid for type bigint
2025-02-01 03:25:12.877 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12345678901234567890"', '$.bigint()');
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.boolean()');
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.boolean()');
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .boolean() can only be applied to a boolean, string, or numeric value
2025-02-01 03:25:12.878 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1.23', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23"', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1e1000', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "nan" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "NaN" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "inf" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.boolean()');
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "-inf" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.879 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.boolean()');
2025-02-01 03:25:12.880 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "100" of jsonpath item method .boolean() is invalid for type boolean
2025-02-01 03:25:12.880 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"100"', '$.boolean()');
2025-02-01 03:25:12.884 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .date() can only be applied to a string
2025-02-01 03:25:12.884 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.date()');
2025-02-01 03:25:12.884 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .date() can only be applied to a string
2025-02-01 03:25:12.884 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.date()');
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .date() can only be applied to a string
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.date()');
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .date() can only be applied to a string
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.date()');
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .date() can only be applied to a string
2025-02-01 03:25:12.885 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.date()');
2025-02-01 03:25:12.886 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  date format is not recognized: "bogus"
2025-02-01 03:25:12.886 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.date()');
2025-02-01 03:25:12.887 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  date format is not recognized: "12:34:56"
2025-02-01 03:25:12.887 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56"', '$.date()');
2025-02-01 03:25:12.887 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  date format is not recognized: "12:34:56 +05:30"
2025-02-01 03:25:12.887 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56 +05:30"', '$.date()');
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to date without time zone usage
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.date()');
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "2" of jsonpath input at character 41
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15"', '$.date(2)');
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .decimal() can only be applied to a string or numeric value
2025-02-01 03:25:12.888 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.decimal()');
2025-02-01 03:25:12.889 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .decimal() can only be applied to a string or numeric value
2025-02-01 03:25:12.889 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.decimal()');
2025-02-01 03:25:12.903 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .decimal() can only be applied to a string or numeric value
2025-02-01 03:25:12.903 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.decimal()');
2025-02-01 03:25:12.907 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .decimal() can only be applied to a string or numeric value
2025-02-01 03:25:12.907 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.decimal()');
2025-02-01 03:25:12.907 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint1"
2025-02-01 03:25:12.907 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains (, 1, [1, 2]).
2025-02-01 03:25:12.907 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('', 1);
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2"
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains (1, 1, [1, 2]).
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('1', 1);
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2"
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains ([], null, [1, 2]).
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('[]');
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint2"
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains ({"b": 1}, 1, [1, 2]).
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('{"b": 1}', 1);
2025-02-01 03:25:12.908 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .decimal() is invalid for type numeric
2025-02-01 03:25:12.908 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.decimal()');
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint3"
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains ({"a": 1}, 1, [1, 2]).
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('{"a": 1}', 1);
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  new row for relation "test_jsonb_constraints" violates check constraint "test_jsonb_constraint4"
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Failing row contains ({"a": 10}, 1, [1, 2]).
2025-02-01 03:25:12.908 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  INSERT INTO test_jsonb_constraints VALUES ('{"a": 10}', 1);
2025-02-01 03:25:12.911 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .decimal()
2025-02-01 03:25:12.911 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.decimal()');
2025-02-01 03:25:12.912 UTC client backend[30534] pg_regress/json ERROR:  could not determine row type for result of json_populate_record
2025-02-01 03:25:12.912 UTC client backend[30534] pg_regress/json HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:12.912 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_populate_record(null::record, '{"x": 0, "y": 1}');
2025-02-01 03:25:12.913 UTC client backend[30534] pg_regress/json ERROR:  value for domain j_ordered_pair violates check constraint "j_ordered_pair_check"
2025-02-01 03:25:12.913 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_populate_record(row(1,2)::j_ordered_pair, '{"x": 1, "y": 0}');
2025-02-01 03:25:12.915 UTC client backend[30534] pg_regress/json ERROR:  invalid input syntax for type timestamp: "[100,200,300]"
2025-02-01 03:25:12.915 UTC client backend[30534] 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-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .decimal()
2025-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.decimal()');
2025-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .decimal()
2025-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.decimal()');
2025-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .decimal()
2025-02-01 03:25:12.915 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.decimal()');
2025-02-01 03:25:12.916 UTC client backend[30534] pg_regress/json ERROR:  could not determine row type for result of json_populate_recordset
2025-02-01 03:25:12.916 UTC client backend[30534] pg_regress/json HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:12.916 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_populate_recordset(null::record, '[{"x": 0, "y": 1}]');
2025-02-01 03:25:12.917 UTC client backend[30534] pg_regress/json ERROR:  could not determine row type for result of json_populate_recordset
2025-02-01 03:25:12.917 UTC client backend[30534] pg_regress/json HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:12.917 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_populate_recordset(null::record, '[]');
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json ERROR:  value for domain j_ordered_pair violates check constraint "j_ordered_pair_check"
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_populate_recordset(row(1,2)::j_ordered_pair, '[{"x": 1, "y": 0}]');
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json DETAIL:  Returned row contains 1 attribute, but query expects 2.
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json STATEMENT:  select * from json_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text);
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:12.918 UTC client backend[30534] pg_regress/json DETAIL:  Returned type integer at ordinal position 1, but query expects text.
2025-02-01 03:25:12.918 UTC client backend[30534] 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-02-01 03:25:12.919 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric
2025-02-01 03:25:12.919 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345.678', '$.decimal(6, 2)');
2025-02-01 03:25:12.923 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345.678" of jsonpath item method .decimal() is invalid for type numeric
2025-02-01 03:25:12.923 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345.678', '$.decimal(4, 6)');
2025-02-01 03:25:12.927 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NUMERIC precision 0 must be between 1 and 1000
2025-02-01 03:25:12.927 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345.678', '$.decimal(0, 6)');
2025-02-01 03:25:12.927 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NUMERIC precision 1001 must be between 1 and 1000
2025-02-01 03:25:12.927 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345.678', '$.decimal(1001, 6)');
2025-02-01 03:25:12.937 UTC client backend[30534] pg_regress/json ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:12.937 UTC client backend[30534] pg_regress/json DETAIL:  Returned row contains 3 attributes, but query expects 2.
2025-02-01 03:25:12.937 UTC client backend[30534] 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-02-01 03:25:12.937 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NUMERIC precision -6 must be between 1 and 1000
2025-02-01 03:25:12.937 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1234.5678', '$.decimal(-6, +2)');
2025-02-01 03:25:12.937 UTC autovacuum worker[30604] LOG:  autovacuum: dropping orphan temp table "regression.pg_temp_32.t_gin_test_tbl"
2025-02-01 03:25:12.939 UTC client backend[30534] pg_regress/json ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:12.939 UTC client backend[30534] pg_regress/json DETAIL:  Returned type integer at ordinal position 1, but query expects text.
2025-02-01 03:25:12.939 UTC client backend[30534] pg_regress/json STATEMENT:  select * from json_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text);
2025-02-01 03:25:12.940 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NUMERIC scale -1001 must be between -1000 and 1000
2025-02-01 03:25:12.940 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1234.5678', '$.decimal(6, -1001)');
2025-02-01 03:25:12.940 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.940 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time()'));
2025-02-01 03:25:12.941 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NUMERIC scale 1001 must be between -1000 and 1000
2025-02-01 03:25:12.941 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1234.5678', '$.decimal(6, 1001)');
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date()'));
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.time_tz()'));
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp()'));
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.941 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.timestamp_tz()'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time_tz())'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.time())'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time())'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.time_tz())'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.timestamp_tz())'));
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.942 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.timestamp_tz())'));
2025-02-01 03:25:12.943 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.943 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.time() < $.datetime("HH:MI TZH"))'));
2025-02-01 03:25:12.943 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.943 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.date() < $.datetime("HH:MI TZH"))'));
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI TZH"))'));
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp() < $.datetime("HH:MI"))'));
2025-02-01 03:25:12.945 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  precision of jsonpath item method .decimal() is out of range for type integer
2025-02-01 03:25:12.945 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12.3', '$.decimal(12345678901,1)');
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.945 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI TZH"))'));
2025-02-01 03:25:12.945 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  scale of jsonpath item method .decimal() is out of range for type integer
2025-02-01 03:25:12.945 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12.3', '$.decimal(1,12345678901)');
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp_tz() < $.datetime("HH:MI"))'));
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '12:34'::timetz AS x));
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.date() < $x' PASSING '1234'::int AS x));
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.946 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.timestamp(2) < $.timestamp(3))'));
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .integer() can only be applied to a string or numeric value
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.integer()');
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .integer() can only be applied to a string or numeric value
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.integer()');
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .integer() can only be applied to a string or numeric value
2025-02-01 03:25:12.947 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.integer()');
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .integer() can only be applied to a string or numeric value
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.integer()');
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23"', '$.integer()');
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.integer()');
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1e1000', '$.integer()');
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "nan" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.948 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.integer()');
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "NaN" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.integer()');
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "inf" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.integer()');
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "-inf" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.949 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.integer()');
2025-02-01 03:25:12.950 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345678901" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.950 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('12345678901', '$.integer()');
2025-02-01 03:25:12.950 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "12345678901" of jsonpath item method .integer() is invalid for type integer
2025-02-01 03:25:12.950 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12345678901"', '$.integer()');
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .number() can only be applied to a string or numeric value
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.number()');
2025-02-01 03:25:12.951 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.951 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime())'));
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .number() can only be applied to a string or numeric value
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.number()');
2025-02-01 03:25:12.951 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.951 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.a ? (@.datetime() < $.datetime("HH:MI TZH"))'));
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .number() can only be applied to a string or numeric value
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.number()');
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .number() can only be applied to a string or numeric value
2025-02-01 03:25:12.951 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.number()');
2025-02-01 03:25:12.953 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  argument "1.23aaa" of jsonpath item method .number() is invalid for type numeric
2025-02-01 03:25:12.953 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"1.23aaa"', '$.number()');
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .number()
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"nan"', '$.number()');
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .number()
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"NaN"', '$.number()');
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .number()
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"inf"', '$.number()');
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  NaN or Infinity is not allowed for jsonpath item method .number()
2025-02-01 03:25:12.954 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"-inf"', '$.number()');
2025-02-01 03:25:12.956 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.956 UTC client backend[30549] 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-02-01 03:25:12.957 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value
2025-02-01 03:25:12.957 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.string()');
2025-02-01 03:25:12.959 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value
2025-02-01 03:25:12.959 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.string()');
2025-02-01 03:25:12.959 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .string() can only be applied to a boolean, string, numeric, or datetime value
2025-02-01 03:25:12.959 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.string()');
2025-02-01 03:25:12.960 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.960 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() < $x' PASSING '12:34'::timetz AS x));
2025-02-01 03:25:12.961 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.961 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_QUERY(js, '$.datetime() ? (@ == $x)' PASSING '12:34'::time AS x));
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +5:30"', '$.timestamp().string()');
2025-02-01 03:25:12.962 UTC client backend[30534] pg_regress/json ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.962 UTC client backend[30534] pg_regress/json HINT:  The arguments of json_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.962 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object('{a,b,c}'::text[]);
2025-02-01 03:25:12.962 UTC client backend[30534] pg_regress/json ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.962 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object('{a,b,c}'::text[], '{d,e,f}'::text[]);
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:12.962 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz().string()');
2025-02-01 03:25:12.963 UTC client backend[30534] pg_regress/json ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.963 UTC client backend[30534] pg_regress/json HINT:  The arguments of json_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.963 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object('a', 'b', 'c');
2025-02-01 03:25:12.963 UTC client backend[30534] pg_regress/json ERROR:  null value not allowed for object key
2025-02-01 03:25:12.963 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(NULL, 'a');
2025-02-01 03:25:12.963 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.963 UTC client backend[30549] 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-02-01 03:25:12.963 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.963 UTC client backend[30549] 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-02-01 03:25:12.964 UTC client backend[30534] pg_regress/json ERROR:  argument list must have even number of elements
2025-02-01 03:25:12.964 UTC client backend[30534] pg_regress/json HINT:  The arguments of json_build_object() must consist of alternating keys and values.
2025-02-01 03:25:12.964 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(VARIADIC '{a,b,c}'::text[]);
2025-02-01 03:25:12.965 UTC client backend[30534] pg_regress/json ERROR:  null value not allowed for object key
2025-02-01 03:25:12.965 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(VARIADIC ARRAY[NULL, 'a']::text[]);
2025-02-01 03:25:12.965 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type timestamp: "[100, 200, false]"
2025-02-01 03:25:12.965 UTC client backend[30532] 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-02-01 03:25:12.965 UTC client backend[30532] pg_regress/jsonb ERROR:  domain jsb_int_not_null does not allow null values
2025-02-01 03:25:12.965 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"x": 43.2}') q;
2025-02-01 03:25:12.965 UTC client backend[30532] pg_regress/jsonb ERROR:  domain jsb_int_not_null does not allow null values
2025-02-01 03:25:12.965 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT i FROM jsonb_populate_record(NULL::jsbrec_i_not_null, '{"i": null}') q;
2025-02-01 03:25:12.966 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.966 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ia".
2025-02-01 03:25:12.966 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": 123}') q;
2025-02-01 03:25:12.967 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.967 UTC client backend[30532] pg_regress/jsonb HINT:  See the array element [1] of key "ia".
2025-02-01 03:25:12.967 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], 2]}') q;
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time() can only be applied to a string
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.time()');
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time() can only be applied to a string
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.time()');
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time() can only be applied to a string
2025-02-01 03:25:12.968 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.time()');
2025-02-01 03:25:12.969 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time() can only be applied to a string
2025-02-01 03:25:12.969 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.time()');
2025-02-01 03:25:12.969 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time() can only be applied to a string
2025-02-01 03:25:12.969 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.time()');
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time format is not recognized: "bogus"
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.time()');
2025-02-01 03:25:12.970 UTC client backend[30532] pg_regress/jsonb ERROR:  malformed JSON array
2025-02-01 03:25:12.970 UTC client backend[30532] pg_regress/jsonb DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.970 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia FROM jsonb_populate_record(NULL::jsbrec, '{"ia": [[1], [2, 3]]}') q;
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time format is not recognized: "2023-08-15"
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15"', '$.time()');
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timetz to time without time zone usage
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:12.970 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56 +05:30"', '$.time()');
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ia1".
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia1 FROM jsonb_populate_record(NULL::jsbrec, '{"ia1": 123}') q;
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ia1d".
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": 123}') q;
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb ERROR:  value for domain jsb_int_array_1d violates check constraint "jsb_int_array_1d_check"
2025-02-01 03:25:12.971 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia1d FROM jsonb_populate_record(NULL::jsbrec, '{"ia1d": [1, "2", null, 4]}') q;
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "-" of jsonpath input at character 43
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789"', '$.time(-1)');
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "2.0" of jsonpath input at character 43
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789"', '$.time(2.0)');
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time precision of jsonpath item method .time() is out of range for type integer
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789"', '$.time(12345678901)');
2025-02-01 03:25:12.972 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIME(10) precision reduced to maximum allowed, 6
2025-02-01 03:25:12.972 UTC client backend[30532] pg_regress/jsonb ERROR:  malformed JSON array
2025-02-01 03:25:12.972 UTC client backend[30532] pg_regress/jsonb DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.972 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], [3]]}') q;
2025-02-01 03:25:12.973 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.973 UTC client backend[30532] pg_regress/jsonb HINT:  See the array element [1] of key "ia2".
2025-02-01 03:25:12.973 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia2 FROM jsonb_populate_record(NULL::jsbrec, '{"ia2": [[1, 2], 3, 4]}') q;
2025-02-01 03:25:12.973 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIME(8) precision reduced to maximum allowed, 6
2025-02-01 03:25:12.973 UTC client backend[30532] pg_regress/jsonb ERROR:  value for domain jsb_int_array_2d violates check constraint "jsb_int_array_2d_check"
2025-02-01 03:25:12.973 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ia2d FROM jsonb_populate_record(NULL::jsbrec, '{"ia2d": [[1, "2"], [null, 4]]}') q;
2025-02-01 03:25:12.974 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  functions in index expression must be marked IMMUTABLE
2025-02-01 03:25:12.974 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  CREATE INDEX ON test_jsonb_mutability (JSON_VALUE(js, '$' DEFAULT random()::int ON ERROR));
2025-02-01 03:25:12.975 UTC client backend[30534] pg_regress/json ERROR:  null value not allowed for object key
2025-02-01 03:25:12.975 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(null,2);
2025-02-01 03:25:12.975 UTC client backend[30534] pg_regress/json ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.975 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(r,2) FROM (SELECT 1 AS a, 2 AS b) r;
2025-02-01 03:25:12.976 UTC client backend[30534] pg_regress/json ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.976 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object(json '{"a":1,"b":2}', 3);
2025-02-01 03:25:12.976 UTC client backend[30534] pg_regress/json ERROR:  key value must be scalar, not array, composite, or json
2025-02-01 03:25:12.976 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_build_object('{1,2,3}'::int[], 3);
2025-02-01 03:25:12.977 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time_tz() can only be applied to a string
2025-02-01 03:25:12.977 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.time_tz()');
2025-02-01 03:25:12.978 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time_tz() can only be applied to a string
2025-02-01 03:25:12.978 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.time_tz()');
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time_tz() can only be applied to a string
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.time_tz()');
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time_tz() can only be applied to a string
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.time_tz()');
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .time_tz() can only be applied to a string
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.time_tz()');
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time_tz format is not recognized: "bogus"
2025-02-01 03:25:12.979 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.time_tz()');
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb ERROR:  malformed JSON array
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.980 UTC client backend[30532] 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-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ta".
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": 123}') q;
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb HINT:  See the array element [1] of key "ta".
2025-02-01 03:25:12.980 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ta FROM jsonb_populate_record(NULL::jsbrec, '{"ta": [[1, 2, 3], {"k": "v"}]}') q;
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time_tz format is not recognized: "2023-08-15"
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15"', '$.time_tz()');
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time_tz format is not recognized: "2023-08-15 12:34:56"
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56"', '$.time_tz()');
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  DEFAULT expression must not return a set at character 50
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(js, '$'  RETURNING int DEFAULT ret_setint() ON ERROR) FROM test_jsonb_mutability;
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "-" of jsonpath input at character 50
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(-1)');
2025-02-01 03:25:12.981 UTC client backend[30532] pg_regress/jsonb ERROR:  value too long for type character(10)
2025-02-01 03:25:12.981 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT c FROM jsonb_populate_record(NULL::jsbrec, '{"c": "aaaaaaaaaaaaa"}') q;
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "2.0" of jsonpath input at character 50
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(2.0)');
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  DEFAULT expression must not contain column references at character 50
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(js, '$'  RETURNING int DEFAULT b + 1 ON ERROR) FROM test_jsonb_mutability;
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time precision of jsonpath item method .time_tz() is out of range for type integer
2025-02-01 03:25:12.981 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56.789 +05:30"', '$.time_tz(12345678901)');
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50
2025-02-01 03:25:12.981 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(js, '$'  RETURNING int DEFAULT sum(1) over() ON ERROR) FROM test_jsonb_mutability;
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ca".
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": 123}') q;
2025-02-01 03:25:12.982 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 50
2025-02-01 03:25:12.982 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(js, '$'  RETURNING int DEFAULT (SELECT 1) ON ERROR) FROM test_jsonb_mutability;
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb ERROR:  value too long for type character(10)
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": ["aaaaaaaaaaaaaaaa"]}') q;
2025-02-01 03:25:12.982 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIME(10) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb HINT:  See the array element [1] of key "ca".
2025-02-01 03:25:12.982 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT ca FROM jsonb_populate_record(NULL::jsbrec, '{"ca": [[1, 2, 3], {"k": "v"}]}') q;
2025-02-01 03:25:12.983 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIME(8) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:25:12.983 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp() can only be applied to a string
2025-02-01 03:25:12.983 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.timestamp()');
2025-02-01 03:25:12.983 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp() can only be applied to a string
2025-02-01 03:25:12.983 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.timestamp()');
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp() can only be applied to a string
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.timestamp()');
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp() can only be applied to a string
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.timestamp()');
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp() can only be applied to a string
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.timestamp()');
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp format is not recognized: "bogus"
2025-02-01 03:25:12.984 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.timestamp()');
2025-02-01 03:25:12.986 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp format is not recognized: "12:34:56"
2025-02-01 03:25:12.986 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56"', '$.timestamp()');
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp format is not recognized: "12:34:56 +05:30"
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56 +05:30"', '$.timestamp()');
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "-" of jsonpath input at character 54
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(-1)');
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "2.0" of jsonpath input at character 54
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(2.0)');
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time precision of jsonpath item method .timestamp() is out of range for type integer
2025-02-01 03:25:12.988 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789"', '$.timestamp(12345678901)');
2025-02-01 03:25:12.989 UTC client backend[30534] pg_regress/json ERROR:  null value not allowed for object key
2025-02-01 03:25:12.989 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object_agg(name, type) FROM foo;
2025-02-01 03:25:12.990 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.990 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "jsa".
2025-02-01 03:25:12.990 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsa FROM jsonb_populate_record(NULL::jsbrec, '{"jsa": 123}') q;
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json ERROR:  array must have even number of elements
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object('{a,b,c}');
2025-02-01 03:25:12.991 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIMESTAMP(10) precision reduced to maximum allowed, 6
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json ERROR:  array must have two columns
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object('{{a},{b}}');
2025-02-01 03:25:12.991 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIMESTAMP(8) precision reduced to maximum allowed, 6
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json ERROR:  array must have two columns
2025-02-01 03:25:12.991 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object('{{a,b,c},{b,c,d}}');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp_tz() can only be applied to a string
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('null', '$.timestamp_tz()');
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json ERROR:  wrong number of array subscripts
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json STATEMENT:  SELECT json_object('{{{a,b},{c,d}},{{b,c},{d,e}}}');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp_tz() can only be applied to a string
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('true', '$.timestamp_tz()');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp_tz() can only be applied to a string
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('1', '$.timestamp_tz()');
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json ERROR:  wrong number of array subscripts
2025-02-01 03:25:12.992 UTC client backend[30534] 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-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json ERROR:  mismatched array dimensions
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json STATEMENT:  select json_object('{a,b,c,"d e f",g}','{1,2,3,"a b c"}');
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json ERROR:  mismatched array dimensions
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json STATEMENT:  select json_object('{a,b,c,"d e f"}','{1,2,3,"a b c",g}');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp_tz() can only be applied to a string
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('[]', 'strict $.timestamp_tz()');
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json ERROR:  null value not allowed for object key
2025-02-01 03:25:12.992 UTC client backend[30534] pg_regress/json STATEMENT:  select json_object('{a,b,NULL,"d e f"}','{1,2,3,"a b c"}');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  jsonpath item method .timestamp_tz() can only be applied to a string
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('{}', '$.timestamp_tz()');
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp_tz format is not recognized: "bogus"
2025-02-01 03:25:12.992 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"bogus"', '$.timestamp_tz()');
2025-02-01 03:25:12.993 UTC client backend[30534] pg_regress/json ERROR:  duplicate JSON object key value: "0"
2025-02-01 03:25:12.993 UTC client backend[30534] pg_regress/json STATEMENT:  select json_object_agg_unique(mod(i,100), i) from generate_series(0, 199) i;
2025-02-01 03:25:12.997 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON EMPTY expression (DEFAULT) to the RETURNING type
2025-02-01 03:25:12.997 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  value for domain queryfuncs_test_domain violates check constraint "queryfuncs_test_domain_check"
2025-02-01 03:25:12.997 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '{"d1": "H"}', '$.a2' RETURNING queryfuncs_test_domain DEFAULT 'foo'::queryfuncs_test_domain ON EMPTY);
2025-02-01 03:25:12.997 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.997 UTC client backend[30534] pg_regress/json HINT:  See the value of key "ia".
2025-02-01 03:25:12.997 UTC client backend[30534] pg_regress/json STATEMENT:  select * from json_to_record('{"ia": 123}') as x(ia _int4);
2025-02-01 03:25:12.998 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from date to timestamptz without time zone usage
2025-02-01 03:25:12.998 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:12.998 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15"', '$.timestamp_tz()');
2025-02-01 03:25:12.998 UTC client backend[30534] pg_regress/json ERROR:  expected JSON array
2025-02-01 03:25:12.998 UTC client backend[30534] pg_regress/json HINT:  See the array element [1] of key "ia".
2025-02-01 03:25:12.998 UTC client backend[30534] pg_regress/json STATEMENT:  select * from json_to_record('{"ia": [[1], 2]}') as x(ia _int4);
2025-02-01 03:25:12.998 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp_tz format is not recognized: "12:34:56"
2025-02-01 03:25:12.998 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56"', '$.timestamp_tz()');
2025-02-01 03:25:12.991 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot call populate_composite on a scalar
2025-02-01 03:25:12.991 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": 123}') q;
2025-02-01 03:25:12.998 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55
2025-02-01 03:25:12.998 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a'  RETURNING int DEFAULT (SELECT '"1"')::jsonb ON ERROR);
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  timestamp_tz format is not recognized: "12:34:56 +05:30"
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56 +05:30"', '$.timestamp_tz()');
2025-02-01 03:25:12.999 UTC client backend[30534] pg_regress/json ERROR:  malformed JSON array
2025-02-01 03:25:12.999 UTC client backend[30534] pg_regress/json DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:12.999 UTC client backend[30534] pg_regress/json STATEMENT:  select * from json_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4);
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "-" of jsonpath input at character 61
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(-1)');
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  syntax error at or near "2.0" of jsonpath input at character 61
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(2.0)');
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 73
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a' RETURNING queryfuncs_test_domain DEFAULT (select '"1"')::queryfuncs_test_domain ON ERROR);
2025-02-01 03:25:12.999 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot call populate_composite on an array
2025-02-01 03:25:12.999 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT rec FROM jsonb_populate_record(NULL::jsbrec, '{"rec": [1, 2]}') q;
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  time precision of jsonpath item method .timestamp_tz() is out of range for type integer
2025-02-01 03:25:12.999 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56.789 +05:30"', '$.timestamp_tz(12345678901)');
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 55
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a'  RETURNING int DEFAULT (SELECT 1)::oid::int ON ERROR);
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57
2025-02-01 03:25:12.999 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a'  RETURNING int[] DEFAULT (SELECT '{1}')::oid[]::int[] ON ERROR);
2025-02-01 03:25:12.999 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:12.999 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "reca".
2025-02-01 03:25:12.999 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": 123}') q;
2025-02-01 03:25:13.000 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 57
2025-02-01 03:25:13.000 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a'  RETURNING int[] DEFAULT (SELECT '{1}')::text COLLATE "C" ON ERROR);
2025-02-01 03:25:13.000 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot call populate_composite on a scalar
2025-02-01 03:25:13.000 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT reca FROM jsonb_populate_record(NULL::jsbrec, '{"reca": [1, 2]}') q;
2025-02-01 03:25:13.002 UTC client backend[30532] pg_regress/jsonb ERROR:  value too long for type character(2)
2025-02-01 03:25:13.002 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_record(NULL::jsb_char2, '{"a": "aaa"}') q;
2025-02-01 03:25:13.003 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:13.003 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "a".
2025-02-01 03:25:13.003 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_record(NULL::jsb_ia, '{"a": 43.2}') q;
2025-02-01 03:25:13.004 UTC client backend[30532] pg_regress/jsonb ERROR:  malformed JSON array
2025-02-01 03:25:13.004 UTC client backend[30532] pg_regress/jsonb DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:13.004 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_record(NULL::jsb_ia2, '{"a": [[1], [2, 3]]}') q;
2025-02-01 03:25:13.004 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIMESTAMP(10) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:25:13.004 UTC client backend[30546] pg_regress/jsonb_jsonpath WARNING:  TIMESTAMP(8) WITH TIME ZONE precision reduced to maximum allowed, 6
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to time without time zone usage
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()');
2025-02-01 03:25:13.005 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  can only specify a constant, non-aggregate function, or operator expression for DEFAULT at character 62
2025-02-01 03:25:13.005 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY('"a"', '$.a'  RETURNING someparent DEFAULT (SELECT '(1)')::somechild::someparent ON ERROR);
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34:56"', '$.time_tz()');
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.005 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()');
2025-02-01 03:25:13.006 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.006 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.006 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz()');
2025-02-01 03:25:13.006 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  input string is too short for datetime format
2025-02-01 03:25:13.006 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy HH24:MI TZH")');
2025-02-01 03:25:13.007 UTC client backend[30532] pg_regress/jsonb ERROR:  domain jsb_i_not_null does not allow null values
2025-02-01 03:25:13.007 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_record(NULL::jsb_i_not_null_rec, '{"a": null}') q;
2025-02-01 03:25:13.008 UTC client backend[30532] pg_regress/jsonb ERROR:  value for domain jsb_i_gt_1 violates check constraint "jsb_i_gt_1_check"
2025-02-01 03:25:13.008 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_record(NULL::jsb_i_gt_1_rec, '{"a": 1}') q;
2025-02-01 03:25:13.008 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  input string is too short for datetime format
2025-02-01 03:25:13.008 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34"', '$.datetime("HH24:MI TZH")');
2025-02-01 03:25:13.009 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to time without time zone usage
2025-02-01 03:25:13.009 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.009 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()');
2025-02-01 03:25:13.010 UTC client backend[30532] pg_regress/jsonb ERROR:  could not determine row type for result of jsonb_populate_record
2025-02-01 03:25:13.010 UTC client backend[30532] pg_regress/jsonb HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:13.010 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_populate_record(null::record, '{"x": 0, "y": 1}');
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()');
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.010 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56"', '$.timestamp_tz()');
2025-02-01 03:25:13.011 UTC client backend[30532] pg_regress/jsonb ERROR:  value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check"
2025-02-01 03:25:13.011 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_populate_record(row(1,2)::jb_ordered_pair, '{"x": 1, "y": 0}');
2025-02-01 03:25:13.012 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  input string is too short for datetime format
2025-02-01 03:25:13.012 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"10-03-2017 12:34"', '$.datetime("dd-mm-yyyy HH24:MI TZH")');
2025-02-01 03:25:13.014 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  input string is too short for datetime format
2025-02-01 03:25:13.014 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"12:34"', '$.datetime("HH24:MI TZH")');
2025-02-01 03:25:13.015 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to time without time zone usage
2025-02-01 03:25:13.015 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.015 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.time()');
2025-02-01 03:25:13.016 UTC client backend[30532] pg_regress/jsonb ERROR:  invalid input syntax for type timestamp: "[100, 200, 300]"
2025-02-01 03:25:13.016 UTC client backend[30532] 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-02-01 03:25:13.016 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.016 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.016 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2023-08-15 12:34:56 +05:30"', '$.timestamp()');
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb ERROR:  could not determine row type for result of jsonb_populate_recordset
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_populate_recordset(null::record, '[{"x": 0, "y": 1}]');
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb ERROR:  could not determine row type for result of jsonb_populate_recordset
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb HINT:  Provide a non-null record argument, or call the function in the FROM clause using a column definition list.
2025-02-01 03:25:13.017 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_populate_recordset(null::record, '[]');
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb ERROR:  value for domain jb_ordered_pair violates check constraint "jb_ordered_pair_check"
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb STATEMENT:  SELECT jsonb_populate_recordset(row(1,2)::jb_ordered_pair, '[{"x": 1, "y": 0}]');
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb DETAIL:  Returned row contains 1 attribute, but query expects 2.
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_recordset(row(0::int),'[{"a":"1","b":"2"},{"a":"3"}]') q (a text, b text);
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:13.019 UTC client backend[30532] pg_regress/jsonb DETAIL:  Returned type integer at ordinal position 1, but query expects text.
2025-02-01 03:25:13.019 UTC client backend[30532] 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-02-01 03:25:13.020 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  syntax error at or near " " of jsonpath input
2025-02-01 03:25:13.020 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '{"a": 123}', 'error' || ' ' || 'error');
2025-02-01 03:25:13.021 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  datetime format is not recognized: "2017-03-10t12:34:56+3:10"
2025-02-01 03:25:13.021 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use a datetime template argument to specify the input data format.
2025-02-01 03:25:13.021 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2017-03-10t12:34:56+3:10"', '$.datetime()');
2025-02-01 03:25:13.021 UTC client backend[30532] pg_regress/jsonb ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:13.021 UTC client backend[30532] pg_regress/jsonb DETAIL:  Returned row contains 3 attributes, but query expects 2.
2025-02-01 03:25:13.021 UTC client backend[30532] 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-02-01 03:25:13.021 UTC client backend[30532] pg_regress/jsonb ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:13.021 UTC client backend[30532] pg_regress/jsonb DETAIL:  Returned type integer at ordinal position 1, but query expects text.
2025-02-01 03:25:13.021 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_populate_recordset(row(1000000000::int,50::int),'[{"b":"2"},{"a":"3"}]') q (a text, b text);
2025-02-01 03:25:13.022 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  datetime format is not recognized: "2017-03-10t12:34:56.789+3:10"
2025-02-01 03:25:13.022 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use a datetime template argument to specify the input data format.
2025-02-01 03:25:13.022 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query('"2017-03-10t12:34:56.789+3:10"', '$.datetime()');
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb HINT:  See the value of key "ia".
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_to_record('{"ia": 123}') as x(ia _int4);
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb ERROR:  expected JSON array
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb HINT:  See the array element [1] of key "ia".
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_to_record('{"ia": [[1], 2]}') as x(ia _int4);
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb ERROR:  malformed JSON array
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb DETAIL:  Multidimensional arrays must have sub-arrays with matching dimensions.
2025-02-01 03:25:13.023 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select * from jsonb_to_record('{"ia": [[1], [2, 3]]}') as x(ia _int4);
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from date to timestamptz without time zone usage
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "12:34:56", "01:02:03+04", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].datetime() ? (@ == "10.03.2017".datetime("dd.mm.yyyy"))');
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from date to timestamptz without time zone usage
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.025 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "12:34:56", "01:02:03+04", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].datetime() ? (@ >= "10.03.2017".datetime("dd.mm.yyyy"))');
2025-02-01 03:25:13.026 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from date to timestamptz without time zone usage
2025-02-01 03:25:13.026 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.026 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "12:34:56", "01:02:03+04", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].datetime() ? (@ <  "10.03.2017".datetime("dd.mm.yyyy"))');
2025-02-01 03:25:13.028 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not find jsonpath variable "xyz"
2025-02-01 03:25:13.028 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb 'null', '$xyz' PASSING 1 AS xy);
2025-02-01 03:25:13.028 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not find jsonpath variable "xy"
2025-02-01 03:25:13.028 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb 'null', '$xy' PASSING 1 AS xyz);
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to date without time zone usage
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].date() ? (@ == "2017-03-10".date())');
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to date without time zone usage
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].date() ? (@ >= "2017-03-10".date())');
2025-02-01 03:25:13.029 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not find jsonpath variable "Xyz"
2025-02-01 03:25:13.029 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb 'null', '$Xyz' PASSING 1 AS Xyz);
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to date without time zone usage
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.029 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10", "2017-03-11", "2017-03-09", "2017-03-10 00:00:00", "2017-03-10 12:34:56", "2017-03-10 01:02:03+04", "2017-03-10 03:00:00+03"]',
		'$[*].date() ? (@ <  "2017-03-10".date())');
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid ON ERROR behavior at character 35
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Only ERROR, TRUE, FALSE, or UNKNOWN is allowed in ON ERROR for JSON_EXISTS().
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_EXISTS(jsonb '1', '$' DEFAULT 1 ON ERROR);
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid ON ERROR behavior at character 34
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Only ERROR, NULL, or DEFAULT expression is allowed in ON ERROR for JSON_VALUE().
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1', '$' EMPTY ON ERROR);
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  invalid ON ERROR behavior at character 34
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  Only ERROR, NULL, EMPTY ARRAY, EMPTY OBJECT, or DEFAULT expression is allowed in ON ERROR for JSON_QUERY().
2025-02-01 03:25:13.030 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '1', '$' TRUE ON ERROR);
2025-02-01 03:25:13.030 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.030 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.030 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].datetime() ? (@ == "12:35".datetime("HH24:MI"))');
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].datetime() ? (@ >= "12:35".datetime("HH24:MI"))');
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.031 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].datetime() ? (@ <  "12:35".datetime("HH24:MI"))');
2025-02-01 03:25:13.034 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timetz to time without time zone usage
2025-02-01 03:25:13.034 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.034 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].time() ? (@ == "12:35:00".time())');
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timetz to time without time zone usage
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].time() ? (@ >= "12:35:00".time())');
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timetz to time without time zone usage
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00", "12:35:00", "12:36:00", "12:35:00+00", "12:35:00+01", "13:35:00+01", "2017-03-10 12:35:00", "2017-03-10 12:35:00+01"]',
		'$[*].time() ? (@ <  "12:35:00".time())');
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timetz to time without time zone usage
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.035 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00.123", "12:35:00.123", "12:36:00.1123", "12:35:00.1123+00", "12:35:00.123+01", "13:35:00.123+01", "2017-03-10 12:35:00.1", "2017-03-10 12:35:00.123+01"]',
		'$[*].time(2) ? (@ >= "12:35:00.123".time(2))');
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].datetime() ? (@ == "12:35 +1".datetime("HH24:MI TZH"))');
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.037 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].datetime() ? (@ >= "12:35 +1".datetime("HH24:MI TZH"))');
2025-02-01 03:25:13.038 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.038 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.038 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10", "2017-03-10 12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].datetime() ? (@ <  "12:35 +1".datetime("HH24:MI TZH"))');
2025-02-01 03:25:13.039 UTC client backend[30534] pg_regress/json ERROR:  wrong flag in flag array: ""
2025-02-01 03:25:13.039 UTC client backend[30534] pg_regress/json HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.039 UTC client backend[30534] 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-02-01 03:25:13.040 UTC client backend[30534] pg_regress/json ERROR:  wrong flag type, only arrays and scalars are allowed
2025-02-01 03:25:13.040 UTC client backend[30534] 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-02-01 03:25:13.040 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(2)
2025-02-01 03:25:13.040 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR);
2025-02-01 03:25:13.040 UTC client backend[30534] pg_regress/json ERROR:  flag array element is not a string
2025-02-01 03:25:13.040 UTC client backend[30534] pg_regress/json HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.040 UTC client backend[30534] 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-02-01 03:25:13.040 UTC client backend[30534] pg_regress/json ERROR:  flag array element is not a string
2025-02-01 03:25:13.040 UTC client backend[30534] pg_regress/json HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.040 UTC client backend[30534] 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-02-01 03:25:13.041 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(2)
2025-02-01 03:25:13.041 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_QUERY(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR);
2025-02-01 03:25:13.041 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(2)
2025-02-01 03:25:13.041 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2 ERROR ON ERROR);
2025-02-01 03:25:13.042 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  value too long for type character(2)
2025-02-01 03:25:13.042 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '123', '$' RETURNING queryfuncs_char2_chk ERROR ON ERROR);
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].time_tz() ? (@ == "12:35:00 +1".time_tz())');
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].time_tz() ? (@ >= "12:35:00 +1".time_tz())');
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00+01", "12:35:00+01", "12:36:00+01", "12:35:00+02", "12:35:00-02", "10:35:00", "11:35:00", "12:35:00", "2017-03-10 12:35:00 +1"]',
		'$[*].time_tz() ? (@ <  "12:35:00 +1".time_tz())');
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from time to timetz without time zone usage
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.047 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["12:34:00.123+01", "12:35:00.123+01", "12:36:00.1123+01", "12:35:00.1123+02", "12:35:00.123-02", "10:35:00.123", "11:35:00.1", "12:35:00.123", "2017-03-10 12:35:00.123 +1"]',
		'$[*].time_tz(2) ? (@ >= "12:35:00.123 +1".time_tz(2))');
2025-02-01 03:25:13.048 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.048 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.048 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ == "10.03.2017 12:35".datetime("dd.mm.yyyy HH24:MI"))');
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ >= "10.03.2017 12:35".datetime("dd.mm.yyyy HH24:MI"))');
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.049 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ < "10.03.2017 12:35".datetime("dd.mm.yyyy HH24:MI"))');
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp() ? (@ == "2017-03-10 12:35:00".timestamp())');
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp() ? (@ >= "2017-03-10 12:35:00".timestamp())');
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00", "2017-03-10 12:35:00", "2017-03-10 12:36:00", "2017-03-10 12:35:00+01", "2017-03-10 13:35:00+01", "2017-03-10 12:35:00-01", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp() ? (@ < "2017-03-10 12:35:00".timestamp())');
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamptz to timestamp without time zone usage
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.051 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00.123", "2017-03-10 12:35:00.123", "2017-03-10 12:36:00.1123", "2017-03-10 12:35:00.1123+01", "2017-03-10 13:35:00.123+01", "2017-03-10 12:35:00.1-01", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp(2) ? (@ >= "2017-03-10 12:35:00.123".timestamp(2))');
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ == "10.03.2017 12:35 +1".datetime("dd.mm.yyyy HH24:MI TZH"))');
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ >= "10.03.2017 12:35 +1".datetime("dd.mm.yyyy HH24:MI TZH"))');
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.054 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11", "12:34:56", "12:34:56+01"]',
		'$[*].datetime() ? (@ < "10.03.2017 12:35 +1".datetime("dd.mm.yyyy HH24:MI TZH"))');
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  bit string too long for type bit varying(3)
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3  DEFAULT '111111' ON ERROR);
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  could not coerce ON ERROR expression (DEFAULT) to the RETURNING type
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs DETAIL:  value for domain queryfuncs_d_varbit3 violates check constraint "queryfuncs_d_varbit3_check"
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1234', '$' RETURNING queryfuncs_d_varbit3  DEFAULT '01' ON ERROR);
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  bit string length 3 does not match type bit(2)
2025-02-01 03:25:13.055 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '"111"', '$'  RETURNING bit(2) ERROR ON ERROR);
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp_tz() ? (@ == "2017-03-10 12:35:00 +1".timestamp_tz())');
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp_tz() ? (@ >= "2017-03-10 12:35:00 +1".timestamp_tz())');
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00+01", "2017-03-10 12:35:00+01", "2017-03-10 12:36:00+01", "2017-03-10 12:35:00+02", "2017-03-10 12:35:00-02", "2017-03-10 10:35:00", "2017-03-10 11:35:00", "2017-03-10 12:35:00", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp_tz() ? (@ < "2017-03-10 12:35:00 +1".timestamp_tz())');
2025-02-01 03:25:13.057 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  cannot cast behavior expression of type integer to bit at character 63
2025-02-01 03:25:13.057 UTC client backend[30549] pg_regress/sqljson_queryfuncs HINT:  You will need to explicitly cast the expression to type bit.
2025-02-01 03:25:13.057 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '1234', '$' RETURNING bit(3)  DEFAULT 1 ON ERROR);
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  cannot convert value from timestamp to timestamptz without time zone usage
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath HINT:  Use *_tz() function for time zone support.
2025-02-01 03:25:13.057 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  select jsonb_path_query(
		'["2017-03-10 12:34:00.123+01", "2017-03-10 12:35:00.123+01", "2017-03-10 12:36:00.1123+01", "2017-03-10 12:35:00.1123+02", "2017-03-10 12:35:00.123-02", "2017-03-10 10:35:00.123", "2017-03-10 11:35:00.1", "2017-03-10 12:35:00.123", "2017-03-10", "2017-03-11"]',
		'$[*].timestamp_tz(2) ? (@ >= "2017-03-10 12:35:00.123 +1".timestamp_tz(2))');
2025-02-01 03:25:13.058 UTC client backend[30549] pg_regress/sqljson_queryfuncs ERROR:  bit string length 4 does not match type bit(3)
2025-02-01 03:25:13.058 UTC client backend[30549] pg_regress/sqljson_queryfuncs STATEMENT:  SELECT JSON_VALUE(jsonb '"111"', '$.a'  RETURNING bit(3) DEFAULT '1111' ON EMPTY);
2025-02-01 03:25:13.071 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  could not find jsonpath variable "undefined_var"
2025-02-01 03:25:13.071 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_query('[{"a": 1}]', '$undefined_var');
2025-02-01 03:25:13.071 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  JSON object does not contain key "a"
2025-02-01 03:25:13.071 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_query_array('[{"a": 1}, {"a": 2}, {}]', 'strict $[*].a');
2025-02-01 03:25:13.072 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  JSON object does not contain key "a"
2025-02-01 03:25:13.072 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_query_first('[{"a": 1}, {"a": 2}, {}]', 'strict $[*].a');
2025-02-01 03:25:13.073 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  could not find jsonpath variable "undefined_var"
2025-02-01 03:25:13.073 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_query_first('[{"a": 1}]', '$undefined_var');
2025-02-01 03:25:13.074 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  could not find jsonpath variable "undefined_var"
2025-02-01 03:25:13.074 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_exists('[{"a": 1}]', '$undefined_var');
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('1', '$', silent => false);
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('"a"', '$', silent => false);
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('{}', '$', silent => false);
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('[true]', '$', silent => false);
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('{}', 'lax $.a', silent => false);
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  JSON object does not contain key "a"
2025-02-01 03:25:13.075 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('{}', 'strict $.a', silent => false);
2025-02-01 03:25:13.076 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  single boolean result is expected
2025-02-01 03:25:13.076 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('[true, true]', '$[*]', silent => false);
2025-02-01 03:25:13.076 UTC client backend[30546] pg_regress/jsonb_jsonpath ERROR:  could not find jsonpath variable "undefined_var"
2025-02-01 03:25:13.076 UTC client backend[30546] pg_regress/jsonb_jsonpath STATEMENT:  SELECT jsonb_path_match('[{"a": 1}]', '$undefined_var');
2025-02-01 03:25:13.227 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 2 is null
2025-02-01 03:25:13.227 UTC client backend[30532] 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-02-01 03:25:13.228 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 2 is null
2025-02-01 03:25:13.228 UTC client backend[30532] 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-02-01 03:25:13.229 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 2 is not an integer: "-1e"
2025-02-01 03:25:13.229 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '{"n":null, "a":1, "b":[1,2], "c":{"1":2}, "d":{"1":[2,3]}}'::jsonb #- '{b,-1e}';
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot delete from scalar
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"a"'::jsonb - 'a';
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot delete from scalar
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"a"'::jsonb - 1;
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot delete from object using integer index
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '{}'::jsonb -  1;
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot delete path in scalar
2025-02-01 03:25:13.230 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"a"'::jsonb #- '{a}';
2025-02-01 03:25:13.231 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot set path in scalar
2025-02-01 03:25:13.231 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set('"a"','{a}','"b"');
2025-02-01 03:25:13.233 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 2 is not an integer: "non_integer"
2025-02-01 03:25:13.233 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set('{"a": [1, 2, 3]}', '{a, non_integer}', '"new_value"');
2025-02-01 03:25:13.233 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 3 is not an integer: "non_integer"
2025-02-01 03:25:13.233 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, non_integer}', '"new_value"');
2025-02-01 03:25:13.234 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 3 is null
2025-02-01 03:25:13.234 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set('{"a": {"b": [1, 2, 3]}}', '{a, b, NULL}', '"new_value"');
2025-02-01 03:25:13.234 UTC client backend[30532] pg_regress/jsonb ERROR:  null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception"
2025-02-01 03:25:13.234 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, null);
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb ERROR:  null_value_treatment must be "delete_key", "return_target", "use_json_null", or "raise_exception"
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, true, 'no_such_treatment');
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb ERROR:  JSON value must not be null
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb DETAIL:  Exception was raised because null_value_treatment is "raise_exception".
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb HINT:  To avoid, either change the null_value_treatment argument or ensure that an SQL NULL is not passed.
2025-02-01 03:25:13.235 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_set_lax('{"a":1,"b":2}', '{b}', null, null_value_treatment => 'raise_exception') as raise_exception;
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb HINT:  Try using the function jsonb_set to replace key value.
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"');
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb HINT:  Try using the function jsonb_set to replace key value.
2025-02-01 03:25:13.239 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_insert('{"a": {"b": "value"}}', '{a, b}', '"new_value"', true);
2025-02-01 03:25:13.241 UTC client backend[30532] pg_regress/jsonb ERROR:  subscript type numeric is not supported at character 34
2025-02-01 03:25:13.241 UTC client backend[30532] pg_regress/jsonb HINT:  jsonb subscript must be coercible to either integer or text.
2025-02-01 03:25:13.241 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('[1, "2", null]'::jsonb)[1.0];
2025-02-01 03:25:13.243 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript does not support slices at character 32
2025-02-01 03:25:13.243 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('{"a": 1}'::jsonb)['a':'b'];
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript does not support slices at character 36
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('[1, "2", null]'::jsonb)[1:2];
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript does not support slices at character 35
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('[1, "2", null]'::jsonb)[:2];
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript does not support slices at character 34
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('[1, "2", null]'::jsonb)[1:];
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript does not support slices
2025-02-01 03:25:13.247 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select ('[1, "2", null]'::jsonb)[:];
2025-02-01 03:25:13.256 UTC client backend[30532] pg_regress/jsonb ERROR:  jsonb subscript in assignment must not be null
2025-02-01 03:25:13.256 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json[NULL] = '1';
2025-02-01 03:25:13.259 UTC client backend[30532] pg_regress/jsonb ERROR:  path element at position 1 is out of range: -8
2025-02-01 03:25:13.259 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json[-8] = '1';
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json['a']['b'] = '1';
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.281 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json['a']['b']['c'] = '1';
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json['a'][0] = '1';
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json['a'][0]['c'] = '1';
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json['a'][0][0] = '1';
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json[0] = '1';
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot replace existing key
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb DETAIL:  The path assumes key is a composite object, but it is a scalar value.
2025-02-01 03:25:13.282 UTC client backend[30532] pg_regress/jsonb STATEMENT:  update test_jsonb_subscript set test_json[0][0] = '1';
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb ERROR:  wrong flag in flag array: ""
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::jsonb, '""');
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb ERROR:  wrong flag type, only arrays and scalars are allowed
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::jsonb, '{}');
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb ERROR:  flag array element is not a string
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::jsonb, 'null');
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb ERROR:  flag array element is not a string
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb HINT:  Possible values are: "string", "numeric", "boolean", "key", and "all".
2025-02-01 03:25:13.303 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select jsonb_to_tsvector('english', '{"a": "aaa in bbb", "b": 123, "c": 456, "d": true, "f": false, "g": null}'::jsonb, '["all", null]');
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb array to type boolean
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '[]'::jsonb::bool;
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb array to type double precision
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '[1.0]'::jsonb::float;
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb array to type real
2025-02-01 03:25:13.306 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '[1.0]'::jsonb::float4;
2025-02-01 03:25:13.311 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb string to type smallint
2025-02-01 03:25:13.311 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"hello"'::jsonb::int2;
2025-02-01 03:25:13.311 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb string to type integer
2025-02-01 03:25:13.311 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"hello"'::jsonb::int4;
2025-02-01 03:25:13.312 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb string to type bigint
2025-02-01 03:25:13.312 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '"hello"'::jsonb::int8;
2025-02-01 03:25:13.312 UTC client backend[30532] pg_regress/jsonb ERROR:  cannot cast jsonb object to type numeric
2025-02-01 03:25:13.312 UTC client backend[30532] pg_regress/jsonb STATEMENT:  select '{}'::jsonb::numeric;
2025-02-01 03:25:13.474 UTC client backend[30766] pg_regress/with ERROR:  could not implement recursive UNION
2025-02-01 03:25:13.474 UTC client backend[30766] pg_regress/with DETAIL:  All column datatypes must be hashable.
2025-02-01 03:25:13.474 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE t(n) AS (
	    VALUES ('01'::varbit)
	UNION
	    SELECT n || '10'::varbit FROM t WHERE n < '100'::varbit
	)
	SELECT n FROM t;
2025-02-01 03:25:13.487 UTC client backend[30766] pg_regress/with ERROR:  operator does not exist: text + integer at character 63
2025-02-01 03:25:13.487 UTC client backend[30766] pg_regress/with HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.487 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE t(n) AS (
	    SELECT '7'
	UNION ALL
	    SELECT n+1 FROM t WHERE n < 10
	)
	SELECT n, pg_typeof(n) FROM t;
2025-02-01 03:25:13.508 UTC client backend[30772] pg_regress/domain ERROR:  cannot drop type domaindroptest because other objects depend on it
2025-02-01 03:25:13.508 UTC client backend[30772] pg_regress/domain DETAIL:  type dependenttypetest depends on type domaindroptest
2025-02-01 03:25:13.508 UTC client backend[30772] pg_regress/domain HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:13.508 UTC client backend[30772] pg_regress/domain STATEMENT:  drop domain domaindroptest;
2025-02-01 03:25:13.509 UTC client backend[30772] pg_regress/domain ERROR:  type "domaindroptest" does not exist
2025-02-01 03:25:13.509 UTC client backend[30772] pg_regress/domain STATEMENT:  drop domain domaindroptest cascade;
2025-02-01 03:25:13.510 UTC client backend[30769] pg_regress/plancache ERROR:  relation "pcachetest" does not exist at character 35
2025-02-01 03:25:13.510 UTC client backend[30769] pg_regress/plancache STATEMENT:  EXECUTE prepstmt;
2025-02-01 03:25:13.510 UTC client backend[30769] pg_regress/plancache ERROR:  relation "pcachetest" does not exist at character 44
2025-02-01 03:25:13.510 UTC client backend[30769] pg_regress/plancache STATEMENT:  EXECUTE prepstmt2(123);
2025-02-01 03:25:13.515 UTC client backend[30772] pg_regress/domain ERROR:  type "no_such_type" does not exist at character 25
2025-02-01 03:25:13.515 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as no_such_type;
2025-02-01 03:25:13.517 UTC client backend[30772] pg_regress/domain ERROR:  foreign key constraints not possible for domains at character 29
2025-02-01 03:25:13.517 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int constraint cc REFERENCES this_table_not_exists(i);
2025-02-01 03:25:13.518 UTC client backend[30777] pg_regress/prepare ERROR:  prepared statement "q1" already exists
2025-02-01 03:25:13.518 UTC client backend[30777] pg_regress/prepare STATEMENT:  PREPARE q1 AS SELECT 2;
2025-02-01 03:25:13.522 UTC client backend[30772] pg_regress/domain ERROR:  not-null constraints for domains cannot be marked NO INHERIT at character 30
2025-02-01 03:25:13.522 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 not null no inherit;
2025-02-01 03:25:13.524 UTC client backend[30769] pg_regress/plancache ERROR:  cached plan must not change result type
2025-02-01 03:25:13.524 UTC client backend[30769] pg_regress/plancache STATEMENT:  EXECUTE prepstmt;
2025-02-01 03:25:13.525 UTC client backend[30771] pg_regress/polymorphism ERROR:  operator does not exist: point + integer at character 13
2025-02-01 03:25:13.525 UTC client backend[30771] pg_regress/polymorphism HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.525 UTC client backend[30771] pg_regress/polymorphism QUERY:  
	  select x + 1
	
2025-02-01 03:25:13.525 UTC client backend[30771] pg_regress/polymorphism CONTEXT:  SQL function "polyf" during inlining
2025-02-01 03:25:13.525 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(point(3,4));
2025-02-01 03:25:13.527 UTC client backend[30772] pg_regress/domain ERROR:  conflicting NULL/NOT NULL constraints at character 39
2025-02-01 03:25:13.527 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 not null null;
2025-02-01 03:25:13.529 UTC client backend[30772] pg_regress/domain ERROR:  multiple default expressions at character 49
2025-02-01 03:25:13.529 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 not null default 3 default 3;
2025-02-01 03:25:13.530 UTC client backend[30784] pg_regress/sequence ERROR:  INCREMENT must not be zero
2025-02-01 03:25:13.530 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 0;
2025-02-01 03:25:13.530 UTC client backend[30784] pg_regress/sequence ERROR:  MINVALUE (20) must be less than MAXVALUE (-1)
2025-02-01 03:25:13.530 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY -1 MINVALUE 20;
2025-02-01 03:25:13.532 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine element type of "anyarray" argument
2025-02-01 03:25:13.532 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(stavalues1) from pg_statistic;
2025-02-01 03:25:13.532 UTC client backend[30772] pg_regress/domain ERROR:  invalid input syntax for type integer: "h" at character 39
2025-02-01 03:25:13.532 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail int4 DEFAULT 3 + 'h';
2025-02-01 03:25:13.534 UTC client backend[30784] pg_regress/sequence ERROR:  MINVALUE (1) must be less than MAXVALUE (-20)
2025-02-01 03:25:13.534 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 1 MAXVALUE -20;
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  collations are not supported by type integer at character 22
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail int4 collate "C";
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  "anyelement" is not a valid base type for a domain at character 25
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as anyelement;
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  unique constraints not possible for domains at character 30
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 unique;
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  primary key constraints not possible for domains at character 30
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 PRIMARY key;
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  specifying GENERATED not supported for domains at character 30
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 constraint cc generated by default as identity;
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain ERROR:  check constraints for domains cannot be marked NO INHERIT at character 30
2025-02-01 03:25:13.535 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 constraint cc check (values > 1) no inherit;
2025-02-01 03:25:13.536 UTC client backend[30772] pg_regress/domain ERROR:  specifying constraint deferrability not supported for domains at character 63
2025-02-01 03:25:13.536 UTC client backend[30772] pg_regress/domain STATEMENT:  create domain d_fail as int4 constraint cc check (values > 1) deferrable;
2025-02-01 03:25:13.538 UTC client backend[30784] pg_regress/sequence ERROR:  START value (10) cannot be greater than MAXVALUE (-1)
2025-02-01 03:25:13.538 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY -1 START 10;
2025-02-01 03:25:13.539 UTC client backend[30784] pg_regress/sequence ERROR:  START value (-10) cannot be less than MINVALUE (1)
2025-02-01 03:25:13.539 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx INCREMENT BY 1 START -10;
2025-02-01 03:25:13.539 UTC client backend[30784] pg_regress/sequence ERROR:  CACHE (0) must be greater than zero
2025-02-01 03:25:13.539 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx CACHE 0;
2025-02-01 03:25:13.540 UTC client backend[30784] pg_regress/sequence ERROR:  invalid OWNED BY option
2025-02-01 03:25:13.540 UTC client backend[30784] pg_regress/sequence HINT:  Specify OWNED BY table.column or OWNED BY NONE.
2025-02-01 03:25:13.540 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY nobody;
2025-02-01 03:25:13.541 UTC client backend[30769] pg_regress/plancache ERROR:  cached plan must not change result type
2025-02-01 03:25:13.541 UTC client backend[30769] pg_regress/plancache STATEMENT:  EXECUTE prepstmt2(123);
2025-02-01 03:25:13.547 UTC client backend[30784] pg_regress/sequence ERROR:  sequence cannot be owned by relation "pg_class_oid_index"
2025-02-01 03:25:13.547 UTC client backend[30784] pg_regress/sequence DETAIL:  This operation is not supported for indexes.
2025-02-01 03:25:13.547 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY pg_class_oid_index.oid;
2025-02-01 03:25:13.547 UTC client backend[30771] pg_regress/polymorphism ERROR:  return type anyarray is not supported for SQL functions
2025-02-01 03:25:13.547 UTC client backend[30771] pg_regress/polymorphism CONTEXT:  SQL function "polyf" during inlining
2025-02-01 03:25:13.547 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(stavalues1) from pg_statistic;
2025-02-01 03:25:13.549 UTC client backend[30784] pg_regress/sequence ERROR:  sequence must be in same schema as table it is linked to
2025-02-01 03:25:13.549 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY pg_class.relname;
2025-02-01 03:25:13.549 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine result data type
2025-02-01 03:25:13.549 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:25:13.549 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function polyf(x anyelement) returns anyrange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2025-02-01 03:25:13.554 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "attmp_wrong" does not exist
2025-02-01 03:25:13.554 UTC client backend[30781] pg_regress/alter_table STATEMENT:  COMMENT ON TABLE attmp_wrong IS 'table comment';
2025-02-01 03:25:13.557 UTC client backend[30784] pg_regress/sequence ERROR:  column "b" of relation "sequence_test_table" does not exist
2025-02-01 03:25:13.557 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx OWNED BY sequence_test_table.b;
2025-02-01 03:25:13.561 UTC client backend[30781] pg_regress/alter_table ERROR:  column name "xmin" conflicts with a system column name
2025-02-01 03:25:13.561 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp ADD COLUMN xmin integer;
2025-02-01 03:25:13.561 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(5)
2025-02-01 03:25:13.561 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO basictest values ('88', 'haha', 'short text', '123.12');
2025-02-01 03:25:13.562 UTC client backend[30787] pg_regress/conversion ERROR:  conversion "myconv" already exists
2025-02-01 03:25:13.562 UTC client backend[30787] pg_regress/conversion STATEMENT:  CREATE CONVERSION myconv FOR 'LATIN1' TO 'UTF8' FROM iso8859_1_to_utf8;
2025-02-01 03:25:13.563 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 32
2025-02-01 03:25:13.563 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Couldn't find end of Start Tag wrong line 1
	<wrong
	      ^
2025-02-01 03:25:13.563 UTC client backend[30785] pg_regress/xml STATEMENT:  INSERT INTO xmltest VALUES (3, '<wrong');
2025-02-01 03:25:13.567 UTC client backend[30771] pg_regress/polymorphism ERROR:  function polyf(int4range, integer, numeric) does not exist at character 8
2025-02-01 03:25:13.567 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.567 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(int4range(42, 49), 11, 4.5) as fail;
2025-02-01 03:25:13.569 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(5)
2025-02-01 03:25:13.569 UTC client backend[30772] pg_regress/domain CONTEXT:  COPY basictest, line 1, column testvarchar: "notsoshorttext"
2025-02-01 03:25:13.569 UTC client backend[30772] pg_regress/domain STATEMENT:  COPY basictest (testvarchar) FROM stdin;
2025-02-01 03:25:13.570 UTC client backend[30771] pg_regress/polymorphism ERROR:  function polyf(int4multirange, integer, numeric) does not exist at character 8
2025-02-01 03:25:13.570 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.570 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(multirange(int4range(42, 49)), 11, 4.5) as fail;
2025-02-01 03:25:13.570 UTC client backend[30787] pg_regress/conversion ERROR:  default conversion for LATIN1 to UTF8 already exists
2025-02-01 03:25:13.570 UTC client backend[30787] pg_regress/conversion STATEMENT:  CREATE DEFAULT CONVERSION public.mydef2 FOR 'LATIN1' TO 'UTF8' FROM iso8859_1_to_utf8;
2025-02-01 03:25:13.571 UTC client backend[30787] pg_regress/conversion ERROR:  conversion "myconv_bad" does not exist
2025-02-01 03:25:13.571 UTC client backend[30787] pg_regress/conversion STATEMENT:  COMMENT ON CONVERSION myconv_bad IS 'foo';
2025-02-01 03:25:13.573 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML comment
2025-02-01 03:25:13.573 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlcomment('test-');
2025-02-01 03:25:13.573 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine result data type
2025-02-01 03:25:13.573 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:25:13.573 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function polyf(x anycompatible) returns anycompatiblerange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2025-02-01 03:25:13.573 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML comment
2025-02-01 03:25:13.573 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlcomment('--test');
2025-02-01 03:25:13.574 UTC client backend[30785] pg_regress/xml ERROR:  argument of XMLCONCAT must be type xml, not type integer at character 18
2025-02-01 03:25:13.574 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlconcat(1, 2);
2025-02-01 03:25:13.574 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 25
2025-02-01 03:25:13.574 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Couldn't find end of Start Tag syntax line 1
	<syntax
	       ^
2025-02-01 03:25:13.574 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlconcat('bad', '<syntax');
2025-02-01 03:25:13.579 UTC client backend[30785] pg_regress/xml ERROR:  unnamed XML attribute value must be a column reference at character 66
2025-02-01 03:25:13.579 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlelement(name element,
	                  xmlattributes ('unnamed and wrong'));
2025-02-01 03:25:13.579 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine result data type
2025-02-01 03:25:13.579 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anycompatiblemultirange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:25:13.579 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function polyf(x anycompatible) returns anycompatiblemultirange as $$
	  select array[x + 1, x + 2]
	$$ language sql;
2025-02-01 03:25:13.580 UTC client backend[30782] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe)" at character 8
2025-02-01 03:25:13.580 UTC client backend[30782] pg_regress/rowtypes DETAIL:  Too few columns.
2025-02-01 03:25:13.580 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select '(Joe)'::fullname;
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe,,)" at character 8
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes DETAIL:  Too many columns.
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select '(Joe,,)'::fullname;
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes ERROR:  malformed record literal: "[]" at character 8
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes DETAIL:  Missing left parenthesis.
2025-02-01 03:25:13.581 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select '[]'::fullname;
2025-02-01 03:25:13.582 UTC client backend[30782] pg_regress/rowtypes ERROR:  malformed record literal: "(Joe,Blow) /" at character 8
2025-02-01 03:25:13.582 UTC client backend[30782] pg_regress/rowtypes DETAIL:  Junk after right parenthesis.
2025-02-01 03:25:13.582 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select '(Joe,Blow) /'::fullname;
2025-02-01 03:25:13.582 UTC client backend[30771] pg_regress/polymorphism ERROR:  function polyf(integer, numeric[], integer, numeric) does not exist at character 48
2025-02-01 03:25:13.582 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.582 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x), y, pg_typeof(y)
	  from polyf(11, array[1, 2.2], 42, 34.5);
2025-02-01 03:25:13.583 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2025-02-01 03:25:13.583 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  column "xyz" of relation "x" does not exist
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x (xyz) from stdin;
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format CSV, FORMAT CSV);
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (freeze off, freeze on);
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 35
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (delimiter ',', delimiter ',');
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 30
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (null ' ', null ' ');
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (header off, header on);
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 31
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (quote ':', quote ':');
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 32
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (escape ':', escape ':');
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 37
2025-02-01 03:25:13.585 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_quote (a), force_quote *);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 40
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_not_null (a), force_not_null (b));
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 36
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (force_null (a), force_null (b));
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 45
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (convert_selectively (a), convert_selectively (b));
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 42
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (encoding 'sql_ascii', encoding 'sql_ascii');
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 37
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (on_error ignore, on_error ignore);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 43
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (log_verbosity default, log_verbosity verbose);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot specify DELIMITER in BINARY mode
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format BINARY, delimiter ',');
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot specify NULL in BINARY mode
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format BINARY, null 'x');
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  only ON_ERROR STOP is allowed in BINARY mode
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format BINARY, on_error ignore);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY ON_ERROR "unsupported" not recognized at character 20
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (on_error unsupported);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE requires CSV mode
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_quote(a));
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE requires CSV mode
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_quote *);
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE cannot be used with COPY FROM
2025-02-01 03:25:13.586 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format CSV, force_quote(a));
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_QUOTE cannot be used with COPY FROM
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format CSV, force_quote *);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL requires CSV mode
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_not_null(a));
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL requires CSV mode
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_not_null *);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL cannot be used with COPY TO
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x to stdout (format CSV, force_not_null(a));
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NOT_NULL cannot be used with COPY TO
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x to stdout (format CSV, force_not_null *);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NULL requires CSV mode
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_null(a));
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NULL requires CSV mode
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (format TEXT, force_null *);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NULL cannot be used with COPY TO
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x to stdout (format CSV, force_null(a));
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY FORCE_NULL cannot be used with COPY TO
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x to stdout (format CSV, force_null *);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY ON_ERROR cannot be used with COPY TO at character 34
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x to stdout (format BINARY, on_error unsupported);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY LOG_VERBOSITY "unsupported" not recognized at character 20
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin (log_verbosity unsupported);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY REJECT_LIMIT requires ON_ERROR to be set to IGNORE
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin with (reject_limit 1);
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 ERROR:  REJECT_LIMIT (0) must be greater than zero
2025-02-01 03:25:13.587 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin with (on_error ignore, reject_limit 0);
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 ERROR:  column "d" specified more than once
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x (a, b, c, d, e, d, c) from stdin;
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 ERROR:  invalid input syntax for type integer: ""
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY x, line 1, column a: ""
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 ERROR:  missing data for column "e"
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2000	230	23	23"
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 ERROR:  missing data for column "e"
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2001	231	\N	\N"
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 ERROR:  extra data after last expected column
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY x, line 1: "2002	232	40	50	60	70	80"
2025-02-01 03:25:13.588 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin;
2025-02-01 03:25:13.588 UTC client backend[30772] pg_regress/domain ERROR:  division by zero
2025-02-01 03:25:13.588 UTC client backend[30772] pg_regress/domain STATEMENT:  select * from pg_input_error_info('0', 'weirdfloat');
2025-02-01 03:25:13.589 UTC client backend[30785] pg_regress/xml ERROR:  XML attribute name "a" appears more than once at character 65
2025-02-01 03:25:13.589 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlelement(name duplicate, xmlattributes(1 as a, 2 as b, 3 as a));
2025-02-01 03:25:13.597 UTC client backend[30782] pg_regress/rowtypes ERROR:  missing FROM-clause entry for table "q" at character 12
2025-02-01 03:25:13.597 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select f1, q.c1 from quadtable;
2025-02-01 03:25:13.605 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2025-02-01 03:25:13.605 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.605 UTC client backend[30785] pg_regress/xml ERROR:  timestamp out of range
2025-02-01 03:25:13.605 UTC client backend[30785] pg_regress/xml DETAIL:  XML does not support infinite timestamp values.
2025-02-01 03:25:13.605 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlelement(name foo, xmlattributes('infinity'::timestamp as bar));
2025-02-01 03:25:13.606 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2025-02-01 03:25:13.606 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: xmlParseEntityRef: no name
	<invalidentity>&</invalidentity>
	                ^
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<invalidentity>&</invalidentity>');
2025-02-01 03:25:13.607 UTC client backend[30783] pg_regress/copy2 ERROR:  WHERE clause not allowed with COPY TO at character 18
2025-02-01 03:25:13.607 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x TO stdout WHERE a = 1;
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<undefinedentity>&idontexist;</undefinedentity>
	                             ^
2025-02-01 03:25:13.607 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<undefinedentity>&idontexist;</undefinedentity>');
2025-02-01 03:25:13.608 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content
2025-02-01 03:25:13.608 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<twoerrors>&idontexist;</unbalanced>
	                       ^
	line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
	<twoerrors>&idontexist;</unbalanced>
	                                    ^
2025-02-01 03:25:13.608 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(content '<twoerrors>&idontexist;</unbalanced>');
2025-02-01 03:25:13.608 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.608 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2025-02-01 03:25:13.608 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.608 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a;
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	   
	   ^
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(document '   ');
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	abc
	^
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(document 'abc');
2025-02-01 03:25:13.609 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type because input has type unknown
2025-02-01 03:25:13.609 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: xmlParseEntityRef: no name
	<invalidentity>&</abc>
	                ^
	line 1: Opening and ending tag mismatch: invalidentity line 1 and abc
	<invalidentity>&</abc>
	                      ^
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<invalidentity>&</abc>');
2025-02-01 03:25:13.609 UTC client backend[30783] pg_regress/copy2 ERROR:  column "f" does not exist at character 25
2025-02-01 03:25:13.609 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE f > 60003;
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<undefinedentity>&idontexist;</abc>
	                             ^
	line 1: Opening and ending tag mismatch: undefinedentity line 1 and abc
	<undefinedentity>&idontexist;</abc>
	                                   ^
2025-02-01 03:25:13.609 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<undefinedentity>&idontexist;</abc>');
2025-02-01 03:25:13.610 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot alter table "fullname" because column "people.fn" uses its row type
2025-02-01 03:25:13.610 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  alter table fullname add column suffix text default '';
2025-02-01 03:25:13.610 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document
2025-02-01 03:25:13.610 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Entity 'idontexist' not defined
	<twoerrors>&idontexist;</unbalanced>
	                       ^
	line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
	<twoerrors>&idontexist;</unbalanced>
	                                    ^
2025-02-01 03:25:13.610 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlparse(document '<twoerrors>&idontexist;</unbalanced>');
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence ERROR:  sequence type must be smallint, integer, or bigint
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS text;
2025-02-01 03:25:13.610 UTC client backend[30783] pg_regress/copy2 ERROR:  aggregate functions are not allowed in COPY FROM WHERE conditions at character 29
2025-02-01 03:25:13.610 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a = max(x.b);
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence ERROR:  type "nosuchtype" does not exist at character 35
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS nosuchtype;
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence ERROR:  MAXVALUE (100000) is out of range for sequence data type smallint
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS smallint MAXVALUE 100000;
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence ERROR:  MINVALUE (-100000) is out of range for sequence data type smallint
2025-02-01 03:25:13.610 UTC client backend[30784] pg_regress/sequence STATEMENT:  CREATE SEQUENCE sequence_testx AS smallint MINVALUE -100000;
2025-02-01 03:25:13.611 UTC client backend[30784] pg_regress/sequence ERROR:  MAXVALUE (100000) is out of range for sequence data type smallint
2025-02-01 03:25:13.611 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test8 AS smallint;
2025-02-01 03:25:13.611 UTC client backend[30782] pg_regress/rowtypes ERROR:  subfield "c1" is of type complex but expression is of type integer at character 22
2025-02-01 03:25:13.611 UTC client backend[30782] pg_regress/rowtypes HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:13.611 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  update quadtable set q.c1 = 12;
2025-02-01 03:25:13.611 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML processing instruction
2025-02-01 03:25:13.611 UTC client backend[30785] pg_regress/xml DETAIL:  XML processing instruction target name cannot be "xml".
2025-02-01 03:25:13.611 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlpi(name xml);
2025-02-01 03:25:13.612 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot use subquery in COPY FROM WHERE condition at character 27
2025-02-01 03:25:13.612 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a IN (SELECT 1 FROM x);
2025-02-01 03:25:13.612 UTC client backend[30784] pg_regress/sequence ERROR:  MINVALUE (-100000) is out of range for sequence data type smallint
2025-02-01 03:25:13.612 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test10 AS smallint;
2025-02-01 03:25:13.612 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML processing instruction
2025-02-01 03:25:13.612 UTC client backend[30785] pg_regress/xml DETAIL:  XML processing instruction cannot contain "?>".
2025-02-01 03:25:13.612 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlpi(name foo, 'in?>valid');
2025-02-01 03:25:13.613 UTC client backend[30783] pg_regress/copy2 ERROR:  set-returning functions are not allowed in COPY FROM WHERE conditions at character 31
2025-02-01 03:25:13.613 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a IN (generate_series(1,5));
2025-02-01 03:25:13.613 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML processing instruction
2025-02-01 03:25:13.613 UTC client backend[30785] pg_regress/xml DETAIL:  XML processing instruction target name cannot be "xml".
2025-02-01 03:25:13.613 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlpi(name xml, null);
2025-02-01 03:25:13.614 UTC client backend[30783] pg_regress/copy2 ERROR:  window functions are not allowed in COPY FROM WHERE conditions at character 29
2025-02-01 03:25:13.614 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY x from stdin WHERE a = row_number() over(b);
2025-02-01 03:25:13.614 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2025-02-01 03:25:13.614 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.619 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(4)
2025-02-01 03:25:13.619 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO domarrtest values (NULL, '{{"toolong","b","c"},{"d","e","f"}}');
2025-02-01 03:25:13.628 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.628 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_e" references "truncate_a".
2025-02-01 03:25:13.628 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.628 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a,trunc_b;
2025-02-01 03:25:13.628 UTC client backend[30777] pg_regress/prepare ERROR:  wrong number of parameters for prepared statement "q3"
2025-02-01 03:25:13.628 UTC client backend[30777] pg_regress/prepare DETAIL:  Expected 5 parameters but got 1.
2025-02-01 03:25:13.628 UTC client backend[30777] pg_regress/prepare STATEMENT:  EXECUTE q3('bool');
2025-02-01 03:25:13.629 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblemultirange because input has type unknown
2025-02-01 03:25:13.629 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select polyf(null);
2025-02-01 03:25:13.630 UTC client backend[30777] pg_regress/prepare ERROR:  wrong number of parameters for prepared statement "q3"
2025-02-01 03:25:13.630 UTC client backend[30777] pg_regress/prepare DETAIL:  Expected 5 parameters but got 6.
2025-02-01 03:25:13.630 UTC client backend[30777] pg_regress/prepare STATEMENT:  EXECUTE q3('bytea', 5::smallint, 10.5::float, false, 4::bigint, true);
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp02a(*) (SFUNC = stfnp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.632 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp04a(*) (SFUNC = stfp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.633 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.633 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.633 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp04b(*) (SFUNC = stfp, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.635 UTC client backend[30777] pg_regress/prepare ERROR:  parameter $3 of type boolean cannot be coerced to the expected type double precision at character 38
2025-02-01 03:25:13.635 UTC client backend[30777] pg_regress/prepare HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:13.635 UTC client backend[30777] pg_regress/prepare STATEMENT:  EXECUTE q3(5::smallint, 10.5::float, false, 4::bigint, 'bytea');
2025-02-01 03:25:13.635 UTC client backend[30777] pg_regress/prepare ERROR:  type "nonexistenttype" does not exist at character 12
2025-02-01 03:25:13.635 UTC client backend[30777] pg_regress/prepare STATEMENT:  PREPARE q4(nonexistenttype) AS SELECT $1;
2025-02-01 03:25:13.637 UTC client backend[30785] pg_regress/xml ERROR:  not an XML document
2025-02-01 03:25:13.637 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlserialize(document 'bad' as text);
2025-02-01 03:25:13.638 UTC client backend[30785] pg_regress/xml ERROR:  not an XML document
2025-02-01 03:25:13.638 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '<foo>73</foo><bar><val x="y">42</val></bar>' AS text INDENT);
2025-02-01 03:25:13.638 UTC client backend[30785] pg_regress/xml ERROR:  not an XML document
2025-02-01 03:25:13.638 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT 'text node<foo>73</foo>text node<bar><val x="y">42</val></bar>' AS text INDENT);
2025-02-01 03:25:13.639 UTC client backend[30785] pg_regress/xml ERROR:  not an XML document
2025-02-01 03:25:13.639 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '' AS text INDENT);
2025-02-01 03:25:13.639 UTC client backend[30785] pg_regress/xml ERROR:  not an XML document
2025-02-01 03:25:13.639 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xmlserialize(DOCUMENT '  ' AS text INDENT);
2025-02-01 03:25:13.640 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(4)
2025-02-01 03:25:13.640 UTC client backend[30772] pg_regress/domain CONTEXT:  COPY domarrtest, line 1, column testchar4arr: "{qwerty,w,e}"
2025-02-01 03:25:13.640 UTC client backend[30772] pg_regress/domain STATEMENT:  COPY domarrtest FROM stdin;
2025-02-01 03:25:13.641 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 8
2025-02-01 03:25:13.641 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<>
	 ^
2025-02-01 03:25:13.641 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT '<>' IS NOT DOCUMENT;
2025-02-01 03:25:13.643 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document at character 14
2025-02-01 03:25:13.643 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Start tag expected, '<' not found
	bad
	^
2025-02-01 03:25:13.643 UTC client backend[30785] pg_regress/xml STATEMENT:  EXECUTE foo ('bad');
2025-02-01 03:25:13.646 UTC client backend[30773] pg_regress/returning ERROR:  cannot perform INSERT RETURNING on relation "voo"
2025-02-01 03:25:13.646 UTC client backend[30773] pg_regress/returning HINT:  You need an unconditional ON INSERT DO INSTEAD rule with a RETURNING clause.
2025-02-01 03:25:13.646 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO voo VALUES(12,'zoo') RETURNING *, f1*2;
2025-02-01 03:25:13.646 UTC client backend[30773] pg_regress/returning ERROR:  RETURNING list has too many entries
2025-02-01 03:25:13.646 UTC client backend[30773] pg_regress/returning STATEMENT:  CREATE OR REPLACE RULE voo_i AS ON INSERT TO voo DO INSTEAD
	  INSERT INTO foo VALUES(new.*, 57) RETURNING *;
2025-02-01 03:25:13.647 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML document at character 12
2025-02-01 03:25:13.647 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Extra content at the end of the document
	<!DOCTYPE a><a/><b/>
	                ^
2025-02-01 03:25:13.647 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xml '<!DOCTYPE a><a/><b/>';
2025-02-01 03:25:13.648 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.648 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2025-02-01 03:25:13.648 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.648 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a,trunc_e;
2025-02-01 03:25:13.650 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.650 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_d" references "trunc_c".
2025-02-01 03:25:13.650 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_d" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.650 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c;
2025-02-01 03:25:13.651 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.651 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_e" references "trunc_c".
2025-02-01 03:25:13.651 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.651 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,trunc_d;
2025-02-01 03:25:13.655 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2025-02-01 03:25:13.655 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp11b(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp12b(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp15a(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp16a(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.657 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp17b(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp18b(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp19a(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, FINALFUNC = ffp, INITCOND = '{}');
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.658 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggp19b(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, INITCOND = '{}');
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn02a(*) (SFUNC = stfnp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.659 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn02b(*) (SFUNC = stfnp, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.663 UTC client backend[30804] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2025-02-01 03:25:13.663 UTC client backend[30804] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2025-02-01 03:25:13.664 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.664 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2025-02-01 03:25:13.664 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.664 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,trunc_d,trunc_e,truncate_a;
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 12
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<!-- hi--> oops <!DOCTYPE a><a/>
	                 ^
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xml '<!-- hi--> oops <!DOCTYPE a><a/>';
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 12
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: StartTag: invalid element name
	<!-- hi--> <oops/> <!DOCTYPE a><a/>
	                    ^
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xml '<!-- hi--> <oops/> <!DOCTYPE a><a/>';
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml ERROR:  invalid XML content at character 12
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Extra content at the end of the document
	<!DOCTYPE a><a/><b/>
	                ^
2025-02-01 03:25:13.671 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xml '<!DOCTYPE a><a/><b/>';
2025-02-01 03:25:13.671 UTC client backend[30784] pg_regress/sequence ERROR:  null value in column "f2" of relation "serialtest1" violates not-null constraint
2025-02-01 03:25:13.671 UTC client backend[30784] pg_regress/sequence DETAIL:  Failing row contains (wrong, null).
2025-02-01 03:25:13.671 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest1 VALUES ('wrong', NULL);
2025-02-01 03:25:13.680 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.680 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.680 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn04a(*) (SFUNC = stfp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.680 UTC client backend[30772] pg_regress/domain ERROR:  duplicate key value violates unique constraint "dcomptable_d1_key"
2025-02-01 03:25:13.680 UTC client backend[30772] pg_regress/domain DETAIL:  Key (d1)=((1,2)) already exists.
2025-02-01 03:25:13.680 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable values (row(1,2)::dcomptype);
2025-02-01 03:25:13.683 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2025-02-01 03:25:13.683 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn07a(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.683 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(integer[], anyelement) does not exist
2025-02-01 03:25:13.683 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn07b(BASETYPE = anyelement, SFUNC = tfnp, STYPE = int[],
	  INITCOND = '{}');
2025-02-01 03:25:13.684 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(integer[], anyelement) does not exist
2025-02-01 03:25:13.684 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn11a(BASETYPE = anyelement, SFUNC = tf1p, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.684 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfp(integer[], anyelement) does not exist
2025-02-01 03:25:13.684 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn12a(BASETYPE = anyelement, SFUNC = tfp, STYPE = int[],
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.688 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.688 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2025-02-01 03:25:13.688 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.688 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncate_a RESTRICT;
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn13a(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.688 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn13b(BASETYPE = int, SFUNC = tfnp, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn14a(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn14b(BASETYPE = int, SFUNC = tf2p, STYPE = anyarray,
	  INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn15a(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tfnp(anyarray, anyelement) does not exist
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn15b(BASETYPE = anyelement, SFUNC = tfnp,
	  STYPE = anyarray, INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn16a(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf2p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.691 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn16b(BASETYPE = anyelement, SFUNC = tf2p,
	  STYPE = anyarray, INITCOND = '{}');
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn17a(BASETYPE = int, SFUNC = tf1p, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine transition data type
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anyarray requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn18a(BASETYPE = int, SFUNC = tfp, STYPE = anyarray,
	  FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism ERROR:  function tf1p(anyarray, anyelement) does not exist
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn19a(BASETYPE = anyelement, SFUNC = tf1p,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism ERROR:  function ffnp(anyarray) does not exist
2025-02-01 03:25:13.692 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  CREATE AGGREGATE myaggn20a(BASETYPE = anyelement, SFUNC = tfp,
	  STYPE = anyarray, FINALFUNC = ffnp, INITCOND = '{}');
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain ERROR:  column "d1" of table "dcomptable" contains values that violate the new constraint
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain dcomptype add constraint c2 check ((value).r > (value).i);
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain STATEMENT:  select row(2,1)::dcomptype;
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.708 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable values (row(2,1)::comptype);
2025-02-01 03:25:13.709 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.709 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable (d1.r, d1.i) values(100, 99);
2025-02-01 03:25:13.709 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.709 UTC client backend[30772] pg_regress/domain STATEMENT:  update dcomptable set d1.r = (d1).r + 1 where (d1).i > 0;
2025-02-01 03:25:13.709 UTC client backend[30781] pg_regress/alter_table ERROR:  column number must be in range from 1 to 32767 at character 36
2025-02-01 03:25:13.709 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 0 SET STATISTICS 1000;
2025-02-01 03:25:13.709 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter statistics on non-expression column "a" of index "attmp_idx"
2025-02-01 03:25:13.709 UTC client backend[30781] pg_regress/alter_table HINT:  Alter statistics on table column instead.
2025-02-01 03:25:13.709 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 1 SET STATISTICS 1000;
2025-02-01 03:25:13.714 UTC client backend[30773] pg_regress/returning ERROR:  invalid reference to FROM-clause entry for table "foo" at character 49
2025-02-01 03:25:13.714 UTC client backend[30773] pg_regress/returning HINT:  Perhaps you meant to reference the table alias "bar".
2025-02-01 03:25:13.714 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo AS bar DEFAULT VALUES RETURNING foo.*;
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning ERROR:  syntax error at or near "nonsuch" at character 48
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo DEFAULT VALUES RETURNING WITH (nonsuch AS something) *;
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning ERROR:  table name "foo" specified more than once at character 48
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo DEFAULT VALUES RETURNING WITH (new AS foo) *;
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning ERROR:  OLD cannot be specified multiple times at character 68
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS o, new AS n, old AS o) *;
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning ERROR:  NEW cannot be specified multiple times at character 68
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS o, new AS n, new AS n) *;
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning ERROR:  table name "x" specified more than once at character 58
2025-02-01 03:25:13.718 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO foo DEFAULT VALUES RETURNING WITH (old AS x, new AS x) *;
2025-02-01 03:25:13.723 UTC client backend[30764] pg_regress/limit ERROR:  SKIP LOCKED and WITH TIES options cannot be used together at character 87
2025-02-01 03:25:13.723 UTC client backend[30764] pg_regress/limit STATEMENT:  SELECT  thousand
			FROM onek WHERE thousand < 5
			ORDER BY thousand FETCH FIRST 1 ROW WITH TIES FOR UPDATE SKIP LOCKED;
2025-02-01 03:25:13.723 UTC client backend[30804] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2025-02-01 03:25:13.723 UTC client backend[30804] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2025-02-01 03:25:13.723 UTC client backend[30764] pg_regress/limit ERROR:  WITH TIES cannot be specified without ORDER BY clause at character 103
2025-02-01 03:25:13.723 UTC client backend[30764] pg_regress/limit STATEMENT:  SELECT ''::text AS two, unique1, unique2, stringu1
			FROM onek WHERE unique1 > 50
			FETCH FIRST 2 ROW WITH TIES;
2025-02-01 03:25:13.725 UTC client backend[30804] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2025-02-01 03:25:13.725 UTC client backend[30804] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2025-02-01 03:25:13.728 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.728 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "truncate_a" references "trunc_c".
2025-02-01 03:25:13.728 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "truncate_a" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.728 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c;
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_d" references "trunc_c".
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_d" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a;
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_e" references "trunc_c".
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_e" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a,trunc_d;
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "trunc_b" references "truncate_a".
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "trunc_b" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:13.729 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE trunc_c,truncate_a,trunc_d,trunc_e;
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence ERROR:  smallint out of range
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f3)
	  VALUES ('bogus', -32769);
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence ERROR:  smallint out of range
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f4)
	  VALUES ('bogus', -32769);
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence ERROR:  smallint out of range
2025-02-01 03:25:13.731 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f3)
	  VALUES ('bogus', 32768);
2025-02-01 03:25:13.732 UTC client backend[30784] pg_regress/sequence ERROR:  smallint out of range
2025-02-01 03:25:13.732 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f4)
	  VALUES ('bogus', 32768);
2025-02-01 03:25:13.732 UTC client backend[30784] pg_regress/sequence ERROR:  bigint out of range
2025-02-01 03:25:13.732 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f5)
	  VALUES ('bogus', -9223372036854775809);
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence ERROR:  bigint out of range
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f6)
	  VALUES ('bogus', -9223372036854775809);
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence ERROR:  bigint out of range
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f5)
	  VALUES ('bogus', 9223372036854775808);
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence ERROR:  bigint out of range
2025-02-01 03:25:13.735 UTC client backend[30784] pg_regress/sequence STATEMENT:  INSERT INTO serialTest2 (f1, f6)
	  VALUES ('bogus', 9223372036854775808);
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache DETAIL:  Failing row contains (null).
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(null);
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache DETAIL:  Failing row contains (1).
2025-02-01 03:25:13.741 UTC client backend[30769] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(1);
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp ERROR:  relation "temptest" does not exist at character 15
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp STATEMENT:  SELECT * FROM temptest;
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp ERROR:  ON COMMIT can only be used on temporary tables
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp STATEMENT:  CREATE TABLE temptest(col int) ON COMMIT DELETE ROWS;
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp ERROR:  ON COMMIT can only be used on temporary tables
2025-02-01 03:25:13.743 UTC client backend[30804] pg_regress/temp STATEMENT:  CREATE TABLE temptest(col) ON COMMIT DELETE ROWS AS SELECT 1;
2025-02-01 03:25:13.746 UTC client backend[30769] pg_regress/plancache ERROR:  new row for relation "pc_list_part_def" violates partition constraint
2025-02-01 03:25:13.746 UTC client backend[30769] pg_regress/plancache DETAIL:  Failing row contains (2).
2025-02-01 03:25:13.746 UTC client backend[30769] pg_regress/plancache STATEMENT:  execute pstmt_def_insert(2);
2025-02-01 03:25:13.750 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2025-02-01 03:25:13.750 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2025-02-01 03:25:13.750 UTC client backend[30784] pg_regress/sequence ERROR:  currval of sequence "sequence_test" is not yet defined in this session
2025-02-01 03:25:13.750 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT currval('sequence_test'::regclass);
2025-02-01 03:25:13.750 UTC client backend[30785] pg_regress/xml ERROR:  empty XPath expression
2025-02-01 03:25:13.750 UTC client backend[30785] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2025-02-01 03:25:13.750 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xpath('', '<!-- error -->');
2025-02-01 03:25:13.753 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2025-02-01 03:25:13.753 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2025-02-01 03:25:13.754 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter statistics on non-expression column "b" of index "attmp_idx"
2025-02-01 03:25:13.754 UTC client backend[30781] pg_regress/alter_table HINT:  Alter statistics on table column instead.
2025-02-01 03:25:13.754 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 3 SET STATISTICS 1000;
2025-02-01 03:25:13.755 UTC client backend[30781] pg_regress/alter_table ERROR:  column number 4 of relation "attmp_idx" does not exist
2025-02-01 03:25:13.755 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX attmp_idx ALTER COLUMN 4 SET STATISTICS 1000;
2025-02-01 03:25:13.756 UTC client backend[30789] pg_regress/plpgsql ERROR:  function tg_hub_adjustslots_wrong(character, integer, integer) does not exist
2025-02-01 03:25:13.756 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  COMMENT ON FUNCTION tg_hub_adjustslots_wrong(bpchar, integer, integer) IS 'function with args';
2025-02-01 03:25:13.774 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction
2025-02-01 03:25:13.774 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY vistest FROM stdin CSV FREEZE;
2025-02-01 03:25:13.779 UTC client backend[30773] pg_regress/returning ERROR:  column reference "new.f1" is ambiguous at character 120
2025-02-01 03:25:13.779 UTC client backend[30773] pg_regress/returning DETAIL:  It could refer to either a PL/pgSQL variable or a table column.
2025-02-01 03:25:13.779 UTC client backend[30773] pg_regress/returning QUERY:  UPDATE foo SET f1 = new.f1, f3 = new.f3, f4 = new.f4 * 10
	    FROM joinme WHERE f2 = f2j AND f2 = old.f2
	    RETURNING new.f1, new.f4
2025-02-01 03:25:13.779 UTC client backend[30773] pg_regress/returning CONTEXT:  PL/pgSQL function joinview_upd_trig_fn() line 4 at SQL statement
2025-02-01 03:25:13.779 UTC client backend[30773] pg_regress/returning STATEMENT:  UPDATE joinview SET f3 = f3 + 1, f4 = 7 WHERE f3 = 58
	  RETURNING old.*, new.*, *, new.f3 - old.f3 AS delta_f3;
2025-02-01 03:25:13.786 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "attmp" does not exist at character 15
2025-02-01 03:25:13.786 UTC client backend[30781] pg_regress/alter_table STATEMENT:  SELECT * FROM attmp;
2025-02-01 03:25:13.787 UTC client backend[30804] pg_regress/temp ERROR:  unsupported ON COMMIT and foreign key combination
2025-02-01 03:25:13.787 UTC client backend[30804] pg_regress/temp DETAIL:  Table "temptest4" references "temptest3", but they do not have the same ON COMMIT setting.
2025-02-01 03:25:13.787 UTC client backend[30804] pg_regress/temp STATEMENT:  COMMIT;
2025-02-01 03:25:13.792 UTC client backend[30783] pg_regress/copy2 ERROR:  null value in column "b" of relation "forcetest" violates not-null constraint
2025-02-01 03:25:13.792 UTC client backend[30783] pg_regress/copy2 DETAIL:  Failing row contains (3, null, , null, null).
2025-02-01 03:25:13.792 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY forcetest, line 1: "3,,"""
2025-02-01 03:25:13.792 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b), FORCE_NOT_NULL(c));
2025-02-01 03:25:13.793 UTC client backend[30783] pg_regress/copy2 ERROR:  FORCE_NOT_NULL column "b" not referenced by COPY
2025-02-01 03:25:13.793 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL(b));
2025-02-01 03:25:13.793 UTC client backend[30783] pg_regress/copy2 ERROR:  FORCE_NULL column "b" not referenced by COPY
2025-02-01 03:25:13.793 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY forcetest (d, e) FROM STDIN WITH (FORMAT csv, FORCE_NULL(b));
2025-02-01 03:25:13.794 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 73
2025-02-01 03:25:13.794 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NOT_NULL *, FORCE_NOT_NULL(b));
2025-02-01 03:25:13.795 UTC client backend[30783] pg_regress/copy2 ERROR:  conflicting or redundant options at character 69
2025-02-01 03:25:13.795 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY forcetest (a, b, c) FROM STDIN WITH (FORMAT csv, FORCE_NULL *, FORCE_NULL(b));
2025-02-01 03:25:13.796 UTC client backend[30784] pg_regress/sequence ERROR:  cannot drop sequence t1_f1_seq because other objects depend on it
2025-02-01 03:25:13.796 UTC client backend[30784] pg_regress/sequence DETAIL:  default value for column f1 of table t1 depends on sequence t1_f1_seq
2025-02-01 03:25:13.796 UTC client backend[30784] pg_regress/sequence HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:13.796 UTC client backend[30784] pg_regress/sequence STATEMENT:  DROP SEQUENCE t1_f1_seq;
2025-02-01 03:25:13.797 UTC client backend[30784] pg_regress/sequence ERROR:  cannot drop sequence myseq2 because other objects depend on it
2025-02-01 03:25:13.797 UTC client backend[30784] pg_regress/sequence DETAIL:  default value for column f2 of table t1 depends on sequence myseq2
2025-02-01 03:25:13.797 UTC client backend[30784] pg_regress/sequence HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:13.797 UTC client backend[30784] pg_regress/sequence STATEMENT:  DROP SEQUENCE myseq2;
2025-02-01 03:25:13.800 UTC client backend[30773] pg_regress/returning ERROR:  column old.f3 does not exist at character 38
2025-02-01 03:25:13.800 UTC client backend[30773] pg_regress/returning STATEMENT:  UPDATE foo SET f4 = f4 + 1 RETURNING old.f3;
2025-02-01 03:25:13.801 UTC client backend[30773] pg_regress/returning ERROR:  RETURNING must have at least one column at character 38
2025-02-01 03:25:13.801 UTC client backend[30773] pg_regress/returning STATEMENT:  INSERT INTO zerocol SELECT RETURNING old.*, new.*, *;
2025-02-01 03:25:13.808 UTC client backend[30784] pg_regress/sequence ERROR:  sequence "t1_f1_seq" does not exist
2025-02-01 03:25:13.808 UTC client backend[30784] pg_regress/sequence STATEMENT:  DROP SEQUENCE t1_f1_seq;
2025-02-01 03:25:13.809 UTC client backend[30784] pg_regress/sequence ERROR:  cannot open relation "serialtest1"
2025-02-01 03:25:13.809 UTC client backend[30784] pg_regress/sequence DETAIL:  This operation is not supported for tables.
2025-02-01 03:25:13.809 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE serialTest1 CYCLE;
2025-02-01 03:25:13.815 UTC client backend[30784] pg_regress/sequence ERROR:  RESTART value (0) cannot be less than MINVALUE (1)
2025-02-01 03:25:13.815 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test2 RESTART WITH 0;
2025-02-01 03:25:13.815 UTC client backend[30784] pg_regress/sequence ERROR:  RESTART value (40) cannot be greater than MAXVALUE (-1)
2025-02-01 03:25:13.815 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test4 RESTART WITH 40;
2025-02-01 03:25:13.818 UTC client backend[30784] pg_regress/sequence ERROR:  nextval: reached maximum value of sequence "sequence_test2" (36)
2025-02-01 03:25:13.818 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp ERROR:  function nonempty(unknown) does not exist at character 8
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp STATEMENT:  select nonempty('');
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp ERROR:  value for domain nonempty violates check constraint "nonempty_check"
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp STATEMENT:  select pg_temp.nonempty('');
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp ERROR:  value for domain nonempty violates check constraint "nonempty_check"
2025-02-01 03:25:13.819 UTC client backend[30804] pg_regress/temp STATEMENT:  select ''::nonempty;
2025-02-01 03:25:13.820 UTC client backend[30764] pg_regress/limit ERROR:  row count cannot be null in FETCH FIRST ... WITH TIES clause
2025-02-01 03:25:13.820 UTC client backend[30764] pg_regress/limit STATEMENT:  CREATE VIEW limit_thousand_v_3 AS SELECT thousand FROM onek WHERE thousand < 995
			ORDER BY thousand FETCH FIRST NULL ROWS WITH TIES;
2025-02-01 03:25:13.825 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.825 UTC client backend[30772] pg_regress/domain STATEMENT:  select makedcomp(2,1);
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of index part_attmp_index
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX part_attmp_index RENAME TO fail;
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of index part_attmp1_index
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX part_attmp1_index RENAME TO fail;
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of table part_at2tmp
2025-02-01 03:25:13.825 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_at2tmp RENAME TO fail;
2025-02-01 03:25:13.826 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of table part_at2tmp1
2025-02-01 03:25:13.826 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_at2tmp1 RENAME TO fail;
2025-02-01 03:25:13.830 UTC client backend[30771] pg_regress/polymorphism ERROR:  function add_group(smallint[], bigint, integer) does not exist
2025-02-01 03:25:13.830 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create aggregate build_group(int8, integer) (
	  SFUNC = add_group,
	  STYPE = int2[]
	);
2025-02-01 03:25:13.858 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "c1"
2025-02-01 03:25:13.858 UTC client backend[30772] pg_regress/domain STATEMENT:  select row(0,1)::dcomptype;
2025-02-01 03:25:13.859 UTC client backend[30772] pg_regress/domain ERROR:  operator does not exist: character varying > double precision
2025-02-01 03:25:13.859 UTC client backend[30772] pg_regress/domain HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.859 UTC client backend[30772] pg_regress/domain STATEMENT:  alter type comptype alter attribute r type varchar;
2025-02-01 03:25:13.865 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of index onek_unique1
2025-02-01 03:25:13.865 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER INDEX onek_unique1 RENAME TO fail;
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml ERROR:  could not parse XML document
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: xmlns: '<' is not a valid URI
	<invalidns xmlns='&lt;'/>
	                       ^
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xpath('/*', '<invalidns xmlns=''&lt;''/>');
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml ERROR:  could not parse XML document
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml DETAIL:  line 1: Namespace prefix nosuchprefix on tag is not defined
	<nosuchprefix:tag/>
	                 ^
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT xpath('/*', '<nosuchprefix:tag/>');
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml WARNING:  line 1: xmlns: URI relative is not absolute
	<relativens xmlns='relative'/>
	                            ^
2025-02-01 03:25:13.866 UTC client backend[30785] pg_regress/xml CONTEXT:  SQL function "xpath" statement 1
2025-02-01 03:25:13.870 UTC client backend[30784] pg_regress/sequence ERROR:  nextval: reached minimum value of sequence "sequence_test2" (-36)
2025-02-01 03:25:13.870 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2025-02-01 03:25:13.871 UTC client backend[30784] pg_regress/sequence ERROR:  setval: value -100 is out of bounds for sequence "sequence_test2" (5..36)
2025-02-01 03:25:13.871 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', -100);
2025-02-01 03:25:13.872 UTC client backend[30784] pg_regress/sequence ERROR:  setval: value 100 is out of bounds for sequence "sequence_test2" (5..36)
2025-02-01 03:25:13.872 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', 100);
2025-02-01 03:25:13.889 UTC client backend[30772] pg_regress/domain ERROR:  cannot drop column r of composite type comptype because other objects depend on it
2025-02-01 03:25:13.889 UTC client backend[30772] pg_regress/domain DETAIL:  constraint c1 depends on column r of composite type comptype
2025-02-01 03:25:13.889 UTC client backend[30772] pg_regress/domain HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:13.889 UTC client backend[30772] pg_regress/domain STATEMENT:  alter type comptype drop attribute r;
2025-02-01 03:25:13.902 UTC client backend[30785] pg_regress/xml ERROR:  XMLTABLE function has 1 columns available but 2 columns specified
2025-02-01 03:25:13.902 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT * FROM XMLTABLE (ROW () PASSING null COLUMNS v1 timestamp) AS f (v1, v2);
2025-02-01 03:25:13.907 UTC client backend[30785] pg_regress/xml ERROR:  DEFAULT namespace is not supported
2025-02-01 03:25:13.907 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT * FROM XMLTABLE(XMLNAMESPACES(DEFAULT 'http://x.y'),
	                      '/rows/row'
	                      PASSING '<rows xmlns="http://x.y"><row><a>10</a></row></rows>'
	                      COLUMNS a int PATH 'a');
2025-02-01 03:25:13.916 UTC client backend[30783] pg_regress/copy2 ERROR:  new row for relation "check_con_tbl" violates check constraint "check_con_tbl_check"
2025-02-01 03:25:13.916 UTC client backend[30783] pg_regress/copy2 DETAIL:  Failing row contains (0).
2025-02-01 03:25:13.916 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY check_con_tbl, line 1: "0"
2025-02-01 03:25:13.916 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy check_con_tbl from stdin;
2025-02-01 03:25:13.924 UTC client backend[30785] pg_regress/xml ERROR:  more than one value returned by column XPath expression
2025-02-01 03:25:13.924 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT * FROM xmltable('/root' passing '<root><element>a1a<!-- aaaa -->a2a<?aaaaa?> <!--z-->  bbbb<x>xxx</x>cccc</element></root>' COLUMNS element text PATH 'element/text()');
2025-02-01 03:25:13.929 UTC client backend[30772] pg_regress/domain ERROR:  duplicate key value violates unique constraint "dcomptable_d1_key"
2025-02-01 03:25:13.929 UTC client backend[30772] pg_regress/domain DETAIL:  Key (d1)=({"(1,2)"}) already exists.
2025-02-01 03:25:13.929 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable values (array[row(1,2)]::dcomptypea);
2025-02-01 03:25:13.933 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of view attmp_view_new
2025-02-01 03:25:13.933 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER VIEW attmp_view_new RENAME TO fail;
2025-02-01 03:25:13.936 UTC client backend[30785] pg_regress/xml ERROR:  null is not allowed in column "size"
2025-02-01 03:25:13.936 UTC client backend[30785] pg_regress/xml STATEMENT:  SELECT  xmltable.*
	   FROM (SELECT data FROM xmldata) x,
	        LATERAL XMLTABLE('/ROWS/ROW'
	                         PASSING data
	                         COLUMNS id int PATH '@id',
	                                  _id FOR ORDINALITY,
	                                  country_name text PATH 'COUNTRY_NAME' NOT NULL,
	                                  country_id text PATH 'COUNTRY_ID',
	                                  region_id int PATH 'REGION_ID',
	                                  size float PATH 'SIZE' NOT NULL,
	                                  unit text PATH 'SIZE/@unit',
	                                  premier_name text PATH 'PREMIER_NAME' DEFAULT 'not specified');
2025-02-01 03:25:13.945 UTC client backend[30772] pg_regress/domain ERROR:  column "d1" of table "dcomptable" contains values that violate the new constraint
2025-02-01 03:25:13.945 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain dcomptypea add constraint c2 check (value[1].r > value[1].i);
2025-02-01 03:25:13.947 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.947 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_func';
2025-02-01 03:25:13.948 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2025-02-01 03:25:13.948 UTC client backend[30772] pg_regress/domain STATEMENT:  select array[row(2,1)]::dcomptypea;
2025-02-01 03:25:13.952 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot compare arrays of different element types
2025-02-01 03:25:13.952 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select max(histogram_bounds) from pg_stats where tablename = 'pg_am';
2025-02-01 03:25:13.953 UTC client backend[30783] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2025-02-01 03:25:13.953 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY rls_t1 TO stdout;
2025-02-01 03:25:13.955 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2025-02-01 03:25:13.955 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable values (array[row(2,1)]::comptype[]);
2025-02-01 03:25:13.955 UTC client backend[30783] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2025-02-01 03:25:13.955 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY rls_t1 (a, b, c) TO stdout;
2025-02-01 03:25:13.955 UTC client backend[30783] pg_regress/copy2 ERROR:  permission denied for table rls_t1
2025-02-01 03:25:13.955 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY rls_t1 (c) TO stdout;
2025-02-01 03:25:13.956 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.956 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_func';
2025-02-01 03:25:13.956 UTC client backend[30771] pg_regress/polymorphism ERROR:  function "array_in" in FROM has unsupported return type anyarray at character 15
2025-02-01 03:25:13.956 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from array_in('{1,2,3}','int4'::regtype,-1);
2025-02-01 03:25:13.956 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot accept a value of type anyrange
2025-02-01 03:25:13.956 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select anyrange_in('[10,20)','int4range'::regtype,-1);
2025-02-01 03:25:13.956 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.956 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_operator';
2025-02-01 03:25:13.957 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2025-02-01 03:25:13.957 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dcomptable (d1[1].r, d1[1].i) values(100, 99);
2025-02-01 03:25:13.958 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptypea violates check constraint "c1"
2025-02-01 03:25:13.958 UTC client backend[30772] pg_regress/domain STATEMENT:  update dcomptable set d1[1].r = d1[1].r + 1 where d1[1].i > 0;
2025-02-01 03:25:13.961 UTC client backend[30771] pg_regress/polymorphism ERROR:  function myleast() does not exist at character 8
2025-02-01 03:25:13.961 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.961 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select myleast();
2025-02-01 03:25:13.962 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.962 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_type';
2025-02-01 03:25:13.967 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.967 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_view';
2025-02-01 03:25:13.972 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop index onek_unique1_constraint because constraint onek_unique1_constraint on table onek requires it
2025-02-01 03:25:13.972 UTC client backend[30781] pg_regress/alter_table HINT:  You can drop constraint onek_unique1_constraint on table onek instead.
2025-02-01 03:25:13.972 UTC client backend[30781] pg_regress/alter_table STATEMENT:  DROP INDEX onek_unique1_constraint;
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism ERROR:  function formarray(numeric, numeric[]) does not exist at character 8
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select formarray(1.1, array[1.2,55.5]);
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism ERROR:  function formarray(integer, text) does not exist at character 8
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select formarray(1, 'x'::text);
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism ERROR:  function formarray(integer, text[]) does not exist at character 8
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:13.972 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select formarray(1, variadic array['x'::text]);
2025-02-01 03:25:13.973 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.973 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_sequence';
2025-02-01 03:25:13.974 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot copy to view "instead_of_insert_tbl_view"
2025-02-01 03:25:13.974 UTC client backend[30783] pg_regress/copy2 HINT:  To enable copying to a view, provide an INSTEAD OF INSERT trigger.
2025-02-01 03:25:13.974 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY instead_of_insert_tbl_view FROM stdin;
2025-02-01 03:25:13.976 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop index onek_unique1_constraint_foo because constraint onek_unique1_constraint_foo on table onek requires it
2025-02-01 03:25:13.976 UTC client backend[30781] pg_regress/alter_table HINT:  You can drop constraint onek_unique1_constraint_foo on table onek instead.
2025-02-01 03:25:13.976 UTC client backend[30781] pg_regress/alter_table STATEMENT:  DROP INDEX onek_unique1_constraint_foo;
2025-02-01 03:25:13.977 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.977 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2025-02-01 03:25:13.978 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.978 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2025-02-01 03:25:13.979 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.979 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2025-02-01 03:25:13.981 UTC client backend[30804] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:13.981 UTC client backend[30804] pg_regress/temp STATEMENT:  prepare transaction 'twophase_tab';
2025-02-01 03:25:13.997 UTC client backend[30783] pg_regress/copy2 ERROR:  invalid input syntax for type integer: "a"
2025-02-01 03:25:13.997 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 2, column n: "a"
2025-02-01 03:25:13.997 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error stop);
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer, integer, integer) does not exist at character 8
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc(10, 20, 30);
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc() does not exist
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  drop function dfunc();
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer) does not exist
2025-02-01 03:25:14.003 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  drop function dfunc(int);
2025-02-01 03:25:14.004 UTC client backend[30771] pg_regress/polymorphism ERROR:  input parameters after one with a default value must also have defaults at character 34
2025-02-01 03:25:14.004 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function dfunc(a int = 1, b int) returns int as $$
	  select $1 + $2;
	$$ language sql;
2025-02-01 03:25:14.011 UTC client backend[30853] pg_regress/temp ERROR:  cannot PREPARE a transaction that has operated on temporary objects
2025-02-01 03:25:14.011 UTC client backend[30853] pg_regress/temp STATEMENT:  PREPARE TRANSACTION 'twophase_search';
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 ERROR:  invalid input syntax for type widget: "1"
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY hard_err, line 1, column foo: "1"
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY hard_err FROM STDIN WITH (on_error ignore);
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 ERROR:  missing data for column "k"
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 1: "1	{1}"
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error ignore);
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 ERROR:  extra data after last expected column
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 1: "1	{1}	3	abc"
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error ignore);
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 ERROR:  skipped more than REJECT_LIMIT (3) rows due to data type incompatibility
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY check_ign_err, line 5, column n: ""
2025-02-01 03:25:14.025 UTC client backend[30783] pg_regress/copy2 STATEMENT:  COPY check_ign_err FROM STDIN WITH (on_error ignore, reject_limit 3);
2025-02-01 03:25:14.027 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc() is not unique at character 8
2025-02-01 03:25:14.027 UTC client backend[30771] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2025-02-01 03:25:14.027 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc();
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc() is not unique at character 8
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc();
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer) is not unique at character 8
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc(1);
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer, integer) is not unique at character 8
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2025-02-01 03:25:14.037 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc(1, 2);
2025-02-01 03:25:14.039 UTC client backend[30771] pg_regress/polymorphism ERROR:  only input parameters can have default values at character 23
2025-02-01 03:25:14.039 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function dfunc(out int = 20) returns int as $$
	  select 1;
	$$ language sql;
2025-02-01 03:25:14.042 UTC client backend[30784] pg_regress/sequence ERROR:  relation "asdf" does not exist
2025-02-01 03:25:14.042 UTC client backend[30784] pg_regress/sequence STATEMENT:  COMMENT ON SEQUENCE asdf IS 'won''t work';
2025-02-01 03:25:14.044 UTC client backend[30772] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check"
2025-02-01 03:25:14.044 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into pitable values(array[-1]);
2025-02-01 03:25:14.044 UTC client backend[30772] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check" at character 28
2025-02-01 03:25:14.044 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into pitable values('{0}');
2025-02-01 03:25:14.045 UTC client backend[30772] pg_regress/domain ERROR:  value for domain posint violates check constraint "posint_check"
2025-02-01 03:25:14.045 UTC client backend[30772] pg_regress/domain STATEMENT:  update pitable set f1[1] = 0;
2025-02-01 03:25:14.048 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc() does not exist at character 8
2025-02-01 03:25:14.048 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.048 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc();
2025-02-01 03:25:14.049 UTC client backend[30784] pg_regress/sequence ERROR:  lastval is not yet defined in this session
2025-02-01 03:25:14.049 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT lastval();
2025-02-01 03:25:14.052 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot remove parameter defaults from existing function
2025-02-01 03:25:14.052 UTC client backend[30771] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(integer[]) first.
2025-02-01 03:25:14.052 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a variadic int[]) returns int as
	$$ select array_upper($1, 1) $$ language sql;
2025-02-01 03:25:14.058 UTC client backend[30784] pg_regress/sequence ERROR:  lastval is not yet defined in this session
2025-02-01 03:25:14.058 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT lastval();
2025-02-01 03:25:14.069 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(4)
2025-02-01 03:25:14.069 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into vc4table values(array['too long']);
2025-02-01 03:25:14.076 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer) is not unique at character 8
2025-02-01 03:25:14.076 UTC client backend[30771] pg_regress/polymorphism HINT:  Could not choose a best candidate function. You might need to add explicit type casts.
2025-02-01 03:25:14.076 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select dfunc(1);
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain ERROR:  column "f1" is of type dposinta[] but expression is of type integer[] at character 34
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dposintatable values(array[array[42]]);
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain ERROR:  column "f1" is of type dposinta[] but expression is of type posint[] at character 34
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:14.087 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dposintatable values(array[array[42]::posint[]]);
2025-02-01 03:25:14.088 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer) does not exist at character 15
2025-02-01 03:25:14.088 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.088 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(0);
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism ERROR:  argument name "x" used more than once at character 39
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(x := 20, b := 10, x := 30);
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism ERROR:  positional argument cannot follow named argument at character 34
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(10, b := 20, 30);
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(x => integer, b => integer, c => integer) does not exist at character 15
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(x := 10, b := 20, c := 30);
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer, integer, a => integer) does not exist at character 15
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.091 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(10, 10, a := 20);
2025-02-01 03:25:14.092 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(integer, c => integer, d => integer) does not exist at character 15
2025-02-01 03:25:14.092 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.092 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc(1,c := 2,d := 3);
2025-02-01 03:25:14.095 UTC client backend[30771] pg_regress/polymorphism ERROR:  function dfunc(unknown, c => integer, b => date) does not exist at character 15
2025-02-01 03:25:14.095 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.095 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select * from dfunc('Hello World', c := 20, b := '2009-07-25'::date);
2025-02-01 03:25:14.098 UTC client backend[30772] pg_regress/domain ERROR:  wrong number of array subscripts
2025-02-01 03:25:14.098 UTC client backend[30772] pg_regress/domain STATEMENT:  update dposintatable set f1[2][1] = array[97];
2025-02-01 03:25:14.098 UTC client backend[30772] pg_regress/domain ERROR:  syntax error at or near "[" at character 33
2025-02-01 03:25:14.098 UTC client backend[30772] pg_regress/domain STATEMENT:  update dposintatable set (f1[2])[1] = array[98];
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot change name of input parameter "c"
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(character varying,numeric) first.
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a varchar = 'def a', out _a varchar, x numeric = NULL, out _c numeric)
	returns record as $$
	  select $1, $2;
	$$ language sql;
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot change name of input parameter "c"
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism HINT:  Use DROP FUNCTION dfunc(character varying,numeric) first.
2025-02-01 03:25:14.102 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create or replace function dfunc(a varchar = 'def a', out _a varchar, numeric = NULL, out _c numeric)
	returns record as $$
	  select $1, $2;
	$$ language sql;
2025-02-01 03:25:14.103 UTC client backend[30771] pg_regress/polymorphism ERROR:  parameter name "a" used more than once at character 34
2025-02-01 03:25:14.103 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function testpolym(a int, a int) returns int as $$ select 1;$$ language sql;
2025-02-01 03:25:14.103 UTC client backend[30771] pg_regress/polymorphism ERROR:  parameter name "a" used more than once at character 43
2025-02-01 03:25:14.103 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function testpolym(int, out a int, out a int) returns int as $$ select 1;$$ language sql;
2025-02-01 03:25:14.104 UTC client backend[30771] pg_regress/polymorphism ERROR:  parameter name "a" used more than once at character 38
2025-02-01 03:25:14.104 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function testpolym(out a int, inout a int) returns int as $$ select 1;$$ language sql;
2025-02-01 03:25:14.104 UTC client backend[30771] pg_regress/polymorphism ERROR:  parameter name "a" used more than once at character 34
2025-02-01 03:25:14.104 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function testpolym(a int, inout a int) returns int as $$ select 1;$$ language sql;
2025-02-01 03:25:14.110 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot rename inherited constraint "con1"
2025-02-01 03:25:14.110 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE constraint_rename_test2 RENAME CONSTRAINT con1 TO con1foo;
2025-02-01 03:25:14.110 UTC client backend[30781] pg_regress/alter_table ERROR:  inherited constraint "con1" must be renamed in child tables too
2025-02-01 03:25:14.110 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY constraint_rename_test RENAME CONSTRAINT con1 TO con1foo;
2025-02-01 03:25:14.116 UTC client backend[30775] pg_regress/truncate ERROR:  relation "truncate_a_id1" does not exist at character 16
2025-02-01 03:25:14.116 UTC client backend[30775] pg_regress/truncate STATEMENT:  SELECT nextval('truncate_a_id1');
2025-02-01 03:25:14.119 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate only a partitioned table
2025-02-01 03:25:14.119 UTC client backend[30775] pg_regress/truncate HINT:  Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly.
2025-02-01 03:25:14.119 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE ONLY truncparted;
2025-02-01 03:25:14.139 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate only a partitioned table
2025-02-01 03:25:14.139 UTC client backend[30775] pg_regress/truncate HINT:  Do not specify the ONLY keyword, or use TRUNCATE ONLY on the partitions directly.
2025-02-01 03:25:14.139 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE ONLY truncparted;
2025-02-01 03:25:14.140 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dcomptype violates check constraint "dcomptype_check"
2025-02-01 03:25:14.140 UTC client backend[30772] pg_regress/domain STATEMENT:  update dcomptable set f1[1].cf1 = -1;
2025-02-01 03:25:14.160 UTC client backend[30783] pg_regress/copy2 ERROR:  cannot specify DEFAULT in BINARY mode
2025-02-01 03:25:14.160 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format binary, default '\D');
2025-02-01 03:25:14.160 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY default representation cannot use newline or carriage return
2025-02-01 03:25:14.160 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default E'\n');
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY default representation cannot use newline or carriage return
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default E'\r');
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY delimiter character must not appear in the DEFAULT specification
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (delimiter ';', default 'test;test');
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 ERROR:  CSV quote character must not appear in the DEFAULT specification
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format csv, quote '"', default 'test"test');
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 ERROR:  NULL specification and DEFAULT specification cannot be the same
2025-02-01 03:25:14.161 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default '\N');
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 ERROR:  unexpected default marker in COPY data
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 DETAIL:  Column "id" has no default value.
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY copy_default, line 1: "\D	value	'2022-07-04'"
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (default '\D');
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 ERROR:  unexpected default marker in COPY data
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 DETAIL:  Column "id" has no default value.
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 CONTEXT:  COPY copy_default, line 1: "\D,value,2022-07-04"
2025-02-01 03:25:14.162 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy copy_default from stdin with (format csv, default '\D');
2025-02-01 03:25:14.163 UTC client backend[30784] pg_regress/sequence ERROR:  cannot execute nextval() in a read-only transaction
2025-02-01 03:25:14.163 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT nextval('sequence_test2');
2025-02-01 03:25:14.165 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.165 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO nulltest DEFAULT VALUES;
2025-02-01 03:25:14.166 UTC client backend[30772] pg_regress/domain ERROR:  domain dcheck does not allow null values
2025-02-01 03:25:14.166 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into nulltest values ('a', 'b', 'c', 'd', NULL);
2025-02-01 03:25:14.167 UTC client backend[30772] pg_regress/domain ERROR:  new row for relation "nulltest" violates check constraint "nulltest_col5_check"
2025-02-01 03:25:14.167 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (a, b, c, d, a).
2025-02-01 03:25:14.167 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into nulltest values ('a', 'b', 'c', 'd', 'a');
2025-02-01 03:25:14.169 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, point) does not exist at character 29
2025-02-01 03:25:14.169 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.169 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, point(1,2)) x;
2025-02-01 03:25:14.171 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.171 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO nulltest values (NULL, 'b', 'c', 'd', 'd');
2025-02-01 03:25:14.172 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.172 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO nulltest values ('a', NULL, 'c', 'd', 'c');
2025-02-01 03:25:14.172 UTC client backend[30772] pg_regress/domain ERROR:  null value in column "col3" of relation "nulltest" violates not-null constraint
2025-02-01 03:25:14.172 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (a, b, null, d, c).
2025-02-01 03:25:14.172 UTC client backend[30772] pg_regress/domain STATEMENT:  INSERT INTO nulltest values ('a', 'b', NULL, 'd', 'c');
2025-02-01 03:25:14.172 UTC client backend[30784] pg_regress/sequence ERROR:  cannot execute setval() in a read-only transaction
2025-02-01 03:25:14.172 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT setval('sequence_test2', 1);
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain ERROR:  null value in column "col3" of relation "nulltest" violates not-null constraint
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (a, b, null, d, d).
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain CONTEXT:  COPY nulltest, line 1: "a	b	\N	d	d"
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain ERROR:  domain dcheck does not allow null values
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain CONTEXT:  COPY nulltest, line 1, column col5: null input
2025-02-01 03:25:14.174 UTC client backend[30772] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2025-02-01 03:25:14.175 UTC client backend[30772] pg_regress/domain ERROR:  new row for relation "nulltest" violates check constraint "nulltest_col5_check"
2025-02-01 03:25:14.175 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (a, b, c, null, a).
2025-02-01 03:25:14.175 UTC client backend[30772] pg_regress/domain CONTEXT:  COPY nulltest, line 3: "a	b	c	\N	a"
2025-02-01 03:25:14.175 UTC client backend[30772] pg_regress/domain STATEMENT:  COPY nulltest FROM stdin;
2025-02-01 03:25:14.176 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, integer[]) does not exist at character 29
2025-02-01 03:25:14.176 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.176 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[1,2]) x;
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, point[]) does not exist at character 29
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[point(1,2)]) x;
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.180 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2025-02-01 03:25:14.183 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.183 UTC client backend[30772] pg_regress/domain STATEMENT:  SELECT cast(NULL as dnotnull);
2025-02-01 03:25:14.183 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.183 UTC client backend[30772] pg_regress/domain STATEMENT:  SELECT cast(cast(NULL as dnull) as dnotnull);
2025-02-01 03:25:14.183 UTC client backend[30784] pg_regress/sequence ERROR:  permission denied for sequence seq3
2025-02-01 03:25:14.183 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT nextval('seq3');
2025-02-01 03:25:14.184 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnull does not allow null values
2025-02-01 03:25:14.184 UTC client backend[30772] pg_regress/domain STATEMENT:  SELECT cast(col4 as dnotnull) from nulltest;
2025-02-01 03:25:14.186 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not determine interpretation of row comparison operator ~~ at character 25
2025-02-01 03:25:14.186 UTC client backend[30782] pg_regress/rowtypes HINT:  Row comparison operators must be associated with btree operator families.
2025-02-01 03:25:14.186 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select ROW('ABC','DEF') ~~ ROW('DEF','ABC') as fail;
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(numeric, int4range) does not exist at character 29
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.187 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, int4range(4,7)) x;
2025-02-01 03:25:14.188 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblerange because input has type unknown
2025-02-01 03:25:14.188 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, '[4,7)') x;
2025-02-01 03:25:14.189 UTC client backend[30775] pg_regress/truncate ERROR:  cannot truncate a table referenced in a foreign key constraint
2025-02-01 03:25:14.189 UTC client backend[30775] pg_regress/truncate DETAIL:  Table "truncpart" references "truncprim".
2025-02-01 03:25:14.189 UTC client backend[30775] pg_regress/truncate HINT:  Truncate table "truncpart" at the same time, or use TRUNCATE ... CASCADE.
2025-02-01 03:25:14.189 UTC client backend[30775] pg_regress/truncate STATEMENT:  TRUNCATE TABLE truncprim;
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(int4range, numrange) does not exist at character 29
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(int4range(11,12), numrange(4,7)) x;
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine result data type
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:25:14.192 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function anyctest(anycompatible)
	returns anycompatiblerange as $$
	  select $1
	$$ language sql;
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, integer) does not exist at character 29
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, 12) x;
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(numeric, int4multirange) does not exist at character 29
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.193 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, multirange(int4range(4,7))) x;
2025-02-01 03:25:14.194 UTC client backend[30771] pg_regress/polymorphism ERROR:  could not determine polymorphic type anycompatiblemultirange because input has type unknown
2025-02-01 03:25:14.194 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11.2, '{[4,7)}') x;
2025-02-01 03:25:14.194 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(int4multirange, nummultirange) does not exist at character 29
2025-02-01 03:25:14.194 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.194 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(multirange(int4range(11,12)), multirange(numrange(4,7))) x;
2025-02-01 03:25:14.195 UTC client backend[30771] pg_regress/polymorphism ERROR:  cannot determine result data type
2025-02-01 03:25:14.195 UTC client backend[30771] pg_regress/polymorphism DETAIL:  A result of type anycompatiblemultirange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:25:14.195 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  create function anyctest(anycompatible)
	returns anycompatiblemultirange as $$
	  select $1
	$$ language sql;
2025-02-01 03:25:14.196 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer[], integer[]) does not exist at character 29
2025-02-01 03:25:14.196 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.196 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(array[11], array[1,2]) x;
2025-02-01 03:25:14.199 UTC client backend[30783] pg_regress/copy2 ERROR:  COPY DEFAULT cannot be used with COPY TO
2025-02-01 03:25:14.199 UTC client backend[30783] pg_regress/copy2 STATEMENT:  copy (select 1 as test) TO stdout with (default '\D');
2025-02-01 03:25:14.203 UTC client backend[30771] pg_regress/polymorphism ERROR:  function anyctest(integer, numeric[], integer, numeric) does not exist at character 29
2025-02-01 03:25:14.203 UTC client backend[30771] pg_regress/polymorphism HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.203 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, array[1, 2.2], 42, 34.5) x;
2025-02-01 03:25:14.206 UTC client backend[30771] pg_regress/polymorphism ERROR:  invalid input syntax for type integer: "12.2" at character 42
2025-02-01 03:25:14.206 UTC client backend[30771] pg_regress/polymorphism STATEMENT:  select x, pg_typeof(x) from anyctest(11, '12.2') x;
2025-02-01 03:25:14.208 UTC client backend[30784] pg_regress/sequence ERROR:  permission denied for sequence seq3
2025-02-01 03:25:14.208 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT currval('seq3');
2025-02-01 03:25:14.226 UTC client backend[30772] pg_regress/domain ERROR:  null value in column "col5" of relation "defaulttest" violates not-null constraint
2025-02-01 03:25:14.226 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12).
2025-02-01 03:25:14.226 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into defaulttest(col4) values(0);
2025-02-01 03:25:14.230 UTC client backend[30772] pg_regress/domain ERROR:  null value in column "col5" of relation "defaulttest" violates not-null constraint
2025-02-01 03:25:14.230 UTC client backend[30772] pg_regress/domain DETAIL:  Failing row contains (3, 12, 5, 0, null, 88, 8000, 12.12).
2025-02-01 03:25:14.230 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into defaulttest(col4) values(0);
2025-02-01 03:25:14.239 UTC client backend[30784] pg_regress/sequence ERROR:  permission denied for sequence seq3
2025-02-01 03:25:14.239 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT lastval();
2025-02-01 03:25:14.240 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types bigint and integer at record column 1
2025-02-01 03:25:14.240 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select * from int8_tbl i8 where i8 in (row(123,456));
2025-02-01 03:25:14.247 UTC client backend[30784] pg_regress/sequence ERROR:  permission denied for sequence seq3
2025-02-01 03:25:14.247 UTC client backend[30784] pg_regress/sequence STATEMENT:  SELECT setval('seq3', 5);
2025-02-01 03:25:14.247 UTC client backend[30766] pg_regress/with ERROR:  search column "foo" not in WITH query column list at character 146
2025-02-01 03:25:14.247 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by foo, tar set seq
	select * from search_graph;
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with ERROR:  search sequence column name "label" already used in WITH query column list at character 146
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set label
	select * from search_graph;
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with ERROR:  search column "f" specified more than once at character 146
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t, f set seq
	select * from search_graph;
2025-02-01 03:25:14.248 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify column "nosuch" in record data type at character 9
2025-02-01 03:25:14.248 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select (row(1, 2.0)).nosuch;
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the left side of the UNION must be a SELECT
2025-02-01 03:25:14.248 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set seq
	select * from search_graph order by seq;
2025-02-01 03:25:14.249 UTC client backend[30784] pg_regress/sequence ERROR:  must be owner of sequence sequence_test2
2025-02-01 03:25:14.249 UTC client backend[30784] pg_regress/sequence STATEMENT:  ALTER SEQUENCE sequence_test2 START WITH 1;
2025-02-01 03:25:14.249 UTC client backend[30766] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the right side of the UNION must be a SELECT
2025-02-01 03:25:14.249 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph0 g
		union all
		(select * from graph0 g
		union all
		select g.*
		from graph0 g, search_graph sg
		where g.f = sg.t)
	) search depth first by f, t set seq
	select * from search_graph order by seq;
2025-02-01 03:25:14.249 UTC client backend[30766] pg_regress/with ERROR:  with a SEARCH or CYCLE clause, the recursive reference to WITH query "x" must be at the top level of its right-hand SELECT
2025-02-01 03:25:14.249 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive x(col) as (
		select 1
		union
		(with x as (select * from x)
		 select * from x)
	) search depth first by col set seq
	select * from x;
2025-02-01 03:25:14.249 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify column "f3" in record data type at character 9
2025-02-01 03:25:14.249 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select (r).f3 from (select row(1, 2.0) as r) ss;
2025-02-01 03:25:14.251 UTC client backend[30772] pg_regress/domain ERROR:  column "col1" of table "domnotnull" contains null values
2025-02-01 03:25:14.251 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain dnotnulltest set not null;
2025-02-01 03:25:14.252 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare rows of zero length at character 14
2025-02-01 03:25:14.252 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select ROW() = ROW();
2025-02-01 03:25:14.259 UTC client backend[30772] pg_regress/domain ERROR:  column "col2" of table "domnotnull" contains null values
2025-02-01 03:25:14.259 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain dnotnulltest set not null;
2025-02-01 03:25:14.262 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnulltest does not allow null values
2025-02-01 03:25:14.262 UTC client backend[30772] pg_regress/domain STATEMENT:  update domnotnull set col1 = null;
2025-02-01 03:25:14.265 UTC client backend[30772] pg_regress/domain ERROR:  domain dnotnulltest does not allow null values
2025-02-01 03:25:14.265 UTC client backend[30772] pg_regress/domain STATEMENT:  update domnotnull set col1 = null;
2025-02-01 03:25:14.270 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify an ordering operator for type cantcompare at character 27
2025-02-01 03:25:14.270 UTC client backend[30782] pg_regress/rowtypes HINT:  Use an explicit ordering operator or modify the query.
2025-02-01 03:25:14.270 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select * from cc order by f1;
2025-02-01 03:25:14.286 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2025-02-01 03:25:14.286 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 < row(1, 'abc')::testtype3;
2025-02-01 03:25:14.288 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2025-02-01 03:25:14.288 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 <> row(1, 'abc')::testtype3;
2025-02-01 03:25:14.297 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2025-02-01 03:25:14.297 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 < row(1)::testtype5;
2025-02-01 03:25:14.297 UTC client backend[30772] pg_regress/domain ERROR:  column "col1" of table "domcontest" contains values that violate the new constraint
2025-02-01 03:25:14.297 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain con add constraint t check (VALUE < 1);
2025-02-01 03:25:14.297 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2025-02-01 03:25:14.297 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 <> row(1)::testtype5;
2025-02-01 03:25:14.300 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify a comparison function for type point
2025-02-01 03:25:14.300 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, '(1,2)')::testtype6 < row(1, '(1,3)')::testtype6;
2025-02-01 03:25:14.305 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify an equality operator for type point
2025-02-01 03:25:14.305 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, '(1,2)')::testtype6 <> row(1, '(1,3)')::testtype6;
2025-02-01 03:25:14.313 UTC client backend[30772] pg_regress/domain ERROR:  value for domain con violates check constraint "con_check"
2025-02-01 03:25:14.313 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into domcontest values (-5);
2025-02-01 03:25:14.314 UTC client backend[30772] pg_regress/domain ERROR:  value for domain con violates check constraint "t"
2025-02-01 03:25:14.314 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into domcontest values (42);
2025-02-01 03:25:14.320 UTC client backend[30772] pg_regress/domain ERROR:  value for domain con violates check constraint "con_check"
2025-02-01 03:25:14.320 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into domcontest values (-5);
2025-02-01 03:25:14.322 UTC client backend[30772] pg_regress/domain ERROR:  constraint "nonexistent" of domain "con" does not exist
2025-02-01 03:25:14.322 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain con drop constraint nonexistent;
2025-02-01 03:25:14.334 UTC client backend[30772] pg_regress/domain ERROR:  column "col1" of table "domconnotnulltest" contains null values
2025-02-01 03:25:14.334 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain connotnull add not null;
2025-02-01 03:25:14.336 UTC client backend[30772] pg_regress/domain ERROR:  column "col2" of table "domconnotnulltest" contains null values
2025-02-01 03:25:14.336 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain connotnull add not null;
2025-02-01 03:25:14.343 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2025-02-01 03:25:14.343 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *< row(1, 'abc')::testtype3;
2025-02-01 03:25:14.343 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare dissimilar column types integer and text at record column 2
2025-02-01 03:25:14.343 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *<> row(1, 'abc')::testtype3;
2025-02-01 03:25:14.343 UTC client backend[30766] pg_regress/with ERROR:  cycle column "foo" not in WITH query column list at character 144
2025-02-01 03:25:14.343 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle foo, tar set is_cycle using path
	select * from search_graph;
2025-02-01 03:25:14.344 UTC client backend[30766] pg_regress/with ERROR:  CYCLE types boolean and integer cannot be matched at character 184
2025-02-01 03:25:14.344 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to true default 55 using path
	select * from search_graph;
2025-02-01 03:25:14.348 UTC client backend[30766] pg_regress/with ERROR:  could not identify an equality operator for type point
2025-02-01 03:25:14.348 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to point '(1,1)' default point '(0,0)' using path
	select * from search_graph;
2025-02-01 03:25:14.348 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2025-02-01 03:25:14.348 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *< row(1)::testtype5;
2025-02-01 03:25:14.348 UTC client backend[30766] pg_regress/with ERROR:  cycle mark column name "label" already used in WITH query column list at character 144
2025-02-01 03:25:14.348 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set label to true default false using path
	select * from search_graph;
2025-02-01 03:25:14.349 UTC client backend[30782] pg_regress/rowtypes ERROR:  cannot compare record types with different numbers of columns
2025-02-01 03:25:14.349 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select row(1, 2)::testtype1 *<> row(1)::testtype5;
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with ERROR:  cycle path column name "label" already used in WITH query column list at character 144
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set is_cycle to true default false using label
	select * from search_graph;
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with ERROR:  cycle mark column name and cycle path column name are the same at character 144
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t set foo to true default false using foo
	select * from search_graph;
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with ERROR:  cycle column "f" specified more than once at character 144
2025-02-01 03:25:14.349 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) cycle f, t, f set is_cycle to true default false using path
	select * from search_graph;
2025-02-01 03:25:14.350 UTC client backend[30766] pg_regress/with ERROR:  search sequence column name and cycle mark column name are the same at character 144
2025-02-01 03:25:14.350 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set foo
	  cycle f, t set foo to true default false using path
	select * from search_graph;
2025-02-01 03:25:14.350 UTC client backend[30766] pg_regress/with ERROR:  search sequence column name and cycle path column name are the same at character 144
2025-02-01 03:25:14.350 UTC client backend[30766] pg_regress/with STATEMENT:  with recursive search_graph(f, t, label) as (
		select * from graph g
		union all
		select g.*
		from graph g, search_graph sg
		where g.f = sg.t
	) search depth first by f, t set foo
	  cycle f, t set is_cycle to true default false using foo
	select * from search_graph;
2025-02-01 03:25:14.362 UTC client backend[30772] pg_regress/domain ERROR:  domain connotnull does not allow null values
2025-02-01 03:25:14.362 UTC client backend[30772] pg_regress/domain STATEMENT:  update domconnotnulltest set col1 = null;
2025-02-01 03:25:14.378 UTC client backend[30772] pg_regress/domain ERROR:  column "stuff" of table "thethings" contains values that violate the new constraint
2025-02-01 03:25:14.378 UTC client backend[30772] pg_regress/domain STATEMENT:  ALTER DOMAIN things ADD CONSTRAINT meow CHECK (VALUE < 11);
2025-02-01 03:25:14.379 UTC client backend[30772] pg_regress/domain ERROR:  column "stuff" of table "thethings" contains values that violate the new constraint
2025-02-01 03:25:14.379 UTC client backend[30772] pg_regress/domain STATEMENT:  ALTER DOMAIN things VALIDATE CONSTRAINT meow;
2025-02-01 03:25:14.382 UTC client backend[30789] pg_regress/plpgsql ERROR:  duplicate key value violates unique constraint "pfield_name"
2025-02-01 03:25:14.382 UTC client backend[30789] pg_regress/plpgsql DETAIL:  Key (name)=(PF1_1) already exists.
2025-02-01 03:25:14.382 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  insert into PField values ('PF1_1', 'should fail due to unique index');
2025-02-01 03:25:14.385 UTC client backend[30789] pg_regress/plpgsql ERROR:  WS.not.there         does not exist
2025-02-01 03:25:14.385 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_backlink_set(character,character) line 30 at RAISE
	PL/pgSQL function tg_backlink_a() line 17 at assignment
2025-02-01 03:25:14.385 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  update PSlot set backlink = 'WS.not.there' where slotname = 'PS.base.a1';
2025-02-01 03:25:14.389 UTC client backend[30774] pg_regress/largeobject ERROR:  large object read request is too large
2025-02-01 03:25:14.389 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_get(34505);
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function result type must be integer because of OUT parameters
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int) RETURNS float
	AS 'select $1+1' LANGUAGE sql;
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function result type must be record because of OUT parameters
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int, out f3 text) RETURNS int
	AS 'select $1+1' LANGUAGE sql;
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot change return type of existing function
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs HINT:  Use DROP FUNCTION rngfunc(integer) first.
2025-02-01 03:25:14.392 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION rngfunc(in f1 int, out f2 int, out f3 text)
	RETURNS record
	AS 'select $1+1' LANGUAGE sql;
2025-02-01 03:25:14.395 UTC client backend[30789] pg_regress/plpgsql ERROR:  illegal backlink beginning with XX
2025-02-01 03:25:14.395 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_backlink_set(character,character) line 47 at RAISE
	PL/pgSQL function tg_backlink_a() line 17 at assignment
2025-02-01 03:25:14.395 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  update PSlot set backlink = 'XX.illegal' where slotname = 'PS.base.a1';
2025-02-01 03:25:14.397 UTC client backend[30789] pg_regress/plpgsql ERROR:  PS.not.there         does not exist
2025-02-01 03:25:14.397 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_slotlink_set(character,character) line 30 at RAISE
	PL/pgSQL function tg_slotlink_a() line 17 at assignment
2025-02-01 03:25:14.397 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  update PSlot set slotlink = 'PS.not.there' where slotname = 'PS.base.a1';
2025-02-01 03:25:14.399 UTC client backend[30790] pg_regress/rangefuncs ERROR:  could not determine polymorphic type because input has type unknown
2025-02-01 03:25:14.399 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  SELECT dup('xyz');
2025-02-01 03:25:14.399 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot change name of input parameter "f1"
2025-02-01 03:25:14.399 UTC client backend[30790] pg_regress/rangefuncs HINT:  Use DROP FUNCTION dup(anyelement) first.
2025-02-01 03:25:14.399 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE OR REPLACE FUNCTION dup (inout f2 anyelement, out f3 anyarray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2025-02-01 03:25:14.399 UTC client backend[30772] pg_regress/domain ERROR:  domain dom does not allow null values
2025-02-01 03:25:14.399 UTC client backend[30772] pg_regress/domain STATEMENT:  select * from domview;
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with ERROR:  WITH query "x" has 1 columns available but 2 columns specified at character 6
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with STATEMENT:  WITH x(n, b) AS (SELECT 1)
	SELECT * FROM x;
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT SELECT n+1 FROM x)
		SELECT * FROM x;
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 INTERSECT ALL SELECT n+1 FROM x)
		SELECT * FROM x;
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT SELECT n+1 FROM x)
		SELECT * FROM x;
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2025-02-01 03:25:14.400 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 EXCEPT ALL SELECT n+1 FROM x)
		SELECT * FROM x;
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with ERROR:  recursive query "x" does not have the form non-recursive-term UNION [ALL] recursive-term at character 16
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT n FROM x)
		SELECT * FROM x;
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within its non-recursive term at character 39
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT n FROM x UNION ALL SELECT 1)
		SELECT * FROM x;
2025-02-01 03:25:14.401 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dom violates check constraint "domchkgt6"
2025-02-01 03:25:14.401 UTC client backend[30772] pg_regress/domain STATEMENT:  select * from domview;
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within a subquery at character 54
2025-02-01 03:25:14.401 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (
	  WITH x1 AS (SELECT 1 FROM x)
	    SELECT 0
	    UNION
	    SELECT * FROM x1)
		SELECT * FROM x;
2025-02-01 03:25:14.402 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within its non-recursive term at character 55
2025-02-01 03:25:14.402 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (
	  (WITH x1 AS (SELECT 1 FROM x) SELECT * FROM x1)
	  UNION
	  SELECT 0)
		SELECT * FROM x;
2025-02-01 03:25:14.402 UTC client backend[30766] pg_regress/with ERROR:  ORDER BY in a recursive query is not implemented at character 63
2025-02-01 03:25:14.402 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (
	  SELECT 0 UNION SELECT 1
	  ORDER BY (SELECT n FROM x))
		SELECT * FROM x;
2025-02-01 03:25:14.402 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot determine result data type
2025-02-01 03:25:14.402 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  A result of type anyelement requires at least one input of type anyelement, anyarray, anynonarray, anyenum, anyrange, or anymultirange.
2025-02-01 03:25:14.402 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE FUNCTION bad (f1 int, out f2 anyelement, out f3 anyarray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2025-02-01 03:25:14.404 UTC client backend[30782] pg_regress/rowtypes ERROR:  column "f1" is of type integer but expression is of type compos at character 82
2025-02-01 03:25:14.404 UTC client backend[30782] pg_regress/rowtypes HINT:  You will need to rewrite or cast the expression.
2025-02-01 03:25:14.404 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  create function fcompos1(v compos) returns void as $$
	insert into compos values (v);  -- fail
	$$ language sql;
2025-02-01 03:25:14.404 UTC client backend[30789] pg_regress/plpgsql ERROR:  illegal slotlink beginning with XX
2025-02-01 03:25:14.404 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_slotlink_set(character,character) line 77 at RAISE
	PL/pgSQL function tg_slotlink_a() line 17 at assignment
2025-02-01 03:25:14.404 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  update PSlot set slotlink = 'XX.illegal' where slotname = 'PS.base.a1';
2025-02-01 03:25:14.405 UTC client backend[30789] pg_regress/plpgsql ERROR:  duplicate key value violates unique constraint "hslot_name"
2025-02-01 03:25:14.405 UTC client backend[30789] pg_regress/plpgsql DETAIL:  Key (slotname)=(HS.base.hub1.1      ) already exists.
2025-02-01 03:25:14.405 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  insert into HSlot values ('HS', 'base.hub1', 1, '');
2025-02-01 03:25:14.405 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_open(INV_WRITE) in a read-only transaction
2025-02-01 03:25:14.405 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_open(2121, x'20000'::int);
2025-02-01 03:25:14.405 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot determine result data type
2025-02-01 03:25:14.405 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  A result of type anycompatible requires at least one input of type anycompatible, anycompatiblearray, anycompatiblenonarray, anycompatiblerange, or anycompatiblemultirange.
2025-02-01 03:25:14.405 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  CREATE FUNCTION bad (f1 anyarray, out f2 anycompatible, out f3 anycompatiblearray)
	AS 'select $1, array[$1,$1]' LANGUAGE sql;
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql ERROR:  no manual manipulation of HSlot
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_hslot_biu() line 12 at RAISE
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  insert into HSlot values ('HS', 'base.hub1', 20, '');
2025-02-01 03:25:14.406 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_create() in a read-only transaction
2025-02-01 03:25:14.406 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_create(42);
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql ERROR:  no manual manipulation of HSlot
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_hslot_bd() line 12 at RAISE
2025-02-01 03:25:14.406 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  delete from HSlot;
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_creat() in a read-only transaction
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_creat(42);
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_unlink() in a read-only transaction
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_unlink(42);
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 95
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM y LEFT JOIN x ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 83
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM x RIGHT JOIN y ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within an outer join at character 83
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT a FROM y WHERE a = 1
		UNION ALL
		SELECT x.n+1 FROM x FULL JOIN y ON x.n = y.a WHERE n < 10)
	SELECT * FROM x;
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lowrite() in a read-only transaction
2025-02-01 03:25:14.407 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lowrite(42, 'x');
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within a subquery at character 114
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x
	                          WHERE n IN (SELECT * FROM x))
	  SELECT * FROM x;
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with ERROR:  aggregate functions are not allowed in a recursive query's recursive term at character 51
2025-02-01 03:25:14.407 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT count(*) FROM x)
	  SELECT * FROM x;
2025-02-01 03:25:14.407 UTC client backend[30789] pg_regress/plpgsql ERROR:  system "notthere" does not exist
2025-02-01 03:25:14.407 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_iface_biu() line 8 at RAISE
2025-02-01 03:25:14.407 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  insert into IFace values ('IF', 'notthere', 'eth0', '');
2025-02-01 03:25:14.408 UTC client backend[30766] pg_regress/with ERROR:  aggregate functions are not allowed in a recursive query's recursive term at character 51
2025-02-01 03:25:14.408 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT sum(n) FROM x)
	  SELECT * FROM x;
2025-02-01 03:25:14.408 UTC client backend[30766] pg_regress/with ERROR:  ORDER BY in a recursive query is not implemented at character 71
2025-02-01 03:25:14.408 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x ORDER BY 1)
	  SELECT * FROM x;
2025-02-01 03:25:14.409 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_import() in a read-only transaction
2025-02-01 03:25:14.409 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_import('/tmp/cirrus-ci-build/build/testrun/regress/regress/results/lotest.txt');
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  OFFSET in a recursive query is not implemented at character 78
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x LIMIT 10 OFFSET 1)
	  SELECT * FROM x;
2025-02-01 03:25:14.409 UTC client backend[30789] pg_regress/plpgsql ERROR:  IFace slotname "IF.orion.ethernet_interface_name_too_long" too long (20 char max)
2025-02-01 03:25:14.409 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function tg_iface_biu() line 14 at RAISE
2025-02-01 03:25:14.409 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  insert into IFace values ('IF', 'orion', 'ethernet_interface_name_too_long', '');
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  FOR UPDATE/SHARE in a recursive query is not implemented
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT n+1 FROM x FOR UPDATE)
	  SELECT * FROM x;
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "x" must not appear within a subquery at character 77
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE x(id) AS (values (1)
	    UNION ALL
	    SELECT (SELECT * FROM x) FROM x WHERE id < 5
	) SELECT * FROM x;
2025-02-01 03:25:14.409 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_truncate() in a read-only transaction
2025-02-01 03:25:14.409 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_truncate(42, 0);
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  mutual recursion between WITH items is not implemented at character 18
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE
	  x (id) AS (SELECT 1 UNION ALL SELECT id+1 FROM y WHERE id < 5),
	  y (id) AS (SELECT 1 UNION ALL SELECT id+1 FROM x WHERE id < 5)
	SELECT * FROM x;
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 140
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          UNION ALL
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 158
2025-02-01 03:25:14.409 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
		   SELECT * FROM
	       (SELECT i+1 FROM foo WHERE i < 10
	          UNION ALL
	       SELECT i+1 FROM foo WHERE i < 5) AS t
	) SELECT * FROM foo;
2025-02-01 03:25:14.410 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "foo" must not appear within EXCEPT at character 137
2025-02-01 03:25:14.410 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          EXCEPT
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2025-02-01 03:25:14.410 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "foo" must not appear more than once at character 140
2025-02-01 03:25:14.410 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	    (values (1)
	    UNION ALL
	       (SELECT i+1 FROM foo WHERE i < 10
	          INTERSECT
	       SELECT i+1 FROM foo WHERE i < 5)
	) SELECT * FROM foo;
2025-02-01 03:25:14.411 UTC client backend[30766] pg_regress/with ERROR:  recursive query "foo" column 1 has type integer in non-recursive term but type numeric overall at character 37
2025-02-01 03:25:14.411 UTC client backend[30766] pg_regress/with HINT:  Cast the output of the non-recursive term to the correct type.
2025-02-01 03:25:14.411 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	   (SELECT i FROM (VALUES(1),(2)) t(i)
	   UNION ALL
	   SELECT (i+1)::numeric(10,0) FROM foo WHERE i < 10)
	SELECT * FROM foo;
2025-02-01 03:25:14.411 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_truncate64() in a read-only transaction
2025-02-01 03:25:14.411 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_truncate64(42, 0);
2025-02-01 03:25:14.412 UTC client backend[30766] pg_regress/with ERROR:  recursive query "foo" column 1 has type numeric(3,0) in non-recursive term but type numeric overall at character 37
2025-02-01 03:25:14.412 UTC client backend[30766] pg_regress/with HINT:  Cast the output of the non-recursive term to the correct type.
2025-02-01 03:25:14.412 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE foo(i) AS
	   (SELECT i::numeric(3,0) FROM (VALUES(1),(2)) t(i)
	   UNION ALL
	   SELECT (i+1)::numeric(10,0) FROM foo WHERE i < 10)
	SELECT * FROM foo;
2025-02-01 03:25:14.415 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_from_bytea() in a read-only transaction
2025-02-01 03:25:14.415 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_from_bytea(0, 'x');
2025-02-01 03:25:14.415 UTC client backend[30774] pg_regress/largeobject ERROR:  cannot execute lo_put() in a read-only transaction
2025-02-01 03:25:14.415 UTC client backend[30774] pg_regress/largeobject STATEMENT:  SELECT lo_put(42, 0, 'x');
2025-02-01 03:25:14.416 UTC client backend[30782] pg_regress/rowtypes ERROR:  function text(fullname) does not exist at character 8
2025-02-01 03:25:14.416 UTC client backend[30782] pg_regress/rowtypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.416 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select text(fullname) from fullname;
2025-02-01 03:25:14.417 UTC client backend[30782] pg_regress/rowtypes ERROR:  column fullname.text does not exist at character 8
2025-02-01 03:25:14.417 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select fullname.text from fullname;
2025-02-01 03:25:14.417 UTC client backend[30766] pg_regress/with ERROR:  cannot refer to OLD within WITH query
2025-02-01 03:25:14.417 UTC client backend[30766] pg_regress/with STATEMENT:  CREATE RULE r2 AS ON UPDATE TO x DO INSTEAD
	    WITH t AS (SELECT OLD.*) UPDATE y SET a = t.n FROM t;
2025-02-01 03:25:14.417 UTC client backend[30782] pg_regress/rowtypes ERROR:  function text(record) does not exist at character 8
2025-02-01 03:25:14.417 UTC client backend[30782] pg_regress/rowtypes HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.417 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select text(row('Jim', 'Beam'));
2025-02-01 03:25:14.418 UTC client backend[30782] pg_regress/rowtypes ERROR:  could not identify column "text" in record data type at character 9
2025-02-01 03:25:14.418 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  select (row('Jim', 'Beam')).text;
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain STATEMENT:  select 'y1234'::dtop;
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain STATEMENT:  select 'y123'::dtop;
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain STATEMENT:  select 'yz23'::dtop;
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dtop_check"
2025-02-01 03:25:14.423 UTC client backend[30772] pg_regress/domain STATEMENT:  select 'xz23'::dtop;
2025-02-01 03:25:14.430 UTC client backend[30766] pg_regress/with ERROR:  relation "outermost" does not exist at character 96
2025-02-01 03:25:14.430 UTC client backend[30766] pg_regress/with DETAIL:  There is a WITH item named "outermost", but it cannot be referenced from this part of the query.
2025-02-01 03:25:14.430 UTC client backend[30766] pg_regress/with HINT:  Use WITH RECURSIVE, or re-order the WITH items to remove forward references.
2025-02-01 03:25:14.430 UTC client backend[30766] pg_regress/with STATEMENT:  WITH outermost(x) AS (
	  SELECT 1
	  UNION (WITH innermost as (SELECT 2)
	         SELECT * FROM outermost  -- fail
	         UNION SELECT * FROM innermost)
	)
	SELECT * FROM outermost ORDER BY 1;
2025-02-01 03:25:14.432 UTC client backend[30766] pg_regress/with ERROR:  recursive reference to query "outermost" must not appear within a subquery at character 69
2025-02-01 03:25:14.432 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE outermost(x) AS (
	  WITH innermost as (SELECT 2 FROM outermost) -- fail
	    SELECT * FROM innermost
	    UNION SELECT * from outermost
	)
	SELECT * FROM outermost ORDER BY 1;
2025-02-01 03:25:14.433 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(4)
2025-02-01 03:25:14.433 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dtest values('x1234');
2025-02-01 03:25:14.433 UTC client backend[30772] pg_regress/domain ERROR:  value too long for type character varying(4)
2025-02-01 03:25:14.433 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dtest values('y1234');
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dtest values('y123');
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dinter_check"
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dtest values('yz23');
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain ERROR:  value for domain dtop violates check constraint "dtop_check"
2025-02-01 03:25:14.434 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dtest values('xz23');
2025-02-01 03:25:14.438 UTC client backend[30790] pg_regress/rangefuncs LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp30790.0", size 140000
2025-02-01 03:25:14.438 UTC client backend[30790] pg_regress/rangefuncs CONTEXT:  SQL function "rngfunc1" statement 1
2025-02-01 03:25:14.438 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select t.a, t, t.a from rngfunc1(10000) t limit 1;
2025-02-01 03:25:14.438 UTC client backend[30790] pg_regress/rangefuncs LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp30790.1", size 277788
2025-02-01 03:25:14.438 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select t.a, t, t.a from rngfunc1(10000) t limit 1;
2025-02-01 03:25:14.461 UTC client backend[30772] pg_regress/domain ERROR:  domain str_domain does not allow null values
2025-02-01 03:25:14.461 UTC client backend[30772] pg_regress/domain STATEMENT:  alter table domain_test add column c str_domain;
2025-02-01 03:25:14.485 UTC client backend[30772] pg_regress/domain ERROR:  value for domain str_domain2 violates check constraint "str_domain2_check"
2025-02-01 03:25:14.485 UTC client backend[30772] pg_regress/domain STATEMENT:  alter table domain_test add column d str_domain2;
2025-02-01 03:25:14.485 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c" referenced in foreign key constraint does not exist
2025-02-01 03:25:14.485 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key(c) references attmp2 match full;
2025-02-01 03:25:14.486 UTC client backend[30781] pg_regress/alter_table ERROR:  column "b" referenced in foreign key constraint does not exist
2025-02-01 03:25:14.486 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key(a) references attmp2(b) match full;
2025-02-01 03:25:14.487 UTC client backend[30781] pg_regress/alter_table ERROR:  insert or update on table "attmp3" violates foreign key constraint "attmpconstr"
2025-02-01 03:25:14.487 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (a)=(5) is not present in table "attmp2".
2025-02-01 03:25:14.487 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 add constraint attmpconstr foreign key (a) references attmp2 match full;
2025-02-01 03:25:14.489 UTC client backend[30766] pg_regress/with ERROR:  INSERT ... SELECT rule actions are not supported for queries having data-modifying statements in WITH
2025-02-01 03:25:14.489 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t1 AS ( DELETE FROM bug6051 RETURNING * )
	INSERT INTO bug6051 SELECT * FROM t1;
2025-02-01 03:25:14.492 UTC client backend[30781] pg_regress/alter_table ERROR:  insert or update on table "attmp3" violates foreign key constraint "attmpconstr"
2025-02-01 03:25:14.492 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (a)=(5) is not present in table "attmp2".
2025-02-01 03:25:14.492 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 validate constraint attmpconstr;
2025-02-01 03:25:14.495 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row
2025-02-01 03:25:14.495 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 ADD CONSTRAINT b_greater_than_ten CHECK (b > 10);
2025-02-01 03:25:14.496 UTC client backend[30772] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2025-02-01 03:25:14.496 UTC client backend[30772] pg_regress/domain STATEMENT:  execute s1(0);
2025-02-01 03:25:14.496 UTC client backend[30772] pg_regress/domain ERROR:  domain pos_int does not allow null values
2025-02-01 03:25:14.496 UTC client backend[30772] pg_regress/domain STATEMENT:  execute s1(NULL);
2025-02-01 03:25:14.497 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "b_greater_than_ten" of relation "attmp3" is violated by some row
2025-02-01 03:25:14.497 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 VALIDATE CONSTRAINT b_greater_than_ten;
2025-02-01 03:25:14.497 UTC client backend[30789] pg_regress/plpgsql ERROR:  operator does not exist: point + integer at character 3
2025-02-01 03:25:14.497 UTC client backend[30789] pg_regress/plpgsql HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.497 UTC client backend[30789] pg_regress/plpgsql QUERY:  x + 1
2025-02-01 03:25:14.497 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function f1(anyelement) line 3 at RETURN
2025-02-01 03:25:14.497 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select f1(point(3,4));
2025-02-01 03:25:14.499 UTC client backend[30782] pg_regress/rowtypes ERROR:  missing FROM-clause entry for table "d" at character 8
2025-02-01 03:25:14.499 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  SELECT d.a FROM (SELECT compositetable AS d FROM compositetable) s;
2025-02-01 03:25:14.499 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot validate NOT ENFORCED constraint
2025-02-01 03:25:14.499 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 VALIDATE CONSTRAINT b_greater_than_ten_not_enforced;
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']);
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs ERROR:  return type mismatch in function declared to return record
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Final statement returns integer instead of point at column 1.
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs CONTEXT:  SQL function "array_to_set" during startup
2025-02-01 03:25:14.501 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text);
2025-02-01 03:25:14.503 UTC client backend[30772] pg_regress/domain ERROR:  domain pos_int does not allow null values
2025-02-01 03:25:14.503 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization
2025-02-01 03:25:14.503 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(3);
2025-02-01 03:25:14.503 UTC client backend[30782] pg_regress/rowtypes ERROR:  column "ctid" not found in data type compositetable at character 9
2025-02-01 03:25:14.503 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  SELECT (d).ctid FROM (SELECT compositetable AS d FROM compositetable) s;
2025-02-01 03:25:14.504 UTC client backend[30782] pg_regress/rowtypes ERROR:  column "nonexistent" not found in data type compositetable at character 9
2025-02-01 03:25:14.504 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  SELECT (NULL::compositetable).nonexistent;
2025-02-01 03:25:14.504 UTC client backend[30790] pg_regress/rangefuncs ERROR:  return type mismatch in function declared to return record
2025-02-01 03:25:14.504 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Final statement returns integer instead of point at column 1.
2025-02-01 03:25:14.504 UTC client backend[30790] pg_regress/rangefuncs CONTEXT:  SQL function "array_to_set" during inlining
2025-02-01 03:25:14.504 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from array_to_set(array['one', 'two']) as t(f1 point,f2 text);
2025-02-01 03:25:14.505 UTC client backend[30782] pg_regress/rowtypes ERROR:  column "oid" not found in data type compositetable at character 9
2025-02-01 03:25:14.505 UTC client backend[30782] pg_regress/rowtypes STATEMENT:  SELECT (NULL::compositetable).oid;
2025-02-01 03:25:14.505 UTC client backend[30772] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2025-02-01 03:25:14.505 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 2 during statement block local variable initialization
2025-02-01 03:25:14.505 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(3);
2025-02-01 03:25:14.508 UTC client backend[30772] pg_regress/domain ERROR:  domain pos_int does not allow null values
2025-02-01 03:25:14.508 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(null);
2025-02-01 03:25:14.508 UTC client backend[30772] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2025-02-01 03:25:14.508 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(0);
2025-02-01 03:25:14.509 UTC client backend[30772] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2025-02-01 03:25:14.509 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) line 4 at assignment
2025-02-01 03:25:14.509 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(1);
2025-02-01 03:25:14.509 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "b_le_20" of relation "attmp6" is violated by some row
2025-02-01 03:25:14.509 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp3 VALIDATE CONSTRAINT b_le_20;
2025-02-01 03:25:14.510 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2025-02-01 03:25:14.510 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc();
2025-02-01 03:25:14.512 UTC client backend[30789] pg_regress/plpgsql ERROR:  cannot determine element type of "anyarray" argument
2025-02-01 03:25:14.512 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select f1(stavalues1) from pg_statistic;
2025-02-01 03:25:14.513 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is required for functions returning "record" at character 15
2025-02-01 03:25:14.513 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc();
2025-02-01 03:25:14.514 UTC client backend[30772] pg_regress/domain ERROR:  value for domain pos_int violates check constraint "pos_int_check"
2025-02-01 03:25:14.514 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function doubledecrement(pos_int) while casting return value to function's return type
2025-02-01 03:25:14.514 UTC client backend[30772] pg_regress/domain STATEMENT:  select doubledecrement(2);
2025-02-01 03:25:14.518 UTC client backend[30789] pg_regress/plpgsql ERROR:  PL/pgSQL functions cannot accept type anyarray
2025-02-01 03:25:14.518 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "f1" near line 1
2025-02-01 03:25:14.518 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select f1(stavalues1) from pg_statistic;
2025-02-01 03:25:14.523 UTC client backend[30789] pg_regress/plpgsql ERROR:  cannot determine result data type
2025-02-01 03:25:14.523 UTC client backend[30789] pg_regress/plpgsql DETAIL:  A result of type anyrange requires at least one input of type anyrange or anymultirange.
2025-02-01 03:25:14.523 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function f1(x anyelement) returns anyrange as $$
	begin
	  return array[x + 1, x + 2];
	end$$ language plpgsql;
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is redundant for a function returning a named composite type at character 34
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from testrngfunc() as t(f1 int8,f2 int8);
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is redundant for a function with OUT parameters at character 38
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from pg_get_keywords() as t(f1 int8,f2 int8);
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs ERROR:  a column definition list is only allowed for functions returning "record" at character 27
2025-02-01 03:25:14.524 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from sin(3) as t(f1 int8,f2 int8);
2025-02-01 03:25:14.526 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "check_a_is_2" of relation "parent_noinh_convalid" is violated by some row
2025-02-01 03:25:14.526 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table parent_noinh_convalid validate constraint check_a_is_2;
2025-02-01 03:25:14.527 UTC client backend[30772] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2025-02-01 03:25:14.527 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2025-02-01 03:25:14.532 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot drop column moredrop of table users because other objects depend on it
2025-02-01 03:25:14.532 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  view usersview depends on column moredrop of table users
2025-02-01 03:25:14.532 UTC client backend[30790] pg_regress/rangefuncs HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:14.532 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  alter table users drop column moredrop;
2025-02-01 03:25:14.536 UTC client backend[30790] pg_regress/rangefuncs ERROR:  attribute 5 of type record has been dropped
2025-02-01 03:25:14.536 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from usersview;
2025-02-01 03:25:14.536 UTC client backend[30790] pg_regress/rangefuncs ERROR:  cannot alter type of a column used by a view or rule
2025-02-01 03:25:14.536 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  rule _RETURN on view usersview depends on column "seq"
2025-02-01 03:25:14.536 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  alter table users alter column seq type numeric;
2025-02-01 03:25:14.538 UTC client backend[30781] pg_regress/alter_table ERROR:  there is no unique constraint matching given keys for referenced table "attmp4"
2025-02-01 03:25:14.538 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE attmp5 add constraint attmpconstr foreign key(a) references attmp4(a) match full;
2025-02-01 03:25:14.541 UTC client backend[30790] pg_regress/rangefuncs ERROR:  attribute 2 of type record has wrong type
2025-02-01 03:25:14.541 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Table has type numeric, but query expects integer.
2025-02-01 03:25:14.541 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from usersview;
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned type integer at ordinal position 2, but query expects numeric.
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from rngfuncbar();
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 2.
2025-02-01 03:25:14.546 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from rngfuncbar();
2025-02-01 03:25:14.547 UTC client backend[30772] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2025-02-01 03:25:14.547 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2025-02-01 03:25:14.552 UTC client backend[30789] pg_regress/plpgsql ERROR:  function f1(int4range, integer, numeric) does not exist at character 8
2025-02-01 03:25:14.552 UTC client backend[30789] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.552 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select f1(int4range(42, 49), 11, 4.5) as fail;
2025-02-01 03:25:14.555 UTC client backend[30789] pg_regress/plpgsql ERROR:  cannot determine result data type
2025-02-01 03:25:14.555 UTC client backend[30789] pg_regress/plpgsql DETAIL:  A result of type anycompatiblerange requires at least one input of type anycompatiblerange or anycompatiblemultirange.
2025-02-01 03:25:14.555 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function f1(x anycompatible) returns anycompatiblerange as $$
	begin
	  return array[x + 1, x + 2];
	end$$ language plpgsql;
2025-02-01 03:25:14.556 UTC client backend[30772] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2025-02-01 03:25:14.556 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2025-02-01 03:25:14.557 UTC client backend[30766] pg_regress/with ERROR:  WITH RECURSIVE is not supported for MERGE statement
2025-02-01 03:25:14.557 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE cte_basic AS (SELECT 1 a, 'cte_basic val' b)
	MERGE INTO m USING (select 0 k, 'merge source SubPlan' v) o ON m.k=o.k
	WHEN MATCHED THEN UPDATE SET v = (SELECT b || ' merge update' FROM cte_basic WHERE cte_basic.a = m.k LIMIT 1)
	WHEN NOT MATCHED THEN INSERT VALUES(o.k, o.v);
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 2.
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int);
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned row contains 3 attributes, but query expects 4.
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int, f int, g int);
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned type integer at ordinal position 3, but query expects double precision.
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  with a(b) as (values (row(1,2,3)))
	select * from a, coalesce(b) as c(d int, e int, f float);
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs ERROR:  function return row and query-specified return row do not match
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs DETAIL:  Returned row contains 1 attribute, but query expects 2.
2025-02-01 03:25:14.562 UTC client backend[30790] pg_regress/rangefuncs STATEMENT:  select * from int8_tbl, coalesce(row(1)) as (a int, b int);
2025-02-01 03:25:14.573 UTC client backend[30772] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2025-02-01 03:25:14.573 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2025-02-01 03:25:14.573 UTC client backend[30789] pg_regress/plpgsql ERROR:  function f1(integer, numeric[], integer, numeric) does not exist at character 48
2025-02-01 03:25:14.573 UTC client backend[30789] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:14.573 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select x, pg_typeof(x), y, pg_typeof(y)
	  from f1(11, array[1, 2.2], 42, 34.5);
2025-02-01 03:25:14.575 UTC client backend[30789] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function with OUT parameters at character 74
2025-02-01 03:25:14.575 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function f1(in i int, out j int) returns int as $$
	begin
	  return i+1;
	end$$ language plpgsql;
2025-02-01 03:25:14.598 UTC client backend[30772] pg_regress/domain ERROR:  cannot alter type "posint" because column "ddtest2.f1" uses it
2025-02-01 03:25:14.598 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c1 check(value >= 0);
2025-02-01 03:25:14.607 UTC client backend[30772] pg_regress/domain ERROR:  value for domain posint2 violates check constraint "posint2_check"
2025-02-01 03:25:14.607 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into ddtest2 values(11);
2025-02-01 03:25:14.607 UTC client backend[30772] pg_regress/domain ERROR:  value for domain posint2 violates check constraint "c1"
2025-02-01 03:25:14.607 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into ddtest2 values(-2);
2025-02-01 03:25:14.608 UTC client backend[30772] pg_regress/domain ERROR:  column "f1" of table "ddtest2" contains values that violate the new constraint
2025-02-01 03:25:14.608 UTC client backend[30772] pg_regress/domain STATEMENT:  alter domain posint add constraint c2 check(value >= 10);
2025-02-01 03:25:14.614 UTC client backend[30772] pg_regress/domain ERROR:  numeric field overflow
2025-02-01 03:25:14.614 UTC client backend[30772] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2025-02-01 03:25:14.614 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2025-02-01 03:25:14.614 UTC client backend[30772] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2025-02-01 03:25:14.616 UTC client backend[30772] pg_regress/domain ERROR:  numeric field overflow
2025-02-01 03:25:14.616 UTC client backend[30772] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2025-02-01 03:25:14.616 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2025-02-01 03:25:14.616 UTC client backend[30772] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2025-02-01 03:25:14.620 UTC client backend[30772] pg_regress/domain ERROR:  numeric field overflow
2025-02-01 03:25:14.620 UTC client backend[30772] pg_regress/domain DETAIL:  A field with precision 4, scale 2 must round to an absolute value less than 10^2.
2025-02-01 03:25:14.620 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(numeric) line 5 at assignment
2025-02-01 03:25:14.620 UTC client backend[30772] pg_regress/domain STATEMENT:  select array_elem_check(121.00);
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer.
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer.
2025-02-01 03:25:14.624 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable(ptest1);
2025-02-01 03:25:14.625 UTC client backend[30772] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2025-02-01 03:25:14.625 UTC client backend[30772] pg_regress/domain STATEMENT:  select array[2,1]::orderedpair;
2025-02-01 03:25:14.632 UTC client backend[30781] pg_regress/alter_table ERROR:  insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey"
2025-02-01 03:25:14.632 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (ftest1)=(43) is not present in table "pktable".
2025-02-01 03:25:14.632 UTC client backend[30781] pg_regress/alter_table STATEMENT:  INSERT INTO FKTABLE VALUES(43);
2025-02-01 03:25:14.633 UTC client backend[30772] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2025-02-01 03:25:14.633 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into op values (array[2,1]);
2025-02-01 03:25:14.634 UTC client backend[30772] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2025-02-01 03:25:14.634 UTC client backend[30772] pg_regress/domain STATEMENT:  update op set f1[2] = 0;
2025-02-01 03:25:14.637 UTC client backend[30772] pg_regress/domain ERROR:  value for domain orderedpair violates check constraint "orderedpair_check"
2025-02-01 03:25:14.637 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function array_elem_check(integer) line 5 at assignment
2025-02-01 03:25:14.637 UTC client backend[30772] pg_regress/domain STATEMENT:  select array_elem_check(-1);
2025-02-01 03:25:14.638 UTC client backend[30766] pg_regress/with ERROR:  recursive query "t" must not contain data-modifying statements at character 16
2025-02-01 03:25:14.638 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE t AS (
		INSERT INTO y
			SELECT * FROM t
	)
	VALUES(FALSE);
2025-02-01 03:25:14.638 UTC client backend[30766] pg_regress/with ERROR:  WITH query "t" does not have a RETURNING clause at character 54
2025-02-01 03:25:14.638 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	SELECT * FROM t;
2025-02-01 03:25:14.639 UTC client backend[30766] pg_regress/with ERROR:  recursive query "t" must not contain data-modifying statements at character 16
2025-02-01 03:25:14.639 UTC client backend[30766] pg_regress/with STATEMENT:  WITH RECURSIVE t(action, a) AS (
		MERGE INTO y USING (VALUES (11)) v(a) ON y.a = v.a
			WHEN NOT MATCHED THEN INSERT VALUES (v.a)
			RETURNING merge_action(), (SELECT a FROM t)
	)
	SELECT * FROM t;
2025-02-01 03:25:14.639 UTC client backend[30766] pg_regress/with ERROR:  WITH clause containing a data-modifying statement must be at the top level at character 23
2025-02-01 03:25:14.639 UTC client backend[30766] pg_regress/with STATEMENT:  SELECT * FROM (
		WITH t AS (UPDATE y SET a=a+1 RETURNING *)
		SELECT * FROM t
	) ss;
2025-02-01 03:25:14.639 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_fkey" cannot be implemented
2025-02-01 03:25:14.639 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: numeric and integer.
2025-02-01 03:25:14.639 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references pktable;
2025-02-01 03:25:14.640 UTC client backend[30766] pg_regress/with ERROR:  conditional DO INSTEAD rules are not supported for data-modifying statements in WITH
2025-02-01 03:25:14.640 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2025-02-01 03:25:14.640 UTC client backend[30772] pg_regress/domain ERROR:  value for domain di violates check constraint "pos"
2025-02-01 03:25:14.640 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function dom_check(integer) line 4 at assignment
2025-02-01 03:25:14.640 UTC client backend[30772] pg_regress/domain STATEMENT:  select dom_check(0);
2025-02-01 03:25:14.642 UTC client backend[30766] pg_regress/with ERROR:  DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH
2025-02-01 03:25:14.642 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2025-02-01 03:25:14.643 UTC client backend[30766] pg_regress/with ERROR:  DO INSTEAD NOTIFY rules are not supported for data-modifying statements in WITH
2025-02-01 03:25:14.643 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2025-02-01 03:25:14.644 UTC client backend[30766] pg_regress/with ERROR:  DO ALSO rules are not supported for data-modifying statements in WITH
2025-02-01 03:25:14.644 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2025-02-01 03:25:14.645 UTC client backend[30766] pg_regress/with ERROR:  multi-statement DO INSTEAD rules are not supported for data-modifying statements in WITH
2025-02-01 03:25:14.645 UTC client backend[30766] pg_regress/with STATEMENT:  WITH t AS (
		INSERT INTO y VALUES(0)
	)
	VALUES(FALSE);
2025-02-01 03:25:14.645 UTC client backend[30772] pg_regress/domain ERROR:  value for domain di violates check constraint "pos"
2025-02-01 03:25:14.645 UTC client backend[30772] pg_regress/domain CONTEXT:  PL/pgSQL function dom_check(integer) line 4 at assignment
2025-02-01 03:25:14.645 UTC client backend[30772] pg_regress/domain STATEMENT:  select dom_check(0);
2025-02-01 03:25:14.646 UTC client backend[30766] pg_regress/with ERROR:  syntax error at or near "with" at character 19
2025-02-01 03:25:14.646 UTC client backend[30766] pg_regress/with STATEMENT:  create table foo (with baz);
2025-02-01 03:25:14.646 UTC client backend[30766] pg_regress/with ERROR:  syntax error at or near "with" at character 19
2025-02-01 03:25:14.646 UTC client backend[30766] pg_regress/with STATEMENT:  create table foo (with ordinality);
2025-02-01 03:25:14.647 UTC client backend[30766] pg_regress/with ERROR:  relation "with_test" does not exist at character 43
2025-02-01 03:25:14.647 UTC client backend[30766] pg_regress/with STATEMENT:  WITH with_test AS (SELECT 42) INSERT INTO with_test VALUES (1);
2025-02-01 03:25:14.651 UTC client backend[30772] pg_regress/domain ERROR:  value for domain inotnull violates check constraint "inotnull_check"
2025-02-01 03:25:14.651 UTC client backend[30772] pg_regress/domain STATEMENT:  select null::inotnull;
2025-02-01 03:25:14.655 UTC client backend[30781] pg_regress/alter_table ERROR:  insert or update on table "fktable" violates foreign key constraint "fktable_ftest1_fkey"
2025-02-01 03:25:14.655 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (ftest1)=(43) is not present in table "pktable".
2025-02-01 03:25:14.655 UTC client backend[30781] pg_regress/alter_table STATEMENT:  INSERT INTO FKTABLE VALUES(43);
2025-02-01 03:25:14.660 UTC client backend[30772] pg_regress/domain ERROR:  value for domain inotnull violates check constraint "inotnull_check"
2025-02-01 03:25:14.660 UTC client backend[30772] pg_regress/domain STATEMENT:  insert into dom_table values (null);
2025-02-01 03:25:14.665 UTC client backend[30772] pg_regress/domain ERROR:  specifying constraint enforceability not supported for domains at character 90
2025-02-01 03:25:14.665 UTC client backend[30772] pg_regress/domain STATEMENT:  CREATE DOMAIN constraint_enforced_dom AS int CONSTRAINT the_constraint CHECK (value > 0) ENFORCED;
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain ERROR:  specifying constraint enforceability not supported for domains at character 94
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain STATEMENT:  CREATE DOMAIN constraint_not_enforced_dom AS int CONSTRAINT the_constraint CHECK (value > 0) NOT ENFORCED;
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain ERROR:  CHECK constraints cannot be marked ENFORCED at character 86
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain STATEMENT:  ALTER DOMAIN constraint_enforced_dom ADD CONSTRAINT the_constraint CHECK (value > 0) ENFORCED;
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain ERROR:  CHECK constraints cannot be marked NOT ENFORCED at character 86
2025-02-01 03:25:14.666 UTC client backend[30772] pg_regress/domain STATEMENT:  ALTER DOMAIN constraint_enforced_dom ADD CONSTRAINT the_constraint CHECK (value > 0) NOT ENFORCED;
2025-02-01 03:25:14.668 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2025-02-01 03:25:14.668 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer.
2025-02-01 03:25:14.668 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2) references pktable;
2025-02-01 03:25:14.672 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2025-02-01 03:25:14.672 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest1" of the referenced table are of incompatible types: cidr and integer.
2025-02-01 03:25:14.672 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
	     references pktable(ptest1, ptest2);
2025-02-01 03:25:14.677 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest1_ftest2_fkey" cannot be implemented
2025-02-01 03:25:14.677 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest1" of the referencing table and "ptest2" of the referenced table are of incompatible types: integer and inet.
2025-02-01 03:25:14.677 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1, ftest2)
	     references pktable(ptest2, ptest1);
2025-02-01 03:25:14.678 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "fktable_ftest2_ftest1_fkey" cannot be implemented
2025-02-01 03:25:14.678 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "ftest2" of the referencing table and "ptest1" of the referenced table are of incompatible types: inet and integer.
2025-02-01 03:25:14.678 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest2, ftest1)
	     references pktable(ptest1, ptest2);
2025-02-01 03:25:14.688 UTC client backend[30789] pg_regress/plpgsql ERROR:  cursor "test1" does not exist
2025-02-01 03:25:14.688 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  fetch next from test1;
2025-02-01 03:25:14.692 UTC client backend[30789] pg_regress/plpgsql ERROR:  variable "rc" is declared CONSTANT
2025-02-01 03:25:14.692 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function constant_refcursor() line 5 at OPEN
2025-02-01 03:25:14.692 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select constant_refcursor();
2025-02-01 03:25:14.703 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for parameter "param2" of cursor "c1" specified more than once at character 198
2025-02-01 03:25:14.703 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test3() returns void as $$
	declare
	    c1 cursor (param1 int, param2 int) for select * from rc_test where a > param1 and b > param2;
	begin
	    open c1(param2 := 20, 21);
	end
	$$ language plpgsql;
2025-02-01 03:25:14.703 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc_test1"
2025-02-01 03:25:14.703 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (2).
2025-02-01 03:25:14.703 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2025-02-01 03:25:14.704 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for parameter "param1" of cursor "c1" specified more than once at character 188
2025-02-01 03:25:14.704 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test4() returns void as $$
	declare
	    c1 cursor (param1 int, param2 int) for select * from rc_test where a > param1 and b > param2;
	begin
	    open c1(20, param1 := 21);
	end
	$$ language plpgsql;
2025-02-01 03:25:14.705 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for parameter "p2" of cursor "c1" specified more than once at character 191
2025-02-01 03:25:14.705 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test5() returns void as $$
	declare
	  c1 cursor (p1 int, p2 int) for
	    select * from tenk1 where thousand = p1 and tenthous = p2;
	begin
	  open c1 (p2 := 77, p2 := 42);
	end
	$$ language plpgsql;
2025-02-01 03:25:14.705 UTC client backend[30789] pg_regress/plpgsql ERROR:  not enough arguments for cursor "c1" at character 189
2025-02-01 03:25:14.705 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function namedparmcursor_test6() returns void as $$
	declare
	  c1 cursor (p1 int, p2 int) for
	    select * from tenk1 where thousand = p1 and tenthous = p2;
	begin
	  open c1 (p2 := 77);
	end
	$$ language plpgsql;
2025-02-01 03:25:14.707 UTC client backend[30789] pg_regress/plpgsql ERROR:  division by zero
2025-02-01 03:25:14.707 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL expression "42/0 AS p1, 77 AS p2"
	PL/pgSQL function namedparmcursor_test7() line 6 at OPEN
2025-02-01 03:25:14.707 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select namedparmcursor_test7();
2025-02-01 03:25:14.708 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "atacc_test1" of relation "atacc1" is violated by some row
2025-02-01 03:25:14.708 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 check (test>3);
2025-02-01 03:25:14.711 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test1" does not exist
2025-02-01 03:25:14.711 UTC client backend[30781] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "atacc1.test".
2025-02-01 03:25:14.711 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 check (test1>3);
2025-02-01 03:25:14.714 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc_test1"
2025-02-01 03:25:14.714 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (4, 4, 2).
2025-02-01 03:25:14.714 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2,test3) values (4,4,2);
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql ERROR:  too many parameters specified for RAISE
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "raise_test1" near line 3
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function raise_test1(int) returns int as $$
	begin
	    raise notice 'This message has too many parameters!', $1;
	    return $1;
	end;
	$$ language plpgsql;
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql ERROR:  too few parameters specified for RAISE
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  compilation of PL/pgSQL function "raise_test2" near line 3
2025-02-01 03:25:14.718 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function raise_test2(int) returns int as $$
	begin
	    raise notice 'This message has too few parameters: %, %, %', $1, $1;
	    return $1;
	end;
	$$ language plpgsql;
2025-02-01 03:25:14.720 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_check"
2025-02-01 03:25:14.720 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (4, 3).
2025-02-01 03:25:14.720 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (3, 4);
2025-02-01 03:25:14.743 UTC client backend[30789] pg_regress/plpgsql ERROR:  syntax error at or near "Johnny" at character 83
2025-02-01 03:25:14.743 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function bad_sql1() returns int as $$
	declare a int;
	begin
	    a := 5;
	    Johnny Yuma;
	    a := 10;
	    return a;
	end$$ language plpgsql;
2025-02-01 03:25:14.746 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc2" violates check constraint "foo"
2025-02-01 03:25:14.746 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (-3).
2025-02-01 03:25:14.746 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc2 (test2) values (-3);
2025-02-01 03:25:14.761 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc3" violates check constraint "foo"
2025-02-01 03:25:14.761 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, -3, null).
2025-02-01 03:25:14.761 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc3 (test2) values (-3);
2025-02-01 03:25:14.762 UTC client backend[30789] pg_regress/plpgsql ERROR:  syntax error at or near "the" at character 99
2025-02-01 03:25:14.762 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function bad_sql2() returns int as $$
	declare r record;
	begin
	    for r in select I fought the law, the law won LOOP
	        raise notice 'in loop';
	    end loop;
	    return 5;
	end;$$ language plpgsql;
2025-02-01 03:25:14.766 UTC client backend[30789] pg_regress/plpgsql ERROR:  missing expression at or near ";" at character 74
2025-02-01 03:25:14.766 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function missing_return_expr() returns int as $$
	begin
	    return ;
	end;$$ language plpgsql;
2025-02-01 03:25:14.767 UTC client backend[30789] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function returning void at character 72
2025-02-01 03:25:14.767 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create function void_return_expr() returns void as $$
	begin
	    return 5;
	end;$$ language plpgsql;
2025-02-01 03:25:14.786 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "atacc2" is not a parent of relation "atacc3"
2025-02-01 03:25:14.786 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc3 no inherit atacc2;
2025-02-01 03:25:14.798 UTC client backend[30789] pg_regress/plpgsql ERROR:  control reached end of function without RETURN
2025-02-01 03:25:14.798 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function missing_return_expr()
2025-02-01 03:25:14.798 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select missing_return_expr();
2025-02-01 03:25:14.798 UTC client backend[30781] pg_regress/alter_table ERROR:  child table is missing constraint "foo"
2025-02-01 03:25:14.798 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2025-02-01 03:25:14.800 UTC client backend[30781] pg_regress/alter_table ERROR:  child table is missing column "test2"
2025-02-01 03:25:14.800 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2025-02-01 03:25:14.800 UTC client backend[30781] pg_regress/alter_table ERROR:  child table "atacc3" has different type for column "test2"
2025-02-01 03:25:14.800 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2025-02-01 03:25:14.810 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "atacc2" would be inherited from more than once
2025-02-01 03:25:14.810 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc3 inherit atacc2;
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table ERROR:  circular inheritance not allowed
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table DETAIL:  "atacc3" is already a child of "atacc2".
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc2 inherit atacc3;
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table ERROR:  circular inheritance not allowed
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table DETAIL:  "atacc2" is already a child of "atacc2".
2025-02-01 03:25:14.811 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc2 inherit atacc2;
2025-02-01 03:25:14.819 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "foo"
2025-02-01 03:25:14.819 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (-3).
2025-02-01 03:25:14.819 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (-3);
2025-02-01 03:25:14.820 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "foo" of relation "atacc2" is violated by some row
2025-02-01 03:25:14.820 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc2 add constraint foo check (test>0) no inherit;
2025-02-01 03:25:14.830 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2025-02-01 03:25:14.830 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(2) already exists.
2025-02-01 03:25:14.830 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2025-02-01 03:25:14.833 UTC client backend[30781] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2025-02-01 03:25:14.833 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(0) is duplicated.
2025-02-01 03:25:14.833 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter column test type integer using 0;
2025-02-01 03:25:14.839 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "sqlstate" does not exist at character 1
2025-02-01 03:25:14.839 UTC client backend[30789] pg_regress/plpgsql QUERY:  sqlstate
2025-02-01 03:25:14.839 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function excpt_test1() line 3 at RAISE
2025-02-01 03:25:14.839 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select excpt_test1();
2025-02-01 03:25:14.842 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "sqlstate" does not exist at character 1
2025-02-01 03:25:14.842 UTC client backend[30789] pg_regress/plpgsql QUERY:  sqlstate
2025-02-01 03:25:14.842 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function excpt_test2() line 5 at RAISE
2025-02-01 03:25:14.842 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select excpt_test2();
2025-02-01 03:25:14.844 UTC client backend[30781] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2025-02-01 03:25:14.844 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(2) is duplicated.
2025-02-01 03:25:14.844 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 unique (test);
2025-02-01 03:25:14.851 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test1" named in key does not exist
2025-02-01 03:25:14.851 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 unique (test1);
2025-02-01 03:25:14.856 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2025-02-01 03:25:14.856 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test, test2)=(4, 4) already exists.
2025-02-01 03:25:14.856 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (4,4);
2025-02-01 03:25:14.885 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc1_test_key"
2025-02-01 03:25:14.885 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(3) already exists.
2025-02-01 03:25:14.885 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (2, 3);
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(2) already exists.
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values (2);
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (4, null).
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test) values(NULL);
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table ERROR:  multiple primary keys for table "atacc1" are not allowed
2025-02-01 03:25:14.903 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_oid1 primary key(id);
2025-02-01 03:25:14.918 UTC client backend[30781] pg_regress/alter_table ERROR:  could not create unique index "atacc_test1"
2025-02-01 03:25:14.918 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(2) is duplicated.
2025-02-01 03:25:14.918 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test);
2025-02-01 03:25:14.922 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test" of relation "atacc1" contains null values
2025-02-01 03:25:14.922 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test);
2025-02-01 03:25:14.927 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test1" of relation "atacc1" does not exist
2025-02-01 03:25:14.927 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test1 primary key (test1);
2025-02-01 03:25:14.936 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test2" of relation "atacc1" contains null values
2025-02-01 03:25:14.936 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add column test2 int primary key;
2025-02-01 03:25:14.936 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:14.936 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:14.936 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2025-02-01 03:25:14.936 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.967 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned no rows
2025-02-01 03:25:14.967 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2025-02-01 03:25:14.967 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.969 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:14.969 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:14.969 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2025-02-01 03:25:14.969 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.978 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned no rows
2025-02-01 03:25:14.978 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2025-02-01 03:25:14.978 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.980 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:14.980 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2025-02-01 03:25:14.980 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.985 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned no rows
2025-02-01 03:25:14.985 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2025-02-01 03:25:14.985 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2025-02-01 03:25:14.985 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.991 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned no rows
2025-02-01 03:25:14.991 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = '''Valame Dios!'' dijo Sancho; ''no le dije yo a vuestra merced que mirase bien lo que hacia?'''
2025-02-01 03:25:14.991 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2025-02-01 03:25:14.991 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.993 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:14.993 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2025-02-01 03:25:14.993 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:14.993 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 8 at SQL statement
2025-02-01 03:25:14.993 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.995 UTC client backend[30781] pg_regress/alter_table ERROR:  check constraint "atacc1_chk" of relation "atacc1" is violated by some row
2025-02-01 03:25:14.995 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 validate constraint atacc1_chk, alter a type int;
2025-02-01 03:25:14.996 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:14.996 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:14.996 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at SQL statement
2025-02-01 03:25:14.996 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:14.998 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned no rows
2025-02-01 03:25:14.998 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: $1 = '0', $2 = 'foo'
2025-02-01 03:25:14.998 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2025-02-01 03:25:14.998 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:15.000 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:15.000 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: $1 = '1'
2025-02-01 03:25:15.000 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2025-02-01 03:25:15.000 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:15.001 UTC client backend[30781] pg_regress/alter_table ERROR:  multiple primary keys for table "atacc1" are not allowed
2025-02-01 03:25:15.001 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add constraint atacc_test2 primary key (test);
2025-02-01 03:25:15.002 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:15.002 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 5 at EXECUTE
2025-02-01 03:25:15.002 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc_test1"
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test, test2)=(4, 4) already exists.
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (4,4);
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, 3).
2025-02-01 03:25:15.002 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (NULL,3);
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "test2" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (3, null).
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (3, NULL);
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, null).
2025-02-01 03:25:15.004 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test,test2) values (NULL,NULL);
2025-02-01 03:25:15.005 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:15.005 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:15.005 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 10 at SQL statement
2025-02-01 03:25:15.005 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:15.009 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:15.009 UTC client backend[30789] pg_regress/plpgsql DETAIL:  parameters: p1 = '2', p3 = 'foo'
2025-02-01 03:25:15.009 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:15.009 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stricttest() line 10 at SQL statement
2025-02-01 03:25:15.009 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stricttest();
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table ERROR:  duplicate key value violates unique constraint "atacc1_pkey"
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key (test)=(3) already exists.
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (2, 3);
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "test" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, 1).
2025-02-01 03:25:15.010 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (test2, test) values (1, NULL);
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table pg_class alter column relname drop not null;
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table pg_class alter relname set not null;
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "non_existent" does not exist
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table non_existent alter column bar set not null;
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "non_existent" does not exist
2025-02-01 03:25:15.012 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table non_existent alter column bar drop not null;
2025-02-01 03:25:15.015 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 88
2025-02-01 03:25:15.015 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "out1" shadows a previously defined variable at character 97
2025-02-01 03:25:15.021 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 88
2025-02-01 03:25:15.022 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "out1" shadows a previously defined variable at character 97
2025-02-01 03:25:15.028 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "f1" shadows a previously defined variable at character 93
2025-02-01 03:25:15.032 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 76
2025-02-01 03:25:15.033 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "in1" shadows a previously defined variable at character 101
2025-02-01 03:25:15.036 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test" is in a primary key
2025-02-01 03:25:15.036 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter column test drop not null;
2025-02-01 03:25:15.039 UTC client backend[30789] pg_regress/plpgsql WARNING:  variable "f1" shadows a previously defined variable at character 88
2025-02-01 03:25:15.041 UTC client backend[30789] pg_regress/plpgsql ERROR:  variable "f1" shadows a previously defined variable at character 78
2025-02-01 03:25:15.041 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create or replace function shadowtest(f1 int)
		returns boolean as $$
	declare f1 int; begin return 1; end $$ language plpgsql;
2025-02-01 03:25:15.042 UTC client backend[30789] pg_regress/plpgsql ERROR:  function shadowtest(integer) does not exist at character 8
2025-02-01 03:25:15.042 UTC client backend[30789] pg_regress/plpgsql HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:15.042 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select shadowtest(1);
2025-02-01 03:25:15.047 UTC client backend[30789] pg_regress/plpgsql WARNING:  query returned more than one row
2025-02-01 03:25:15.047 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:15.047 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at SQL statement
2025-02-01 03:25:15.052 UTC client backend[30789] pg_regress/plpgsql ERROR:  query returned more than one row
2025-02-01 03:25:15.052 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns a single row, or use LIMIT 1.
2025-02-01 03:25:15.052 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at SQL statement
2025-02-01 03:25:15.052 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare x int;
	begin
	  select v from generate_series(1,2) g(v) into x;
	end;
	$$;
2025-02-01 03:25:15.055 UTC client backend[30789] pg_regress/plpgsql WARNING:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.055 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_warnings is active.
2025-02-01 03:25:15.055 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.055 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 6 at SQL statement
2025-02-01 03:25:15.056 UTC client backend[30789] pg_regress/plpgsql WARNING:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.056 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_warnings is active.
2025-02-01 03:25:15.056 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.056 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 8 at SQL statement
2025-02-01 03:25:15.059 UTC client backend[30789] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.059 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2025-02-01 03:25:15.059 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.059 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 6 at SQL statement
2025-02-01 03:25:15.059 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  x int;
	  y int;
	begin
	  select 1 into x, y;
	  select 1,2 into x, y;
	  select 1,2,3 into x, y;
	end
	$$;
2025-02-01 03:25:15.060 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test" of relation "atacc1" contains null values
2025-02-01 03:25:15.060 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test set not null;
2025-02-01 03:25:15.062 UTC client backend[30781] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2025-02-01 03:25:15.062 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter bar set not null;
2025-02-01 03:25:15.063 UTC client backend[30781] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2025-02-01 03:25:15.063 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter bar drop not null;
2025-02-01 03:25:15.064 UTC client backend[30789] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.064 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2025-02-01 03:25:15.064 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.064 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 8 at SQL statement
2025-02-01 03:25:15.064 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  x int;
	  y int;
	begin
	  select * from test_01 into x, y; -- should be ok
	  raise notice 'ok';
	  select * from test_01 into x;    -- should to fail
	end;
	$$;
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action ALTER COLUMN ... DROP NOT NULL cannot be performed on relation "myview"
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table myview alter column test drop not null;
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action ALTER COLUMN ... SET NOT NULL cannot be performed on relation "myview"
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2025-02-01 03:25:15.064 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table myview alter column test set not null;
2025-02-01 03:25:15.065 UTC client backend[30789] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.065 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2025-02-01 03:25:15.065 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.065 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 7 at SQL statement
2025-02-01 03:25:15.065 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  t test_01;
	begin
	  select 1, 2 into t;  -- should be ok
	  raise notice 'ok';
	  select 1, 2, 3 into t; -- should fail;
	end;
	$$;
2025-02-01 03:25:15.067 UTC client backend[30789] pg_regress/plpgsql ERROR:  number of source and target fields in assignment does not match
2025-02-01 03:25:15.067 UTC client backend[30789] pg_regress/plpgsql DETAIL:  strict_multi_assignment check of extra_errors is active.
2025-02-01 03:25:15.067 UTC client backend[30789] pg_regress/plpgsql HINT:  Make sure the query returns the exact list of columns.
2025-02-01 03:25:15.067 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 5 at SQL statement
2025-02-01 03:25:15.067 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare
	  t test_01;
	begin
	  select 1 into t; -- should fail;
	end;
	$$;
2025-02-01 03:25:15.068 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test_a" of relation "atacc1" contains null values
2025-02-01 03:25:15.068 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null;
2025-02-01 03:25:15.071 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test_a" of relation "atacc1" contains null values
2025-02-01 03:25:15.071 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null;
2025-02-01 03:25:15.076 UTC client backend[30789] pg_regress/plpgsql ERROR:  cursor can only scan forward
2025-02-01 03:25:15.076 UTC client backend[30789] pg_regress/plpgsql HINT:  Declare it with SCROLL option to enable backward scan.
2025-02-01 03:25:15.076 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function sc_test() line 7 at FETCH
2025-02-01 03:25:15.076 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from sc_test();
2025-02-01 03:25:15.079 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test_b" of relation "atacc1" contains null values
2025-02-01 03:25:15.079 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_a set not null, alter test_b set not null;
2025-02-01 03:25:15.080 UTC client backend[30781] pg_regress/alter_table ERROR:  column "test_b" of relation "atacc1" contains null values
2025-02-01 03:25:15.080 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter test_b set not null, alter test_a set not null;
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "a" of relation "parent" violates not-null constraint
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null).
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into parent values (NULL);
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "a" of relation "child" violates not-null constraint
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, foo).
2025-02-01 03:25:15.090 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into child (a, b) values (NULL, 'foo');
2025-02-01 03:25:15.092 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "parent" contains null values
2025-02-01 03:25:15.092 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table only parent alter a set not null;
2025-02-01 03:25:15.093 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "child" contains null values
2025-02-01 03:25:15.093 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table child alter a set not null;
2025-02-01 03:25:15.104 UTC client backend[30781] pg_regress/alter_table ERROR:  invalid input syntax for type integer: "wrong_datatype"
2025-02-01 03:25:15.104 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table def_test alter column c1 set default 'wrong_datatype';
2025-02-01 03:25:15.104 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c3" of relation "def_test" does not exist
2025-02-01 03:25:15.104 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table def_test alter column c3 set default 30;
2025-02-01 03:25:15.117 UTC client backend[30781] pg_regress/alter_table ERROR:  permission denied: "pg_class" is a system catalog
2025-02-01 03:25:15.117 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table pg_class drop column relname;
2025-02-01 03:25:15.119 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "nosuchtable" does not exist
2025-02-01 03:25:15.119 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table nosuchtable drop column bar;
2025-02-01 03:25:15.125 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.125 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 drop a;
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 order by a;
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 order by "........pg.dropped.1........";
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 group by a;
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 group by "........pg.dropped.1........";
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 8
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select a from atacc1;
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table ERROR:  column atacc1.a does not exist at character 8
2025-02-01 03:25:15.127 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select atacc1.a from atacc1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 8
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select a,b,c,d from atacc1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 28
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 where a = 1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 8
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select "........pg.dropped.1........" from atacc1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column atacc1.........pg.dropped.1........ does not exist at character 8
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select atacc1."........pg.dropped.1........" from atacc1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 8
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select "........pg.dropped.1........",b,c,d from atacc1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 28
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select * from atacc1 where "........pg.dropped.1........" = 1;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 19
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  update atacc1 set a = 3;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 31
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  update atacc1 set b = 2 where a = 3;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 19
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  update atacc1 set "........pg.dropped.1........" = 3;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 31
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  update atacc1 set b = 2 where "........pg.dropped.1........" = 3;
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table ERROR:  INSERT has more expressions than target columns at character 40
2025-02-01 03:25:15.128 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 values (10, 11, 12, 13);
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table ERROR:  INSERT has more expressions than target columns at character 45
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 values (default, 11, 12, 13);
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (a) values (10);
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (a) values (default);
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.129 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (a,b,c,d) values (10,11,12,13);
2025-02-01 03:25:15.130 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.130 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 (a,b,c,d) values (default,11,12,13);
2025-02-01 03:25:15.131 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.131 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........") values (10);
2025-02-01 03:25:15.131 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.131 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........") values (default);
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........",b,c,d) values (10,11,12,13);
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist at character 21
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1 ("........pg.dropped.1........",b,c,d) values (default,11,12,13);
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist at character 26
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table STATEMENT:  delete from atacc1 where a = 3;
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist at character 26
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table STATEMENT:  delete from atacc1 where "........pg.dropped.1........" = 3;
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table ERROR:  column "bar" of relation "atacc1" does not exist
2025-02-01 03:25:15.132 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 drop bar;
2025-02-01 03:25:15.134 UTC client backend[30781] pg_regress/alter_table ERROR:  syntax error at or near "WITH" at character 24
2025-02-01 03:25:15.134 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 SET WITH OIDS;
2025-02-01 03:25:15.134 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop system column "xmin"
2025-02-01 03:25:15.134 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 drop xmin;
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action DROP COLUMN cannot be performed on relation "myview"
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for views.
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table myview drop d;
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table STATEMENT:  analyze atacc1(a);
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.137 UTC client backend[30781] pg_regress/alter_table STATEMENT:  analyze atacc1("........pg.dropped.1........");
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table STATEMENT:  vacuum analyze atacc1(a);
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table STATEMENT:  vacuum analyze atacc1("........pg.dropped.1........");
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.138 UTC client backend[30781] pg_regress/alter_table STATEMENT:  comment on column atacc1.a is 'testing';
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table STATEMENT:  comment on column atacc1."........pg.dropped.1........" is 'testing';
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set storage plain;
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.139 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set storage plain;
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set statistics 0;
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set statistics 0;
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set default 3;
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set default 3;
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.140 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a drop default;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" drop default;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a set not null;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" set not null;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter a drop not null;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 alter "........pg.dropped.1........" drop not null;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 rename a to x;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 rename "........pg.dropped.1........" to x;
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add primary key(a);
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "atacc1" does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add primary key("........pg.dropped.1........");
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" named in key does not exist
2025-02-01 03:25:15.142 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add unique(a);
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" named in key does not exist
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add unique("........pg.dropped.1........");
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add check (a > 3);
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2025-02-01 03:25:15.143 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add check ("........pg.dropped.1........" > 3);
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" referenced in foreign key constraint does not exist
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add foreign key (a) references atacc2(id);
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" referenced in foreign key constraint does not exist
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc1 add foreign key ("........pg.dropped.1........") references atacc2(id);
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" referenced in foreign key constraint does not exist
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc2 add foreign key (id) references atacc1(a);
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" referenced in foreign key constraint does not exist
2025-02-01 03:25:15.145 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table atacc2 add foreign key (id) references atacc1("........pg.dropped.1........");
2025-02-01 03:25:15.147 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist
2025-02-01 03:25:15.147 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create index "testing_idx" on atacc1(a);
2025-02-01 03:25:15.147 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" does not exist
2025-02-01 03:25:15.147 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create index "testing_idx" on atacc1("........pg.dropped.1........");
2025-02-01 03:25:15.166 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_value_check"
2025-02-01 03:25:15.166 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (1, 100).
2025-02-01 03:25:15.166 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1(value) values (100);
2025-02-01 03:25:15.167 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "atacc1" violates check constraint "atacc1_value_check"
2025-02-01 03:25:15.167 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (2, 100).
2025-02-01 03:25:15.167 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1(value) values (100);
2025-02-01 03:25:15.168 UTC client backend[30781] pg_regress/alter_table ERROR:  null value in column "id" of relation "atacc1" violates not-null constraint
2025-02-01 03:25:15.168 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null, 0).
2025-02-01 03:25:15.168 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into atacc1(id, value) values (null, 0);
2025-02-01 03:25:15.175 UTC client backend[30789] pg_regress/plpgsql ERROR:  cursor FOR loop must use a bound cursor variable at character 98
2025-02-01 03:25:15.175 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  create or replace function forc_bad() returns void as $$
	declare
	  c refcursor;
	begin
	  for r in c loop
	    raise notice '%', r.i;
	  end loop;
	end;
	$$ language plpgsql;
2025-02-01 03:25:15.188 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" has a type conflict
2025-02-01 03:25:15.188 UTC client backend[30781] pg_regress/alter_table DETAIL:  double precision versus real
2025-02-01 03:25:15.188 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create table child (a float4) inherits (parent);
2025-02-01 03:25:15.189 UTC client backend[30781] pg_regress/alter_table ERROR:  column "b" has a type conflict
2025-02-01 03:25:15.189 UTC client backend[30781] pg_regress/alter_table DETAIL:  numeric(10,4) versus numeric(10,7)
2025-02-01 03:25:15.189 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create table child (b decimal(10,7)) inherits (parent);
2025-02-01 03:25:15.190 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c" has a collation conflict
2025-02-01 03:25:15.190 UTC client backend[30781] pg_regress/alter_table DETAIL:  "C" versus "POSIX"
2025-02-01 03:25:15.190 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create table child (c text collate "POSIX") inherits (parent);
2025-02-01 03:25:15.200 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "attest" does not exist
2025-02-01 03:25:15.200 UTC client backend[30781] pg_regress/alter_table STATEMENT:  copy attest(a) to stdout;
2025-02-01 03:25:15.201 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "attest" does not exist
2025-02-01 03:25:15.201 UTC client backend[30781] pg_regress/alter_table STATEMENT:  copy attest("........pg.dropped.1........") to stdout;
2025-02-01 03:25:15.202 UTC client backend[30781] pg_regress/alter_table ERROR:  extra data after last expected column
2025-02-01 03:25:15.202 UTC client backend[30781] pg_regress/alter_table CONTEXT:  COPY attest, line 1: "10	11	12"
2025-02-01 03:25:15.202 UTC client backend[30781] pg_regress/alter_table STATEMENT:  copy attest from stdin;
2025-02-01 03:25:15.215 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" of relation "attest" does not exist
2025-02-01 03:25:15.215 UTC client backend[30781] pg_regress/alter_table STATEMENT:  copy attest(a) from stdin;
2025-02-01 03:25:15.215 UTC client backend[30781] pg_regress/alter_table ERROR:  column "........pg.dropped.1........" of relation "attest" does not exist
2025-02-01 03:25:15.215 UTC client backend[30781] pg_regress/alter_table STATEMENT:  copy attest("........pg.dropped.1........") from stdin;
2025-02-01 03:25:15.221 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "a"
2025-02-01 03:25:15.221 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table dropColumnchild drop column a;
2025-02-01 03:25:15.223 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "b"
2025-02-01 03:25:15.223 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table only dropColumnChild drop column b;
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot rename inherited column "a"
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table renameColumnChild rename column a to d;
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table ERROR:  inherited column "a" must be renamed in child tables too
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table only renameColumnChild rename column a to d;
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table ERROR:  inherited column "a" must be renamed in child tables too
2025-02-01 03:25:15.228 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table only renameColumn rename column a to d;
2025-02-01 03:25:15.231 UTC client backend[30781] pg_regress/alter_table ERROR:  column must be added to child tables too
2025-02-01 03:25:15.231 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table only renameColumn add column x int;
2025-02-01 03:25:15.233 UTC client backend[30781] pg_regress/alter_table ERROR:  multiple ENFORCED/NOT ENFORCED clauses not allowed at character 70
2025-02-01 03:25:15.233 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table renameColumn add column y int check (x > 0) not enforced enforced;
2025-02-01 03:25:15.237 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2025-02-01 03:25:15.237 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2025-02-01 03:25:15.238 UTC client backend[30781] pg_regress/alter_table ERROR:  column "f1" does not exist at character 8
2025-02-01 03:25:15.238 UTC client backend[30781] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "c1.f2".
2025-02-01 03:25:15.238 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select f1 from c1;
2025-02-01 03:25:15.239 UTC client backend[30789] pg_regress/plpgsql ERROR:  returned record type does not match expected record type
2025-02-01 03:25:15.239 UTC client backend[30789] pg_regress/plpgsql DETAIL:  Returned type unknown does not match expected type character varying in column 2.
2025-02-01 03:25:15.239 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2025-02-01 03:25:15.239 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select compos();
2025-02-01 03:25:15.243 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2025-02-01 03:25:15.243 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2025-02-01 03:25:15.244 UTC client backend[30781] pg_regress/alter_table ERROR:  column "f1" does not exist at character 8
2025-02-01 03:25:15.244 UTC client backend[30781] pg_regress/alter_table HINT:  Perhaps you meant to reference the column "c1.f2".
2025-02-01 03:25:15.244 UTC client backend[30781] pg_regress/alter_table STATEMENT:  select f1 from c1;
2025-02-01 03:25:15.248 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2025-02-01 03:25:15.248 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2025-02-01 03:25:15.257 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "f1"
2025-02-01 03:25:15.257 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table c1 drop column f1;
2025-02-01 03:25:15.278 UTC client backend[30789] pg_regress/plpgsql ERROR:  cannot return non-composite value from function returning composite type
2025-02-01 03:25:15.278 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() line 3 at RETURN
2025-02-01 03:25:15.278 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select compos();
2025-02-01 03:25:15.280 UTC client backend[30789] pg_regress/plpgsql ERROR:  cannot return non-composite value from function returning composite type
2025-02-01 03:25:15.280 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() line 4 at RETURN
2025-02-01 03:25:15.280 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from compos();
2025-02-01 03:25:15.280 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "name"
2025-02-01 03:25:15.280 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table gc1 drop column name;
2025-02-01 03:25:15.282 UTC client backend[30781] pg_regress/alter_table ERROR:  column "name" of relation "gc1" does not exist
2025-02-01 03:25:15.282 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table gc1 drop column name;
2025-02-01 03:25:15.284 UTC client backend[30781] pg_regress/alter_table ERROR:  column "non_existing" of relation "dropcolumnexists" does not exist
2025-02-01 03:25:15.284 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table dropColumnExists drop column non_existing;
2025-02-01 03:25:15.284 UTC client backend[30789] pg_regress/plpgsql ERROR:  invalid input syntax for type integer: "(1,hello)"
2025-02-01 03:25:15.284 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2025-02-01 03:25:15.284 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select compos();
2025-02-01 03:25:15.289 UTC client backend[30789] pg_regress/plpgsql ERROR:  invalid input syntax for type integer: "(1,hello)"
2025-02-01 03:25:15.289 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function compos() while casting return value to function's return type
2025-02-01 03:25:15.289 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select compos();
2025-02-01 03:25:15.294 UTC client backend[30789] pg_regress/plpgsql ERROR:  1 2 3
2025-02-01 03:25:15.294 UTC client backend[30789] pg_regress/plpgsql DETAIL:  some detail info
2025-02-01 03:25:15.294 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 5 at RAISE
2025-02-01 03:25:15.294 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.300 UTC client backend[30789] pg_regress/plpgsql ERROR:  check me
2025-02-01 03:25:15.300 UTC client backend[30789] pg_regress/plpgsql DETAIL:  some detail info
2025-02-01 03:25:15.300 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.300 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.302 UTC client backend[30789] pg_regress/plpgsql ERROR:  check me
2025-02-01 03:25:15.302 UTC client backend[30789] pg_regress/plpgsql DETAIL:  some detail info
2025-02-01 03:25:15.302 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.302 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.304 UTC client backend[30789] pg_regress/plpgsql ERROR:  check me
2025-02-01 03:25:15.304 UTC client backend[30789] pg_regress/plpgsql DETAIL:  some detail info
2025-02-01 03:25:15.304 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.304 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.312 UTC client backend[30789] pg_regress/plpgsql ERROR:  division_by_zero
2025-02-01 03:25:15.312 UTC client backend[30789] pg_regress/plpgsql DETAIL:  some detail info
2025-02-01 03:25:15.312 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.312 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.315 UTC client backend[30789] pg_regress/plpgsql ERROR:  division_by_zero
2025-02-01 03:25:15.315 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.315 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.317 UTC client backend[30789] pg_regress/plpgsql ERROR:  1234F
2025-02-01 03:25:15.317 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.317 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.319 UTC client backend[30789] pg_regress/plpgsql ERROR:  custom message
2025-02-01 03:25:15.319 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.319 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.319 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "c1" violates check constraint "p1_a1_check"
2025-02-01 03:25:15.319 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (11, xyz, 33, 0).
2025-02-01 03:25:15.319 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into c1 values(11,'xyz',33,0);
2025-02-01 03:25:15.323 UTC client backend[30789] pg_regress/plpgsql ERROR:  custom message
2025-02-01 03:25:15.323 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.323 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.329 UTC client backend[30789] pg_regress/plpgsql ERROR:  RAISE option already specified: MESSAGE
2025-02-01 03:25:15.329 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.329 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.330 UTC client backend[30789] pg_regress/plpgsql ERROR:  RAISE option already specified: ERRCODE
2025-02-01 03:25:15.330 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.330 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.333 UTC client backend[30789] pg_regress/plpgsql ERROR:  RAISE without parameters cannot be used outside an exception handler
2025-02-01 03:25:15.333 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 3 at RAISE
2025-02-01 03:25:15.333 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.344 UTC client backend[30781] pg_regress/alter_table ERROR:  column "f1" cannot be cast automatically to type integer
2025-02-01 03:25:15.344 UTC client backend[30781] pg_regress/alter_table HINT:  You might need to specify "USING f1::integer".
2025-02-01 03:25:15.344 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table foo alter f1 TYPE integer;
2025-02-01 03:25:15.359 UTC client backend[30789] pg_regress/plpgsql ERROR:  GET STACKED DIAGNOSTICS cannot be used outside an exception handler
2025-02-01 03:25:15.359 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function stacked_diagnostics_test() line 6 at GET STACKED DIAGNOSTICS
2025-02-01 03:25:15.359 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select stacked_diagnostics_test();
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table ERROR:  column "atcol1" cannot be cast automatically to type boolean
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table HINT:  You might need to specify "USING atcol1::boolean".
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean;
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table ERROR:  result of USING clause for column "atcol1" cannot be cast automatically to type boolean
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table HINT:  You might need to add an explicit cast.
2025-02-01 03:25:15.359 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean using atcol1::int;
2025-02-01 03:25:15.364 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "anothertab" violates check constraint "anothertab_chk"
2025-02-01 03:25:15.364 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (45, null).
2025-02-01 03:25:15.364 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into anothertab (atcol1, atcol2) values (45, null);
2025-02-01 03:25:15.372 UTC client backend[30781] pg_regress/alter_table ERROR:  default for column "atcol1" cannot be cast automatically to type boolean
2025-02-01 03:25:15.372 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean
	        using case when atcol1 % 2 = 0 then true else false end;
2025-02-01 03:25:15.374 UTC client backend[30781] pg_regress/alter_table ERROR:  operator does not exist: boolean <= integer
2025-02-01 03:25:15.374 UTC client backend[30781] pg_regress/alter_table HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-01 03:25:15.374 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table anothertab alter column atcol1 type boolean
	        using case when atcol1 % 2 = 0 then true else false end;
2025-02-01 03:25:15.374 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint "anothertab_chk" of relation "anothertab" does not exist
2025-02-01 03:25:15.374 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table anothertab drop constraint anothertab_chk;
2025-02-01 03:25:15.384 UTC client backend[30789] pg_regress/plpgsql ERROR:  substitute message
2025-02-01 03:25:15.384 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function raise_test() line 7 at RAISE
2025-02-01 03:25:15.384 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select raise_test();
2025-02-01 03:25:15.418 UTC client backend[30789] pg_regress/plpgsql ERROR:  SELECT INTO query does not return tuples
2025-02-01 03:25:15.418 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  SQL statement "select 10 into no_such_table"
	PL/pgSQL function rttest() line 3 at RETURN QUERY
2025-02-01 03:25:15.418 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from rttest();
2025-02-01 03:25:15.419 UTC client backend[30789] pg_regress/plpgsql ERROR:  SELECT INTO query does not return tuples
2025-02-01 03:25:15.419 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  SQL statement "select 10 into no_such_table"
	PL/pgSQL function rttest() line 3 at RETURN QUERY
2025-02-01 03:25:15.419 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from rttest();
2025-02-01 03:25:15.419 UTC client backend[30789] pg_regress/plpgsql ERROR:  relation "no_such_table" does not exist at character 15
2025-02-01 03:25:15.419 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from no_such_table;
2025-02-01 03:25:15.499 UTC client backend[30789] pg_regress/plpgsql ERROR:  schema "nonexistent" does not exist
2025-02-01 03:25:15.499 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  SQL function "error1" statement 1
	PL/pgSQL function error2(text) line 3 at RETURN
2025-02-01 03:25:15.499 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select error2('nonexistent.stuffs');
2025-02-01 03:25:15.515 UTC client backend[30789] pg_regress/plpgsql ERROR:  invalid input syntax for type date: "-1"
2025-02-01 03:25:15.515 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  SQL function "sql_to_date" statement 1
	PL/pgSQL function cast_invoker(integer) while casting return value to function's return type
2025-02-01 03:25:15.515 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select cast_invoker(-1);
2025-02-01 03:25:15.525 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter table "at_tab1" because column "at_tab2.y" uses its row type
2025-02-01 03:25:15.525 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table at_tab1 alter column b type varchar;
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql ERROR:  division by zero
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL expression "1/0"
	PL/pgSQL function fail() line 3 at RETURN
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select fail();
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql ERROR:  division by zero
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL expression "1/0"
	PL/pgSQL function fail() line 3 at RETURN
2025-02-01 03:25:15.532 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select fail();
2025-02-01 03:25:15.533 UTC client backend[30781] pg_regress/alter_table ERROR:  ROW() column has type text instead of type character varying
2025-02-01 03:25:15.533 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into at_tab2 values(1,'42');
2025-02-01 03:25:15.536 UTC client backend[30789] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 78
2025-02-01 03:25:15.536 UTC client backend[30789] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:25:15.536 UTC client backend[30789] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 106
2025-02-01 03:25:15.536 UTC client backend[30789] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:25:15.537 UTC client backend[30789] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 106
2025-02-01 03:25:15.537 UTC client backend[30789] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:25:15.539 UTC client backend[30789] pg_regress/plpgsql WARNING:  nonstandard use of \\ in a string literal at character 1
2025-02-01 03:25:15.539 UTC client backend[30789] pg_regress/plpgsql HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
2025-02-01 03:25:15.539 UTC client backend[30789] pg_regress/plpgsql QUERY:  'foo\\bar\041baz'
2025-02-01 03:25:15.539 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function strtest() line 4 at RETURN
2025-02-01 03:25:15.541 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter table "at_tab1" because column "at_tab2.y" uses its row type
2025-02-01 03:25:15.541 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table at_tab1 alter column b type varchar;
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql ERROR:  RETURN cannot have a parameter in function returning void at character 36
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  DO LANGUAGE plpgsql $$begin return 1; end$$;
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "foo" does not exist at character 33
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql QUERY:  SELECT rtrim(roomno) AS roomno, foo FROM Room ORDER BY roomno
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at FOR over SELECT rows
2025-02-01 03:25:15.564 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  DO $$
	DECLARE r record;
	BEGIN
	    FOR r IN SELECT rtrim(roomno) AS roomno, foo FROM Room ORDER BY roomno
	    LOOP
	        RAISE NOTICE '%, %', r.roomno, r.comment;
	    END LOOP;
	END$$;
2025-02-01 03:25:15.569 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "x" does not exist at character 1
2025-02-01 03:25:15.569 UTC client backend[30789] pg_regress/plpgsql QUERY:  x + 1
2025-02-01 03:25:15.569 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-02-01 03:25:15.569 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare x int := x + 1;  -- error
	begin
	  raise notice 'x = %', x;
	end;
	$$;
2025-02-01 03:25:15.570 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "x" does not exist at character 1
2025-02-01 03:25:15.570 UTC client backend[30789] pg_regress/plpgsql QUERY:  x + 1
2025-02-01 03:25:15.570 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 2 during statement block local variable initialization
2025-02-01 03:25:15.570 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare y int := x + 1;  -- error
	        x int := 42;
	begin
	  raise notice 'x = %, y = %', x, y;
	end;
	$$;
2025-02-01 03:25:15.581 UTC client backend[30789] pg_regress/plpgsql ERROR:  column reference "q1" is ambiguous at character 8
2025-02-01 03:25:15.581 UTC client backend[30789] pg_regress/plpgsql DETAIL:  It could refer to either a PL/pgSQL variable or a table column.
2025-02-01 03:25:15.581 UTC client backend[30789] pg_regress/plpgsql QUERY:  select q1,q2 from int8_tbl
2025-02-01 03:25:15.581 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function conflict_test() line 5 at FOR over SELECT rows
2025-02-01 03:25:15.581 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select * from conflict_test();
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql ERROR:  FOREACH ... SLICE loop variable must be of an array type
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[1,2,3,4]);
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql ERROR:  FOREACH ... SLICE loop variable must be of an array type
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2025-02-01 03:25:15.619 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[[1,2],[3,4]]);
2025-02-01 03:25:15.624 UTC client backend[30789] pg_regress/plpgsql ERROR:  slice dimension (2) is out of the valid range 0..1
2025-02-01 03:25:15.624 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function foreach_test(anyarray) line 4 at FOREACH over array
2025-02-01 03:25:15.624 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select foreach_test(ARRAY[1,2,3,4]);
2025-02-01 03:25:15.647 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2025-02-01 03:25:15.647 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select '{2,1}'::orderedarray;
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function testoa(integer,integer,integer) line 4 at assignment
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select testoa(2,1,3);
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for domain orderedarray violates check constraint "sorted"
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function testoa(integer,integer,integer) line 5 at assignment
2025-02-01 03:25:15.650 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  select testoa(1,2,1);
2025-02-01 03:25:15.691 UTC client backend[30781] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2025-02-01 03:25:15.691 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur1;
2025-02-01 03:25:15.695 UTC client backend[30781] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2025-02-01 03:25:15.695 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur1[];
2025-02-01 03:25:15.699 UTC client backend[30781] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2025-02-01 03:25:15.699 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 array_of_recur1;
2025-02-01 03:25:15.703 UTC client backend[30781] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2025-02-01 03:25:15.703 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table recur1 add column f2 recur2;
2025-02-01 03:25:15.705 UTC client backend[30781] pg_regress/alter_table ERROR:  composite type recur1 cannot be made a member of itself
2025-02-01 03:25:15.705 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table recur1 alter column f2 type recur2;
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql ERROR:  assertion failed
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert 1=0;  -- should fail
	end;
	$$;
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql ERROR:  assertion failed
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2025-02-01 03:25:15.706 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert NULL;  -- should fail
	end;
	$$;
2025-02-01 03:25:15.717 UTC client backend[30781] pg_regress/alter_table ERROR:  column data type integer can only have storage PLAIN
2025-02-01 03:25:15.717 UTC client backend[30781] pg_regress/alter_table STATEMENT:  create table test_storage_failed (a text, b int storage extended);
2025-02-01 03:25:15.717 UTC client backend[30789] pg_regress/plpgsql ERROR:  assertion failed, var = "some value"
2025-02-01 03:25:15.717 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at ASSERT
2025-02-01 03:25:15.717 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare var text := 'some value';
	begin
	  assert 1=0, format('assertion failed, var = "%s"', var);
	end;
	$$;
2025-02-01 03:25:15.718 UTC client backend[30789] pg_regress/plpgsql ERROR:  unhandled assertion
2025-02-01 03:25:15.718 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 3 at ASSERT
2025-02-01 03:25:15.718 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	begin
	  assert 1=0, 'unhandled assertion';
	exception when others then
	  null; -- do nothing
	end;
	$$;
2025-02-01 03:25:15.737 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for domain plpgsql_domain violates check constraint "plpgsql_domain_check"
2025-02-01 03:25:15.737 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at assignment
2025-02-01 03:25:15.737 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare v_test plpgsql_domain := 1;
	begin
	  v_test := 0;  -- fail
	end;
	$$;
2025-02-01 03:25:15.742 UTC client backend[30789] pg_regress/plpgsql ERROR:  value for domain plpgsql_arr_domain violates check constraint "plpgsql_arr_domain_check"
2025-02-01 03:25:15.742 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function inline_code_block line 4 at assignment
2025-02-01 03:25:15.742 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  do $$
	declare v_test plpgsql_arr_domain := array[1];
	begin
	  v_test := 0 || v_test;  -- fail
	end;
	$$;
2025-02-01 03:25:15.767 UTC client backend[30789] pg_regress/plpgsql ERROR:  OLD TABLE can only be specified for a DELETE or UPDATE trigger
2025-02-01 03:25:15.767 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  CREATE TRIGGER transition_table_base_ins_trig
	  AFTER INSERT ON transition_table_base
	  REFERENCING OLD TABLE AS oldtable NEW TABLE AS newtable
	  FOR EACH STATEMENT
	  EXECUTE PROCEDURE transition_table_base_ins_func();
2025-02-01 03:25:16.028 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot convert whole-row table reference
2025-02-01 03:25:16.028 UTC client backend[30781] pg_regress/alter_table DETAIL:  USING expression contains a whole-row table reference.
2025-02-01 03:25:16.028 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE test_type_diff2 ALTER COLUMN int_four TYPE int4 USING (pg_column_size(test_type_diff2));
2025-02-01 03:25:16.035 UTC client backend[30789] pg_regress/plpgsql ERROR:  relation "dx" cannot be the target of a modifying statement
2025-02-01 03:25:16.035 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  SQL statement "INSERT INTO dx VALUES (1000000, 1000000, 'x')"
	PL/pgSQL function transition_table_level2_bad_usage_func() line 3 at SQL statement
2025-02-01 03:25:16.035 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  DELETE FROM transition_table_level2
	  WHERE level2_no BETWEEN 301 AND 305;
2025-02-01 03:25:16.038 UTC client backend[30789] pg_regress/plpgsql ERROR:  RI error
2025-02-01 03:25:16.038 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level1_ri_parent_del_func() line 6 at RAISE
2025-02-01 03:25:16.038 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  DELETE FROM transition_table_level1
	  WHERE level1_no = 25;
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql ERROR:  RI error
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level1_ri_parent_upd_func() line 15 at RAISE
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  UPDATE transition_table_level1 SET level1_no = -1
	  WHERE level1_no = 30;
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql ERROR:  RI error
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE
2025-02-01 03:25:16.040 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  INSERT INTO transition_table_level2 (level2_no, parent_no)
	  VALUES (10000, 10000);
2025-02-01 03:25:16.041 UTC client backend[30789] pg_regress/plpgsql ERROR:  RI error
2025-02-01 03:25:16.041 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function transition_table_level2_ri_child_insupd_func() line 8 at RAISE
2025-02-01 03:25:16.041 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  UPDATE transition_table_level2 SET parent_no = 2000
	  WHERE level2_no = 40;
2025-02-01 03:25:16.066 UTC client backend[30789] pg_regress/plpgsql ERROR:  TRUNCATE triggers with transition tables are not supported
2025-02-01 03:25:16.066 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  CREATE TRIGGER alter_table_under_transition_tables_upd_trigger
	  AFTER TRUNCATE OR UPDATE ON alter_table_under_transition_tables
	  REFERENCING OLD TABLE AS d NEW TABLE AS i
	  FOR EACH STATEMENT EXECUTE PROCEDURE
	    alter_table_under_transition_tables_upd_func();
2025-02-01 03:25:16.069 UTC client backend[30789] pg_regress/plpgsql WARNING:  old table = 1=1,2=2,3=3, new table = 1=11,2=22,3=33
2025-02-01 03:25:16.069 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2025-02-01 03:25:16.074 UTC client backend[30789] pg_regress/plpgsql WARNING:  old table = 1=11,2=22,3=33, new table = 1=1111,2=2222,3=3333
2025-02-01 03:25:16.074 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2025-02-01 03:25:16.084 UTC client backend[30789] pg_regress/plpgsql ERROR:  column "name" does not exist at character 33
2025-02-01 03:25:16.084 UTC client backend[30789] pg_regress/plpgsql QUERY:  (SELECT string_agg(id || '=' || name, ',') FROM d)
2025-02-01 03:25:16.084 UTC client backend[30789] pg_regress/plpgsql CONTEXT:  PL/pgSQL function alter_table_under_transition_tables_upd_func() line 3 at RAISE
2025-02-01 03:25:16.084 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  UPDATE alter_table_under_transition_tables
	  SET id = id;
2025-02-01 03:25:16.117 UTC client backend[30789] pg_regress/plpgsql ERROR:  "x" is not a scalar variable at character 72
2025-02-01 03:25:16.117 UTC client backend[30789] pg_regress/plpgsql STATEMENT:  CREATE FUNCTION fx(x WSlot) RETURNS void AS $$
	BEGIN
	  GET DIAGNOSTICS x = ROW_COUNT;
	  RETURN;
	END; $$ LANGUAGE plpgsql;
2025-02-01 03:25:16.183 UTC client backend[30781] pg_regress/alter_table ERROR:  type "lockmodes" does not exist
2025-02-01 03:25:16.183 UTC client backend[30781] pg_regress/alter_table STATEMENT:  drop type lockmodes;
2025-02-01 03:25:16.183 UTC client backend[30781] pg_regress/alter_table ERROR:  view "my_locks" does not exist
2025-02-01 03:25:16.183 UTC client backend[30781] pg_regress/alter_table STATEMENT:  drop view my_locks;
2025-02-01 03:25:16.227 UTC client backend[30781] pg_regress/alter_table ERROR:  unrecognized parameter "autovacuum_enabled"
2025-02-01 03:25:16.227 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table my_locks set (autovacuum_enabled = false);
2025-02-01 03:25:16.227 UTC client backend[30781] pg_regress/alter_table ERROR:  unrecognized parameter "autovacuum_enabled"
2025-02-01 03:25:16.227 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter view my_locks set (autovacuum_enabled = false);
2025-02-01 03:25:16.263 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "nosuchtype" does not exist
2025-02-01 03:25:16.263 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE nosuchtype ADD ATTRIBUTE b text;
2025-02-01 03:25:16.275 UTC client backend[30781] pg_regress/alter_table ERROR:  column "b" of relation "test_type" already exists
2025-02-01 03:25:16.275 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type ADD ATTRIBUTE b text;
2025-02-01 03:25:16.289 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c" of relation "test_type" does not exist
2025-02-01 03:25:16.289 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type DROP ATTRIBUTE c;
2025-02-01 03:25:16.299 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" does not exist
2025-02-01 03:25:16.299 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type RENAME ATTRIBUTE a TO aa;
2025-02-01 03:25:16.306 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type1" because column "test_tbl1.y" uses it
2025-02-01 03:25:16.306 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar;
2025-02-01 03:25:16.310 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type1" because column "test_tbl1_idx.row" uses it
2025-02-01 03:25:16.310 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type1 ALTER ATTRIBUTE b TYPE varchar;
2025-02-01 03:25:16.329 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2025-02-01 03:25:16.329 UTC client backend[30781] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2025-02-01 03:25:16.329 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 ADD ATTRIBUTE c text;
2025-02-01 03:25:16.341 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2025-02-01 03:25:16.341 UTC client backend[30781] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2025-02-01 03:25:16.341 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 ALTER ATTRIBUTE b TYPE varchar;
2025-02-01 03:25:16.361 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2025-02-01 03:25:16.361 UTC client backend[30781] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2025-02-01 03:25:16.361 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 DROP ATTRIBUTE b;
2025-02-01 03:25:16.377 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter type "test_type2" because it is the type of a typed table
2025-02-01 03:25:16.377 UTC client backend[30781] pg_regress/alter_table HINT:  Use ALTER ... CASCADE to alter the typed tables too.
2025-02-01 03:25:16.377 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_type2 RENAME ATTRIBUTE a TO aa;
2025-02-01 03:25:16.416 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop column a of composite type test_typex because other objects depend on it
2025-02-01 03:25:16.416 UTC client backend[30781] pg_regress/alter_table DETAIL:  constraint test_tblx_y_check on table test_tblx depends on column a of composite type test_typex
2025-02-01 03:25:16.416 UTC client backend[30781] pg_regress/alter_table HINT:  Use DROP ... CASCADE to drop the dependent objects too.
2025-02-01 03:25:16.416 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TYPE test_typex DROP ATTRIBUTE a;
2025-02-01 03:25:16.531 UTC client backend[30781] pg_regress/alter_table ERROR:  table "tt1" has different type for column "y"
2025-02-01 03:25:16.531 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt1 OF tt_t0;
2025-02-01 03:25:16.534 UTC client backend[30781] pg_regress/alter_table ERROR:  table "tt2" has different type for column "y"
2025-02-01 03:25:16.534 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt2 OF tt_t0;
2025-02-01 03:25:16.539 UTC client backend[30781] pg_regress/alter_table ERROR:  table has column "y" where type requires "x"
2025-02-01 03:25:16.539 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt3 OF tt_t0;
2025-02-01 03:25:16.540 UTC client backend[30781] pg_regress/alter_table ERROR:  table is missing column "y"
2025-02-01 03:25:16.540 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt4 OF tt_t0;
2025-02-01 03:25:16.543 UTC client backend[30781] pg_regress/alter_table ERROR:  table has extra column "z"
2025-02-01 03:25:16.543 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt5 OF tt_t0;
2025-02-01 03:25:16.543 UTC client backend[30781] pg_regress/alter_table ERROR:  typed tables cannot inherit
2025-02-01 03:25:16.543 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt6 OF tt_t0;
2025-02-01 03:25:16.572 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "test_drop_constr_child" violates check constraint "test_drop_constr_parent_c_check"
2025-02-01 03:25:16.572 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (null).
2025-02-01 03:25:16.572 UTC client backend[30781] pg_regress/alter_table STATEMENT:  INSERT INTO test_drop_constr_child (c) VALUES (NULL);
2025-02-01 03:25:16.596 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint "foo" for relation "tt9" already exists
2025-02-01 03:25:16.596 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT foo CHECK(c > 4);
2025-02-01 03:25:16.597 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "tt9_c_key" already exists
2025-02-01 03:25:16.597 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key UNIQUE(c);
2025-02-01 03:25:16.597 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint "foo" for relation "tt9" already exists
2025-02-01 03:25:16.597 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT foo UNIQUE(c);
2025-02-01 03:25:16.598 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint "tt9_c_key" for relation "tt9" already exists
2025-02-01 03:25:16.598 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE tt9 ADD CONSTRAINT tt9_c_key CHECK(c > 5);
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter system column "xmin" at character 39
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE comment_test ALTER COLUMN xmin SET DATA TYPE x;
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table ERROR:  type "x" does not exist at character 56
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE x;
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table ERROR:  collations are not supported by type integer at character 60
2025-02-01 03:25:16.657 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE int COLLATE "C";
2025-02-01 03:25:16.667 UTC client backend[30781] pg_regress/alter_table ERROR:  foreign key constraint "comment_test_child_fk" cannot be implemented
2025-02-01 03:25:16.667 UTC client backend[30781] pg_regress/alter_table DETAIL:  Key columns "id" of the referencing table and "id" of the referenced table are of incompatible types: text and integer.
2025-02-01 03:25:16.667 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE comment_test ALTER COLUMN id SET DATA TYPE int USING id::integer;
2025-02-01 03:25:16.695 UTC client backend[30781] pg_regress/alter_table ERROR:  permission denied to create "pg_catalog.new_system_table"
2025-02-01 03:25:16.695 UTC client backend[30781] pg_regress/alter_table DETAIL:  System catalog modifications are currently disallowed.
2025-02-01 03:25:16.695 UTC client backend[30781] pg_regress/alter_table STATEMENT:  CREATE TABLE pg_catalog.new_system_table();
2025-02-01 03:25:16.722 UTC client backend[30781] pg_regress/alter_table ERROR:  could not change table "unlogged2" to logged because it references unlogged table "unlogged1"
2025-02-01 03:25:16.722 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE unlogged2 SET LOGGED;
2025-02-01 03:25:16.743 UTC client backend[30781] pg_regress/alter_table ERROR:  could not change table "logged1" to unlogged because it references logged table "logged2"
2025-02-01 03:25:16.743 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE logged1 SET UNLOGGED;
2025-02-01 03:25:16.826 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2025-02-01 03:25:16.826 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE test_add_column
		ADD COLUMN c2 integer;
2025-02-01 03:25:16.827 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2025-02-01 03:25:16.827 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY test_add_column
		ADD COLUMN c2 integer;
2025-02-01 03:25:16.866 UTC client backend[30781] pg_regress/alter_table ERROR:  column "c2" of relation "test_add_column" already exists
2025-02-01 03:25:16.866 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE test_add_column
		ADD COLUMN c2 integer, -- fail because c2 already exists
		ADD COLUMN c3 integer primary key;
2025-02-01 03:25:17.036 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop column "a" because it is part of the partition key of relation "partitioned"
2025-02-01 03:25:17.036 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned DROP COLUMN a;
2025-02-01 03:25:17.036 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter column "a" because it is part of the partition key of relation "partitioned" at character 38
2025-02-01 03:25:17.036 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ALTER COLUMN a TYPE char(5);
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop column "b" because it is part of the partition key of relation "partitioned"
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned DROP COLUMN b;
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter column "b" because it is part of the partition key of relation "partitioned" at character 38
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ALTER COLUMN b TYPE char(5);
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot specify storage parameters for a partitioned table
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table HINT:  Specify storage parameters for its leaf partitions instead.
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned SET (fillfactor=100);
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot change inheritance of partitioned table
2025-02-01 03:25:17.037 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned INHERIT nonpartitioned;
2025-02-01 03:25:17.038 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot inherit from partitioned table "partitioned"
2025-02-01 03:25:17.038 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE nonpartitioned INHERIT partitioned;
2025-02-01 03:25:17.038 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot add NO INHERIT constraint to partitioned table "partitioned"
2025-02-01 03:25:17.038 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE partitioned ADD CONSTRAINT chk_a CHECK (a > 0) NO INHERIT;
2025-02-01 03:25:17.040 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action ATTACH PARTITION cannot be performed on relation "unparted"
2025-02-01 03:25:17.040 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for tables.
2025-02-01 03:25:17.040 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE unparted ATTACH PARTITION fail_part FOR VALUES IN ('a');
2025-02-01 03:25:17.043 UTC client backend[30781] pg_regress/alter_table ERROR:  invalid bound specification for a list partition at character 63
2025-02-01 03:25:17.043 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES FROM (1) TO (10);
2025-02-01 03:25:17.044 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "nonexistent" does not exist
2025-02-01 03:25:17.044 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION nonexistent FOR VALUES IN (1);
2025-02-01 03:25:17.047 UTC client backend[30781] pg_regress/alter_table ERROR:  must be owner of table not_owned_by_me
2025-02-01 03:25:17.047 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE owned_by_me ATTACH PARTITION not_owned_by_me FOR VALUES IN (1);
2025-02-01 03:25:17.050 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach inheritance child as partition
2025-02-01 03:25:17.050 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION child FOR VALUES IN (1);
2025-02-01 03:25:17.050 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach inheritance parent as partition
2025-02-01 03:25:17.050 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION parent FOR VALUES IN (1);
2025-02-01 03:25:17.053 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "parent" violates partition constraint
2025-02-01 03:25:17.053 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (2, null).
2025-02-01 03:25:17.053 UTC client backend[30781] pg_regress/alter_table STATEMENT:  UPDATE parent SET a = 2 WHERE a = 1;
2025-02-01 03:25:17.055 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach a permanent relation as partition of temporary relation "temp_parted"
2025-02-01 03:25:17.055 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE temp_parted ATTACH PARTITION perm_part FOR VALUES IN (1);
2025-02-01 03:25:17.057 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach a typed table as partition
2025-02-01 03:25:17.057 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.059 UTC client backend[30781] pg_regress/alter_table ERROR:  table "fail_part" contains column "c" not found in parent "list_parted"
2025-02-01 03:25:17.059 UTC client backend[30781] pg_regress/alter_table DETAIL:  The new partition may contain only the columns present in parent.
2025-02-01 03:25:17.059 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.060 UTC client backend[30781] pg_regress/alter_table ERROR:  child table is missing column "b"
2025-02-01 03:25:17.060 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.061 UTC client backend[30781] pg_regress/alter_table ERROR:  child table "fail_part" has different type for column "b"
2025-02-01 03:25:17.061 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.063 UTC client backend[30781] pg_regress/alter_table ERROR:  child table "fail_part" has different collation for column "b"
2025-02-01 03:25:17.063 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.064 UTC client backend[30781] pg_regress/alter_table ERROR:  child table is missing constraint "check_a"
2025-02-01 03:25:17.064 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.065 UTC client backend[30781] pg_regress/alter_table ERROR:  child table "fail_part" has different definition for check constraint "check_a"
2025-02-01 03:25:17.065 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.069 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint "part_fail_a_not_null" conflicts with non-inherited constraint on child table "part_fail"
2025-02-01 03:25:17.069 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION part_fail FOR VALUES IN (2);
2025-02-01 03:25:17.071 UTC client backend[30781] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "part_1" at character 67
2025-02-01 03:25:17.071 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_part FOR VALUES IN (1);
2025-02-01 03:25:17.075 UTC client backend[30781] pg_regress/alter_table ERROR:  partition "fail_def_part" conflicts with existing default partition "def_part" at character 56
2025-02-01 03:25:17.075 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted ATTACH PARTITION fail_def_part DEFAULT;
2025-02-01 03:25:17.077 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "part_2" is violated by some row
2025-02-01 03:25:17.077 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2);
2025-02-01 03:25:17.080 UTC client backend[30781] pg_regress/alter_table ERROR:  updated partition constraint for default partition "list_parted2_def" would be violated by some row
2025-02-01 03:25:17.080 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_3 FOR VALUES IN (11);
2025-02-01 03:25:17.089 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "part1" is violated by some row
2025-02-01 03:25:17.089 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH PARTITION part1 FOR VALUES FROM (1, 1) TO (1, 10);
2025-02-01 03:25:17.094 UTC client backend[30781] pg_regress/alter_table ERROR:  partition "partr_def2" conflicts with existing default partition "partr_def1" at character 54
2025-02-01 03:25:17.094 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH PARTITION partr_def2 DEFAULT;
2025-02-01 03:25:17.096 UTC client backend[30781] pg_regress/alter_table ERROR:  updated partition constraint for default partition "partr_def1" would be violated by some row
2025-02-01 03:25:17.096 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted ATTACH partition part3 FOR VALUES FROM (2, 10) TO (2, 20);
2025-02-01 03:25:17.099 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "part_5_a" is violated by some row
2025-02-01 03:25:17.099 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_5 FOR VALUES IN (5);
2025-02-01 03:25:17.112 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "part_7_a_null" is violated by some row
2025-02-01 03:25:17.112 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_7 FOR VALUES IN (7);
2025-02-01 03:25:17.117 UTC client backend[30781] pg_regress/alter_table ERROR:  updated partition constraint for default partition "part5_def_p1" would be violated by some row
2025-02-01 03:25:17.117 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_5 ATTACH PARTITION part5_p1 FOR VALUES IN ('y');
2025-02-01 03:25:17.118 UTC client backend[30781] pg_regress/alter_table ERROR:  "part_2" is already a partition
2025-02-01 03:25:17.118 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION part_2 FOR VALUES IN (2);
2025-02-01 03:25:17.118 UTC client backend[30781] pg_regress/alter_table ERROR:  circular inheritance not allowed
2025-02-01 03:25:17.118 UTC client backend[30781] pg_regress/alter_table DETAIL:  "part_5" is already a child of "list_parted2".
2025-02-01 03:25:17.118 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_5 ATTACH PARTITION list_parted2 FOR VALUES IN ('b');
2025-02-01 03:25:17.119 UTC client backend[30781] pg_regress/alter_table ERROR:  circular inheritance not allowed
2025-02-01 03:25:17.119 UTC client backend[30781] pg_regress/alter_table DETAIL:  "list_parted2" is already a child of "list_parted2".
2025-02-01 03:25:17.119 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ATTACH PARTITION list_parted2 FOR VALUES IN (0);
2025-02-01 03:25:17.137 UTC client backend[30781] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "hpart_1" at character 63
2025-02-01 03:25:17.137 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 4);
2025-02-01 03:25:17.137 UTC client backend[30781] pg_regress/alter_table ERROR:  partition "fail_part" would overlap partition "hpart_1" at character 63
2025-02-01 03:25:17.137 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 0);
2025-02-01 03:25:17.139 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "hpart_2" is violated by some row
2025-02-01 03:25:17.139 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION hpart_2 FOR VALUES WITH (MODULUS 4, REMAINDER 1);
2025-02-01 03:25:17.143 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "hpart_5_a" is violated by some row
2025-02-01 03:25:17.143 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION hpart_5 FOR VALUES WITH (MODULUS 4, REMAINDER 2);
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table ERROR:  modulus for hash partition must be an integer value greater than zero
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 0, REMAINDER 1);
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table ERROR:  remainder for hash partition must be less than modulus
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 8, REMAINDER 8);
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table ERROR:  every hash partition modulus must be a factor of the next larger modulus
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table DETAIL:  The new modulus 3 is not a factor of 4, the modulus of existing partition "hpart_1".
2025-02-01 03:25:17.147 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted ATTACH PARTITION fail_part FOR VALUES WITH (MODULUS 3, REMAINDER 2);
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action DETACH PARTITION cannot be performed on relation "regular_table"
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for tables.
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE regular_table DETACH PARTITION any_name;
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action DETACH PARTITION cannot be performed on relation "regular_table"
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for tables.
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE regular_table DETACH PARTITION any_name CONCURRENTLY;
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER action DETACH PARTITION ... FINALIZE cannot be performed on relation "regular_table"
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table DETAIL:  This operation is not supported for tables.
2025-02-01 03:25:17.149 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE regular_table DETACH PARTITION any_name FINALIZE;
2025-02-01 03:25:17.151 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "part_4" does not exist
2025-02-01 03:25:17.151 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION part_4;
2025-02-01 03:25:17.151 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "hpart_4" does not exist
2025-02-01 03:25:17.151 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted DETACH PARTITION hpart_4;
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "not_a_part" is not a partition of relation "list_parted2"
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION not_a_part;
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "part_1" is not a partition of relation "list_parted2"
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DETACH PARTITION part_1;
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table ERROR:  relation "not_a_part" is not a partition of relation "hash_parted"
2025-02-01 03:25:17.152 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE hash_parted DETACH PARTITION not_a_part;
2025-02-01 03:25:17.164 UTC client backend[30781] pg_regress/alter_table ERROR:  ALTER TABLE ... DETACH CONCURRENTLY cannot run inside a transaction block
2025-02-01 03:25:17.164 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY;
2025-02-01 03:25:17.165 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot detach partitions concurrently when a default partition exists
2025-02-01 03:25:17.165 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rp CONCURRENTLY;
2025-02-01 03:25:17.165 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot detach partitions concurrently when a default partition exists
2025-02-01 03:25:17.165 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE range_parted2 DETACH PARTITION part_rpd CONCURRENTLY;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  column must be added to child tables too
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ADD COLUMN c int;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop column from only the partitioned table when partitions exist
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 DROP COLUMN b;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot add column to a partition
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ADD COLUMN c text;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited column "b"
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 DROP COLUMN b;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot rename inherited column "b"
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 RENAME COLUMN b to c;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter inherited column "b" at character 33
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ALTER COLUMN b TYPE text;
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint must be added to child tables too
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table HINT:  Do not specify the ONLY keyword.
2025-02-01 03:25:17.197 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ALTER b SET NOT NULL;
2025-02-01 03:25:17.198 UTC client backend[30781] pg_regress/alter_table ERROR:  constraint must be added to child tables too
2025-02-01 03:25:17.198 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted2 ADD CONSTRAINT check_b CHECK (b <> 'zz');
2025-02-01 03:25:17.218 UTC client backend[30781] pg_regress/alter_table ERROR:  column "b" is marked NOT NULL in parent table
2025-02-01 03:25:17.218 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 ALTER b DROP NOT NULL;
2025-02-01 03:25:17.218 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop inherited constraint "check_a2" of relation "part_2"
2025-02-01 03:25:17.218 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 DROP CONSTRAINT check_a2;
2025-02-01 03:25:17.220 UTC client backend[30781] pg_regress/alter_table ERROR:  column "a" is in a primary key
2025-02-01 03:25:17.220 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE ONLY list_parted3 DROP CONSTRAINT list_parted3_a_not_null;
2025-02-01 03:25:17.221 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot add NO INHERIT constraint to partitioned table "list_parted2"
2025-02-01 03:25:17.221 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 add constraint check_b2 check (b <> 'zz') NO INHERIT;
2025-02-01 03:25:17.221 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot inherit from partition "part_2"
2025-02-01 03:25:17.221 UTC client backend[30781] pg_regress/alter_table STATEMENT:  CREATE TABLE inh_test () INHERITS (part_2);
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot inherit from a partition
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE inh_test INHERIT part_2;
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot change inheritance of a partition
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE part_2 INHERIT inh_test;
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot drop column "b" because it is part of the partition key of relation "part_5"
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 DROP COLUMN b;
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot alter column "b" because it is part of the partition key of relation "part_5" at character 39
2025-02-01 03:25:17.222 UTC client backend[30781] pg_regress/alter_table STATEMENT:  ALTER TABLE list_parted2 ALTER COLUMN b TYPE text;
2025-02-01 03:25:17.246 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "p11" is violated by some row
2025-02-01 03:25:17.246 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table p attach partition p1 for values from (1, 2) to (1, 10);
2025-02-01 03:25:17.257 UTC client backend[30781] pg_regress/alter_table ERROR:  partition constraint of relation "defpart_attach_test_d" is violated by some row
2025-02-01 03:25:17.257 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table defpart_attach_test attach partition defpart_attach_test_d default;
2025-02-01 03:25:17.263 UTC client backend[30781] pg_regress/alter_table ERROR:  updated partition constraint for default partition "defpart_attach_test_d" would be violated by some row
2025-02-01 03:25:17.263 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table defpart_attach_test attach partition defpart_attach_test_2 for values in (2);
2025-02-01 03:25:17.268 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach a permanent relation as partition of temporary relation "temp_part_parent"
2025-02-01 03:25:17.268 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table temp_part_parent attach partition perm_part_child default;
2025-02-01 03:25:17.268 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot attach a temporary relation as partition of permanent relation "perm_part_parent"
2025-02-01 03:25:17.268 UTC client backend[30781] pg_regress/alter_table STATEMENT:  alter table perm_part_parent attach partition temp_part_child default;
2025-02-01 03:25:17.272 UTC client backend[30781] pg_regress/alter_table ERROR:  cannot ALTER TABLE "tab_part_attach" because it is being used by active queries in this session
2025-02-01 03:25:17.272 UTC client backend[30781] pg_regress/alter_table CONTEXT:  SQL statement "alter table tab_part_attach attach partition tab_part_attach_1 for values in (1)"
	PL/pgSQL function func_part_attach() line 4 at EXECUTE
2025-02-01 03:25:17.272 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into tab_part_attach values (1);
2025-02-01 03:25:17.339 UTC client backend[30781] pg_regress/alter_table ERROR:  new row for relation "attach_parted_part1" violates partition constraint
2025-02-01 03:25:17.339 UTC client backend[30781] pg_regress/alter_table DETAIL:  Failing row contains (2, 1).
2025-02-01 03:25:17.339 UTC client backend[30781] pg_regress/alter_table STATEMENT:  insert into attach_parted_part1 values (2, 1);
2025-02-01 03:25:17.343 UTC client backend[30781] pg_regress/alter_table WARNING:  "wal_level" is insufficient to publish logical changes
2025-02-01 03:25:17.343 UTC client backend[30781] pg_regress/alter_table HINT:  Set "wal_level" to "logical" before creating subscriptions.
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  value 2 out of bounds for option "fillfactor"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=2);
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  value 110 out of bounds for option "fillfactor"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=110);
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  value -10.0 out of bounds for option "autovacuum_analyze_scale_factor"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "0.000000" and "100.000000".
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = -10.0);
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  value 110.0 out of bounds for option "autovacuum_analyze_scale_factor"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "0.000000" and "100.000000".
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor = 110.0);
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (not_existing_option=2);
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions ERROR:  unrecognized parameter namespace "not_existing_namespace"
2025-02-01 03:25:17.464 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (not_existing_namespace.fillfactor=2);
2025-02-01 03:25:17.465 UTC client backend[32011] pg_regress/reloptions ERROR:  value -30.1 out of bounds for option "fillfactor"
2025-02-01 03:25:17.465 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:17.465 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=-30.1);
2025-02-01 03:25:17.465 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": string
2025-02-01 03:25:17.465 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor='string');
2025-02-01 03:25:17.465 UTC client backend[32006] pg_regress/hash_part ERROR:  could not open relation with OID 0
2025-02-01 03:25:17.465 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition(0, 4, 0, NULL);
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": true
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=true);
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": 12
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=12);
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": 30.5
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled=30.5);
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for boolean option "autovacuum_enabled": string
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_enabled='string');
2025-02-01 03:25:17.466 UTC client backend[32006] pg_regress/hash_part ERROR:  "tenk1" is not a hash partitioned table
2025-02-01 03:25:17.466 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('tenk1'::regclass, 4, 0, NULL);
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for floating point option "autovacuum_analyze_scale_factor": string
2025-02-01 03:25:17.466 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor='string');
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for floating point option "autovacuum_analyze_scale_factor": true
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (autovacuum_analyze_scale_factor=true);
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions ERROR:  parameter "fillfactor" specified more than once
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor=30, fillfactor=40);
2025-02-01 03:25:17.467 UTC client backend[32006] pg_regress/hash_part ERROR:  "mchash1" is not a hash partitioned table
2025-02-01 03:25:17.467 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash1'::regclass, 4, 0, NULL);
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions ERROR:  invalid value for integer option "fillfactor": true
2025-02-01 03:25:17.467 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2(i INT) WITH (fillfactor);
2025-02-01 03:25:17.467 UTC client backend[32006] pg_regress/hash_part ERROR:  modulus for hash partition must be an integer value greater than zero
2025-02-01 03:25:17.467 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 0, 0, NULL);
2025-02-01 03:25:17.468 UTC client backend[32006] pg_regress/hash_part ERROR:  remainder for hash partition must be an integer value greater than or equal to zero
2025-02-01 03:25:17.468 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 1, -1, NULL);
2025-02-01 03:25:17.469 UTC client backend[32006] pg_regress/hash_part ERROR:  remainder for hash partition must be less than modulus
2025-02-01 03:25:17.469 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 1, 1, NULL);
2025-02-01 03:25:17.469 UTC client backend[32006] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (3)
2025-02-01 03:25:17.469 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, NULL::int, NULL::text, NULL::json);
2025-02-01 03:25:17.470 UTC client backend[32006] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (1)
2025-02-01 03:25:17.470 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int);
2025-02-01 03:25:17.470 UTC client backend[32006] pg_regress/hash_part ERROR:  column 2 of the partition key has type text, but supplied value is of type integer
2025-02-01 03:25:17.470 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int);
2025-02-01 03:25:17.475 UTC client backend[32011] pg_regress/reloptions ERROR:  RESET must not include values for parameters
2025-02-01 03:25:17.475 UTC client backend[32011] pg_regress/reloptions STATEMENT:  ALTER TABLE reloptions_test RESET (fillfactor=12);
2025-02-01 03:25:17.475 UTC client backend[32006] pg_regress/hash_part ERROR:  column 2 of the partition key has type "text", but supplied value is of type "integer"
2025-02-01 03:25:17.475 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mchash'::regclass, 2, 1,
									variadic array[1,2]::int[]);
2025-02-01 03:25:17.481 UTC client backend[32006] pg_regress/hash_part ERROR:  number of partitioning columns (2) does not match number of partition keys provided (0)
2025-02-01 03:25:17.481 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0,
									variadic array[]::int[]);
2025-02-01 03:25:17.481 UTC client backend[32006] pg_regress/hash_part ERROR:  column 1 of the partition key has type "integer", but supplied value is of type "timestamp with time zone"
2025-02-01 03:25:17.481 UTC client backend[32006] pg_regress/hash_part STATEMENT:  SELECT satisfies_hash_partition('mcinthash'::regclass, 4, 0,
									variadic array[now(), now()]);
2025-02-01 03:25:17.485 UTC client backend[32007] pg_regress/explain ERROR:  EXPLAIN options ANALYZE and GENERIC_PLAN cannot be used together
2025-02-01 03:25:17.485 UTC client backend[32007] pg_regress/explain CONTEXT:  PL/pgSQL function explain_filter(text) line 5 at FOR over EXECUTE statement
2025-02-01 03:25:17.485 UTC client backend[32007] pg_regress/explain STATEMENT:  select explain_filter('explain (analyze, generic_plan) select unique1 from tenk1 where thousand = $1');
2025-02-01 03:25:17.494 UTC client backend[32011] pg_regress/reloptions ERROR:  null value in column "i" of relation "reloptions_test" violates not-null constraint
2025-02-01 03:25:17.494 UTC client backend[32011] pg_regress/reloptions DETAIL:  Failing row contains (null, null).
2025-02-01 03:25:17.494 UTC client backend[32011] pg_regress/reloptions STATEMENT:  INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL);
2025-02-01 03:25:17.501 UTC client backend[32011] pg_regress/reloptions ERROR:  null value in column "i" of relation "reloptions_test" violates not-null constraint
2025-02-01 03:25:17.501 UTC client backend[32011] pg_regress/reloptions DETAIL:  Failing row contains (null, null).
2025-02-01 03:25:17.501 UTC client backend[32011] pg_regress/reloptions STATEMENT:  INSERT INTO reloptions_test VALUES (1, NULL), (NULL, NULL);
2025-02-01 03:25:17.506 UTC client backend[32011] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2025-02-01 03:25:17.506 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE TABLE reloptions_test2 (i int) WITH (toast.not_existing_option = 42);
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions ERROR:  unrecognized parameter "not_existing_option"
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx ON reloptions_test (s)
		WITH (not_existing_option=2);
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions ERROR:  unrecognized parameter namespace "not_existing_ns"
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx ON reloptions_test (s)
		WITH (not_existing_ns.fillfactor=2);
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions ERROR:  value 1 out of bounds for option "fillfactor"
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=1);
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions ERROR:  value 130 out of bounds for option "fillfactor"
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions DETAIL:  Valid values are between "10" and "100".
2025-02-01 03:25:17.539 UTC client backend[32011] pg_regress/reloptions STATEMENT:  CREATE INDEX reloptions_test_idx2 ON reloptions_test (s) WITH (fillfactor=130);
2025-02-01 03:25:17.546 UTC client backend[32010] pg_regress/indexing ERROR:  cannot create index on partitioned table "idxpart" concurrently
2025-02-01 03:25:17.546 UTC client backend[32010] pg_regress/indexing STATEMENT:  create index concurrently on idxpart (a);
2025-02-01 03:25:17.696 UTC client backend[32017] pg_regress/compression ERROR:  column data type integer does not support compression
2025-02-01 03:25:17.696 UTC client backend[32017] pg_regress/compression STATEMENT:  CREATE TABLE cmdata2 (f1 int COMPRESSION pglz);
2025-02-01 03:25:17.827 UTC client backend[32010] pg_regress/indexing ERROR:  "idxpart_c" is not a partitioned table
2025-02-01 03:25:17.827 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart_c attach partition idxpart1_c for values from (10) to (20);
2025-02-01 03:25:17.829 UTC client backend[32010] pg_regress/indexing ERROR:  ALTER action DETACH PARTITION cannot be performed on relation "idxpart_c"
2025-02-01 03:25:17.829 UTC client backend[32010] pg_regress/indexing DETAIL:  This operation is not supported for partitioned indexes.
2025-02-01 03:25:17.829 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart_c detach partition idxpart1_c;
2025-02-01 03:25:17.881 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop index idxpart1_a_idx because index idxpart_a_idx requires it
2025-02-01 03:25:17.881 UTC client backend[32010] pg_regress/indexing HINT:  You can drop index idxpart_a_idx instead.
2025-02-01 03:25:17.881 UTC client backend[32010] pg_regress/indexing STATEMENT:  drop index idxpart1_a_idx;
2025-02-01 03:25:17.881 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop partitioned index "idxpart_a_idx" concurrently
2025-02-01 03:25:17.881 UTC client backend[32010] pg_regress/indexing STATEMENT:  drop index concurrently idxpart_a_idx;
2025-02-01 03:25:17.893 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop index idxpart1_temp_a_idx because index idxpart_temp_a_idx requires it
2025-02-01 03:25:17.893 UTC client backend[32010] pg_regress/indexing HINT:  You can drop index idxpart_temp_a_idx instead.
2025-02-01 03:25:17.893 UTC client backend[32010] pg_regress/indexing STATEMENT:  drop index idxpart1_temp_a_idx;
2025-02-01 03:25:17.907 UTC client backend[32010] pg_regress/indexing ERROR:  "idxpart" is not an index
2025-02-01 03:25:17.907 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart attach partition idxpart1;
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing ERROR:  "idxpart1" is not an index
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1;
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart_a_b_idx" as a partition of index "idxpart_a_b_idx"
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing DETAIL:  Index "idxpart_a_b_idx" is not an index on any partition of table "idxpart".
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart_a_b_idx;
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing ERROR:  relation "idxpart1_b_idx" does not exist
2025-02-01 03:25:17.908 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_b_idx;
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst1" as a partition of index "idxpart_a_b_idx"
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst1;
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst2" as a partition of index "idxpart_a_b_idx"
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst2;
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_tst3" as a partition of index "idxpart_a_b_idx"
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:17.915 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_tst3;
2025-02-01 03:25:17.917 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2_a_b" as a partition of index "idxpart_a_b_idx"
2025-02-01 03:25:17.917 UTC client backend[32010] pg_regress/indexing DETAIL:  Another index is already attached for partition "idxpart1".
2025-02-01 03:25:17.917 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_b_idx attach partition idxpart1_2_a_b;
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression ERROR:  column "f1" has a compression method conflict
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression DETAIL:  pglz versus lz4
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression STATEMENT:  CREATE TABLE cminh() INHERITS(cmdata, cmdata1);
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression ERROR:  column "f1" has a compression method conflict
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression DETAIL:  pglz versus lz4
2025-02-01 03:25:17.995 UTC client backend[32017] pg_regress/compression STATEMENT:  CREATE TABLE cminh(f1 TEXT COMPRESSION lz4) INHERITS(cmdata);
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression ERROR:  invalid value for parameter "default_toast_compression": ""
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression HINT:  Available values: pglz, lz4.
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression STATEMENT:  SET default_toast_compression = '';
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression ERROR:  invalid value for parameter "default_toast_compression": "I do not exist compression"
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression HINT:  Available values: pglz, lz4.
2025-02-01 03:25:18.007 UTC client backend[32017] pg_regress/compression STATEMENT:  SET default_toast_compression = 'I do not exist compression';
2025-02-01 03:25:18.077 UTC client backend[32013] pg_regress/partition_prune ERROR:  table "part_rev" contains column "c" not found in parent "part"
2025-02-01 03:25:18.077 UTC client backend[32013] pg_regress/partition_prune DETAIL:  The new partition may contain only the columns present in parent.
2025-02-01 03:25:18.077 UTC client backend[32013] pg_regress/partition_prune STATEMENT:  ALTER TABLE part ATTACH PARTITION part_rev FOR VALUES IN (3);
2025-02-01 03:25:18.128 UTC client backend[32017] pg_regress/compression ERROR:  invalid compression method "i_do_not_exist_compression"
2025-02-01 03:25:18.128 UTC client backend[32017] pg_regress/compression STATEMENT:  CREATE TABLE badcompresstbl (a text COMPRESSION I_Do_Not_Exist_Compression);
2025-02-01 03:25:18.132 UTC client backend[32017] pg_regress/compression ERROR:  invalid compression method "i_do_not_exist_compression"
2025-02-01 03:25:18.132 UTC client backend[32017] pg_regress/compression STATEMENT:  ALTER TABLE badcompresstbl ALTER a SET COMPRESSION I_Do_Not_Exist_Compression;
2025-02-01 03:25:18.227 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:18.391 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 2000 buffers (12.2%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 2 recycled; write=0.062 s, sync=0.001 s, total=0.165 s; sync files=0, longest=0.000 s, average=0.000 s; distance=24281 kB, estimate=65370 kB; lsn=0/D6505F8, redo lsn=0/D5A3330
2025-02-01 03:25:18.392 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:18.397 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 163 buffers (1.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.006 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1367 kB, estimate=58970 kB; lsn=0/D71A160, redo lsn=0/D6F9058
2025-02-01 03:25:18.405 UTC client backend[32100] pg_regress/stats ERROR:  unrecognized reset target: "unknown"
2025-02-01 03:25:18.405 UTC client backend[32100] pg_regress/stats HINT:  Target must be "archiver", "bgwriter", "checkpointer", "io", "recovery_prefetch", "slru", or "wal".
2025-02-01 03:25:18.405 UTC client backend[32100] pg_regress/stats STATEMENT:  SELECT pg_stat_reset_shared('unknown');
2025-02-01 03:25:18.417 UTC client backend[32100] pg_regress/stats ERROR:  invalid statistics kind: "zaphod"
2025-02-01 03:25:18.417 UTC client backend[32100] pg_regress/stats STATEMENT:  SELECT pg_stat_have_stats('zaphod', 0, 0);
2025-02-01 03:25:18.599 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart2_a_idx" as a partition of index "idxpart_a_idx"
2025-02-01 03:25:18.599 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:18.599 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_a_idx attach partition idxpart2_a_idx;
2025-02-01 03:25:18.643 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_1b_idx" as a partition of index "idxpart_1_idx"
2025-02-01 03:25:18.643 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:18.643 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_1_idx attach partition idxpart1_1b_idx;
2025-02-01 03:25:18.645 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2b_idx" as a partition of index "idxpart_2_idx"
2025-02-01 03:25:18.645 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:18.645 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_2_idx attach partition idxpart1_2b_idx;
2025-02-01 03:25:18.646 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_2c_idx" as a partition of index "idxpart_2_idx"
2025-02-01 03:25:18.646 UTC client backend[32010] pg_regress/indexing DETAIL:  The index definitions do not match.
2025-02-01 03:25:18.646 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_2_idx attach partition idxpart1_2c_idx;
2025-02-01 03:25:18.750 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:18.755 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 185 buffers (1.1%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.001 s, total=0.005 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1581 kB, estimate=53231 kB; lsn=0/D8A12E8, redo lsn=0/D8846E8
2025-02-01 03:25:18.755 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:18.757 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 40 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.003 s; sync files=0, longest=0.000 s, average=0.000 s; distance=162 kB, estimate=47924 kB; lsn=0/D8CC118, redo lsn=0/D8AD168
2025-02-01 03:25:19.228 UTC client backend[32240] pg_regress/stats LOG:  wait_for_hot_stats delayed 0.101316 seconds
2025-02-01 03:25:19.228 UTC client backend[32240] pg_regress/stats CONTEXT:  PL/pgSQL function wait_for_hot_stats() line 17 at RAISE
2025-02-01 03:25:19.228 UTC client backend[32240] pg_regress/stats STATEMENT:  SELECT wait_for_hot_stats();
2025-02-01 03:25:19.229 UTC client backend[32010] pg_regress/indexing ERROR:  multiple primary keys for table "failpart" are not allowed
2025-02-01 03:25:19.229 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table failpart partition of idxpart (b primary key) for values from (0) to (100);
2025-02-01 03:25:19.300 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.300 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.300 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int unique, b int) partition by range (a, b);
2025-02-01 03:25:19.305 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.305 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2025-02-01 03:25:19.305 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int, b int unique) partition by range (a, b);
2025-02-01 03:25:19.306 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.306 UTC client backend[32010] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.306 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int primary key, b int) partition by range (b, a);
2025-02-01 03:25:19.308 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.308 UTC client backend[32010] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "a" which is part of the partition key.
2025-02-01 03:25:19.308 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int, b int primary key) partition by range (b, a);
2025-02-01 03:25:19.355 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.355 UTC client backend[32010] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.355 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, b int4range, exclude USING GIST (a with = )) partition by range (a, b);
2025-02-01 03:25:19.356 UTC client backend[32010] pg_regress/indexing ERROR:  cannot match partition key to index on column "a" using non-equal operator "-|-"
2025-02-01 03:25:19.356 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, exclude USING GIST (a with -|- )) partition by range (a);
2025-02-01 03:25:19.364 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.364 UTC client backend[32010] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2025-02-01 03:25:19.364 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int4range, b int4range, c int4range, exclude USING GIST (b with =, c with &&)) partition by range (a);
2025-02-01 03:25:19.387 UTC client backend[32010] pg_regress/indexing ERROR:  unsupported PRIMARY KEY constraint with partition key definition
2025-02-01 03:25:19.387 UTC client backend[32010] pg_regress/indexing DETAIL:  PRIMARY KEY constraints cannot be used when partition keys include expressions.
2025-02-01 03:25:19.387 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int primary key, b int) partition by range ((b + a));
2025-02-01 03:25:19.389 UTC client backend[32010] pg_regress/indexing ERROR:  unsupported UNIQUE constraint with partition key definition
2025-02-01 03:25:19.389 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraints cannot be used when partition keys include expressions.
2025-02-01 03:25:19.389 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart (a int unique, b int) partition by range ((b + a));
2025-02-01 03:25:19.396 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.396 UTC client backend[32010] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.396 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart add primary key (a);
2025-02-01 03:25:19.482 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.482 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.482 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart add unique (a);
2025-02-01 03:25:19.558 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.558 UTC client backend[32010] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.558 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (a with =);
2025-02-01 03:25:19.567 UTC client backend[32010] pg_regress/indexing ERROR:  cannot match partition key to index on column "a" using non-equal operator "-|-"
2025-02-01 03:25:19.567 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (a with -|-);
2025-02-01 03:25:19.577 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.577 UTC client backend[32010] pg_regress/indexing DETAIL:  EXCLUDE constraint on table "idxpart" lacks column "a" which is part of the partition key.
2025-02-01 03:25:19.577 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart add exclude USING GIST (b with =, c with &&);
2025-02-01 03:25:19.670 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.670 UTC client backend[32010] pg_regress/indexing DETAIL:  PRIMARY KEY constraint on table "idxpart2" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.670 UTC client backend[32010] pg_regress/indexing STATEMENT:  create table idxpart2 partition of idxpart
	for values from (0) to (1000) partition by range (b);
2025-02-01 03:25:19.677 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:19.677 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraint on table "idxpart1" lacks column "b" which is part of the partition key.
2025-02-01 03:25:19.677 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart attach partition idxpart1 for values from (1) to (1000);
2025-02-01 03:25:19.743 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop index idxpart0_pkey because index idxpart_pkey requires it
2025-02-01 03:25:19.743 UTC client backend[32010] pg_regress/indexing HINT:  You can drop index idxpart_pkey instead.
2025-02-01 03:25:19.743 UTC client backend[32010] pg_regress/indexing STATEMENT:  drop index idxpart0_pkey;
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop index idxpart1_pkey because index idxpart_pkey requires it
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing HINT:  You can drop index idxpart_pkey instead.
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing STATEMENT:  drop index idxpart1_pkey;
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop inherited constraint "idxpart0_pkey" of relation "idxpart0"
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart0 drop constraint idxpart0_pkey;
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop inherited constraint "idxpart1_pkey" of relation "idxpart1"
2025-02-01 03:25:19.744 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart1 drop constraint idxpart1_pkey;
2025-02-01 03:25:19.755 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.0", size 499712
2025-02-01 03:25:19.755 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  COMMIT;
2025-02-01 03:25:19.779 UTC client backend[32010] pg_regress/indexing ERROR:  multiple primary keys for table "idxpart1" are not allowed
2025-02-01 03:25:19.779 UTC client backend[32010] pg_regress/indexing STATEMENT:  ALTER TABLE idxpart ATTACH PARTITION idxpart1 FOR VALUES FROM (100) TO (200);
2025-02-01 03:25:19.796 UTC client backend[32010] pg_regress/indexing ERROR:  multiple primary keys for table "idxpart11" are not allowed
2025-02-01 03:25:19.796 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table idxpart attach partition idxpart1 for values from (0) to (10000);
2025-02-01 03:25:19.861 UTC client backend[32010] pg_regress/indexing ERROR:  column "a" of table "idxpart0" is not marked NOT NULL
2025-02-01 03:25:19.861 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table only idxpart add primary key (a);
2025-02-01 03:25:19.922 UTC client backend[32010] pg_regress/indexing ERROR:  cannot attach index "idxpart1_a_idx" as a partition of index "idxpart_pkey"
2025-02-01 03:25:19.922 UTC client backend[32010] pg_regress/indexing DETAIL:  The index "idxpart_pkey" belongs to a constraint in table "idxpart" but no constraint exists for index "idxpart1_a_idx".
2025-02-01 03:25:19.922 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter index idxpart_pkey attach partition idxpart1_a_idx;
2025-02-01 03:25:19.978 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart1_a_idx"
2025-02-01 03:25:19.978 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(65536) already exists.
2025-02-01 03:25:19.978 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into idxpart select 2^g, format('two to power of %s', g) from generate_series(15, 17) g;
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart2_a_idx"
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(285714) already exists.
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into idxpart select a * 2, b || b from idxpart where a between 2^16 and 2^19;
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "idxpart2_a_idx"
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(572814) already exists.
2025-02-01 03:25:19.980 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into idxpart values (572814, 'five');
2025-02-01 03:25:20.119 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.3", size 425984
2025-02-01 03:25:20.119 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.126 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.4", size 270336
2025-02-01 03:25:20.126 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.127 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart1_a_b_idx"
2025-02-01 03:25:20.127 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(1) already exists.
2025-02-01 03:25:20.127 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into covidxpart values (1, 1);
2025-02-01 03:25:20.131 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart3_a_b_idx"
2025-02-01 03:25:20.131 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(3) already exists.
2025-02-01 03:25:20.131 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into covidxpart values (3, 1);
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing ERROR:  duplicate key value violates unique constraint "covidxpart4_a_b_idx"
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing DETAIL:  Key (a)=(4) already exists.
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing STATEMENT:  insert into covidxpart values (4, 1);
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing ERROR:  unique constraint on partitioned table must include all partitioning columns
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing DETAIL:  UNIQUE constraint on table "covidxpart" lacks column "a" which is part of the partition key.
2025-02-01 03:25:20.138 UTC client backend[32010] pg_regress/indexing STATEMENT:  create unique index on covidxpart (b) include (a);
2025-02-01 03:25:20.145 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop inherited constraint "parted_pk_detach_test1_pkey" of relation "parted_pk_detach_test1"
2025-02-01 03:25:20.145 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table parted_pk_detach_test1 drop constraint parted_pk_detach_test1_pkey;
2025-02-01 03:25:20.154 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.2", size 876544
2025-02-01 03:25:20.154 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.155 UTC client backend[32010] pg_regress/indexing ERROR:  cannot drop inherited constraint "parted_uniq_detach_test1_a_key" of relation "parted_uniq_detach_test1"
2025-02-01 03:25:20.155 UTC client backend[32010] pg_regress/indexing STATEMENT:  alter table parted_uniq_detach_test1 drop constraint parted_uniq_detach_test1_a_key;
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.6", size 270336
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.7", size 425984
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.5", size 344064
2025-02-01 03:25:20.164 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.165 UTC client backend[32004] pg_regress/tuplesort LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp32004.1", size 974848
2025-02-01 03:25:20.165 UTC client backend[32004] pg_regress/tuplesort STATEMENT:  SELECT
	    (array_agg(id ORDER BY id DESC NULLS FIRST))[0:5],
	    (array_agg(abort_increasing ORDER BY abort_increasing DESC NULLS LAST))[0:5],
	    (array_agg(id::text ORDER BY id::text DESC NULLS LAST))[0:5],
	    percentile_disc(0.99) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.01) WITHIN GROUP (ORDER BY id),
	    percentile_disc(0.8) WITHIN GROUP (ORDER BY abort_increasing),
	    percentile_disc(0.2) WITHIN GROUP (ORDER BY id::text),
	    rank('00000000-0000-0000-0000-000000000000', '2', '2') WITHIN GROUP (ORDER BY noabort_increasing, id, id::text)
	FROM (
	    SELECT * FROM abbrev_abort_uuids
	    UNION ALL
	    SELECT NULL, NULL, NULL, NULL, NULL) s;
2025-02-01 03:25:20.336 UTC client backend[32010] pg_regress/indexing ERROR:  division by zero
2025-02-01 03:25:20.336 UTC client backend[32010] pg_regress/indexing STATEMENT:  create index concurrently parted_isvalid_idx_11 on parted_isvalid_tab_11 ((a/b));
2025-02-01 03:25:20.509 UTC client backend[32484] pg_regress/event_trigger ERROR:  function pg_backend_pid must return type event_trigger
2025-02-01 03:25:20.509 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger
	   on ddl_command_start
	   execute procedure pg_backend_pid();
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger ERROR:  trigger functions can only be called as triggers
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger CONTEXT:  compilation of PL/pgSQL function "test_event_trigger" near line 1
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  SELECT test_event_trigger();
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger ERROR:  event trigger functions cannot have declared arguments
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger CONTEXT:  compilation of PL/pgSQL function "test_event_trigger_arg" near line 1
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create function test_event_trigger_arg(name text)
	returns event_trigger as $$ BEGIN RETURN 1; END $$ language plpgsql;
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger ERROR:  SQL functions cannot return type event_trigger
2025-02-01 03:25:20.514 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create function test_event_trigger_sql() returns event_trigger as $$
	SELECT 1 $$ language sql;
2025-02-01 03:25:20.515 UTC client backend[32484] pg_regress/event_trigger ERROR:  unrecognized event name "elephant_bootstrap"
2025-02-01 03:25:20.515 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger on elephant_bootstrap
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.516 UTC client backend[32484] pg_regress/event_trigger ERROR:  unrecognized filter variable "food"
2025-02-01 03:25:20.516 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when food in ('sandwich')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.516 UTC client backend[32484] pg_regress/event_trigger ERROR:  filter value "sandwich" not recognized for filter variable "tag"
2025-02-01 03:25:20.516 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('sandwich')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  filter value "create skunkcabbage" not recognized for filter variable "tag"
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('create table', 'create skunkcabbage')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  event triggers are not supported for DROP EVENT TRIGGER
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('DROP EVENT TRIGGER')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE ROLE
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE ROLE')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE DATABASE
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE DATABASE')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  event triggers are not supported for CREATE TABLESPACE
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('CREATE TABLESPACE')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  filter variable "tag" specified more than once
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   when tag in ('create table') and tag in ('CREATE FUNCTION')
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger ERROR:  syntax error at or near "'argument not allowed'" at character 106
2025-02-01 03:25:20.519 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger2 on ddl_command_start
	   execute procedure test_event_trigger('argument not allowed');
2025-02-01 03:25:20.521 UTC client backend[32484] pg_regress/event_trigger ERROR:  permission denied to create event trigger "regress_event_trigger_noperms"
2025-02-01 03:25:20.521 UTC client backend[32484] pg_regress/event_trigger HINT:  Must be superuser to create an event trigger.
2025-02-01 03:25:20.521 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  create event trigger regress_event_trigger_noperms on ddl_command_start
	   execute procedure test_event_trigger();
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger ERROR:  permission denied to change owner of event trigger "regress_event_trigger"
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger HINT:  The owner of an event trigger must be a superuser.
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  alter event trigger regress_event_trigger owner to regress_evt_user;
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger ERROR:  event trigger "regress_event_trigger2" already exists
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  alter event trigger regress_event_trigger rename to regress_event_trigger2;
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger ERROR:  event trigger "regress_event_trigger" does not exist
2025-02-01 03:25:20.545 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  drop event trigger regress_event_trigger;
2025-02-01 03:25:20.546 UTC client backend[32484] pg_regress/event_trigger ERROR:  role "regress_evt_user" cannot be dropped because some objects depend on it
2025-02-01 03:25:20.546 UTC client backend[32484] pg_regress/event_trigger DETAIL:  owner of event trigger regress_event_trigger3
	owner of user mapping for regress_evt_user on server useless_server
	owner of default privileges on new relations belonging to role regress_evt_user
2025-02-01 03:25:20.546 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  drop role regress_evt_user;
2025-02-01 03:25:20.584 UTC client backend[32484] pg_regress/event_trigger ERROR:  object audit_tbls.schema_two_table_three of type table cannot be dropped
2025-02-01 03:25:20.584 UTC client backend[32484] pg_regress/event_trigger CONTEXT:  PL/pgSQL function undroppable() line 14 at RAISE
	SQL statement "DROP TABLE IF EXISTS audit_tbls.schema_two_table_three"
	PL/pgSQL function test_evtrig_dropped_objects() line 8 at EXECUTE
2025-02-01 03:25:20.584 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  DROP SCHEMA schema_one, schema_two CASCADE;
2025-02-01 03:25:20.593 UTC client backend[32484] pg_regress/event_trigger ERROR:  object schema_one.table_three of type table cannot be dropped
2025-02-01 03:25:20.593 UTC client backend[32484] pg_regress/event_trigger CONTEXT:  PL/pgSQL function undroppable() line 14 at RAISE
2025-02-01 03:25:20.593 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  DROP SCHEMA schema_one, schema_two CASCADE;
2025-02-01 03:25:20.719 UTC client backend[32484] pg_regress/event_trigger ERROR:  pg_event_trigger_table_rewrite_oid() can only be called in a table_rewrite event trigger function
2025-02-01 03:25:20.719 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  select pg_event_trigger_table_rewrite_oid();
2025-02-01 03:25:20.732 UTC client backend[32484] pg_regress/event_trigger ERROR:  rewrites not allowed
2025-02-01 03:25:20.732 UTC client backend[32484] pg_regress/event_trigger CONTEXT:  PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE
2025-02-01 03:25:20.732 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  alter table rewriteme alter column foo type numeric;
2025-02-01 03:25:20.781 UTC client backend[32484] pg_regress/event_trigger ERROR:  cannot alter type "rewritetype" because column "rewritemetoo3.a" uses it
2025-02-01 03:25:20.781 UTC client backend[32484] pg_regress/event_trigger STATEMENT:  alter type rewritetype alter attribute a type varchar cascade;
2025-02-01 03:25:21.789 UTC client backend[32741] pg_regress/tablespace ERROR:  tablespace location must be an absolute path
2025-02-01 03:25:21.789 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspace LOCATION 'relative';
2025-02-01 03:25:21.789 UTC client backend[32741] pg_regress/tablespace ERROR:  tablespace location must be an absolute path
2025-02-01 03:25:21.789 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspace LOCATION '';
2025-02-01 03:25:21.790 UTC client backend[32741] pg_regress/tablespace ERROR:  unrecognized parameter "some_nonexistent_parameter"
2025-02-01 03:25:21.790 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_tblspacewith LOCATION '' WITH (some_nonexistent_parameter = true);
2025-02-01 03:25:21.792 UTC client backend[32741] pg_regress/tablespace ERROR:  unrecognized parameter "some_nonexistent_parameter"
2025-02-01 03:25:21.792 UTC client backend[32741] pg_regress/tablespace STATEMENT:  ALTER TABLESPACE regress_tblspace SET (some_nonexistent_parameter = true);
2025-02-01 03:25:21.792 UTC client backend[32741] pg_regress/tablespace ERROR:  RESET must not include values for parameters
2025-02-01 03:25:21.792 UTC client backend[32741] pg_regress/tablespace STATEMENT:  ALTER TABLESPACE regress_tblspace RESET (random_page_cost = 2.0);
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move system relation "pg_am_name_index"
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_am;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_am;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move system relation "pg_authid_rolname_index"
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_authid;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_authid;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move system relation "pg_toast_1262_index"
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) INDEX pg_toast.pg_toast_1262_index;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) INDEX CONCURRENTLY pg_toast.pg_toast_1262_index;
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move system relation "pg_toast_1262_index"
2025-02-01 03:25:21.793 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE pg_toast.pg_toast_1262;
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE CONCURRENTLY pg_toast.pg_toast_1262;
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move system relation "pg_authid_rolname_index"
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) TABLE pg_authid;
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot reindex system catalogs concurrently
2025-02-01 03:25:21.794 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) TABLE CONCURRENTLY pg_authid;
2025-02-01 03:25:21.808 UTC client backend[32741] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2025-02-01 03:25:21.808 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) INDEX regress_tblspace_test_tbl_idx;
2025-02-01 03:25:21.808 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot move non-shared relation to tablespace "pg_global"
2025-02-01 03:25:21.808 UTC client backend[32741] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE pg_global) INDEX CONCURRENTLY regress_tblspace_test_tbl_idx;
2025-02-01 03:25:21.935 UTC client backend[32741] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2025-02-01 03:25:21.935 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_1 PARTITION OF testschema.part FOR VALUES IN (1);
2025-02-01 03:25:21.940 UTC client backend[32741] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2025-02-01 03:25:21.940 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_3 PARTITION OF testschema.part FOR VALUES IN (3);
2025-02-01 03:25:21.943 UTC client backend[32741] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2025-02-01 03:25:21.943 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.part_78 PARTITION OF testschema.part FOR VALUES IN (7, 8)
	  PARTITION BY LIST (a);
2025-02-01 03:25:22.203 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2025-02-01 03:25:22.203 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE pg_default;
2025-02-01 03:25:22.205 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2025-02-01 03:25:22.205 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE pg_default) PARTITION BY LIST (a);
2025-02-01 03:25:22.206 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2025-02-01 03:25:22.206 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE regress_tblspace;
2025-02-01 03:25:22.209 UTC client backend[32741] pg_regress/tablespace ERROR:  cannot specify default tablespace for partitioned relations
2025-02-01 03:25:22.209 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE regress_tblspace) PARTITION BY LIST (a);
2025-02-01 03:25:22.753 UTC client backend[32741] pg_regress/tablespace ERROR:  only shared relations can be placed in pg_global tablespace
2025-02-01 03:25:22.753 UTC client backend[32741] pg_regress/tablespace STATEMENT:  ALTER INDEX testschema.part_a_idx SET TABLESPACE pg_global;
2025-02-01 03:25:22.754 UTC client backend[32741] pg_regress/tablespace ERROR:  duplicate key value violates unique constraint "anindex"
2025-02-01 03:25:22.754 UTC client backend[32741] pg_regress/tablespace DETAIL:  Key (column1)=(1) already exists.
2025-02-01 03:25:22.754 UTC client backend[32741] pg_regress/tablespace STATEMENT:  INSERT INTO testschema.atable VALUES(1);
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace ERROR:  directory "/no/such/location" does not exist
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLESPACE regress_badspace LOCATION '/no/such/location';
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace ERROR:  tablespace "regress_nosuchspace" does not exist
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace STATEMENT:  CREATE TABLE bar (i int) TABLESPACE regress_nosuchspace;
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace ERROR:  tablespace "regress_tblspace" cannot be dropped because some objects depend on it
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace DETAIL:  tablespace for index testschema.part_a_idx
2025-02-01 03:25:22.759 UTC client backend[32741] pg_regress/tablespace STATEMENT:  DROP TABLESPACE regress_tblspace;
2025-02-01 03:25:22.760 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:22.801 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 1368 buffers (8.3%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 recycled; write=0.014 s, sync=0.001 s, total=0.042 s; sync files=0, longest=0.000 s, average=0.000 s; distance=14643 kB, estimate=44596 kB; lsn=0/E6FA160, redo lsn=0/E6FA108
2025-02-01 03:25:22.806 UTC client backend[32741] pg_regress/tablespace ERROR:  tablespace "regress_tblspace" is not empty
2025-02-01 03:25:22.806 UTC client backend[32741] pg_regress/tablespace STATEMENT:  DROP TABLESPACE regress_tblspace;
2025-02-01 03:25:22.827 UTC client backend[32907] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2025-02-01 03:25:22.827 UTC client backend[32907] pg_regress/tablespace STATEMENT:  CREATE TABLE tablespace_table (i int) TABLESPACE regress_tblspace;
2025-02-01 03:25:22.834 UTC client backend[32907] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2025-02-01 03:25:22.834 UTC client backend[32907] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace) TABLE tablespace_table;
2025-02-01 03:25:22.834 UTC client backend[32907] pg_regress/tablespace ERROR:  permission denied for tablespace regress_tblspace
2025-02-01 03:25:22.834 UTC client backend[32907] pg_regress/tablespace STATEMENT:  REINDEX (TABLESPACE regress_tblspace, CONCURRENTLY) TABLE tablespace_table;
2025-02-01 03:25:22.852 UTC checkpointer[29659] LOG:  checkpoint starting: immediate force wait
2025-02-01 03:25:22.854 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 44 buffers (0.3%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=338 kB, estimate=40170 kB; lsn=0/E74E9B8, redo lsn=0/E74E960
2025-02-01 03:25:22.868 UTC postmaster[25306] LOG:  received fast shutdown request
2025-02-01 03:25:22.868 UTC postmaster[25306] LOG:  aborting any active transactions
2025-02-01 03:25:22.873 UTC checkpointer[29659] LOG:  shutting down
2025-02-01 03:25:22.873 UTC checkpointer[29659] LOG:  checkpoint starting: shutdown immediate
2025-02-01 03:25:22.874 UTC checkpointer[29659] LOG:  checkpoint complete: wrote 24 buffers (0.1%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=133 kB, estimate=36166 kB; lsn=0/E76FD60, redo lsn=0/E76FD60
2025-02-01 03:25:22.899 UTC postmaster[25306] LOG:  database system is shut down